From cb901c3a3d10109b043638fc5ab52b054e7cd0e2 Mon Sep 17 00:00:00 2001 From: Derek Martin Date: Wed, 7 Aug 2019 10:03:31 -0500 Subject: [PATCH] Update naming-conventions.md Closes https://github.com/MicrosoftDocs/architecture-center/issues/1688 --- docs/best-practices/naming-conventions.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/best-practices/naming-conventions.md b/docs/best-practices/naming-conventions.md index ee93846d227..d6b15d904e0 100644 --- a/docs/best-practices/naming-conventions.md +++ b/docs/best-practices/naming-conventions.md @@ -43,6 +43,8 @@ A recommended pattern for naming subscriptions is: | Contoso |IT |InternalApps |Production |Contoso IT InternalApps Production | | Contoso |IT |InternalApps |Dev |Contoso IT InternalApps Dev | +Like all Azure services, there are limits placed on the value of Subscription Names. The length must be 1-64 characters and they must be alphanumeric and cannot contain these characters: `<` `>` `;` `|`. + For more information on how to organize subscriptions for larger enterprises, see [Azure enterprise scaffold - prescriptive subscription governance](/azure/architecture/cloud-adoption/appendix/azure-scaffold). ## Use affixes to avoid ambiguity