Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AADEntitlementManagementRoleAssignment can fail due to incorrect scope and resulting roledefinitionId #5620

Open
mlhickey opened this issue Jan 11, 2025 · 0 comments

Comments

@mlhickey
Copy link
Contributor

Description of the issue

Currently, calling Get-MgBetaRoleManagementEntitlementManagementRoleAssignment can result in return of roles outside of intended scope which will then fail when trying to resolve with
Get-MgBetaRoleManagementEntitlementManagementRoleDefinition -UnifiedRoleDefinitionId $config.RoleDefinitionId
Recommendation is to use -ExpandProperty RoleDefinition on the initial call with prevents the error and reduces additional calls to retrieve definition data

Microsoft 365 DSC Version

DEV/1.25.108.1

Which workloads are affected

Azure Active Directory (Entra ID)

The DSC configuration

Verbose logs showing the problem

Environment Information + PowerShell Version

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant