Issue Encountered During Windows 365 Defender Onboarding - AADSTS50131 Error

Riadh Zehani 125 Reputation points
2023-09-19T22:23:46.5066667+00:00

While in the process of onboarding Windows 365 Defender and connecting it to Sentinel, we have encountered an issue that is currently preventing us from completing the installation successfully.

The exact nature of the issue is not clear to us, and we require assistance in resolving it promptly.

We have attempted a workaround from the following link (https://www.graber.cloud/en/aadsts50131-device-not-required-state/#:~:text=the%20AADSTS50131%20error-,The%20error%20%22AADSTS50131%3A%20Device%20is%20not%20in%20required%20device%20state,developments%20that%20address%20the%20APIs), but unfortunately, it did not resolve the problem.

Could you please provide guidance or steps on how to diagnose and rectify this problem?2023-09-19 22_53_01-Boîte de réception - Riadh.Zehani@tn.ey.com - Outlook

Microsoft Sentinel
Microsoft Sentinel
A scalable, cloud-native solution for security information event management and security orchestration automated response. Previously known as Azure Sentinel.
1,135 questions
0 comments No comments
{count} votes

Accepted answer
  1. 2023-09-21T06:48:15.9633333+00:00

    Hello @Riadh Zehani , the AADSTS50131 error while connecting Microsoft 365 Defender to Sentinel is caused by classic conditional access policies created by the Intune integration. Re-attempt the connection this time from an Azure AD registered device.

    Let us know if you need additional assistance. If the answer was helpful, please accept it and rate it so that others facing a similar issue can easily find a solution.

    0 comments No comments

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.