Check to see if legacy authentication methods are blocked. This is typically done by security defaults or a conditional access policy.
Solution Baseline - Block legacy auth
2
This makes a lot of sense from a best-practice perspective.
From an implementation perspective, are you thinking we'd have an option to set an override policy and disable the offending setting/policy or are you just wanting a notification about the “drift”?
Ideally, if there was a way from the solution baseline to enforce this, that would be what we are really looking for. At a minimum a check to see if these were enabled/disabled and ability to accept the drift or just a report-only action.
We appreciate your feature request—community input is essential to our ongoing development.
Next steps:
• We will review your suggestion and update its status during the evaluation process.
• If further clarification is needed, we'll contact you via comments.
We also encourage others to contribute through feedback and voting.
Next steps:
• We will review your suggestion and update its status during the evaluation process.
• If further clarification is needed, we'll contact you via comments.
We also encourage others to contribute through feedback and voting.
Please sign in to leave a comment.
Comments (3 comments)