OAuth 2.0 for Microsoft Dataverse
Configure Alteryx Analytics Cloud (AAC) to integrate with your Microsoft Dataverse deployment using OAuth 2.0 to authenticate.
Prerequisites
OAuth 2.0 is supported for Microsoft Dataverse, which is available on Microsoft Azure.
OAuth 2.0 authentication must be enabled in AACAAC. For more information, seeEnable OAuth 2.0 Authentication.
ヒント
OAuth 2.0 for Microsoft Dataverse may work for other tenant-based identity providers. You can use this solution as a template for creating the required objects in your identity provider's console and AACAAC.
Create OAuth 2.0 Client App in Azure
In the Azure console, you must create the client app.
Steps:
Login to Azure: https://portal.azure.com/#home
Select Azure Active Directory > App Registrations > New registration.
Specify the following fields:
Field
Description
Name
The name of the app.
Supported Account Types
Select either:
Single tenant
Multi tenant
Redirect URI
Specify the URL in the following format, depending your project or workspace login:
https://<Login_URL>/oauth2/callback
Example:
https://ayxpreview.alteryxcloud.com/oauth2/callback
To create the new registration, click Register.
Overview tab:
注記
Copy the value for the Application (client) Id. This value must be applied in AACAAC.
Branding tab: (optional) Specify the following fields:
Field
Description
Name
The name of the app should match the value you specified previously.
Logo
Upload a preferred logo for the app.
Homepage URL
Set this value to the following:
https://trifacta.com
Terms of Service URL
Set this value to the following:
https://www.trifacta.com/terms-conditions/
Privacy Policy
Set this value to the following:
https://www.trifacta.com/privacy-policy/
Publisher Domain
Set this value to the following:
trifacta.com
MPN ID
If you are a Microsoft Partner, you can specify your MPN ID.
Certificates & Secrets tab: To create a new client secret:
Select New client secret.
Set the Expires option to
Never
.Select Add.
注記
Copy the Value field. This value is the client secret and must be applied in AACAAC.
API Permissions tab:
Select Add a permission.
Grant these permissions.
API
Permissions name
Type
Admin consent request
Dynamics CRM
user_impersonation
Delegated
No
Microsoft Graph
User Read
Delegated
No
Save your changes.
Create OAuth 2.0 Client for Microsoft Dataverse
After the Microsoft Dataverse client app is created, you must create an OAuth 2.0 client in AACAAC, which is used to integrate with the OAuth 2.0 Client app that you created in Azure.
Steps:
Login to AACAAC as a workspace administrator.
In the lefthand menu, select User menu > Admin console > OAuth 2.0 Clients.
In the OAuth 2.0 Clients page, click Register OAuth 2.0.0 Client.
Specify the fields for the new client:
Field
Description
Type
Microsoft Dataverse
Name
Enter a name for the client.
Client ID
Paste the value of the Application (client) Id that was generated when you created the client app in Azure.
Client Secret
Paste the value of the client secret that was generated when you created the client app in Azure.
Authorization URL
Single tenant:
https://login.microsoftonline.com/<tenant_identifier>/oauth2/v2.0/authorize
Multi-tenant:
https://login.microsoftonline.com/common/oauth2/v2.0/authorize
Token URL
Single tenant:
https://login.microsoftonline.com/<tenant_identifier>/oauth2/v2.0/token
Multi-tenant:
https://login.microsoftonline.com/common/oauth2/v2.0/authorize
Scopes
Set the scopes to the following values:
注記
Individual scopes must be separated by a space.
https://xxxxxx.crm.dynamics.com/user_impersonation offline_access
Access Token Expires In
Set this value to the following:
3599999
.Refresh Token Expires In
Set this value to the following:
7775999999
.To save your OAuth 2.0 client, click Save.
For more information, see Create OAuth2 Client.
Create Microsoft Dataverse Connection
After you have created the two OAuth 2.0 client references, you can create a connection to your Microsoft Dataverse data.
注記
You must create a separate connection for each OAuth 2.0 client that is available in AACAAC.
For more information, see Microsoft Dataverse Connections.