Microsoft Dynamics AX
Universal Importer for Confluence
Kim Landis (Unlicensed)
Phillip Hanegan
EmpowerID provides connectors for a wide range of user directories and resource systems. As an administrator, you can use these connectors to quickly connect EmpowerID to your organization's identity-aware systems and applications. When you do so, you create an account store for that application in the EmpowerID Identity Warehouse and use that account store to configure how you want EmpowerID to manage the identity information in that system.
EmpowerID Dynamics AX connector allows organizations to bring the user data in their Dynamics AX system to EmpowerID, where it can be managed and synchronized with data in any connected back-end user directories. Once connected, you can manage this data from EmpowerID in the following ways:
- Provision new users
- Edit user attributes
- Delete users
Additionally, EmpowerID provides Provisioning policies or Resource Entitlements (RETs) that allow you to automatically provision DAX accounts for any person within your organization based on your policy requirements. For more information on RETs and DAX, see Creating Provisioning Policies for Microsoft Dynamics AX.
Prerequisites
In order to connect EmpowerID to Dynamics AX, you need to have a Dynamics AX server with the Dynamics AX client installed. In addition, you need to have the installer for the EmpowerID Dynamics AX Web services. This installer is a separate package that needs to be requested from EmpowerID.
- Installing the EmpowerID Dynamics AX Web Services
- Connecting EmpowerID to your Dynamics AX User directory
- Configuring the Dynamics AX Account Store in EmpowerID
- Connecting EmpowerID to your Dynamics AX Worker directory
Before connecting EmpowerID to a directory system, you should determine whether you want EmpowerID to provision Person objects from the user accounts it discovers in the account store. If you do, then you should be able to answer the following questions before turning on inventory.
- When do you want EmpowerID to provision Person objects for those user accounts? At inventory or at a later point in time using the Account Inbox (recommended)?
- If inventory provisioning is desired, in what Business Role and Location should those Person objects be placed?
- How many user accounts can one Person have in the account store?
- If people can have more than one user account in the account store, do you want EmpowerID to attempt to automatically join any user accounts meeting the conditions of your Join rules to an existing Person during inventory?
- Do you want attribute flow to occur between EmpowerID and the account store? If so, what rules do you want to apply?
- If you have Resource