You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Updating or creating a CA policy should work also by specificing not all the parameters.
E.g disabling an existing policy by just specifing displayname, state (and the other common params like tenantid,..) throws a bad request by the way the conditions are constructed in the code.
Updating with graph works with just providing the parameters that should change. Link to update CA policy
For creating though, there are some minimum params required.
The minimum according to graph api docs is an appliction rule, an user rule and grant/session control --> link
Microsoft 365 DSC Version
1.23.1018.1
Which workloads are affected
Azure Active Directory
The DSC configuration
AADConditionalAccessPolicy "Microsoft-managed: Multifactor authentication for admins accessing Microsoft Admin Portals"
{
ApplicationId =$ConfigurationData.NonNodeData.ApplicationId;
CertificateThumbprint =$ConfigurationData.NonNodeData.CertificateThumbprint;
DisplayName ="Microsoft-managed: Multifactor authentication for admins accessing Microsoft Admin Portals";
Ensure ="Present";
State ="disabled";
TenantId =$OrganizationName;
}
Description of the issue
Updating or creating a CA policy should work also by specificing not all the parameters.
E.g disabling an existing policy by just specifing displayname, state (and the other common params like tenantid,..) throws a bad request by the way the conditions are constructed in the code.
Updating with graph works with just providing the parameters that should change.
Link to update CA policy
For creating though, there are some minimum params required.
The minimum according to graph api docs is an appliction rule, an user rule and grant/session control --> link
Microsoft 365 DSC Version
1.23.1018.1
Which workloads are affected
Azure Active Directory
The DSC configuration
Verbose logs showing the problem
Environment Information + PowerShell Version
No response
The text was updated successfully, but these errors were encountered: