Shining star

Microsoft 365 adapter - token lifetime


At one of my customer's systems we see the Microsoft 365 failing relativ shortly after the refresh token has been renewed. I assume this is related to an expired token.


Import failed. Error: The remote server returned an error: (400) Bad Request


From what I can see in various forums, the token lifetime can be configured. Could this be the reason for such behaviour? Could anyone from Flexera please share their experience? If possible, I'd really like to see some documentation regarding such collateral configurations.

Best regards,


Softline Group is Europe's leading independent expert in Software Asset Management.
3 Replies
Frequent contributor

Re: Microsoft 365 adapter - token lifetime

We also experienced this about a week ago or end of Feb, we manually created a new Token.

I guess it was related to a release of the Graph API, since we needed to consent once more.


Active participant

Re: Microsoft 365 adapter - token lifetime

Hi, I've noticed this too with a number of our customers.

Does anyone have the specific setting to change to increase this token expiration? Also, is the expiration relative to the user generating the token, the Beacon application, or the O365 instance, or other?



Re: Microsoft 365 adapter - token lifetime

Information on token lifetime begins on the bottom of page 273 of the Inventory Adapters and Connectors guide:
0 Kudos