azuread_conditional_access_policy: Authentication strength policies hard-coded values path #1602
+49
−1
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
sdx-jkataja
force-pushed
the
authentication-strength-policies-id
branch
from
ec84335 to
f98de92
Compare
manicminer
approved these changes
Jan 7, 2025
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.
Improve documentation to make the authentication strength policy better defined. Add a test case to authentication strength policy with hard-coded values, such as the Phishing resistant MFA policy. This patch does not change the ID handling introduced in #1499 and keeps backwards compatibility, but the add test will fail if the behavior changes again.
Fix #1547