Continuing on from looking at tools to manage Azure, these are quick notes on the Azure deployment model, how resources and resource groups interact, deployment methodologies and how templates and policies work.
Deployment Model
Core concepts
- Resources
The individual building blocks for creating solutions. Contained in one and only one resource group - Resource Groups
Bounding containers of resources. Useful for lifecycle, billing or reporting boundaries around resources. - Role Based Access Control (RBAC)
Provides granular permissions to subscriptions, resource groups and resources to users and service principals within the Active Directry tenant. Can be applied to groups or individual identities. - Tags
Custom names that can be applied against subscriptions, resource groups or resources. Useful for scripting, aggregating billing, reporting - Templates
JSON structured documents that deploy a a related set of resources for a whole or part of a solution. Can be parameterized. They declare and end state : Make it so type deployment. - Policies
JSON structured documents that are assigned to subsciptions that can affect a deployment. Can implement facets of governance or policies such as ensuring tags, limiting infrastructure or ensuring geographic compliance. - Locks
Read only or Delete, used primarily to prevent accidental modification or deletion of resources.
Moving resources
Resources can be moved between groups and subscriptions
- Cannot change a resources location
- Both groups are locked during the move process
- Moving subscriptions require the same AD tenant
- All dependencies must be moved together
Deployment methodologies
- Imperative
- Declarative
ARM Templates
{
"$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json#",
"contentVersion": "",
"parameters": { },
"variables": { },
"resources": [ ],
"outputs": { }
}
Template functions
- Numeric
- String
- Array
- Deployment values
- Resources
Functions, parameters and variables can be combined to produce powerful reusable templates
Note - the diffence between classic deployments and ARM deployments is the existence of the cloud service container in classic. All resources are bound to the cloud service and resource group allocation is handled by the platform.
Peace, Abundance, and Liberty Network (PALnet) Discord Channel. It's a completely public and open space to all members of the Steemit community who voluntarily choose to be there.Congratulations! This post has been upvoted from the communal account, @minnowsupport, by Piquet from the Minnow Support Project. It's a witness project run by aggroed, ausbitbank, teamsteem, theprophet0, someguy123, neoxian, followbtcnews, and netuoso. The goal is to help Steemit grow by supporting Minnows. Please find us at the
If you would like to delegate to the Minnow Support Project you can do so by clicking on the following links: 50SP, 100SP, 250SP, 500SP, 1000SP, 5000SP.
Be sure to leave at least 50SP undelegated on your account.