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(281.6, 57.00000000000001%, 37%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAZ%3C/text%3E%3C/svg%3E)
Dear support,
I've developed an application to use graph api to authenticate over AAD.
It worked for months but now it returns me "StatusCode: BadRequest - Reason: Bad Request"
Where can I see which is the problem with my request?
On client application side I have no more informations on this error.
Application has been developed with these steps:
Token is then passed to another application that perform another request (GetHttpContentWithToken (copied from example)) with scopes "user.read"
Thank you
A cloud-based identity and access management service for securing user authentication and resource access
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more
Dear James,
I've changed nothing recently. Strange thing is that if I use same Bearer token on Postman from my PC it works like a charm. If I use that from linux sever it returns BadRequest error. I really cannot understand what is wrong with my request.
I'm using v1.0
![](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(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Hi @Alberto Zumiani , what version are you using, 1.0 or beta? Have you changed anything recently like policies or subscription types? Is there any issue with your subscription? Have you followed and documents or threads to help resolve the issue? From the troubleshooting guide:
Based on an organization's CA policies, a user accessing Microsoft Graph resources via your app might be challenged for additional information that is not present in the access token your app originally acquired. In this case, your app receives a 400 with an interaction_required error during access token acquisition or a 403 with insufficient_claims error when calling Microsoft Graph. In both cases, the error response contains additional information that can be presented to the authorize endpoint to challenge the user for additional information (like multi-factor authentication or device enrollment).>
Since it has been working for months I don't think there's anything wrong with your implementation unless you recently changed or added something. Please let me know if anything above helps you. If not I will continue looking into this.
Thank you,
James