Clarifying the MFA registration campaign doc #1625
Open
Conversation
This file contains hidden or 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
|
@JoeAtMsft : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
prmerger-automator
bot
added
authentication/subsvc
Change sent to author
entra-id/svc
labels
|
Learn Build status updates of commit 2eddfd6: ✅ Validation status: passed
For more details, please refer to the build report. |
|
Can you review the proposed changes? Important: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
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.
We recently tried to implement this MFA campaign at a customer and struggled with the execution. We thought the MFA campaign would help onboard ALL users to register an initial MFA method, but after many hours, we realized the registration campaign was only designed to step-up users from weaker MFA methods.
We thought adding that wording to the doc would save other customers from time and frustration.
Here is a reddit article that demonstrates some of the frustrations.
https://www.reddit.com/r/AZURE/comments/1j0cmgu/entra_registration_campaign_moving_too_slowly/