O365 Inventory gathering failed. (400) Bad Request.

[andreidrexler]

Hi, 

We have an issue with the O365 Connector.

We generate a token and it works just fine, completes the task with success. 
But that only lasts for a day, the next day we get the error "Inventory gathering failed. Error: The remote server returned an error: (400) Bad Request." 

We then have to go again and generate another token in order for it to work again. So we basically have to generate a new token every day. 

What do you think could be the problem here?

PS: We have multiple clients with O365 connectors (that work just fine), but this specific client is the only one that has two factor authenticator activated on the Microsoft Account. Do you think this could be the reason the token only last for one day?

[JJacildo]

Hello @andreidrexler , since we are getting 400 Bad Requests here. I would double-check if the following values are the same on the O365 connector.

• Authorization Endpoint: https://login.microsoftonline.com/common/oauth2/v2.0/authorize
• Token Endpoint: https://login.microsoftonline.com/common/oauth2/v2.0/token
• Application (client) ID: 5bb1a5a2-0d97-4335-9448-119f7b27aff9
• Redirect URI: https://login.microsoftonline.com/common/oauth2/nativeclient

[andreidrexler]

Hello, 

So our values were a bit different than these. But we tried this method and it still won't work more than one day. 

[Alpesh_Gohil · Accepted solution]

Hi @andreidrexler , I think the O365 connector does not work with accounts using 2FA. Also, you should try using the client secret method to generate the token. This may be a good approach to bypass the 2FA requirement. 

Hope this helps.

Thanks!
 

[karljwogoman]

@andreidrexler
What was the solution to your issue? We have what appears to be an identical issue.

[andreidrexler]

Hi @karljwogoman ,

The solution was the one suggested by @Alpesh_Gohil.
Switched to client secret method and didn't get the error anymore.

[karljwogoman]

Thank you! We are working with our m365 admins to switch to using the client secret. Our connection has been on and off for quite some time. 

[karljwogoman]

After switching to the client secret, our connection to m365 no longer drops. Thanks for providing the solution to this.