How to fix AADSTS650052 error when connecting microsoft ads connector on fivetran

Hi Karan,

Good day!

Registered application behavior is determined by how your Azure AAD tenant has been set up and how users can provide the consent for any app during authentication process. Your Azure AAD tenant administrator can review user consent settings here: https://free.blessedness.top/azure/active-directory/manage-apps/configure-user-consent?pivots=portal#configure-user-consent-settings.

• If you are trying to authenticate but receive error AADSTS650052, there are a few different root causes for this issue. This likely means that the Microsoft Advertising application ID (d42ffc93-c136-491d-b4fd-6f18168c68fd) doesn't exist in your tenant. This can happen if you are trying to authenticate to a tool provider and never created your own Azure App registration and added msads.manage to it. To fix this, you will need to contact the Active Directory administrator and have them run the following Graph API call to add the Microsoft Advertising app to your tenant.

Copy

POST https://graph.microsoft.com/v1.0/servicePrincipals
Content-type: application/json
{
  "appId": "d42ffc93-c136-491d-b4fd-6f18168c68fd"
}

• After running the above command, you may also need to have your administrator grant consent to your tool provider by running the following URL in your browser. This URL grants consent to SA 360. Please replace "client_id=340615a8-1132-4916-80c7-697a67c6c353" with your tool provider's client ID and replace "tenantID" with your tenant ID: https://login.microsoftonline.com/"tenantID"/v2.0/adminconsent?client_id=340615a8-1132-4916-80c7-697a67c6c353&state=12345&scope=d42ffc93-c136-491d-b4fd-6f18168c68fd/msads.manage
• If you are still experiencing issues after following the above steps, please contact support.

References:

• Register an Application
• Application Behavior

Regards,

Manoj