-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Update AD-FS-Prompt-Login.md #8021
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
The right command to use is Update-MgDomainFederationConfiguration not New-MgDomainFederationConfiguration. the latter creates a federation domain configuration, but in this context, this is already in existence. Therefore, an error gets returned "New-MgDomainFederationConfiguration : Domain already has Federation Configuration set." PreferredAuthenticationProtocol - should not be changed FederatedIdpMfaBehavior - is not always populated and shouldn't be changed in this context.
@rodiera : Thanks for your contribution! The author(s) have been notified to review your proposed change. |
Learn Build status updates of commit e97ad35: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
@robinharwood, @Xelu86 #label:"aq-pr-triaged" |
Any updates on this? The current guidance in this document is wrong. Neither FederatedIdpMfaBehavior or PreferredAuthenticationProtocol need to be included here to update PromptLoginBehavior. Furthermore, customers are unnecessarily updating FederatedIdpMfaBehavior and want to revert however there is no way to revert once the property has been updated. So, we are getting pushback on CSS cases when customer follow this guidance and finds out they cannot null FederatedIdpMfaBehavior. The correct command is. |
@robinharwood @Xelu86 #label:"aq-pr-triaged" |
The right command to use is Update-MgDomainFederationConfiguration not New-MgDomainFederationConfiguration. the latter creates a federation domain configuration, but in this context, this is already in existence. Therefore, an error gets returned "New-MgDomainFederationConfiguration : Domain already has Federation Configuration set."
PreferredAuthenticationProtocol - should not be changed FederatedIdpMfaBehavior - is not always populated and shouldn't be changed in this context.