This document contains Azure Naming Conventions used by Adafy.
We use Microsoft's recommended naming conventions.
Some of the resources have special naming conventions. Always check the guideline before applying name.
{customer}-{resource type}-{app name}-{environment}
Here are some examples:
contoso-app-portal-test
contoso-sqldb-users-prod
contoso-vnet-prod-westeu-001
The following tagging patterns are used:
Resources that contains GDPR related customer data, must be marked with gdpr tag.
Example: Key: GDPR, Value: GDPR/True
User who created (or owns) the resource, must be marked with Owner tag with the value of email address.
Example: Key: Owner, Value: xxx.yyy@adafy.com
Following table contains most common resources, their prefixes and examples. {###} = number starting from 001.
{Customer} = customer short name without spaces. For example contoso.
{App Name} = Application/project name without spaces.
{Environment} = dev,test,qa,stage or prod.
{Region} = westus, eastus2, westeurope, usgovia
| Resource Type | Prefix | Name |
|---|---|---|
| App Service (Web App) | app | {Customer}-app-{App Name}-{Environment}-{###} |
| App Service plan | plan- | {Customer}-plan-{App Name}-{Environment} |
| Azure SQL Database server | sql- | {Customer}-sql-{App Name}-{Environment} |
| Azure SQL database | sqldb- | {Customer}-sqldb-{Database Name}-{Environment} |
| Cosmos DB database | cosmos- | {Customer}-cosmos-{App Name}-{Environment} |
| Function app | func- | {Customer}-func-{App Name}-{Environment} |
| Event hub | evh- | {Customer}-evh-{App Name}-{Environment} |
| Resource group | rg- | {Customer}-rg-{App Name}-{Environment} |
| Service Bus | sb- | {Customer}-sb-{App Name}-{Environment} |
| Service Bus queue | sbq- | sbq-{query descriptor} |
| Service Bus topic | sbt- | sbt-{query descriptor} |
| Storage account (general use) | st- | {Customer}st{storage name}{###} |
| Virtual Machine | vm | {Customer}vm{App Name}{###} |
| Virtual network | vnet | {Customer}-vnet-{App Name}-{Environment} |