AzureAD Role Delegation to Groups
Currently in AzureAD msolroles can only be assigned to users and servicePrincipals using the add-msolRoleMember cmdlet. Groups cannot be a msol-roleMember - although the add-msolroleMember cmdlets' RoleMemberType Parameter can be set to Group. But we always get an exception which says that this value is invalid....
Usually we delegate access to resources using ActiveDirectory Groups instead of users, which makes the Management much easier. To achieve a Role Delegation to Groups we have to deploy a Powershell that synchronizes Group-Members with Role-Members of a specific role. This is a valid Workaround but a nasty one compared to a direct delegation to AzureAD Groups.
Pirmin Felber
shared this idea
Just wanted to post another update that this is a high priority, but we do not have any details to announce yet.
Cheers,
/Stuart and Vince
32 comments
-
Anonymous
commented
Do you have any news about this feature of support of AAD security groups in a AAD Roles ?
-
Anonymous
commented
Would like an update on this.
-
Todd Johnson
commented
It's been ~7 months since last update. MS, can you provide another update please?
-
Christian Wiese
commented
Agree with the others. Not having this feature really goes against RBAC fundamentals and increases management overheads for our IT department.
Microsoft please resolve asap.
-
JasonG
commented
is a reference item for the planned work available so customers can look for updates and status, if not is this possible?
-
Lamb, Jeff
commented
Any updates?
-
Andrew Thompson
commented
bump... same as everyone else here.
-
Ben Gliddon
commented
Agree with the others. Not having this feature really goes against RBAC fundamentals and increases management overheads for our IT department.
Microsoft please resolve asap.
-
Cyrille Belfort
commented
This is even more needed than RBAC implementation for company doing scoped outsourcing
-
Daniel Frei
commented
Really surprised this isn't already a thing yet. Any updates?
-
Martin Stolzenberg
commented
This is a much needed feature please implement it as soon as possible...
-
MikeN
commented
I just wanted to provide feedback that this is very much a needed feature.
It seems like a pretty bad engineering oversight when the service was first designed.Best practices 101 says that you should never assign permissions to individual users, you assign permissions to groups and add users to the groups.
-
Simon Butler
commented
Any updates on this high priority update?
-
Anonymous
commented
Much needed feature!
-
Anonymous
commented
Any update on this request?
-
Anonymous
commented
Please make this very necessary change to your roles. It took our entire IT management team by surprise that you could not assign Groups to Azure AD Roles.
-
Chris Allen
commented
I have a customer who is running into this limitation and it is hampering their ability to manage what is a large group of user through RBAC. The option of Role Assignments does not meet their need. Do we have any kind of ETA on this change going in?
-
RE: "High Priority? Request has been posted 2,5 years ago?! Come on Microsoft, this is ridiculous"
Ugh, you are right to be frustrated with us here. I'm not happy with the pace of progress on assigning groups as members of roles, either. It is a high priority for us, but it's proving more difficult for reasons that aren't obvious.
I appreciate everyone who has taken the time to provide feedback. It is valuable, and we take it into account in our planning and prioritization process.
Vince
-
RE: "High Priority? Request has been posted 2,5 years ago?! Come on Microsoft, this is ridiculous"
Ugh, you are right to be frustrated with us here. I'm not happy with the pace of progress on assigning groups as members of roles, either. It is a high priority for us, but it's proving more difficult for reasons that aren't obvious.
I appreciate everyone who has taken the time to provide feedback. It is valuable, and we take it into account in our planning and prioritization process.
Vince
-
Anonymous
commented
High Priority? Request has been posted 2,5 years ago?! Come on Microsoft, this is ridiculous.....