如何增加Azure中的可分配安全组的角色
我要去这个链接
在说的
情况azure。问题是，大型组织（有500多个组 - 我确定他们必须考虑不同的部门/塔/组/应用程序）如何管理此限制？
创建组/访问包时必须遵循哪些最佳实践或架构决定？考虑限制。
谢谢。
I was going via this Link
where it says "A maximum of 500 role-assignable groups can be created in a single Azure AD organization (tenant)."
This looks like a big limitation in Azure. The question is, how are big organization ( having more than 500 groups - I'm sure they must have considering different departments/towers/groups/applicaions) manages this limitations?
What are the best practice or architecture decission must be followed while creating groups/access package? considering limitation.
Thanks.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
根据“ nofollow noreferrer”> 对角色分配组的限制 ，正如您已经提到的那样，
最多可以在单个Azure AD组织（租户）中创建500个可互动的组。首先，角色可分配组的目的是防止滥用分配许可的潜在违规，它只能由全球管理员角色或PIM角色（特权身份管理）创建。由于角色分配安全组的目的是分配角色和强调有关部署Azure Resources或同样场景的要求的权限，因此，可分配的安全组具有很高的价值关注的角色，大多数少于其他组类型。
对于特定订阅，无法更改该限制。通常，较小的机构或组织使用单人租户，这限制了这些情况。
大多数较大的机构（例如拥有超过100万用户）使用 多人租户Architechture ，以避免使用这种服务的房客和配额限制/限制服务。
与区域案例相遇的多租户体系结构，以使大型组织变得容易。
这种情况变得更大的机构可以轻松管理限制。
参考：
According to restriction for role assignable groups, and as you already mentioned that -
A maximum of 500 role-assignable groups can be created in a single Azure AD organization (tenant).First of all, The purpose of role assignable groups is to prevent potential breaches of misuse of assigned permission and it can be created only by Global administrator role or PIM role (privileged identity management). Since the purpose of role assignable security group is to assign role and underline permissions specific to the requirement regarding the deployment of azure resources or likewise scenarios, The role assignable security groups being of high value concern are mostly number few than the other group type.
That limit cannot be changed for particular subscription . Usually smaller institutions or organizations use single tenant and that limit suffices those cases.
Most of the larger institutions(say which have over 1 million users) use multi tenant architechture, to avoid such kind of tenant and quota limitations/ restrictions on services.
Multi-tenant architecture is approached for the regional cases to make easy for larger organisation.
This condition is made bigger institution to manage limitation easily.
Reference : github issue