Limerick DotNet-Azure User Group (LDNA)-Cloud Adoption Framework Governance Overview

I spoke at the Limerick DotNet-Azure User Group (LDNA) about Cloud Adoption Framework – Governance Overview and below are the slides from the session.

The recording should be available in a couple of days so check back the Speaking page.


Cloud Adoption Framework – Manage Overview

The last phase of Cloud Adoption Framework is the Manage phase.

Manage methodology of the Cloud Adoption Framework

Inventory and visibility

First step is to take a complete snapshot of the environment so it can be managed properly. Create inventory of assets and develop visibility into the run state of each asset.

There should be centralized logging about change management, service heath and configuration of IT operations.

Monitor health of Azure servicesAzure Service HealthHealth, performance, and diagnostics for services running in Azure
Log centralizationLog AnalyticsCentral logging for all visibility purposes
Monitoring centralizationAzure MonitorCentral monitoring of operational data and trends
Virtual machine inventory and change trackingChange Tracking and Inventory in Azure AutomationInventory VMs and monitor changes for guest OS level
Subscription monitoringAzure activity logMonitoring change at the subscription level
Guest OS monitoringAzure Monitor for VMsMonitoring changes and performance of VMs
Network monitoringAzure Network WatcherMonitoring network changes and performance
DNS monitoringDNS AnalyticsSecurity, performance, and operations of DNS
Inventory and visibility

Operational Compliance

Establish controls and processes to ensure each state is properly configured and running in a well-governed environment.

Patch managementAzure Automation Update ManagementManagement and scheduling of updates
Policy enforcementAzure PolicyPolicy enforcement to ensure environment and guest compliance
Environment configurationAzure BlueprintsAutomated compliance for core services
Resource configurationDesired State ConfigurationAutomated configuration on guest OS and some aspects of the environment
Operational compliance

Protect and Recover

Ensure all managed assets are protected and can be recovered using baseline management tooling.

Protect dataAzure BackupBack up data and virtual machines in the cloud.
Protect the environmentMicrosoft Defender for CloudStrengthen security and provide advanced threat protection across your hybrid workloads.
Protect and recover

Enhanced Baseline

Evaluate common additions to the baseline that might meet business needs.

DisciplineProcessToolPotential impactLearn more
Inventory and visibilityService change trackingAzure Resource GraphGreater visibility into changes to Azure services might help detect negative effects sooner or remediate faster.Overview of Azure Resource Graph
Inventory and visibilityIT Service Management (ITSM) integrationIT Service Management ConnectorAutomated ITSM connection creates awareness sooner.IT Service Management Connector (ITSMC)
Operational complianceOperations automationAzure AutomationAutomate operational compliance for faster and more accurate response to change.See the following sections
Operational compliancePerformance automationAzure AutomationAutomate operational compliance with performance expectations to resolve common resource specific scaling or sizing issues.See the following sections
Operational complianceMulticloud operationsAzure Automation Hybrid Runbook WorkerAutomate operations across multiple clouds.Hybrid Runbook Worker overview
Operational complianceGuest automationDesired State Configuration (DSC)Code-based configuration of guest operating systems to reduce errors and configuration drift.DSC overview
Protect and recoverBreach notificationMicrosoft Defender for CloudExtend protection to include security-breach recovery triggers.See the following sections
Enhanced Baseline

Platform Specialization

Invest in ongoing operations of a specific workload generally reserved for mission critical workloads.

ProcessToolPurposeSuggested management level
Improve system designMicrosoft Azure Well-Architected FrameworkImproving the architectural design of the platform to improve operationsN/A
Automate remediationAzure AutomationResponding to advanced platform data with platform-specific automationPlatform operations
Service catalogManaged applications centerProviding a self-service catalog of approved solutions that meet organizational standardsPlatform operations
Container performanceAzure Monitor for containersMonitoring and diagnostics of containersPlatform operations
Platform as a service (PaaS) data performanceAzure SQL AnalyticsMonitoring and diagnostics for PaaS databasesPlatform operations
Infrastructure as a service (IaaS) data performanceSQL Server Health CheckMonitoring and diagnostics for IaaS databasesPlatform operations
Platform Specialization

Workload Specialization

Invest in ongoing operations of a shared platform.

Application monitoringApplication InsightsMonitoring and diagnostics for applications
Performance, availability, and usageApplication InsightsAdvanced application monitoring with the application dashboard, composite maps, usage, and tracing
Workload Specialization

Cloud Adoption Framework – Governance Overview

Why is governance important?

Governance is important because it lays down a foundation to have a balance between transformation and risk mitigation such as maintaining compliance, creating cost visibility and control, improving security posture etc.

Here are some questions that should be asked regarding governance:

  • Who is responsible for monitoring, support, and operations?
  • Which services should be migrated to Azure?
  • What roles & responsibilities must be defined?
  • What security measures should we consider?
  • What are the core processes needed
    for service management?
  • How do we ensure a balance between innovation,
    cost and agility?
  • What organizational changes are needed?
  • What key capabilities  must be developed?
  • Azure governance building blocks?

Governance benchmark assessment

Understand business risk

Here are some questions that should be asked when defining corporate policy:

  • What are your compliance requirements?
  • Have you identified your business risks as it relates to cloud?
  • What are your business priorities and reasons for moving to cloud?
  • How do you think about data risks and data governance?
  • Is there a list of applications which are prioritized by business impact?
  • Do you have specific application governance requirements?
  • How do you audit for compliance?

governance pillars

Cost Management

Establish controls and processes to ensure proper allocation of cost across business units.

Define cost management Role-Based Access Control (RBAC) model.

Security Baseline

Establish policies to protect network, assets and data on your Azure environment.

Resource Consistency

Implement the foundation for governance best practices with appropriate resource organization.

Define the appropriate Azure management groups and subscriptions model to reflect security, operations and business hierarchy.

Identity Baseline

Protect your data and assets in the cloud by implementing identity and access control.

Define Azure RBAC model; using RBAC segregate duties within a team and grant only the amount of access to users that they need to perform their job.

Operationalize Azure Privileged Identity Management (PIM) as cloud based identity is an iterative process.

Deployment Acceleration

Establish polices to govern asset configuration or deployments, which could be manual or automated through DevOps best practices.

The DevOps practices in this discipline include:

Infrastructure as code

  • Stand up environments in the fastest means possible.
  • Remove the human element and reliably and repeatable deploy every time.
  • Improve environment visibility and improve developer efficiency
  • Store infrastructure definitions alongside application code.

Continuous integration and continuous deployment

  • Accelerate delivery through automation
  • Simple and easy to use
  • Global community for actions


Governance Minimum Viable Product (MVP)

The below diagram illustrates the governance MVP and three governance iterations. Since these are iterations process, the process will evolve with each workload and maturity of the cloud.

Build the governance MVP

Standard enterpriseComplex enterprise
1. Customers or staff reside largely in one geography1. Customers or staff reside in multiple geographies or require sovereign clouds
2. Business units share a common IT infrastructure2. Multiple business units that do not share a common IT infrastructure
3. Single IT budget3. Budget allocated across business units and currencies
4. Capital expense-driven investments are planned yearly and usually cover only basic maintenance4. Capital expense-driven investments are planned yearly;  often include maintenance and refresh cycles of 3-5 years
5. Datacenter or third-party hosting providers with fewer than five datacenters5. Datacenter or third-party hosting providers with more than five datacenters
6. Networking includes no WAN; or 1-2 WAN providers6. Networking includes complex network or global WAN
7. Identity is a single forest, single domain7.Identity consists of multiple forests, multiple domains
8. Cost Management (cloud accounting) showback model – billing is centralized through IT8. Cost Management (cloud accounting) chargeback model – billing can be distributed through IT procurement
9. Security Baseline – protected data: company financial data and IP. Limited customer data. No third-party compliance requirements.9. Security Baseline (protected data) – Multiple collections of customers’ financial and personal data

This wraps up the Cloud Adoption Framework – Governance Overview.