Recently I’ve published blog post Subscription Level Deployment Schema. When I published it I was not aware that not so many people know what the schemas are used and needed for. With this blog post I want to address this.
Not so long ago in Azure we only had resource group level deployment but a couple of months ago subscription level deployments were implemented. On resource group level we deploy resources like Azure VMs, Service Apps, Azure SQL databases, etc and on subscription level we deploy policy definitions and assignments, resource groups (yes they are resource as well), custom RBAC roles, etc. Because of that it the schema in the ARM templates for resource group and subscription level deployments is different. This is something I haven’t thought about it around the excitement of this new deployment method but my good friend Kristian Nese tipped me. So here are the schemas you should use depending on your deployment:
Azure Stack is extension of Azure and as such I am dealing with it as well. You may end up in a situation where you’ve created User Subscriptions in Azure Stack and after some time you want to delete them. Before deleting them you will need first to delete all the resources inside those subscriptions but the accounts of the owners of these subscriptions are no longer available or the do not want to cooperate. In such cases you can actually change the owners by using PowerShell. For example you can assign your Azure Stack Operator account as owner, login to the subscriptions with it via the User Portal and delete the resources before deleting the subscriptions.
Continue reading “Change Owner of Azure Stack User Subscription”
First I would like to note that the solution below is not official guide from Microsoft and you should use it at your own risk.’’ Continue reading “Migrating VM Role from One Subscription to Another in Azure Pack”