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
Copy file name to clipboardExpand all lines: articles/operator-service-manager/best-practices-onboard-deploy.md
+44-1Lines changed: 44 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: Basic Concepts for Azure Operator Service Manager
3
3
description: Understand Azure Operator Service Manager basic concepts behind onboarding and deploying a network function.
4
4
author: msftadam
5
5
ms.author: adamdor
6
-
ms.date: 10/06/2025
6
+
ms.date: 03/09/2026
7
7
ms.topic: best-practice
8
8
ms.service: azure-operator-service-manager
9
9
---
@@ -202,3 +202,46 @@ As the first step toward cleaning up an onboarded environment, delete publisher
202
202
> Be sure to delete the SNS before you delete the NFDV.
203
203
204
204
Azure Operator Service Manager doesn't delete namespaces as part of any deletion operation. As such, after all resources are deleted, some artifacts might remain on the cluster. To remove any remaining artifacts, you should delete any workload namespaces created on the cluster. Including the namespace deletion operation as part of the workflow pipeline is a recommendation to automate the action.
205
+
206
+
## Azure global service limits and constraints
207
+
208
+
Azure enforces certain global service limits across all Azure services. The following is a curated list of those limits which should be considereed when onboarding, designing or operating workloads using Azure Operator Service Manager.
209
+
210
+
### ARM template limits
211
+
| Value | Limit |
212
+
|-----------|-------|
213
+
|Parameters |256 |
214
+
|Variables| 256 |
215
+
|Resources (including copy count)| 800 |
216
+
|Outputs| 64 |
217
+
|Template expression| 24,576 chars |
218
+
|Resources in exported templates| 200 |
219
+
|Template size| 4 MB |
220
+
|Resource definition size| 1 MB |
221
+
|Parameter file size| 4 MB |
222
+
223
+
### Azure RBAC limits
224
+
|Resource |Limit|
225
+
|---------|-----|
226
+
|Number of Azure role assignments per Azure subscription| 4,000|
227
+
|Number of Azure role assignments per management group| 500|
228
+
|Size of description for Azure role assignments Recommended maximum| 512 chars|
229
+
|Size of condition for Azure role assignments| 8 KB|
230
+
|Number of Azure custom roles per tenant| 5,000|
231
+
|Number of Azure custom roles per tenant (21Vianet)| 2,000|
232
+
|Size of role name for Azure custom roles Recommended maximum| 256 chars|
233
+
|Size of description for Azure custom roles Recommended maximum| 512 chars|
234
+
|Size of an Azure custom role definition| 1 MB|
235
+
|Number of assignable scopes for Azure custom roles| 2,000|
236
+
|Number of system-managed deny assignments per Azure subscription| 2,000|
237
+
238
+
### Other limits
239
+
|Resource |Limit|
240
+
|---------|-----|
241
+
|Maximum duration of system-assigned scope token (OBO) | 4h 30m no refresh|
242
+
|Maximum duration of user assigned managed identity (UAMI) | 24h + refresh|
243
+
|VNF timeout|24h|
244
+
|RPAAS Delete timeout|2h 30m|
245
+
|DTF Orchestration timeout| 7d |
246
+
247
+
For a comprehensive list, see the following article: [Azure subscription and service limits, quotas, and constraints](/azure/azure-resource-manager/management/azure-subscription-service-limits).
0 commit comments