Fix AuthenticationFlows in Conditional Access Policy #4970
Merged
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.
Pull Request (PR) description
This Pull Request addresses an issue where the
AuthenticationFlows
property of a conditional access policy changed in Graph, thus leading to an incorrect provisioning ofTransferMethods
in theAADConditionalAccessPolicy
resource.The new definition of
AuthenticationFlows
is the following:$null
if no transfer method is specified@{ transferMethods = '<value>' }
if a transfer method is specifiedSince one or two values can be used, separated by a comma, an additional check in
Test-TargetResource
was introduced, which checkes that if two values are specified, they can be written in any order.To preserve backwards compatibility since
TransferMethods
doesn't have to be specified (while in newer exports it is always done by default), the property is only checked inTest-TargetResource
if it is contained inPSBoundParameters
. Otherwise, it will be ignored.This Pull Request (PR) fixes the following issues