Skip to content

Commit e0e2c02

Browse files
committed
Update limit increase text
1 parent 0e07a45 commit e0e2c02

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/role-based-access-control/troubleshooting.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.service: role-based-access-control
99
ms.workload: identity
1010
ms.tgt_pltfrm: na
1111
ms.topic: troubleshooting
12-
ms.date: 01/28/2022
12+
ms.date: 02/18/2022
1313
ms.author: rolyon
1414
ms.custom: seohack1, devx-track-azurecli, devx-track-azurepowershell
1515
---
@@ -22,7 +22,7 @@ This article answers some common questions about Azure role-based access control
2222
Azure supports up to **2000** role assignments per subscription. This limit includes role assignments at the subscription, resource group, and resource scopes, but not at the management group scope. If you get the error message "No more role assignments can be created (code: RoleAssignmentLimitExceeded)" when you try to assign a role, try to reduce the number of role assignments in the subscription.
2323

2424
> [!NOTE]
25-
> Starting November 2021, the role assignments limit for a subscription is being increased from **2000** to **4000** over the next several months. Subscriptions that are near the limit will be prioritized first. The limit for the remaining subscriptions will be increased over time. Once the limit increase process is started for a subscription, it still takes multiple weeks to increase the limit.
25+
> Starting November 2021, the role assignments limit for all Azure subscriptions is being automatically increased from **2000** to **4000**. There is no action that you need to take for your subscription. The limit increase will take several months.
2626
2727
If you are getting close to this limit, here are some ways that you can reduce the number of role assignments:
2828

0 commit comments

Comments
 (0)