cloud-adoption
$
npx mdskill add MicrosoftDocs/cloud-adoption-framework/cloud-adoptionDrive Azure integration through strategy, readiness, and governance.
- Aligns organizational leadership with cloud adoption goals and investment plans.
- Accesses Microsoft Azure Cloud Adoption Framework documentation and calculators.
- Structures teams, defines policies, and maps required technical skills.
- Delivers executive-ready documents and operational readiness roadmaps.
SKILL.md
.github/skills/cloud-adoptionView on GitHub ↗
---
name: cloud-adoption
description: How to adopt and integrate the Microsoft Azure cloud into your organization. Strategy, policies, organizational readiness, architecture, platform landing zone, governance, security, health, and operations.
---
## Cloud adoption process
1. Strategy/Executive strategy
- Target audience: Decision makers, C-suite leadership. Anyone responsible for technology investment decisions, or leading a cloud adoption initiative.
- Scope: Scope:(1-2 pages) This is a pre-sales document.
- Intro paragraph: What the goal? What is the challenge? What is the solution?
- Why this solution?
- What level of investment is required? (cost factors, and links to pricing and calculators)
- Time to value?
- How to adopt this technology (level of effort)? (Overview of the following sections so C-suite knows the level of effort).
- Reference: https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/strategy/
2. Plan/Organizational Readiness
- Target audience: Anyone responsible for hiring, skilling, assigning roles and responsibilities, and ensuring organizational readiness for cloud adoption.
- Scope:
- Cloud operating model: Responsibilities, teams structure How to assign responsibility for cloud tasks. How to structure personnel.
- Cloud skilling: Necessary skills for cloud success and resources to get these skills.
- Organizational policies: Guidelines and policies for cloud adoption and usage.
- Reference: https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/plan/prepare-organization-for-cloud
3. Ready (Architecture, platform landing zone)
- Target audience: Anyone responsible for configuring Azure for all workloads and building and maintaining the cloud platform.
- Scope: Platform landing zone:
- Azure agreement and billing:
- Identity and access management: Microsoft Entra ID
- Resource organization: How to structure your management groups
- Platform subscriptions and platform services: networking, management, connectivity, security, monitoring, logs, backups.
- Application landing zone (subscription) distribution process
- Governance and security baselines
- Reference: https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/ready/
4. Govern, Secure, and Manage (Operational standards)
- Target audience: Anyone responsible for governing securing, and monitoring the entire cloud environment.
- Scope:
- Governance: Policies, compliance, cost management, resource consistency, identity and access management, security baselines.
- Security: Threat protection, vulnerability management, security monitoring, incident response.
- Health: Monitoring, alerts, performance optimization, capacity planning.
- Reference: https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/govern/ Secure: https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/secure/overview Manage: https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/manage/ready-cloud-operations
5. Adopt
- Target audience: Anyone responsible for migrating or building workloads in Azure.
- Scope:
- Migration: Strategies and tools for migrating existing workloads to Azure.
- Modernization: Modernizing applications to take advantage of cloud capabilities.
- Cloud-native: Building new cloud-native applications and services in Azure.
- Reference: https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/adopt/overview
More from MicrosoftDocs/cloud-adoption-framework
- acronym-checkEnsures abbreviations are expanded on first use per Microsoft style. Use when asked to check acronyms or abbreviations in documentation.
- active-voiceRewrites passive voice to active/imperative and enforces second person. Use when asked to fix passive voice or improve writing directness.
- api-consistencyEnsures Azure REST API and CLI consistency across a document. Use when asked to check API calls, CLI parameters, or REST consistency.
- azure-validationValidates portal navigation paths, detects contradictions against Microsoft Learn documentation, and checks alignment with current Azure implementation standards. Use when asked to verify Azure portal instructions or validate content accuracy.
- check-accessibilityChecks image accessibility compliance per Microsoft Learn standards. Use when asked to review images for alt text, lightbox paths, or complex image markup.
- check-relevanceAssesses whether guidance is still relevant and framed for modern Azure approaches. Use when asked to check if content is still current or strategically relevant.
- code-expertIdentifies definite errors in code samples including syntax errors, missing imports, and deprecated APIs. Use when asked to review code samples for correctness.
- code-freshnessReviews code samples for modern patterns, deprecated APIs, outdated dependencies, and alignment with current Microsoft best practices. Use when asked to update or modernize code samples.
- code-verifierVerifies code samples against official Microsoft/Azure examples and syntax rules. Use when asked to verify code correctness or validate API usage.
- error-checkIdentifies severe factual errors in content. Use when asked to fact-check documentation for major inaccuracies.