This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(3.2, 28.999999999999996%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJB%3C/text%3E%3C/svg%3E)
Hi!
We operate a reporting service that uses our own app to get data from the Bing Ads API on behalf of our clients. We recently updated our app authentication to use the latest version of the service but since doing that, a subset of our users have been getting this error:
The app needs access to a service ("https://ads.microsoft.com") that your organization "{organization}" has not subscribed to or enabled
We've done our research and found that most cases of this either seem to be due to the user not using a work account to log into the API or that they don't have the appropriate permissions/API access set up. We found other threads here like this that cover these issues and also some people adding how to check in Azure if you have the API enabled.
https://learn.microsoft.com/en-us/answers/questions/409464/bing-ads-api-error-code-650052-1.html
We've given these resources to our customers, but some still come back saying nothing works and they still get the AADSTS650052 error. It is noted in the article about the error that they should contact support and we have directed them to do so, as this appears to be nothing we can fix on our side, it's a problem with their MS account tied to the Microsoft Advertising tool or Azure tenant permissions.
The problem is that Microsoft support keeps bouncing them back to us, linking to irrelevant articles on our portal about how to log in again. This doesn't help. They need help from MS to review their account and check their permissions, but they keep getting redirected back to us and we're in no position to assist.
Is there anything else about this error that we can address on our side as the app owner? Is there other reasons this error can occur that we can tell these users about? Or some clearer way to tell MS support how they can actually help (as that's your own instructions in your own documentation on how to address this)?
Thank you for your help and ideas!
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(19.2, 61%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDN%3C/text%3E%3C/svg%3E)
I know this post is a few months old, but did you ever end up figuring it out? I am in the same situation as you are/were right now.
So I ended up getting looped into the support thread with MS support and the customer, to explain that our product is using the correct API and that it's really not the problem on our side. I also had the trace ID and error log information for that customer so support could look up the exact error.
Turns out the user had converted their Microsoft account into a work account but should not have done this. They did not have Azure set up, so it kept bouncing, looking for an Azure Activity Directory service that didn't actually exist. Support tried to revert their account back to a personal account, but they weren't able to for some reason. The customer basically had to make a brand new Microsoft account and attach it to the Bing Ads manager to finally clear the error.
I hope this helps you figure out what is going on. If there's any way you can get the log and trace IDs for the error, that seemed to really help MS support at least confirm it was happening on their side of the system.