Fix: AuthMethodsPolicyMigration for newer tenants #1567
Merged
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
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.
Tenants which are newly created have the policy migration 'completed' by default. On these tenants, the property policyMigrationState from graph endpoint /beta/policies/authenticationMethodsPolicy is always NULL. Even if you set policyMigrationState to migrationComplete with a PATCH request, the value will remain NULL. In the Entra portal for these tenants, the migration option is also not shown since they are already using the new authentication methods policy.
I have a few tenants where this is the case, causing the alerts and report to show incorrectly.
This PR updates the logic to treat null values as "migration complete" to align with Microsoft's behavior for newly created tenants.