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
The azuread_synchronization_job_provision_on_demand resource should allow for propagation of the entra group being assigned to the enterprise application.
It should retry if the expected group has not yet propagated after being assigned.
Actual Behavior
Sometimes the azuread_synchronization_job_provision_on_demand resource will deploy prior to the entra group assignment to the enterprise application propagating, causing a failed provision.
Below log from the Audit Logs of the Enterprise App The Group 'TestGroup' will be skipped due to the following reasons: 1) This object is not assigned to the application. If you did not expect the object to be skipped, assign the object to the application or change your scoping filter to allow all users and groups to be in scope for provisioning.
Steps to Reproduce
terraform apply
The text was updated successfully, but these errors were encountered:
I think it would make more sense to fix azuread_app_role_assignment so that it waits for propagation to return success rather than retrying azuread_synchronization_job_provision_on_demand until it succeeds. I'm fairly new to using the AzureAD provider, and Azure in general, and was just bit by this because I expected that an assignment was propagated when it returned success. Took me some time to realize.
But either options works. We should at the very least update the documentation on azuread_app_role_assignment to add a notice about propagation.
Community Note
Terraform (and AzureAD Provider) Version
Affected Resource(s)
azuread_synchronization_job_provision_on_demand
Terraform Configuration Files
Expected Behavior
The azuread_synchronization_job_provision_on_demand resource should allow for propagation of the entra group being assigned to the enterprise application.
It should retry if the expected group has not yet propagated after being assigned.
Actual Behavior
Sometimes the azuread_synchronization_job_provision_on_demand resource will deploy prior to the entra group assignment to the enterprise application propagating, causing a failed provision.
Below log from the Audit Logs of the Enterprise App
The Group 'TestGroup' will be skipped due to the following reasons: 1) This object is not assigned to the application. If you did not expect the object to be skipped, assign the object to the application or change your scoping filter to allow all users and groups to be in scope for provisioning.
Steps to Reproduce
terraform apply
The text was updated successfully, but these errors were encountered: