So picture the scenario… You’re working in your Microsoft Azure subscription and you have a Resource Group that you want to delete but it still contains a number of resources. You log in to the Azure portal and find that you can only delete the Resource Group once all the resources within that group have been moved or deleted.
When you have a large number of resources, this can be time consuming and monotonous.
There are a couple of easy ways you can speed up this process by using the following tools:
- Azure PowerShell Module
- Azure Resource Explorer
This article shows you how to use the above methods to quickly delete your Resource Groups and all associated resources.
Continue reading How to: Quickly move or delete all resources in an Azure Resource Group
One of the main things I’m looking to learn at the moment is how best to manage my Azure environment. The first rules I’ve set myself are as follows:
- Use Azure Resource Manager where possible, as Azure Service Management is being deprecated by Microsoft
- Think carefully about grouping Azure resources into Resource Groups based on their management life-cycle – there’s no hard and fast rule around creating Resource Groups, but try to strike a balance between granularity and complexity
- Define and create all Azure resources from Azure Resource Manager Templates (and store these templates outside of Azure) to make the creation, recreation and modification of resources simple
- Treat Azure management, deployment and administration as a DevOps process to gain operational efficiency
- Version control all changes to your Azure deployment so you can rebuild your environment if the worst was to happen
Now I’m no developer and a lot of this stuff is fairly alien to me, but I’ve just started using Visual Studio 2015 RC Community integrated with GitHub to develop and my Azure Resource Manager Templates, and I have to say it was a lot simpler than I expected. I’m going to write a separate post covering this as it’s a topic in itself, so let’s get on and discuss the biggest challenge I’ve faced so far… Understanding the Azure Resource Manager Templates and what I should put in them to deploy my resources.
Continue reading Introducing Azure Resource Manager Templates and Azure Resource Explorer (Preview)
Before starting your journey into Azure IaaS, like in a physical world, one of the main topics which should be understood is networking. This is for many reasons, but most importantly:
- Understanding the basic topology of Azure networks enables correct placement of Virtual Machine workloads
- Understanding how deploying networks in ASM vs. ARM can affect management and functionality
- Understanding the security options within Azure helps you prevent data loss
- Understanding connectivity options helps you to optimise end-user experience
- Understanding how 3rd party appliances can enhance network features and security helps you meet regulatory and governance requirements
While it may not be immediately obvious, some decisions around networking can have a deep and lasting impact on your deployment such as being unable to move a Virtual Machine to a new network without deleting it and re-creating. As your Cloud deployment grows in size and complexity, such problems can quickly escalate and become near impossible to resolve without significant impact to your service.
This first post of the series will focus primarily on the basic topology of the Azure networks, look at the differences between networks in ASM vs. ARM, and touch on some of the core features available in Azure for securing your workloads and data.
Continue reading Microsoft Azure IaaS Networking Introduction (Part 1)
Related to my previous post Start your Azure experience with Azure Resource Manager, the well known Keith Mayer has created an excellent working example of putting ARM to use provisioning the following sample IaaS deployment:
18 Steps for End-to-End IaaS Provisioning in the Cloud with Azure Resource Manager (ARM), PowerShell and Desired State Configuration (DSC)
It’s exciting to see this technology maturing and how we can use this to build our future services.
Continue reading Azure Resource Manager (ARM) Sample Deployment
I’m currently designing an Azure environment for a client and was wondering why Microsoft have provided two different management portals. While both contain a large amount of common functionality, each do so in a different manner and some functionality is only available through one or the other.
Following a meeting with Microsoft Professional Services earlier this month (May 2015), I found out why.
Azure Service Management (ASM)
Microsoft Azure started off life with the (1st Generation) Azure Management Site:
This site uses the original Rest API, and provides all 1st Generation functionality for managing Windows Azure resources.
Continue reading Start your Azure experience with Azure Resource Manager
Mono Consultancy is a forward thinking consultancy, delivering high quality services to enterprise organisations who value high quality solutions, excellent customer service and successful project delivery.
We specialise in data centre design, virtualisation and Cloud computing, but are also passionate about storage and networking.
This blog is a space to discuss the technologies we’re working with and describe how we overcome some of the challenges faced in the real world of Enterprise IT.