Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
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
  • 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

  • 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.

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

Quick Links

🌸 Community Spring Festival 2025 Challenge Winners! 🌸

Congratulations to all our community participants!

Adis Hodzic – Community Spotlight

We are honored to recognize Adis Hodzic as our May 2025 Community…

Kudos to the April Top 10 Community Stars!

Thanks for all your good work in the Community!

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

#1
YUN ZHU Profile Picture

YUN ZHU 448 Super User 2025 Season 1

#2
Sagar Dangar, MCP Profile Picture

Sagar Dangar, MCP 358

#3
Mansi Soni Profile Picture

Mansi Soni 327

Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans