Hi, I'm Ask INFA!
What would you like to know?
ASK INFAPreview
Please to access Bolo.
Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • Administrator
  • All Products

Table of Contents

Search

  1. Connectors and connections
  2. Connection configuration
  3. Connection properties
  4. Swagger file generation for REST V2 connections

Connections

Connections

Back Next

Microsoft Dynamics 365 Mass Ingestion connection properties

Microsoft Dynamics 365 Mass Ingestion connection properties

When you set up a Microsoft Dynamics 365 Mass Ingestion connection, you must configure the connection properties.
The Microsoft Dynamics 365 Mass Ingestion connection requires a native application that is registered in Azure Active Directory (Azure AD) to access the Microsoft Dynamics 365 data. Before you configure the connection, you must register an application in Azure AD to allow the connection to access the Microsoft Dynamics 365 data. For more information about registering an application in Azure AD, see the Microsoft documentation.
The properties of a Microsoft Dynamics 365 Mass Ingestion connection vary based on the authentication method that you specify for the connection. When you create a connection, you can select one of the following authentication methods:
  • OAuth 2.0 Username-Password Flow
    : Authenticates the connection by using the Microsoft Dynamics 365 account login credentials and the client ID of the application registered in Azure AD.
  • OAuth 2.0 Client Secret Flow
    : Authenticates the connection by using the client ID and client secret of the application registered in Azure AD.
  • OAuth 2.0 JWT Bearer Flow
    : Authenticates the connection by using a X509 Public Key Infrastructure (PKI) certificate and a JSON Web Token (JWT). Use this authentication method to gain secured access to Microsoft Dynamics 365 without sharing sensitive information, such as client secret and Microsoft Dynamics 365 account login credentials.

Connection properties for OAuth 2.0 Username-Password Flow authentication

The following table describes the connection properties for a Microsoft Dynamics 365 Mass Ingestion connection configured with OAuth 2.0 Username-Password Flow authentication:
Connection property
Description
Runtime Environment
Name of the runtime environment where you want to run the ingestion tasks.
You must specify a Secure Agent as the runtime environment.
You cannot run
application ingestion
 tasks on a Hosted Agent or serverless runtime environment.
User Name
User name of the Microsoft Dynamics 365 account.
Password
Password for the Microsoft Dynamics 365 account.
Client ID
Client ID of the application registered in Azure AD.
Resource URL
URL of the Microsoft Dynamics 365 organization.
You must enter the resource URL in the following format:
https://<Microsoft_Dynamics_365_org_name>.api.crm8.dynamics.com
OAuth Token URL
OAuth 2.0 token endpoint of the Microsoft Dynamics 365 organization. The application that is registered in Azure AD sends the access token requests to this endpoint.
You must enter the following value in this field:
https://login.windows.net/common/oauth2/token
For more information about the OAuth 2.0 Username-Password Flow authentication method, see the Microsoft Dynamics 365 documentation.

Connection properties for OAuth 2.0 Client Secret Flow authentication

The following table describes the connection properties for a Microsoft Dynamics 365 Mass Ingestion connection configured with OAuth 2.0 Client Secret Flow authentication:
Connection property
Description
Runtime Environment
Name of the runtime environment where you want to run the ingestion tasks.
You must specify a Secure Agent as the runtime environment.
You cannot run
application ingestion
 tasks on a Hosted Agent or serverless runtime environment.
Client ID
Client ID of the application registered in Azure AD.
Client Secret
Client secret of the application registered in Azure AD.
Resource URL
URL of the Microsoft Dynamics 365 organization.
You must enter the resource URL in the following format:
https://<Microsoft_Dynamics_365_org_name>.api.crm8.dynamics.com
OAuth Token URL
OAuth 2.0 token endpoint of the Microsoft Dynamics 365 organization. The application that is registered in Azure AD sends the access token requests to this endpoint.
You must enter the following value in this field:
https://login.microsoftonline.com/<tentant_id>/oauth2/token
For more information about the OAuth 2.0 Client Secret Flow authentication method, see the Microsoft Dynamics 365 documentation.

Connection properties for OAuth 2.0 JWT Bearer Flow authentication

The following table describes the connection properties for a Microsoft Dynamics 365 Mass Ingestion connection configured with OAuth 2.0 JWT Bearer Flow authentication:
Connection property
Description
Runtime Environment
Name of the runtime environment where you want to run the ingestion tasks.
You must specify a Secure Agent as the runtime environment.
You cannot run
application ingestion
 tasks on a Hosted Agent or serverless runtime environment.
Client ID
Client ID of the application registered in Azure AD.
Certificate Signature
Base64URL string that encodes the hexadecimal value which represents the SHA-1 thumbprint of the X509 certificate.
Keystore Path
Absolute path to the keystore file that contains the X509 certificate required to validate a JSON Web Token (JWT) and establish a secure connection with Microsoft Dynamics 365.
The keystore file must be in the Java KeyStore (JKS) format.
Keystore Password
Password for the keystore file.
Private Key Alias
Alias name of the private key used to sign the JWT.
Private Key Password
Password for the private key.
Audience for JWT
URL of the Microsoft Dynamics 365 resource server to which the application that is registered in Azure AD sends the JWT for validation.
You must enter the address in the following format:
https://login.microsoftonline.com/<tentant_id>/oauth2/token
Resource URL
URL of the Microsoft Dynamics 365 organization.
You must enter the resource URL in the following format:
https://<Microsoft_Dynamics_365_org_name>.api.crm8.dynamics.com
OAuth Token URL
OAuth 2.0 token endpoint of the Microsoft Dynamics 365 organization. The application that is registered in Azure AD sends the access token requests to this endpoint.
You must enter the following value in this field:
https://login.microsoftonline.com/<tentant_id>/oauth2/token
For more information about the OAuth 2.0 Client Secret Flow authentication method, see the Microsoft Dynamics 365 documentation.
0 COMMENTS
We’d like to hear from you!