- Preparation is everything
- Setting up Azure governance
- Deployment toolkit
- Identity toolkit
- Security toolkit
- Cost management
- Summary
- Considering the cloud? Think of these 7 things first
- How to create a successful cloud adoption plan? The 4 principles
- 3 challenges companies will face in the rise of PaaS solutions
- How to mitigate the challenges of cloud migration?
- Why do you need a cloud governance model and how to get started?
- How to implement Azure governance? A practical toolkit
- What you need to know about identity and access governance
- How can automation help out with cloud governance?
- See how to master access governance in 5 easy steps
- How to support cloud governance with Azure DevOps: A practical example
Last time, I told you WHAT is cloud governance, and WHY you need it at your organization. Today, I will show you HOW to implement it.
- How to implement an Azure governance model?
- What tools are available for it?
This post has originally been published on Apr 11, 2019. It has since been split into 2 parts and updated for better readability. You can find part 1 here.
In the previous article, we talked about the basics of a cloud governance framework. To recap: it is a way to help you manage your cloud more quickly, consistently, in a controlled way. It has to cover the business aspect of your operations, include the right people, and relevant technology.
Some of the final aspect we’ll cover today, as we finally arrive at the How part of our model. But before jumping to the tools, a few words of caution.
Preparation is everything
Do not aim to address all the aspects and concerns in one big shot (OBS for the acronym game). This is not going to work. When you start this journey, you might not even know what you are going to deploy.
Start with the Minimal Viable Product (or Policies, MVP) in place. First, set up a governance framework for a single type of your subscription (e.g. development environments) with a minimal set of policies.
For instance:
- All assets must be grouped and tagged
- All assets deployed must use the same deployment model
- Each resource needs to be allocated to a cost center.
Once that’s in place, then you can build around it.
Iterations
After building and deploying your MVP, set up a process for incremental growth. Review and iterate your governance model in sprints. Base it on the following:
- New resource types being added/deployed
- The growth of your environment/cloud usage
- New policy elements defined based on your business objectives.
Set up triggers for your policy updates. For example: every time your cloud consumption grows by 20%, you need to review our policies on cost management. Or every time you deploy a new service, you need to review security and auditing controls applied within your framework.
Monitor those triggers! In the beginning, it might be a manual process. For instance, your Cloud Strategy Team needs to review every prepared deployment. They need to identify if it includes new types of resources, and that all deployments are prepared in the right way.
Friendly advice: Automation is cool and needed. Still, don’t aim to automate everything right from the start. Most certainly, don’t delay your first iterations of cloud governance just because you need to automate them!
Would you rather work with a document? Scroll down to find the complete guide available for download!
Setting up Azure governance
Now, let’s take a look at the practical solutions. They include plenty of tools to help you set up governance for your Azure services.
Subscriptions
First of all, accept the fact that you will have multiple subscriptions and environments.
Arrange your subscriptions using Management Groups. This is how you can group them within a single management unit.
As a design strategy, create Management Groups for your environments such as development and/or production.
Within Management Groups, arrange subscriptions based on your organizational approach. These may include the following:
- Departments
- Cost centers
- Application categorization (e.g. critical, non-critical, vendor-managed).
Some organizations use this to simplify billing: one subscription per billing unit.
Within subscriptions, create resource groups per app or workload.
Policies
Define your business goals, risk model, and constraints. Put them all in writing as policies.
Your objective here is to set a foundation for clear and faster adoption of the cloud. Since this might be an early stage of your journey, some things might go wrong (become risks). These may include:
- Team awareness of the cloud and development skills
- You don’t know the exact cost structure of resource usage
- The security model is new to you. You don’t know if it will be applied consistently across all resources and deployments
- Many people and teams will share the environment. They might apply conflicting standards and ways of doing things
- Wrong use of identities might lead to security risks and leakage of data
- Data deployed to the cloud might be against your compliance policies.
Based on those goals and risks, you can identify policies for your environment, e.g.:
Deployment
- All resources need to be deployed with the appropriate tagging and within a resource structure
- All resources must follow a defined deployment model.
Identity
- Only organizational accounts from Azure AD and partners through B2B mechanisms are allowed within the environment
- RBAC model to apply across all resources with specific roles (like a company-wide auditor). All elevated privileges are assigned and mapped to groups only.
Security
- Connectivity between the cloud and the on-prem network goes through a dedicated subscription and its networking setup
- All data needs to be encrypted with the available encryption for services
- Usage of credentials is limited with Managed Service Identity. Additionally, all credentials are stored within the Key Vault.
Cost management
- All resources need to be placed within the management structure
- All resources need to be tagged for the cost center assignment.
This is only the initial set. The next iteration needs to be more in-depth and detailed.
Those policies will be mapped to specific Azure tools. Their implementation will then be based on particular categories. You may also onboard third-party tools and external services. They may help you apply the policies in the environment.
from our brochure
Deployment toolkit
Azure offers several tools to help you implement your policies during the deployment stage. You can use Azure Resources Model (ARM) for all deployments. This way you will not allow manual deployments at all.
Azure Resources Graph extends the ARM Model. It lets you identify resources and check their compliance with your policies.
To enforce your policies and resource compliance, you have another powerful service: Azure Policies. You can apply policies to identity compliant or non-compliant resources. Or, verify compliance at the time of creation and verify specific VMs and services settings.
The best way to ensure that things are configured correctly is to utilize templates in the form of Azure Blueprints. They enable and orchestrate the deployment of:
- Role assignments and RBAC model
- ARM template deployments
- Resource groups
and through this many other services and elements.
You can find a quick introduction to Azure Blueprints in the video below.
An overview of Azure Blueprints – Microsoft Channel 9 Video
More on the entire stack of tools for deployment toolkit in Azure stack and where to apply them is here.
Identity toolkit
We covered this extensively on our blog and elsewhere. Establish your co-existence between on-premises and cloud environments and the choice of authentication methods.
Here you will find a quick comparison for decision support and information.
Still, there are a few important notes to add:
- Use MFA wherever possible and make sure that your admin accounts all use them. When it is available (it is currently in public preview) deploy FIDO compliant devices to your administrators.
- If possible, use Privileged Identity Management to implement the strictest possible permission model for your administrators and other team members.
- Remember about Emergency Access Accounts for your environment. Please remember to protect them. There might be a time when you need them.
Security toolkit
Security is essential. It is among the first concerns raised when a company adopts the cloud. Because of this, it is also well described and addressed through the platform.
Remember: cloud is not magic! It doesn’t work on its own. Even if the controls are there – you need to put them in place!
The basics
Set the basic requirements for your core elements on Azure:
- RBAC model and permissions management
- Encryption of disks and data storage both in storage accounts but also within services
- Networking protection with VNets, network security groups, firewall, and other networking elements.
There are around 20 security-related whitepapers with guidance for those elements. Use them to educate yourself one topic at a time.
Security controls
Familiarize yourself with tools you have on the platform and apply them as security controls.
Azure Security Center is a one-stop shop for monitoring your security strategy. It provides a real-time view into compliance with regulatory requirements for your resources. Make sure to check this as it provides actionable items to improve in this area. Plan your resource coverage with Azure Security Center. It also has a free plan.
Azure Sentinel is a service that provides SIEM capabilities in the cloud and for cloud resources. It gives insight and monitoring across many data sources. You can currently try it for free. Make sure to check if this can be your tool of choice for security and threats monitoring. We can also help you with managing it – see more here.
Watch the video to find out more about Azure Sentinel
Educate yourself on and set up your policies. This is a requirement for the use of platform features and services like the following:
- Azure AD and its security model for resources and access across the platform
- Azure Key Vault for securing sensitive materials, credentials, and keys.
A list of fundamental security tools in your toolkit with a quick comparison can be found here.
Cost management
This is always an essential factor in cloud deployments. To implement it efficiently you need three elements:
- A consistent way of deploying resources within your management structure
- A set of Azure Policies as the first level of control of resources creation and spending
- Actual cost control tools.
The Azure platform provides a tool called Azure Cost Management. There is also an option of using a separate service owned by Microsoft, Cloudyn.
One thing to check for sure is how your subscription payment model supports those solutions. There might be slight differences between EA, CSP or other ways in which you purchase your Azure.
You can also use community and third-party solutions like Azure enterprise usage reports (AER). Or, go straight to Azure with Power BI and create dashboards crafted for you.
Summary
And that’s the end of our guide to implementing Azure governance. I hope you found it helpful. If you prefer this information is video form, you’ll find a summary here:
A summary of subscription management in Azure
In my upcoming articles, you will find more details and tips on how to look after your services with cloud governance. In the meantime, feel free to contact us with any questions!
- As with any framework, start your Azure governance model with an MVP. An initial set of policies will get you started and provide a basis for iteration.
- Azure gives you a multitude of tools to manage your services. First, establish ways to manage your subscriptions and environments. Then, define your deployment, identity, security and cost management policies using tools listed above.
