Adjusting IWA warning message #406
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Haard30
reviewed
Sep 12, 2024
shalinikhare27
previously approved these changes
Sep 12, 2024
Haard30
approved these changes
Sep 12, 2024
shalinikhare27
approved these changes
Sep 12, 2024
mvanchaa
approved these changes
Sep 12, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The IWA warning message that's printed out seems to indicate that folks can bypass 2FA/MFA challenges by using Windows Hello or a smart card. However, I believe this may no longer be true, as multiple folks have indicated that they are indeed using those mechanisms for signing in, but are still being presented with the same error. I am able to confirm this myself as well, where even when signing in with Windows Hello, I get the same MFA warning.
With the shift in the determination of when to present MFA challenges, as well as the hardening around MFA within MSFT, it is becoming clear that the guidelines around MFA challenges are ever-changing. As such, I believe providing suggestions around how to bypass these challenges will do more harm than good.
As such, this PR removes this part of the warning message.