{"id":5753,"date":"2026-01-14T12:58:08","date_gmt":"2026-01-14T11:58:08","guid":{"rendered":"https:\/\/help.ino.cx\/?post_type=ht_kb&p=5753"},"modified":"2026-01-14T12:58:09","modified_gmt":"2026-01-14T11:58:09","slug":"dynamics-365-api-connector","status":"publish","type":"ht_kb","link":"https:\/\/help.ino.cx\/index.php\/help-center\/dynamics-365-api-connector\/","title":{"rendered":"Dynamics 365 API connector"},"content":{"rendered":"\n
\"\"<\/figure>\n\n\n\n

[Reading time: 3 minutes<\/em>]<\/p>\n\n\n\n

Overview<\/h2>\n\n\n\n

This article explains how to configure the Dynamics 365 integration in INO cx.<\/p>\n\n\n\n

Once configured, you can authenticate using Microsoft Azure, synchronize CRM objects, raise CRM cards during interactions, and use Dynamics 365 as an identity provider through SSO.<\/p>\n\n\n\n

1. Prerequisites<\/strong><\/h2>\n\n\n\n

1.1. Microsoft Power Platform<\/strong><\/h3>\n\n\n\n

If you do not yet have a Dynamics 365 environment, create one from your Microsoft Power Platform<\/a> space and assign a suitable user license based on your needs.<\/p>\n\n\n\n

1.2. Microsoft Azure<\/strong><\/h3>\n\n\n\n
    \n
  1. Log in to your Microsoft Azure<\/a> portal.<\/li>\n\n\n\n
  2. Register your new application if you have not already done it.<\/li>\n<\/ol>\n\n\n\n
    \"\"<\/figure>\n\n\n\n
    \"\"<\/figure>\n\n\n\n
      \n
    1. Note the following information from the application registration:\n
        \n
      • Application (client) ID<\/strong><\/li>\n\n\n\n
      • Directory (tenant) ID<\/strong><\/li>\n<\/ul>\n<\/li>\n<\/ol>\n\n\n\n
        \"\"<\/figure>\n\n\n\n
          \n
        1. Add the following redirect URLs<\/strong> to the application:\n
            \n
          • https:\/\/{{domain}}.ino.cx\/api\/authclients\/hbdnakz\/fzefdzs<\/code><\/li>\n\n\n\n
          • https:\/\/{{domain}}.ino.cx\/api\/sso\/login\/oauth\/callback<\/code><\/li>\n<\/ul>\n<\/li>\n<\/ol>\n\n\n\n
            \"\"<\/figure>\n\n\n\n
              \n
            1. Add a new client secret<\/strong>.<\/li>\n<\/ol>\n\n\n\n
              \"\"<\/figure>\n\n\n\n
              \"\"<\/figure>\n\n\n

              Azure will display the Secret client<\/strong> (Value column)<\/strong>\u00a0only once. Make sure to store it securely.<\/p>\n\n\n

              \"\"<\/figure>\n\n\n\n

              2. Dynamics 365 configuration<\/strong> in INO cx<\/h2>\n\n\n\n

              2.1. Authentification method<\/strong><\/h3>\n\n\n\n

              In INO cx, create a new authentication method<\/strong> (Dynamics 365<\/strong> type).
              Use the information collected from Microsoft Azure.<\/p>\n\n\n\n

              \"\"<\/figure>\n\n\n\n
              INO CX field<\/th>Microsoft Azure<\/th><\/tr><\/thead>
              Environment<\/td>Directory (tenant) ID<\/td><\/tr>
              Client ID<\/td>Application (client) ID<\/td><\/tr>
              Token<\/td>Client secret Value<\/td><\/tr>
              Scope<\/td>Permissions granted to the application<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

              2.2. Scopes<\/strong><\/h3>\n\n\n\n

              The following scopes must be configured:<\/p>\n\n\n\n

                \n
              • https:\/\/{{domain}}.crm{{region}}.dynamics.com\/.default<\/code> (mandatory)
                .default setting automatically uses all permissions (scopes) configured for the Azure application.<\/li>\n\n\n\n
              • offline_access<\/code> (optional but recommended)
                Allows automatic refresh of expired or expiring tokens.<\/li>\n<\/ul>\n\n\n\n

                Activate the connection. A confirmation window will open to authorize the link between INO cx and Dynamics 365.<\/p>\n\n\n\n

                \"\"<\/figure>\n\n\n\n

                This connection acts as a service token<\/strong> used for features such as CRM scenarios or interaction assignment. If users do not authenticate via SSO, this service token will be used by default.<\/p>\n\n\n\n

                2.3. SSO connector<\/strong><\/h3>\n\n\n\n

                Create a new SSO connector<\/strong> using the Dynamics 365 authentication method created earlier.<\/p>\n\n\n\n

                \"\"<\/figure>\n\n\n\n

                Associate this SSO connector with your users so they can log in to INO cx directly with their Microsoft account.<\/p>\n\n\n\n

                \"\"<\/figure>\n\n\n\n

                A login URL is provided for this purpose.<\/p>\n\n\n\n

                \"\"<\/figure>\n\n\n\n

                Users logging in via SSO receive their own user token<\/strong>, and therefore only access data they are authorized to view.<\/p>\n\n\n\n

                3. CRM v2 configuration<\/strong><\/h2>\n\n\n\n

                Create a new CRM v2<\/strong> (Dynamics 365<\/strong> type) and select the previously configured authentication method.<\/p>\n\n\n\n

                \"\"<\/figure>\n\n\n\n

                3.1. CRM v2 objects<\/strong><\/h3>\n\n\n\n

                Start creating your CRM objects (Contacts, Accounts, Phonecalls, etc.).<\/p>\n\n\n\n

                \"\"<\/figure>\n\n\n\n
                \"\"<\/figure>\n\n\n\n

                For each object:<\/p>\n\n\n\n

                  \n
                • Add the required fields<\/strong> displayed at the top of the list.
                  These fields are mandatory for correct Dynamics 365 integration.<\/li>\n\n\n\n
                • The field type is automatically selected based on the metadata received from Dynamics 365.<\/li>\n<\/ul>\n\n\n\n
                  \"\"<\/figure>\n\n\n\n
                  \"\"<\/figure>\n\n\n\n

                  3.2. CRM v2 scenarios<\/strong><\/h3>\n\n\n\n

                  Screen-pop scenario<\/strong><\/h4>\n\n\n\n

                  Example: Displaying a Contact record during an incoming call.<\/em><\/p>\n\n\n\n

                  \"\"<\/figure>\n\n\n\n

                  If the caller\u2019s mobile number matches the mobile number of a Contact record in Dynamics 365, the CRM card will be presented to the advisor in the Banner<\/strong> during the interaction.<\/p>\n\n\n\n

                  Interaction assignment scenario<\/strong><\/h4>\n\n\n\n

                  Example: Creating<\/em> a Phonecall from an interaction. Thanks to magic variables, we can
                  retrieve the customer’s phone number and save it in the equivalent Phonecall object field.<\/em><\/p>\n\n\n\n

                  \"\"<\/figure>\n\n\n\n

                  3.3. Profiles association<\/strong><\/h3>\n\n\n\n

                  To make the CRM accessible to advisors, associate the Dynamics 365 CRM v2 with the relevant Profiles<\/strong> in the Maker<\/strong>.
                  Users will then be able to access CRM data directly from the Banner<\/strong>.<\/p>\n\n\n\n

                  \"\"<\/figure>\n","protected":false},"excerpt":{"rendered":"

                  [Reading time: 3 minutes] Overview This article explains how to configure the Dynamics 365 integration in INO cx. Once configured, you can authenticate using Microsoft Azure, synchronize CRM objects, raise CRM cards during interactions, and use Dynamics 365 as an identity provider through SSO. 1. Prerequisites 1.1. Microsoft Power Platform…<\/p>\n","protected":false},"author":5,"comment_status":"closed","ping_status":"closed","template":"","format":"standard","meta":{"footnotes":""},"ht-kb-category":[108],"ht-kb-tag":[180,181],"class_list":["post-5753","ht_kb","type-ht_kb","status-publish","format-standard","hentry","ht_kb_category-integration","ht_kb_tag-connector","ht_kb_tag-ms-dynamics"],"_links":{"self":[{"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/ht-kb\/5753","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/ht-kb"}],"about":[{"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/types\/ht_kb"}],"author":[{"embeddable":true,"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/comments?post=5753"}],"version-history":[{"count":11,"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/ht-kb\/5753\/revisions"}],"predecessor-version":[{"id":5785,"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/ht-kb\/5753\/revisions\/5785"}],"wp:attachment":[{"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/media?parent=5753"}],"wp:term":[{"taxonomy":"ht_kb_category","embeddable":true,"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/ht-kb-category?post=5753"},{"taxonomy":"ht_kb_tag","embeddable":true,"href":"https:\/\/help.ino.cx\/index.php\/wp-json\/wp\/v2\/ht-kb-tag?post=5753"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}