In previous post, we have defined what are Azure Blueprints and how they are important to deploy Azure Environments with a set of compliance and standards packaged together into a single definition. In this post, we are going to go through Blueprint lifecycle making use of Azure Portal. Like many resources within Azure, a blueprint in Azure Blueprints has a typical and natural lifecycle. They’re created, deployed, and finally deleted when no longer needed or relevant. Blueprints supports standard lifecycle operations. It then builds upon them to provide additional levels of status that support common continuous
Continue reading “Create and Manage Blueprints using Azure Portal”
Traditionally, Blueprints are used by architects and engineers to design and build new things. Blueprints are used to ensure that final product are built up to very specifications as laid out and are in the compliance with certain standards and requirements.
Azure Blueprints are used in the same way as traditional blueprints. Using Azure Blueprints, cloud architects and IT groups can design and deploy azure resources repeatedly that adhere to organizational standards, requirements and patterns. By leveraging Azure Blueprints, cloud architects can quickly build and deploy new environments that are always compliant ready. Using Azure Blueprints, teams can deploy new Azure Environments, with a set of built-in Azure Resources, with a trust that they are deploying in accordance with standards and compliance.
Continue reading “Work with Azure Blueprints to design and deploy Governed Azure Environments”
In our previous blog post, we discussed how we can leverage Azure Policy to bring Azure Resources to into compliance with the Organizational configuration standards. We also created a custom Azure Policy and observed its effects on compliance. There are however close to 100 Builtin Azure Policy which are applied at any time under the default initiative. To this, add the number of policies that would be created and applied to manage resources for different departments and to enforce different standards. You’ll be quickly looking at hundreds of Azure Policies and assignments and exclusions and need some help to manage them.
Continue reading “Using Azure Log Analytics Alerts for non-compliant Azure Resources”
In our previous post, we discussed how we can access compliance data for the Azure Resources. Compliance data can be accessed using various channels such as Azure Portal, Azure CLI, Azure REST APIs and Azure PowerShell. Once the compliance data is available, one should check which resources are non-compliant in accordance to the Azure Policy or Initiative, why they are flagged as non-compliant and what actions could be taken to remediate the same. In this blog post, we are going to discuss the same.
Continue reading “Determine Non-Compliance and trigger remediation for Azure Resources”
In our previous blog post, we discussed how we can write custom Azure Policies in accordance with Organization’s Strategic and Compliance Requirements. We also learned how to apply policies at different scope levels in Azure. While planning, writing and applying compliance requirements in the form of Azure Policies is important, it is equally important to audit existing resources for appropriate configurations and settings, evaluate the results and take certain actions. One needs to be evaluate how many resources are compliant with the defined requirements, what resources are non-compliant, what corrective actions can be taken to bring them in compliance and also remove any false positives.
Continue reading “Access Compliance Data and Manage Compliance for Azure Resources”