web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Customer experience | Sales, Customer Insights,...
Answered

Authentication against Dynamics REST API broke over the weekend.

(0) ShareShare
ReportReport
Posted on by 5

Hey!

So I have been running a few applications that authenticate using the method described here: https://docs.microsoft.com/en-us/powerapps/developer/common-data-service/authenticate-oauth#connect-as-an-app in order to use the Dynamics REST API. The only difference being that I don't use c-sharp. I just get the token from login.microsoftonline.com and pass it with my request. Everything worked fine until yestarday (monday 2/12-2019).

We started seeing bugs i production where we were unable to access the API due to a 403. However the request would work at random evey 10th time or so. I tried using the same token and generating a new one for each request, it didn't make a diffrence. The problem persist, still about every 10th request works.

What we also noted is that sending the request trough postman worked. The only difference was that the postman request included 4 cookies (origin unknown). Clever as I am I tried deleting these cookies and reproduced the error in postman, but I didn't back the cookies up.

Now to me this seems weird. The docs never mention using cookies to authenticate. I do not understand how these cookies were even created in the first place either. An even more so the incosnsitencies in that every 10th request works.

The response is a 403 with the following message.

{"error":{"code":"0x80072560","message":"The user is not a member of the organization."}}

Does anyone have the slightest idea what is happening?

I have the same question (0)
  • Verified answer
    a33ik Profile Picture
    84,331 Most Valuable Professional on at

    Hello,

    Get in touch with Microsoft and ask for support. If something used to work and stopped then logical answer is that Microsoft changed something so.. only they can help you with your issue. Support ticket is your way to go.

    Good luck.

  • jenihana Profile Picture
    75 on at

    I am having the exact same problem. Did you find a resolution? I just opened a MS Support Ticket, but was just wondering if you had already resolved.

  • tiptop96 Profile Picture
    5 on at

    Not really, we ended up creating a new user.

    I had used an email address for the application user that was already regsitered with a normal licenced user. We think that it was caused by a lack of privliges on the licenced user, meaning that for some reason the application user was connected to the licenced user. We could se this by the fact that my AAD account and the aplpication user had matching object ids.

    So we cretaed a new application user with a email that was independent of any AAD account and have had no issue sience...

    Regards

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > Customer experience | Sales, Customer Insights, CRM

#1
Tom_Gioielli Profile Picture

Tom_Gioielli 144 Super User 2025 Season 2

#2
#ManoVerse Profile Picture

#ManoVerse 59

#3
Gerardo Rentería García Profile Picture

Gerardo Rentería Ga... 52 Most Valuable Professional

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans