Azure
Azure hierarchy
Management groups help you manage access, policy, and compliance for multiple subscriptions. All subscriptions in a management group automatically inherit the conditions applied to the management group.
Subscriptions logically associate user accounts with the resources they create. Each subscription has limits or quotas on the amount of resources it can create and use. Organizations can use subscriptions to manage costs and the resources created by users, teams, or projects.
Resource groups are logical containers where you can deploy and manage Azure resources like web apps, databases, and storage accounts.
Resources are instances of services that you can create, like virtual machines, storage, or SQL databases.
Azure Price Calculator
You can use this calculator to estimate hourly or monthly costs using Azure before create resources.
https://azure.microsoft.com/en-us/pricing/calculator/
Civil Aviation naming convention
Maintaining a naming standard is important in many ways and we are trying to create these standards for Civav resources in Azure. The default so far is:
civav-env-azureabreviationresource-nameappEng-nameappFra
Examples:
civav-dev-kv-napa-snapa
civav-dev-web-sfoc-coas
For the Recommended abbreviations for Azure resource types you can find more information here:
We have other recommendations for the MAACE team regarding abbreviation and you can find this information here:
Azure Resource Group
To create a new Resource Group, you need to use the TC3OE portal https://tc3oe.tc.gc.ca/ssp-pls/
The standard nomenclature you can find in MAACE-Solution and Data Architecture Services is described above.
References
Azure Icons > http://code.benco.io/icon-collection/azure-icons/