Before creating and using a Connector, please review the following requirements and prerequisites.
- Registering Application in Azure Management Portal
- Specialized Licensing Required
- Technical Assumption
Registering Application in Azure Management Portal
The D365 SCM Connector supports both OAuth 2.0 Code Flow and OAuth 2.0 Client Credentials and requires the following credentials or information for authentication:
Parameter | Description | OAuth2.0 Code flow | OAuth 2.0 Client Credentials |
---|---|---|---|
Client ID | The Application (client) ID that gets assigned when app registration is successful (noted in step # 9 below.)
Specifies the client ID of the application that is registered in Azure Active Directory. To find the application's client ID: from the Azure Management Portal, click Active Directory, click the directory, click the application, and then click Configure. |
X |
X |
Client Secret | The Client Secret value captured in step# 10 below |
X |
X |
Redirect URI | The URI that you provided in step #8 during the app registration process. This specifies the reply URL of the application. The value must match the value of the redirect_uri parameter in the authorization code request. To find the application's reply URL, in the Azure Management Portal, click Active Directory, click the directory, click the application, and then click Configure. |
X |
|
Resource | The base URL of the SCM Account. |
X |
X |
Tenant ID | The Directory (tenant) ID that gets displayed when app registration is successful (see step# 9 below). |
X |
X |
Related Info:
For Authorization Code Grant flow and Service to service calls using client credentials, one must use the Azure Management Portal to register the application in your Azure AD tenant to obtain ClientID, Client Secret, Redirect URI.
Follow these steps to register an application in your AzureAD tenant:
- Register a new application using the Azure portal.
- Sign in to the Azure portal using either a work or school account or a personal Microsoft account.
- If your account gives you access to more than one tenant, select your account in the upper right corner. Set your portal session to the Azure AD tenant that you want.
- Search for and select Azure Active Directory. Under Manage, select App registrations.
- Select New registration.
- In Register an application, enter a meaningful application name to display to users.
- Specify who can use the application. More information can be found here: https://docs.microsoft.com/en-us/azure/active-directory/develop/quickstart-register-app#register-a-new-application-using-the-azure-portal
- Under Redirect URI (optional), select the type of app you're building: Web or Public client (mobile & desktop). Then enter the redirect URI, or reply URL, for your application.
For web applications, provide the base URL of your app. For example, https://localhost:31544 might be the URL for a web app running on your local machine. Users would use this URL to sign in to a web client application.
For public client applications, provide the URI used by Azure AD to return token responses. Enter a value specific to your application, such as myapp://auth.
For examples of web applications or native applications, see the Quickstarts in Microsoft identity platform.
- When finished, select Register.
Result: Azure AD assigns a unique application or client ID to your app. The portal opens your application's Overview page. To add capabilities to your application, you can select other configuration options including branding, certificates and secrets, API permissions, and more.
- Once the app is created, click on the App Name from the listing page. Click on Certificates and Secrets -> New Client Secret, Follow the steps mentioned on the screen to capture the Client Secret.
- Add the APIs to which the registered app will have access to. Click on API Permissions -> Add a permission. For Microsoft Dynamics 365 SCM, Dynamics ERP permissions need to be provided.
- The final step is to add the Client ID (generated in Step 9) to the Microsoft Dynamics 365 SCM application.
Log into the D365 SCM application and search for Azure Active Directory. Click on the New button and add the Client ID (generated in Step 9), a suitable name for the app, and the userId of the admin.
Save the changes when done.
Specialized Licensing Required
The Application Connector requires a specialized server license. See your Customer Account Manager.
Technical Assumption
Effective use of the Connector assumes the following:
- You are familiar with the development and organization of your external application account.
- You know the particulars of your data and the external processes to manage it.
- You have a general understanding of how to create and share resources, and publish (deploy) integration projects in the CIC Studio.
Comments
0 comments
Please sign in to leave a comment.