web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Small and medium business | Business Central, N... / Dataverse Connector - ...
Small and medium business | Business Central, N...
Answered

Dataverse Connector - Failed to acquire an access token from Dataverse

(0) ShareShare
ReportReport
Posted on by FelipeSilva 5

Hello Masters!

I am facing the following error when trying to connect a BC on-prem (version 18) to Dataverse. 

pastedimage1633509614322v1.png

I have created the application user that the documentation requires, created this application user manually in Dataverse, and tested getting a token using Postman.

My domain user is an administrator in Dataverse. And I have also created one user in BC with the same email address and configured the "Super" permission.

Things that I already checked:

 - The Dataverse environment is NOT in admin mode

 - The application user has the correct permission in BC (Delegated - Financials.ReadWrite.All) and in Dataverse (Delegated - user_impersonation)

 - The redirect URL is the one recommended in the connection setup and was also configured in the application user (Azure AD)

Am I missing something else? The error message does not say a lot on this screen.

Categories:
Dynamics 365 Business Central
I have the same question (0)
  • Verified answer
    Marco Mels Profile Picture
    Marco Mels on at
    RE: Dataverse Connector - Failed to acquire an access token from Dataverse

    Hello,

    Okay, in the Azure AD App manifest file, you need to ensure the SignInAudience property is set to multitenant. 

    If it is set to the following:

        "signInAudience": "AzureADMyOrg",


    Change to:

        "signInAudience": "AzureADMultipleOrgs",


    Next if your API permission do not contain the name of your  own Azure AD app with user_impersonation, then you need to set that as well. Both suggestion will lead to a succesfull logon with the Administrator account in BC. If not, then make sure the reply url is set correctly when you run assisted setup for Azure AD configuration. It must have the following format: https://PublicWeBaseUrl/OAuthLanding.htm. The PublicWebBaseUrl is the url to the WebClientInstance. 

    Thanks.

  • FelipeSilva Profile Picture
    FelipeSilva 5 on at
    RE: Dataverse Connector - Failed to acquire an access token from Dataverse

    After changing the "signInAudience" to AzureADMultipleOrgs it worked! Thank you very much for the support!

    Kind Regards,

    Felipe Silva

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

News and Announcements

Join experts in person to explore low code and AI agents at the Power Platform Community Conference sponsored by Microsoft

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Abhilash Warrier – Community Spotlight

We are honored to recognize Abhilash Warrier as our Community Spotlight honoree for…

Congratulations to the September Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Small and medium business | Business Central, NAV, RMS

#1
Rishabh Kanaskar Profile Picture

Rishabh Kanaskar 4,237

#2
Nimsara Jayathilaka. Profile Picture

Nimsara Jayathilaka. 3,425

#3
Sumit Singh Profile Picture

Sumit Singh 2,907

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans