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
I use AADRoleEligibilityScheduleRequest to set eligible role assignment, it works perfectly but as I use it in a scheduled Pipeline to ensure the value is always compliant with our repository, the configuration is applied multiple time per week.
When it run, M365DSC will always remove and re-add the assignment even if the values have not changed:
This action is a problem because people who have already activated their role in PIM, will lose their access and will have to reactivate their roles. So people have activated their role, and all of a sudden, they will no longer be able to perform administrative actions because the role is no longer present.
I would like to be able to launch my pipeline multiple times with the same configuration without the assignment being changed (if the value is identical). So there must be a problem of detection or comparison between the desired value and the value retrieved in Entra ID.
Description of the issue
I use AADRoleEligibilityScheduleRequest to set eligible role assignment, it works perfectly but as I use it in a scheduled Pipeline to ensure the value is always compliant with our repository, the configuration is applied multiple time per week.
When it run, M365DSC will always remove and re-add the assignment even if the values have not changed:
This action is a problem because people who have already activated their role in PIM, will lose their access and will have to reactivate their roles. So people have activated their role, and all of a sudden, they will no longer be able to perform administrative actions because the role is no longer present.
I would like to be able to launch my pipeline multiple times with the same configuration without the assignment being changed (if the value is identical). So there must be a problem of detection or comparison between the desired value and the value retrieved in Entra ID.
Can you please have a look ?
Thank you !
Microsoft 365 DSC Version
1.25.129.1
Which workloads are affected
Azure Active Directory (Entra ID)
The DSC configuration
Verbose logs showing the problem
Environment Information + PowerShell Version
The text was updated successfully, but these errors were encountered: