# SailPoint Microsoft Dynamics 365 for Finance and Operations SaaS Connector Documentation > Microsoft Dynamics 365 for Finance and Operations SaaS Connector Documentation # Documentation # Connecting SailPoint and Microsoft Dynamics 365 for Finance and Operations SaaS To connect SailPoint with Microsoft Dynamics 365 for Finance and Operations, perform the following tasks: ## Adding the Source in SailPoint To connect to SailPoint, perform the following steps. Once the connection is made, you can configure it to meet your company's needs. > [!IMPORTANT] > > By default, the provisioning feature is **disabled**, and the connector only supports read-only operations. To support provisioning operations, you must manually enable the feature in the source configuration. **To configure a new source:** 1. Sign in to SailPoint. 2. Go to **Admin \> Connections \> Sources**. 3. Select **Create New**. 4. Search for the connector by entering the name in the search box, and then select **Actions**. 5. In the **Actions** dropdown list, select the setup method: - [**Express Setup**](<#configuring-a-source-using-express-setup>) - Quickly create a read-only connection to your target system by providing minimal configurations and authentication. On completion, aggregation is automatically started. > **Note** > > Express Setup supports Credential Providers. For information on supported credential providers and configuration, refer to [Credential Providers](). For more information, contact your SailPoint Customer Service Manager. - [**Standard Setup**](<#configuring-a-source-using-standard-setup>) - Provide detailed basic configuration to create the source. Once the source is created, continue with source setup. ### Configuring a Source Using Express Setup Express Setup minimizes the initial configuration process so you can quickly connect the application and immediately begin aggregating user account and entitlement data. 1. Review the directions and select **Start Express Setup**. 2. Review the pre-populated **Source Name**, **Source Owner**, and **Description**. To update, select **Edit**. > **Note** > > The source name must be unique. You can change these settings later in the source configuration. 3. (Optional) If enabled for your organization, select the **Use a Credential Provider** checkbox to manage the source's authentication using a credential provider. > **Note** > > To add a Credential Provider in SailPoint, go to **Admin \> Connections \> Credential Providers**. For more information about credential providers, refer to [Credential Providers](). 4. Configure the authentication to allow SailPoint to connect to the source. For more information, refer to the **Connection Settings** section. 5. Select **Finish**. After a successful test connection, the system creates your source and prompts you to run an aggregation. - If you want to aggregate now, select **Aggregate**. - To see the latest account aggregation history, go to **Account Management \> Account Aggregation**. - To see the list of aggregated source accounts, go to **Account Management \> Accounts**. - If you want to aggregate later, select **Exit**. This returns you to the **Sources** page. Your new source is listed, but contains no accounts or aggregation history yet. ### Configuring a Source Using Standard Setup Use Standard Setup to configure the connector for full feature support. 1. In the **Source Name** field, enter a unique and descriptive name for your source. Source names cannot exceed 128 characters. 2. In the **Description** field, provide additional details about the source to help distinguish it from similar sources. This field allows a maximum of 2,000 characters. 3. In the **Source Owner** field, begin typing the name of an owner. Matches appear after you type two or more letters. For more information, refer to [Assigning a Source Owner](). 4. (Optional) Select a governance group to grant its members [source]() or [role]() sub-admin level oversight of the source and its access. For more information, refer to [Creating and Managing Governance Groups](). 5. If this source represents a primary system containing your organization's personnel records, select the **Authoritative Source** checkbox. For more information, refer to [Creating Identity Profiles](). 6. Select **Continue**. The source is created, and you are navigated to the **Source Setup \> Base Configuration** page. Continue to configure your connected source there. ## Base Configuration Provide the base configuration parameters. Information you entered in the Create New Source dialog is automatically entered into the fields in the Base Configuration page. You can edit this information if necessary. 1. Enter a unique name and description for the source. 2. In the **Source Owner** dropdown list, select the identity that owns this source. - To find a source owner, begin entering their name. 3. (Optional) If enabled for your organization, select the **Use a Credential Provider** checkbox to manage the source's authentication using a credential provider. > **Note** > > To add a credential provider, go to **Admin \> Connections \> Credential Providers**. For more information about credential providers, refer to [Credential Providers](). 4. Configure the authentication to allow SailPoint to connect to the source. Refer to [Connection Settings](<#connection-settings>) for more information. 5. (Optional) In the **Governance Group for Source Management** dropdown list, select a governance group to associate with this source. For more information about governance groups, refer to [Associating Governance Groups with a Source](). 6. (Optional) Choose whether to enable or disable provisioning for the source. Provisioning is disabled by default. - **Enable Provisioning** - Set the toggle to **Enabled** to allow the source to create, update, and deactivate accounts in the connected source system. - **Disable Provisioning** - Set the toggle to **Disabled** to disable provisioning for the source. Disabling provisioning will prevent the creation, updating, or deactivating of accounts on this source. 7. Select **Save**. ## Connection Settings This section contains the information that the source uses to authenticate with the Dynamics 365 FO managed system. After you select **Connection Settings** the following UI page is displayed. > [!NOTE] > > **Screenshot** > > [![Connection Settings for Client Credentials grant type]()]() 1. In the **Base URL** field, enter the base URL for the Dynamics 365 FO portal. The URL format is `https://operations.dynamics.com`. 2. In the **Azure AD Tenant ID** field, enter the valid Tenant ID of the Microsoft Entra ID tenant to be managed by the source. 3. In the **Grant Type** drop-down list, select the OAuth 2.0 grant type supported by the managed system: - Client Credentials - JWT Certificate Credentials 4. In the **Client ID** field, enter the Microsoft Entra ID application Client ID for OAuth 2.0 authentication. 5. In the **Page Size** field, enter the number of objects to fetch in a single page when iterating over large data sets. The range of the Page Size value is 1 to 1000. By default, the page size value is 500. 6. Select **Save**. ### Client Credentials Grant Type If you select **Client Credentials** as a Grant Type, *in addition* to the fields mentioned before, in the **Client Secret** field enter the Microsoft Entra ID application Client Secret for OAuth 2.0 authentication. ### JWT Certificate Credentials Grant Type > [!NOTE] > > **Screenshot** > > [![Connection Settings for JWT Certificate Credentials grant type]()]() > > [![JWT Certificate Credentials connection fields]()]() If you select **JWT Certificate Credentials** as a Grant Type, *in addition* to the fields mentioned before: 1. In the **Certificate** field, enter the content of the certificate file that is uploaded on the Microsoft Entra ID application. 2. In the **Private Key** field, enter text of the private key used for signing the JWT assertion. 3. In the **Private Key Password** field, enter the password for decrypting the private key. 4. Select **Save**. ## Additional Settings ### Provisioning Settings > [!NOTE] > > Ensure users are present in your Microsoft Entra ID tenant. Microsoft has flagged the access method as a security concern if the user isn't present in the Microsoft Entra ID tenant associated with your Finance and Operations environment. > [!NOTE] > > **Screenshot** > > [![Enable Create Account]()]() 1. Select the option **Enable Create Account** to allow users to create accounts. 2. Select **Save**. ## Review and Test Perform a test to confirm the connection to SailPoint. 1. Go to **Review and Test**. 2. Confirm that the entries in each field are correct. If you note any mistakes, return to the section and make corrections. 3. Select **Test Connection**. ## SailPoint Application Onboarding SailPoint application onboarding enables you to easily onboard new applications and create sources following the successful onboarding of a discovery source. To use this feature, continue to **Discovered Applications** in the SailPoint user interface. For more information, refer to [Application Onboarding]() in the SailPoint SaaS documentation. # Integrating SailPoint with Microsoft Dynamics 365 for Finance and Operations SaaS Dynamics 365 is a cloud service from Microsoft, combining several business needs into a single, scalable, and agile platform. Microsoft Dynamics 365 for Finance and Operations (FO) is an ERP system which is a part of the Dynamics 365 product line. It offers the ability to keep track of finances and inventory of the business. Connecting SailPoint to your Dynamics 365 for Finance and Operations SaaS connector allows you to manage Users and Security Role assignments related to read and provision various Dynamics 365 Finance and Operations Native IAM Objects as follows: - **Users**: Users are employees of the organization synced from Entra ID. - **Security Roles**: Users must be assigned to at least one security role to access Finance and Operations. Only security roles can be assigned to users. Granular permissions and child roles are not included in the current scope. > [!NOTE] > > To view the latest features, enhancements, and fixes for all SaaS connectors, refer to the [SaaS Release Notes]() page. ## Supported Features The Microsoft Dynamics 365 for Finance and Operations SaaS connector supports the following features: - Account Management - Account-Group Management ### Account Management The following table describes the supported operations on various objects for the Microsoft Dynamics 365 for Finance and Operations SaaS connector: | Operations | User | | --- | --- | | Aggregation | Yes | | Get Account | Yes | | Enable/Disable Users | Yes | | Add/Remove Entitlements
\- Add/Remove Groups | Yes | | User Creation | Yes | > [!NOTE] > > Users are synchronized from Entra ID. ### Entitlement Management | Operations | Groups | | --- | --- | | Aggregation | Yes | ## Privilege Classification SailPoint Privilege Classification helps organizations systematically categorize and manage the privilege levels of entitlements within their sources. By classifying entitlements as high, medium, or low, administrators can better understand the potential risk and impact associated with specific access rights. This allows automatic assignment of privilege levels based on system recommendations, custom-defined criteria, or a same level across all entitlements. | Privilege Level | Description | | --- | --- | | High | Administrative level access to accounts | | Medium | Administrative level access for a specific role or function | | Low | Only basic access of data | > [!NOTE] > > To manage Privilege Classification, users must have administrative roles such as Org Admin, Source Admin or Source Sub-Admin. For more information, refer to [Managing Privilege Classification](). > [!NOTE] > > **Example** > > [![Recommended Privilege Level - High]()]() > > [![Recommended Privilege Level - Medium]()]() ## Prerequisites The Microsoft Dynamics 365 for Finance and Operations SaaS connector supports OAuth 2.0 authentication with the following grant types: - Client Credentials - JWT Certificate Credentials The following sections describe the configuration that must be performed for each grant type. ### Registering an Application on Microsoft Entra ID Registering the application generates the Tenant ID, Client ID, and Client Secret required for authentication. These are required for later processes. Perform the following: 1. Use either of the following methods to access the Microsoft Entra admin center to perform the configuration: - [Microsoft Azure]() - [Microsoft Entra admin center]() 2. Select **Entra ID** in the left pane. 3. Select **App registrations**. 4. Select **New** registration. 5. On the **Register an application** page, in the **Name** field, enter the name of the application that you want to set up. 6. Select **Register**. An Application is created. On the Application page the **Application ID** (Client ID) and **Tenant ID** are displayed. 7. On the left-hand panel, select **Certificates & secrets**. On the **Certificates & secrets** page, in the **Client secrets** section, select **New client secret**. 8. On the **Add a client secret** page, enter the **Description** to generate a secret, and select the validity duration in the **Expires** list. Select **Add**. Note the value of the client secret that you have just created. ### Client Credentials For the **Client Credentials** (default) grant type based authentication following are the required configurations: - Obtain the Tenant ID, Client ID, and Client Secret from Microsoft Entra by registering the application (steps mentioned in [Registering an Application on Microsoft Entra ID](<#registering-an-application-on-microsoft-entra-id>)). ### JWT Certificate Credentials JWT Certificate Credentials support authentication based on JWT assertions prepared from a certificate and private key. 1. Obtain the Tenant ID and Client ID from Microsoft Entra by registering the application (up to step 6 mentioned in [Registering an Application on Microsoft Entra ID](<#registering-an-application-on-microsoft-entra-id>)). 2. To create a self-signed or CA-signed type X.509 certificate and private key, perform the following steps to register the certificate with the Microsoft identity platform: > **Important** > > The private key must be encrypted with the RSA algorithm and registered at the Entra portal. 1. Log in to the Entra Portal. 2. Select the client application. In the Entra app registration for the client application, select **Certificates & secrets**. 3. Select **Upload certificate** and select the certificate file to upload. 4. Select **Add**. 5. Obtain values for the following configurations: - **Certificate**: Obtain the text file of the same certificate which was uploaded on the Entra portal. - **Private Key**: Obtain the private key text file. - **Private Key Password** ### Additional Steps on the Finance and Operation Instance 1. Create a Microsoft Entra ID application by providing the following details: - **ClientID**: Client ID must match the Client ID registered in Entra ID. - **Name**: Logical name to differentiate the application. - **UserID**: Select the user that is used to manage the connector operation. > **Note** > > The selected user must be assigned to a security role that has the privileges defined in [Required Permissions](<#required-permissions>). ## Required Permissions The following table defines the minimum privileges required by the Security Role assigned to the service account for the connector: | Privilege Name | Permission on Entity/Table provided | | --- | --- | | Maintain security user role association entity | `SystemSecurityUserRoleAssociationEntity`: Required for fetching information related to Users and their associated roles. | | Maintain system security user role duty privilege entity | `SystemSecurityRoleDutyEntity`: Required for fetching information regarding duties associated with a Security Role.
`SystemSecurityRoleEntity`: Required for viewing Security Role information.
`SystemSecurityUserRoleEntity`: Required for viewing and updating User roles. | | Maintain system security user role organization entity | `SystemSecurityUserRoleOrganizationEntity`: Required for viewing and updating user roles for legal entities. | | CompanyInfoEntityView | `CompanyInfoEntity`: Viewing company details present on the managed system. | | View legal entities entity | `OMLegalEntity`: Required for viewing legal entity details present on the managed system. | | Maintain users
Maintain users entity
View users entity | These set of privileges are required for viewing and updating information related to Users on the managed system. These include permissions for:
Tables: `SecurityUserRole` and `UserInfo`
Entities: `SystemUserEntity` | # Provisioning The Microsoft Dynamics 365 for Finance and Operations SaaS connector supports provisioning, allowing you to create and manage accounts and entitlements in Microsoft Dynamics 365 for Finance and Operations directly from SailPoint. **Prerequisite:** Your system is configured for provisioning. When SailPoint provisions new accounts to the source, it uses the attributes on the **Create Account** page as instructions or a template for what to include in the account. This page is also referred to as the *provisioning policy*. When new access is granted on a source where a user does not already have an account, SailPoint automatically includes account creation in the provisioning. This applies whether provisioning is started from an access request or from an automated role or lifecycle state assignment. For direct-connect sources, SailPoint automatically creates the account from this configuration. If the source is not configured as a direct-connect source, SailPoint creates and assigns a provisioning task to the source owner and includes the values for the source owner to use in manually creating the account. > [!IMPORTANT] > > This section describes the default **Create Account** configuration. SailPoint recommends that you work with Services to define a provisioning configuration specific to your company's needs. Be sure to verify large changes to the provisioning policy before implementation. Failure to do so might cause provisioning to fail. ## Default Create Account Attributes > [!NOTE] > > Attributes with an asterisk (\*) are required. | Account Attribute | Description | | --- | --- | | User ID \* | The unique identifier for the user.
**Note**: If `UserName` is not added in the create policy explicitly, the value of the `User ID` is copied in `UserName` for the create API. | | Email \* | The email of the user.
**Note**: If `Alias` is not added in the create policy explicitly, the value of `Email` is copied in `Alias` for the create API. | | Network Domain \* | The domain of the user. Default: `https://sts.windows.net/` | | Account Type \* | The account type of the user. Default: `ClaimsUser` | | Company | The unique ID of the company to which the user belongs to. | > [!NOTE] > > The default values for `UserInfo_language` and `Helplanguage` are set as `en-US` for the create API. # Schema Reference The application schema is used to configure the objects returned from a connector. > [!NOTE] > > - The **Account Schema** tab is used to define the attributes for each object type in the application being configured. The schema attributes can be defined as **Entitlement** or **Multi-Valued**. Refer to [Managing Source Account Schemas]() for more information. > - The schema attributes that are not present by [default](<#default-account-schema>) must be defined as strings if not specified. The Microsoft Dynamics 365 for Finance and Operations SaaS connector uses the following default correlation and object configurations. ## Default Correlation Configuration Before you aggregate accounts from this source, you can map account attributes with their corresponding identity attributes based on your requirements. You can customize the correlation configuration. Refer to [Assigning Source Accounts to Identities]() for more information. When you first create the Microsoft Dynamics 365 for Finance and Operations SaaS source, the default correlation mapping is: | Account Attribute | Operation | Identity Attribute | | --- | --- | --- | | userEmail | Equals | Work email | You can modify the correlation configuration in accordance with your requirements. **To configure a new identity attribute to account attribute correlation:** 1. Go to **Account Management \> Account Correlation**. 2. Select **\+Add Criteria**. 3. In the **Identity Attribute** column, enter the name of the attribute in the SailPoint account schema. 4. In the **Account Attribute** column, enter the name of the correlating attribute in the source account schema. 5. Select **Save**. ## Default Account Schema Each source supports a variety of details, or attributes, about each user who has an account, such as their name, email address, manager name, and location. The set of account attributes each source stores and how they're organized is known as the account's *schema*. To best represent your data, you can configure sources to use an account schema matching the one you use in the external connector. Refer to [Managing Source Account Schemas]() for more information. ### Default Account ID SailPoint requires that certain attributes remain in your configuration. These attributes are referred to as *account IDs*. > [!CAUTION] > > Changing the attribute marked as the account ID after aggregating accounts can result in duplicate accounts being created. To avoid this, either reset the accounts on this source before editing the account ID attribute or edit the account ID attribute before aggregating accounts. > > To resolve issues caused by changing account IDs, reconfigure them to their default values. The following table lists the default account IDs for this connector: | Account ID | Schema Object Type | | --- | --- | | userId | Account | | organizationRoleIdentifier | Group | ### Default Account Attributes The Microsoft Dynamics 365 for Finance and Operations SaaS connector supports the following default account schema attributes and customer configurable attributes. The attributes must be defined as strings if not specified. | Attribute Name | Description | | --- | --- | | userId | Unique identifier for the user. This is an Account ID which must not be changed. | | userName | Unique identifier for the user. | | userEmail | Email of the user. | | organizationRoles | Organization roles assigned to the user. | | networkDomain | The domain of the user. | | accountType | The account type of the user. | | company | The unique ID of the company to which the user belongs to. | | automaticOrganizationRoles | Automatically assigned OrganizationRoles to the user. | ## Default Entitlement Attributes Entitlement attributes define the entitlements, such as groups or roles, that can be assigned to the managed system's user accounts. Refer to [Managing Entitlements]() for more information. > [!CAUTION] > > Changing the attribute marked as the Entitlement ID after aggregating accounts or entitlements can result in duplicate entitlements being created, or access profiles and roles breaking. To avoid this, edit the entitlement schema before performing any aggregations. ### Default Group Attributes The Microsoft Dynamics 365 for Finance and Operations SaaS connector also supports groups. The following attributes must be configured on the managed system and in the SailPoint source schema to manage groups. This section describes the group attributes for the `organizationRole` Native Object type. #### Native Object Type = organizationRole | Attribute Name | Description | | --- | --- | | securityRoleIdentifier | Unique identifier for the Security Role. | | legalEntityId | Unique identifier of the legal entity. | | organizationRoleIdentifier | Unique identifier for the OrganizationRole. This is an Account ID which must not be changed. | | roleDescription | Describes the Security Role function briefly. | | securityRoleUserLicenseType | License type required by the user for the Security Role. | | securityRoleAccessToSensitiveData | Suggests if the Security Role provides access to the sensitive data. | | securityRoleContextString | Displays the context string applied to the Security Role. | | legalEntityName | Name of the legal entity. | | securityRoleName | Name of the Security Role. | | organizationRoleName | Name of the OrganizationRole. | # Troubleshooting If you encounter any of the following issues or errors, SailPoint recommends that you follow the guidance provided below to resolve the error before contacting SailPoint Support. For issues or errors that are not addressed in this connector guide, refer to the following resources for troubleshooting information: - [SailPoint Identity Services Documentation]() - [SailPoint Support Knowledge Base]() - [SailPoint Developer Community]() ## Debug Logs For information about managing additional source settings, including debug logging and downloading connector logs, refer to [Managing Additional Settings](). ## Test Connection / Account Aggregation Fails with an Error Message **Issue**: The parameters for Failing Test Connection and Account Aggregation, including Page Size, Max Retry Count, and Retry Wait Time, support only integer values. **Resolution**: Update the following attributes in the source and retry the use case. ```json [ { "op": "add", "path": "/connectorAttributes/maxRetryCount", "value": 5 }, { "op": "add", "path": "/connectorAttributes/retryWaitTime", "value": 60000 }, { "op": "add", "path": "/connectorAttributes/retryableErrors", "value": [ "Service Unavailable", "ConnectorError", "RuntimeException" ] } ] ``` ## Aggregation Failure **Issue**: Aggregation processes fail with the following error: ```text org.apache.http.NoHttpResponseException: vu59535.west-us-2.privatelink.snowflakecomputing.com:443 failed to respond OR connector.sdk.webservices.exception.WebServicesSdkException: java.net.SocketException: Socket closed ``` **Resolution**: Add the following attributes using the SailPoint REST API, then retry the aggregation process. > [!NOTE] > > For more information on SailPoint's REST APIs, refer to [Best Practices: REST API Authentication]() and [REST API - Update Source (Partial)]() in the SailPoint Developer Community. ```json [ { "op": "add", "path": "/connectorAttributes/conSnowflakeApiRetrySleepTimeSeconds", "value": 60000 }, { "op": "add", "path": "/connectorAttributes/conSnowflakeApiRetryMaxAttempts", "value": 3 }, { "op": "add", "path": "/connectorAttributes/retryableErrors", "value": [error_messages] } ] ```