Dynamics Community Forum Thread Details

Hello,

When trying to enable the connection to CDS / Dataverse, the following error may show up.

The HTTP request was forbidden with client authentication scheme 'Anonymous'. The HTTP request was forbidden with client authentication scheme 'Anonymous'. => The remote server returned an error: (403) Forbidden.Unable to Login to Dynamics CRM Unable to Login to Dynamics CRM

This issue happens because the integration users is not an administrator while the CDS / Dataverse is configured in Administration mode. To resolve, please have a look here:
Administration mode - Power Platform | Microsoft Docs

Dataverse or CDS should not be configured in Admin mode as this will produce the error above.

In addition to the above error, please note the following that we added to the release notes:
Update 16.5 for Microsoft Dynamics 365 Business Central 2020 Release Wave 1 (Application Build 16.5.15953, Platform Build 16.0.15941)

Release note

ID	Title	Functional Area
369662	“Failed to acquire an access token" error message when you try to setup any Oauth2 integration.	Integration

Workaround

Go to nuget.org and download the required package by clicking "Download package": https://www.nuget.org/packages/Microsoft.Identity.Client/4.14.0.
Extract the contents.
Copy the contents from .\microsoft.identity.client.4.14.0\lib\net45\* to the NST binaries location.
Restart the NST.

The application event log file will tell you what nuget package you need, this could however be a different release as written here compared to the note on the released CU page:
(+) Connect BC 160 OnPrem to Common Data Service troubleshooting - Dynamics 365 Business Central Forum Community Forum

Last but not least, we have seen support requests where the following error shows up in application event log file, The message on the screen is again "Failed to acquire an access token".

Server instance: BC160
Category: Security
ClientSessionId:
ClientActivityId:
ServerSessionUniqueId:
ServerActivityId:
EventTime:
Message (LicenseServiceAdalServiceException): RootException: LicenseServiceAdalServiceException
AADSTS50194: Application 'xxx (xxx) is not configured as a multi-tenant application. Usage of the /common endpoint is not supported for such applications created after '10/15/2018'. Use a tenant-specific endpoint or configure the application to be multi-tenant.
Trace ID:
Correlation ID:

To resolve, the Azure AD app must be created as a multi tenant. To do so, do the following.

Logon to Azure Portal

Select Azure Active Directory

Select App Registrations

Select the Azure AD app created for CDS / Dataverse

Select Manifest

Search in the Manifest file for SignInAudience and change AzureADMyOrg to AzureADMultipleOrgs

More information here:

https://docs.microsoft.com/en-us/azure/active-directory/develop/reference-app-manifest

If it is not possible to change the SignInAudience, create a new Azure AD Registration. Documentation here:

https://docs.microsoft.com/en-us/azure/active-directory/develop/quickstart-register-app

Use:

Accounts in any organizational directory

This will set the SignInAudience to the correct value.

Hope this does help to mitigate a few of the scenario's support did receive.

Thanks

Community site session details

When trying to enable connection to CDS / Dataverse from OnPrem Business Central an error may occur

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

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

Featured topics

Product updates