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(25.6, 15%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBS%3C/text%3E%3C/svg%3E)
As of yesterday my application using Office 365 accounts are reporting the following error on requests to graph APIs (email, onedrive, etc)
{
"error": {
"code": "InvalidAuthenticationToken",
"message": "Access token validation failure.",
"innerError": {
"date": "2020-11-11T13:27:22",
"request-id": "f528a476-f882-4d0b-9aab-b5657245e2c0",
"client-request-id": "f528a476-f882-4d0b-9aab-b5657245e2c0"
}
}
}
Things still work find using outlook.com accounts... it's just office 365 accounts reporting this error.
I am confused as to how this would just start all of a sudden after working for more than 3 or more years. This is causing huge problems for customers using the API services.
I have tried re-registering and getting a new token, refreshing tokens, and still get the same error.
Thank you for any assistance. I guess I am not sure what else to provide as it's been a standard request token/refresh that's worked for a while and nothing on my end has changed.
![](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(304, 2%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESM%3C/text%3E%3C/svg%3E)
Hello @Bradley Stone , thank you for reaching out. We would need some more details about this app that you are using particularly would like to know the request URL that is being sent by this app to AAD while trying to fetch the token from AAD. Do share us the following details so that we can dig in a little deeper to figure out the point of failure.
Do share us the following information so that we can understand the failure better and help you further.
Let me know if this is what you need... it's your standard OAuth 2.0 flow as detailed in your docs and has worked successfully for a few years.
Based on the troubleshooting we figured out that the issue was with the tokensize. Since the entire token was not received by the application hence the error was popping up.
The issue was on my end. I didn't realize the token size had changed > 2kb so I wasn't getting the entire token. Thank you for your support and help!