@Paid Search 51 I am experiencing the same issue.
I don't see "Microsoft Advertising API Service" under "APIs my organization uses" tab.
How does one enable it?
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
We are following documentation
, but when we try to Request User Consent, we get the following error message
AADSTS650052: The app needs access to a service ('https://ads.microsoft.com') that your organization 'xxx-xxx-xxxx-xxxx' has not subscribed to or enabled. Contact your IT Admin to review the configuration of your service subscriptions.
How can we fix this?
@Paid Search 51 I am experiencing the same issue.
I don't see "Microsoft Advertising API Service" under "APIs my organization uses" tab.
How does one enable it?
In Azure add API Permission "Microsoft Advertising API Service" to your App Registration
In Azure, go to App Registrations:
- Select your app
- Click on API Permissions from the menu option
- Click Add a Permission
- Click Tab: APIs my organization uses
- Search for Microsoft Advertising API Service
- Select the App and the required msads.manage and ads.manage permissions
For folks who are not able to see the "Microsoft Advertising API Service" in 'APIs my organization uses' - here is a catch which we figure out after trying for a few days.
"Microsoft Advertising API Service" gets added automatically on signing for a Microsoft Advertising account (https://ads.microsoft.com/).
Your Azure account will be under a directory xxx.onmicrosoft.com. You will need a work account user eg: user1@xxx.onmicrosoft.com and will need to signup for Microsoft Advertising account using that user. This will ensure that your Azure direction gets the "Microsoft Advertising API Service"
Any luck on this? I'm facing the same exact issue.
@Ravi Doppalapudi and @Paid Search 51 - If you are still observing this error please contact support to review your account and user credentials.
Hi @Eric Urban - MSFT we are still facing the same issue and contacted support, no update yet.