Updated on
Jun 8, 2026
While configuring your Bing Ads connection, you may encounter several issues. Understanding these common errors can help streamline the setup process and facilitate quick resolutions.
Need admin approval. Improvado needs permission to access resources in your organization that only an admin can grant.
{%docs-informer-end%}Microsoft tags the msads.manage scope (Microsoft Advertising API) as admin-consent-required at the API level. In any Microsoft Entra ID (Azure AD) tenant that uses the default consent policy, which is the default for most enterprise tenants, a regular user cannot grant consent on their own, regardless of their Microsoft Advertising role. Even a user with the Super Admin role in Microsoft Advertising will see this prompt.
This is by Microsoft's design for the Advertising API. It is not an Improvado configuration issue.
A Global Administrator (or Privileged Role Administrator / Cloud Application Administrator) of your Microsoft 365 / Entra ID tenant must grant tenant-wide consent for the Improvado app. This is a one-time action.
Option 1: Grant admin consent via URL (simplest)
Have your Global Administrator open the following URL while signed into your tenant:
https://login.microsoftonline.com/common/adminconsent?client_id=fa54b799-584e-4181-94c2-6bb53879ede5
This displays the permissions Improvado requests and applies consent organization-wide. After that, any user in your tenant can complete the Improvado to Bing Ads connection without the admin-approval prompt.
Option 2: Grant admin consent via the Entra portal
The user who creates the Bing Ads connection in Improvado needs the Data Manager role (or higher) in their Improvado workspace. The Data Load Manager role alone is not enough to finalize the connection. See Available user roles. Once admin consent is in place and the user has the Data Manager role, retry the Bing Ads connection. It will complete without the approval prompt, and extraction resumes on the next scheduled run.
cannot get code for Bing. Error description=AADSTS650052
{%docs-informer-end%}The AADSTS650052 error indicates that Microsoft's Advertising API Service lacked a required Service Principal during consent attempts. Despite "Allow user consent for apps" settings, certain Microsoft applications still demand admin-level authorization for proper tenant initialization.
Starting April 2025, Microsoft began enforcing mandatory service principal registration for all multi-tenant applications. Previously, Microsoft silently issued tokens even when the tenant lacked a service principal. Now, this is blocked. Learn more about this change.
Option 1: Sign in to Microsoft Advertising with a Tenant Admin (simplest)
Contact your Azure AD Global Administrator to establish access. Have the Azure AD Global Administrator log in directly to ads.microsoft.com and connect the Bing Ads account. This action grants necessary admin consent and automatically provisions the required service principal. After that, go back to Improvado and retry the connection.
Option 2: Create the Service Principal via Microsoft Graph API
If Option 1 doesn't work, the administrator can provision the service principal manually.
Using Microsoft Graph Explorer:
POST https://graph.microsoft.com/v1.0/servicePrincipals
Content-Type: application/json
{
"appId": "d42ffc93-c136-491d-b4fd-6f18168c68fd"
}
Alternatively, using Azure CLI:
az ad sp create --id d42ffc93-c136-491d-b4fd-6f18168c68fd
Wait a few minutes for propagation, then retry the Improvado connection.
Option 3: Grant Admin Consent via URL
The administrator can visit this URL in a browser (replace {your-tenant-id} with your Microsoft Entra ID tenant ID):
https://login.microsoftonline.com/{your-tenant-id}/adminconsent?client_id=d42ffc93-c136-491d-b4fd-6f18168c68fd
To find your tenant ID: go to Azure Portal → Microsoft Entra ID → Overview → Tenant ID.
"You must use a different identity type to sign in to Bing Ads with the same email."
{%docs-informer-end%}Your Microsoft Advertising account is linked to a specific identity provider (Microsoft or Google). You are trying to authorize through a different identity provider than the one your account was created with.
If you're unsure which identity provider your account uses, go to ads.microsoft.com and check which sign-in method works.
If none of the provided solutions worked, feel free to raise a request via the Service Desk.
Improvado team is always happy to help with any other questions you might have! Send us an email.
Contact your Customer Success Manager or raise a request in Improvado Service Desk.