Skip to main content
All CollectionsGetAccept Automation
How to Connect Microsoft Dynamics 365 with GetAccept Automation
How to Connect Microsoft Dynamics 365 with GetAccept Automation

Learn how to connect Microsoft Dynamics 365 to GetAccept Automation, including setup, authentication, and troubleshooting tips.

Updated over 3 months ago

Introduction

This article describes how to connect to your Microsoft Dynamics 365 environment following an invite from GetAccept to our iPaaS service called GetAccept Automation.

GetAccept Automation is a powerful iPaaS service that connects you to over 500+ community connectors. To access the GetAccept Automation, you need a subscription and an invitation. Contact our sales department to learn more.

Requirements

  • An active subscription and invitation to GetAccept Automation.

  • Authorization Level: Dataverse read/write access to the relevant tables in Microsoft Dynamics. Such as search contacts, read contacts, write to contacts, search/read/write accounts, and write opportunities.

Invitation and Basic Setup

Once you have been invited to GetAccept Automation, you will receive an email asking you to create your account. Follow the instructions to create the account and log in to the platform.

  • Important: After logging in, ensure you switch the workspace from "My Workspace" to your company workspace by clicking on your profile image in the top left corner and selecting the workspace that matches your organization's name.

  • If you encounter any issues with logging in or accessing your GetAccept Automation workspace, please contact your Customer Success Manager or our Customer Support team for assistance.

For a detailed guide on setting up your account and navigating your workspace, please refer to the full article: Getting Started with GetAccept Automation.

Navigate to the Microsoft Dynamics 365 Connector

Following the invite, account setup, and navigation to the correct workspace, you will find all relevant connectors under Projects and Connections, there will also be a project folder where all of your connectors are placed.

Once you have identified the Microsoft Dynamics 365 connector, click to open it and you will see this view:

Connection setup

Connector Fields Overview

Field

Description

Connection name

Give this connection a descriptive name to indicate which Dynamics 365 instance it is connected to.

Subdomain

The subdomain of your Dynamics 365 instance.

Account type

Indicate if you are connecting to a cloud instance or an on-premise instance.

AD domain Name
Only for on-premise instance

The Active Directory server.

Client ID

The client ID.

Client secret

The client secret.

How to connect Microsoft Dynamics 365

Find out how to create a connection to your Microsoft Dynamics 365 instance, through the cloud app or the on-premise application.

Connecting to a cloud Microsoft Dynamics 365 instance

To connect to Microsoft 365 Dynamics on GetAccept Automation, you need to obtain a client ID by registering your Microsoft 365 Dynamics app with Azure Active Directory. We walk through the process of registering Microsoft 365 Dynamics below.

  1. Sign in to the Microsoft Azure management portal by using an account with administrator permission. You must use an account in the same Office 365 subscription (tenant) as you intend to register the app:

    Azure Homepage

    Microsoft Azure homepage

  2. Click App registrations:

    App Registration

    App registrations are located on the navigation menu on the left.

  3. If you already have an application, use that ID. If not, proceed to click Add. Provide a name for the application to add (typically "GetAccept Automation"). Choose the account type as "Accounts in this organizational directory only (Single tenant)" and provide a redirect URI value of https://www.workato.com/oauth/callback. Click Register at the bottom of the page:

    Add application

    Register the application.

  4. Your new application will be displayed on your app registrations. Select your new app to open the app details:

    Add

    Select the newly created application.

  5. ​In your app details page, create a Client Secret under the Certificates & Secrets section. This will be required for the connection setup:

    New client secret

    Create client secret.

  6. In the right menu click API permissions > Add a permission:

    Required permissions

    Click Required permissions.

  7. Select Dynamics CRM from the Microsoft API tab:

    Dynamics CRM

    Select Dynamics 365 Online API access.

  8. Select Delegated permission, then check the user_impersonation checkbox. Select Add permissions:

    Add permissions

    Add permissions.

  9. Retrieve the application (client) ID as the client ID to connect to GetAccept Automation:

    Application ID

    Retrieve the Application ID.

  10. Retrieve the Client secret to connect to GetAccept Automation:

    Retrieve client secret

    Retrieve the client secret.

Connecting to an on-premise Microsoft Dynamics 365 instance

To connect to Microsoft 365 Dynamics on GetAccept Automation, you need to obtain a client ID by registering the Microsoft 365 Dynamics App with Active Directory Federation Service. Click here(opens new window) to read more on how to register an on-premise Dynamics app with Active Directory Federation Service.

Extending refresh token expiration time

Whenever you connect to a Dynamics app, GetAccept Automation gets an access token to be able to read and write to your Dynamics instance. This access token is valid until its expiry date. GetAccept Automation also gets an accompanying refresh token with this access token. Whenever your access token expires, GetAccept Automation can request for a new access token with the refresh token. Dynamics will check that this refresh token is still valid (i.e. the token has not been revoked), and provide a new pair of access and refresh tokens.

However, refresh tokens have expiry dates as well. If both the access token and refresh token expires before GetAccept Automation requests for new tokens, the Dynamics connection will no longer be valid, and a re-connection is required from the user. When this happens, GetAccept Automation's requests to Dynamics will get a 400 response. If your workspace is using a Dynamics 365 trigger, this results in your recipe experiencing trigger errors. If you are using a Dynamics CRM action, this results in job errors.

To ensure your recipes run continuously without requiring intervention, extend your refresh token expiration time, or set it to unlimited. You can apply and scope it to an OAuth application instead of applying it to the entire organization.

Read more about token lifetimes in the Microsoft documentation(opens new window).

Troubleshooting

AADSTS900971: No reply address provided

For the error message AADSTS900971, it means that the redirect URI value is incorrect, make sure that you've added the URI https://www.workato.com/oauth/callback in the configuration, read more about it here.

Sorry, but we’re having trouble signing you in.
AADSTS900971: No reply address provided.
Did this answer your question?