# SailPoint Microsoft Dynamics 365 Business Central Online SaaS Connector Documentation > Microsoft Dynamics 365 Business Central Online SaaS Connector Documentation # Documentation # Connecting SailPoint and Microsoft Dynamics 365 Business Central Online SaaS To connect SailPoint with Microsoft Dynamics 365 Business Central Online, 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 Business Central Online 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 **Environmental URL** field enter the Business Central environment URL as displayed in Business Central admin center. The URL format is `https://businesscentral.dynamics.com//`. For more information on obtaining the Environment URL, refer to [Obtaining the Environment URL](<#obtaining-the-environment-url>). 2. In the **Grant Type** dropdown list, choose one of the following OAuth 2.0 grant type supported by the Dynamics 365 Business Central managed system: - Client Credentials - JWT Certificate Credentials - Refresh Token/ Auth Code 3. In the **Client ID** field, enter the Entra ID application Client ID for OAuth 2.0 authentication. 4. 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 999. By default, the page size value is 500. 5. Select **Save**. ### Obtaining the Environment URL 1. Sign in to [Dynamics Business Center](). 2. Go to **Setting \> Admin Center \> Environments**. 3. Select the name of the Environment. 4. Copy the URL to use. ### 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 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**. ### Refresh Token/ Auth Code Grant If you select **Refresh Token / Auth Code** as a Grant Type, *in addition* to the fields mentioned before: > [!NOTE] > > **Screenshot** > > [![Connection Settings for Refresh Token grant type]()]() 1. In the **Client Secret** field, enter the Entra ID application Client Secret for OAuth 2.0 authentication. 2. In the **Refresh Token** field, enter a valid refresh token. ## 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 Business Central Online SaaS Microsoft Dynamics 365 Business Central Online is an ERP system offered by Microsoft. It includes sales, services, finance, and operations teams within a single cloud business management solution. Connecting SailPoint to your Business Central allows you to manage identity and access management use cases related to reading and provisioning various Dynamics 365 Business Central Native IAM Objects as follows: - **Users**: Business Central licensed users synchronized from Microsoft Entra ID. - **User Groups**: Group object which is used to assign set of permission sets to set of users (deprecated for v25 and above.) - **Permission Sets**: It is a container of permissions. Permissions define granular access on the Business Central objects. - **Security Groups**: Used to assign a set of permission sets to a group of users defined in the external system. > [!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 Business Central Online 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 Business Central Online SaaS connector: | Operations | Licensed User | | --- | --- | | Aggregation | Yes | | Get Account | Yes | | Enable/Disable Users | Yes | | Add/Remove Entitlements
• Add/Remove Permission Set
• *(Applicable only for Refresh Token authentication and Business Central v24 and below)* Add/Remove Groups | Yes | ### Using Security Group Object for Pre-existing Sources With Dynamics 365 Business Central v25 and later, security groups have been introduced for user management. Consequently, user groups are deprecated. When upgrading for v25+, ensure that any references to the `userGroup` schema are removed from your configurations. API to add new ROLE schema: > [!NOTE] > > **Details** > > Method: POST > > URL: `v2025/sources//schemas` > > JSON Payload example: > > ```json > { > "type": "securityGroup", > "displayAttribute": "displayName", > "nativeObjectType": "securityGroup", > "identityAttribute": "id", > "attributes": [ > { > "name": "id", > "type": "string", > "description": "The unique ID of the security group." > }, > { > "name": "code", > "type": "string", > "description": "The code of the security group." > }, > { > "name": "groupName", > "type": "string", > "description": "The group name of the security group." > } > ] > } > ``` > [!NOTE] > > Licensed Users are synchronized from Microsoft Entra ID. ### Entitlement Management | Operations | Permission Sets | Groups | | --- | --- | --- | | Aggregation | Yes | 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] > > **Examples** > > [![Recommended Privilege Level - High]()]() > > [![Recommended Privilege Level - Medium]()]() > > [![Recommended Privilege Level - Low]()]() ## Prerequisites The Microsoft Dynamics 365 Business Central Online SaaS connector supports OAuth 2.0 authentication with the following grant types: - Client Credentials - JWT Certificate Credentials - Refresh Token/ Auth Code The following sections describe the configuration that must be performed for each grant type. ### Registering an Application on Microsoft Entra ID Perform the following: 1. User can use any of the following Entra Management Portal 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. Set the **Redirect URI** to `https://businesscentral.dynamics.com/OAuthLanding.htm`. 7. Select **Register**. An Application is created. On the Application page the **Application ID** (Client ID) and **Tenant ID** are displayed. 8. On the left-hand panel, select **Certificates & secrets**. On the **Certificates & secrets** page, in the **Client secrets** section, select **New client secret**. 9. On the **Add a client secret** page, enter the **Description** to generate a secret, select the validity duration in the **Expires** list. Select **Add**. 10. Note the value of the client secret that you have just created. ### Client Credentials For the default Client Credentials grant type based authentication, following are the required configurations: - Obtain Tenant ID, Client ID, Client Secret from Entra ID 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 supports Authentication based on JWT assertion prepared from Certificate and Private Key. 1. Obtain Client ID from Entra by registering the application (up to step 7 mentioned in [Registering an Application on Microsoft Entra ID](<#registering-an-application-on-microsoft-entra-id>)). 2. To create a Certificate (self-signed or CA signed) of type X.509, the Private Key must be encrypted with the RSA algorithm and registered at the Entra ID portal. Complete the following steps to register the certificate with the Microsoft identity platform: 1. Sign 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** ### Refresh Token For refresh token, the delegated permissions on the Entra application are used (while [Registering an Application on Microsoft Entra ID](<#registering-an-application-on-microsoft-entra-id>)). For more information on assigning the appropriate permissions to the Business Central, refer to [Required Permissions](<#required-permissions>). Perform the following to obtain the authorization code: 1. Obtain the authorization code using the following sample request URL: ```text https://login.microsoftonline.com/.onmicrosoft.com/oauth2/v2.0/authorize?client_id=&scope=offline_access https://api.businesscentral.dynamics.com/.default&response_type=code&redirect_uri=https://businesscentral.dynamics.com/OAuthLanding.htm&response_mode=query&state= ``` > **Note** > > In the above URL, replace the values of ``, ``, and ``. Add the following parameter details: | Parameter | Description | | --- | --- | | client\_id | Client ID of the registered application. | | response\_type | For authorization code the value must be code. | | redirect\_uri | The value of this must be a redirect URI to the URL that was configured while registering the application, that is, `https://businesscentral.dynamics.com/OAuthLanding.htm` | | response\_mode | To get the code in string parameter on your redirect URI, it must be a query. | | scope | offline\_access `https://api.businesscentral.dynamics.com/.default` | | state | This can be any number. The same value is returned along with the authorization code. | 2. The response in the address bar would be displayed as follows: ```text https://businesscentral.dynamics.com/OAuthLanding.htm?code=OAQABAAIAAAAm-06blBE1TpVMil8KPQ41U9..&state=1234566&session_state=9557b1f1-0fd8-4e12-a39f-213cfcd12153 ``` From the above response, copy the code present between `code=` and `&state`. 3. Obtain the Refresh Token as follows using the Auth code you copied: 1. Execute the following POST: - Request URL: `https://login.microsoftonline.com//oauth2/v2.0/token` - Content-Type: `application/x-www-form-urlencoded` - Request body: - `client_id` - `client_secret` - `grant_type`: As you intend to redeem the Auth Code it should be authorization\_code - `code`: Authorization code obtained in previous steps - `redirect_uri`: The value of this must be a redirect URI to the URL that was configured while registering the application - `scope`: Enter `offline_access https://api.businesscentral.dynamics.com/.default` 2. Copy `Refresh Token` from the response. ### Creating an Application User on Business Central Online Perform the following: 1. Open the Dynamics 365 Business Central portal. 2. In the **Search** field, search for **Entra ID Application**. 3. Select **New**. 4. Add the Client ID (created in [Client Credentials](<#client-credentials>)/[JWT Certificate Credentials](<#jwt-certificate-credentials>) depending on the Grant Type selected). > **Note** > > Application ID is the Client ID of the Application registered in Entra. 5. Under **User Groups** and **User Group permissions** add permissions in Administrator permissions section and save the application. > **Note** > > Client secret to be effectively used with a refresh token (or any token exchange requiring client authentication), the client created in Entra ID should be a confidential client. ## Required Permissions Assign the following permissions based on the operation to be performed: - **Read Operations**: The registered Entra ID application must have **Automation.ReadWrite.All** permission on the Entra portal and the Entra ID application must be a member of the **D365 AUTOMATION** and **D365 SECURITY** groups on Business Central Online. - **Write Operations**: In addition to permissions required for read operations, the Entra ID application or the delegated user of refresh token must be a member of **SUPER** permission set on Business Central Online. Perform the following steps to assign the permissions: 1. The Client Credentials /JWT Certificate Credentials Grant Type requires the following permissions on the Entra ID application: 1. Under API permissions select **Add Permissions**, and then select **Dynamics 365 Business Central \> Application Permissions \> Automation.ReadWrite.All**. 2. After assigning permission select **Grant admin consent for...** 3. Add the same application on Dynamics Business Central using the Entra ID Applications page. Assign D365 AUTOMATION and D365 SECURITY under the **User Groups** table, clear the value in Company Name column if present. 4. To support all write operations, assign SUPER permission set under **User Permissions** table, and clear the value in Company Name column if present. 5. After assigning the permissions select **Grant Consent** and enable the toggle. 2. The Refresh Token Grant Type requires the following permission on the Entra ID application: 1. Under **API permissions** select **Add Permissions \> Dynamics 365 Business Central \> Delegated permissions \> user\_impersonation**. 2. The Business Central user under which access code and refresh token are generated must be a member of the D365 AUTOMATION and D365 Security groups to support read operations and add assign SUPER permission set to support write operation. # 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 Business Central Online SaaS connector uses the following default correlation and object configurations. ## Default Correlation Configuration Prior to aggregation, you can map account attributes with their corresponding identity attribute in accordance with your requirements. By default, the following correlation configuration is present in your source: 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 Business Central Online SaaS source, the default correlation mapping is: | Identity Attribute | Operation | Account Attribute | | --- | --- | --- | | Display Name | Equals | displayName | ## 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 | | --- | --- | | userSecurityId | Account | | objectId | userGroup (deprecated for v25 and above) | | objectId | permissionSet | | objectId | securityGroup | ### Default Account Attributes The following lists the account attributes: | Attribute Name | Description | | --- | --- | | securityGroups | securityGroup membership of the user. | | displayName | Entra ID account's first name and last name. | | userName | The Business Central user name. | | state | The login state of the user. For example, Enabled or Disabled. | | userGroups (deprecated for v25 and above) | User group memberships of the user. | | userPermissions | Permission sets that are assigned to the user. | | userSecurityId | The unique identifier for the user. This is an Account ID which must not be changed. | ## Group Attributes This section describes the group attributes for the following Native Object types: - userGroup (deprecated for v25 and above) - permissionSet - securityGroup ### Native Object Type = userGroup | Attribute Name | Description | | --- | --- | | objectId | Customized unique identifier for the group. This is an Account ID which must not be changed. | | code | Unique identifier for the group. | | assignToAllNewUsers | A flag to indicate assignment of all new users to the user group. | | defaultProfileID | Default Profile ID. | | displayName | The display name for the group. | ### Native Object Type = permissionSet | Attribute Name | Description | | --- | --- | | objectId | Customized unique identifier for the permissionSet. This is an Account ID which must not be changed. | | appId | ID of the associated extension application. | | displayName | The display name for the permissionSet. | | extensionName | The Extension name of the permissionSet. | | permissionId | The Unique identifier for the permissionSet. | | scope | The scope of the permissionSet Object. | ### Native Object Type = securityGroup | Attribute Name | Description | | --- | --- | | id | The unique ID of the security group. | | code | The code of the security group. | | groupName | The group name of the security group. | # 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 below 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] } ] ``` ## Account and User Group Aggregation Failure **Issue**: Aggregation Fails when tried to get user groups (fails for Business Central v25 and above.) > [!IMPORTANT] > > User Aggregation failed. Error: 400 BadRequest : Could not find a property named 'userGroupMembers' on type 'Microsoft.NAV.user'. **Resolution**: If Business Central version is upgraded to v25 or above, refer to Using Security Group Object for Pre-existing Sources for guidance on adding security group schema.