Microsoft Dynamics Provisioning Policies

Provisioning Policies allow you to automate the provisioning, moving, disabling, and de-provisioning of resources for users based on their roles, memberships and locations within your organization.

This topic demonstrates the following:

  • How to create a provisioning policy that provisions Dynamics AX user accounts

  • How to assign the provisioning policy to an EmpowerID actor type

  • How to add configuration parameters to the policy

Prerequisites

  • EmpowerID must first be connected to DAX. For details, see Connecting to Microsoft Dynamics AX.

  • RET provisioning and RET deprovisioning must be enabled on the DAX account store.

Dynamics AX (DAX) has two types of users, Active Directory users and Claims users. By default, DAX provisions all users as Claims Users. Thus, to create both types of users through RET policies, EmpowerID recommends you create a RET policy for both.

Provisioning policies can be targeted against any number or combination of Management Roles, groups, Business Roles and Locations, Query-Based collections, as well as individual people.

How to create a provisioning policy for Dynamics AX User Accounts

  1. n the navbar, expand Identity Lifecycle and click Provisioning Policies (RETs).

  2. On the Policies page, click the Add button at the top of the grid.

     

  3. Under Choose Type, select Default from the Object Type To Provision drop-down.

     

  4. In the General section of the form fill in the following fields:

    1. Name — Enter a name for the policy.

    2. Description — Enter a description for the policy.

    3. Resource Type — Select User Account.

    4. Resource System — Select your inventoried DAX User resource system.

    5. Object Class — Enter User.

    6. Creation Path — Optional; leave as is.

  5. In the Throttling Settings section of the form, specify the provisioning and deprovisioning thresholds for the policy. These settings are as follows:

    • All Provisions Require Approval — If this option is selected, the provisioning of each RET specified by the policy will need to be approved by a user delegated access to the Resource Entitlement Inbox.

    • All Deprovisions Require Approval — If this option is selected, the deprovisioning of each RET specified by the policy will need to be approved by a user delegated access to the Resource Entitlement Inbox.

    • Require Approval if Provision Batch Larger Than Threshold — This field allows you to set a numeric value that needs to be reached by a single run of the Resource Entitlement Inbox before an approver needs to approve the provisions. If the threshold is reached, EmpowerID will not provision any of the Salesforce user accounts until approval is granted.

    • Require Approval if Deprovision Batch Larger Than Threshold — This field allows you to set a numeric value that needs to be reached by a single run of the Resource Entitlement Inbox before an approver needs to approve the deprovisions. If the threshold is reached, EmpowerID will not deprovision any of the Salesforce user accounts until approval is granted.

  6. In the Advanced section of the form, do the following:

    1. Select a desired option from the On Claim Action drop-down. You have the following options:

      • Do Nothing — No action occurs. This tells EmpowerID to simply mark any previous resources assigned to the user that match this policy as RET-managed resources. For example, if the user already has a DAX user account and is placed in a Management Role targeted by the RET policy, EmpowerID marks that user's DAX account as RET managed.

      • Delete and Recreate — The user account is deleted and recreated.

      • Move — Marks any previous resources assigned to the user that match the RET as RET-managed resources and moves the user object to the OU specified by the RET policy.

      • Publish Workflow Event — Executes custom workflow code.

    2. Select a desired option from the On Transform Action drop-down. You have the following options:

      • Do Nothing — No action occurs.

      • Delete and Recreate — The user account is deleted and recreated.

      • Move — Marks this resource with the new RET policy number and moves the user object to the OU specified by the RET policy

      • Publish Workflow Event — Executes custom workflow code.

    3. Select a desired option from the On Revoke Action drop-down. You have the following options:

      • Do Nothing — No action occurs.

      • Deprovision — The user account is deleted if the person no longer meets the criteria to receive the resource from the RET, such as would occur if the person was terminated or moved to a Business Role and Location without a RET policy for the specified resource.

      • Disable — The user account is disabled if the person no longer meets the criteria to receive the resource from the RET.

      • Disable and Move — The user account is disabled and moved to the OU specified in the OU to Move Disabled Users field if the person no longer meets the criteria to receive the resource from the RET.

      • Publish Workflow Event — Executes custom workflow code.

    4. Leave the Creation Location Path Resolver Assembly and Creation Location Path Resolver Type fields empty. These fields allow you to use a custom assembly to set where an account (or any RET that requires a path) should be created.

  7. Click Save to create the policy.

  8. After EmpowerID creates the policy, you should be directed to the completed Policy Details page for the policy.

     

Next, assign the policy you just created to one or more targets as demonstrated below.

How to assign the provisioning policy

  1. On the Policy Details page, click the Find Policies breadcrumb. 



  2. Search for the policy you just created and then click the Display Name link for it.



    This directs you to the View page for the policy. This page allows you to manage the policy as needed. 



  3. On the View page, click the Assignees accordion to expand it. This accordion allows you to assign the policy to any or the following EmpowerID actor types:

    • Business Roles and Locations — All people in the selected Business Role and Location combinations receive the resource granted by the policy.

    • Management Roles — All people in the selected Management Roles receive the resource granted by the policy.

    • Management Role Definitions — All Management Roles that are children of the selected Management Role Definition receive the resource granted by the policy.

    • Query-Based Collections (SetGroup) — All people in the selected collection receive the resource granted by the policy.

    • Groups — All people in the selected groups receive the resource granted by the policy.

    • People — All people selected receive the resource granted by the policy.

  4. From the Assignees accordion, click the Add button above the assignee type to which you are making the assignment.

  5. In the Add Entry pane that appears, search for and select the appropriate assignee.

  6. Enter a number to specify the priority for the RET policy in the Priority field. This value is used to determine the priority of the RET if the user qualifies for the same RET via another assignment, such as being a member of a group that has the same policy. The lower the number, the higher the priority. 

     

  7. Click Save.

  8. If you are creating this provisioning policy for DAX users with an Active Directory user account type, please proceed to How to add configuration parameters; if this provisioning policy is for DAX users with the Claims user account type, simply click the main Save button.

How to add configuration parameters

  1. On the View page, expand the Add Configuration Parameters accordion and click the Add button.

     

  2. Enter the following information in the General pane:

    1. Name — accountType

    2. Configuration Value — Active Directory User

  3. Click Save to save the parameter and close the pane.

  4. On the main page, click Save.

IN THIS ARTICLE