Get started: Build a cloud governance team
A cloud governance team ensures that cloud-adoption risks and risk tolerance are properly evaluated and managed. The team identifies risks that can't be tolerated by the business, and it converts risks into governing corporate policies.
Step 1: Determine whether a cloud governance team is needed
The official guidance in the Cloud Adoption Framework is to always create a cloud governance team. At first, the team might be very small. Regardless of its size, its role is important. If a team isn't needed, a group or individual on an existing adoption team should agree to fulfill the responsibilities associated with cloud governance functions.
Deliverables:
- Determine whether you need a cloud governance team.
- Align responsibilities across teams by developing a cross-team matrix that identifies responsible, accountable, consulted, and informed (RACI) parties. Document the decision and the responsible individuals using the RACI template in the
Org Alignmentworksheet.
Guidance to support deliverable completion:
- Cloud governance functions might already be spread across multiple individuals or teams. Having a team that goes by the title cloud governance team isn't important, but the required capabilities should reside with an accountable party or team.
- If the company's long-term cloud adoption strategy can be delivered from one landing zone in one cloud environment, the amount of governance and operations efforts might be small enough for delivery by one person or one team. That team is unlikely to be called cloud governance, because it serves many functions beyond cloud governance. Even for that team, this getting started guide can help ensure that it can deliver on this important function of governance.
| Accountable team | Responsible and supporting teams |
|---|---|
Step 2: Align with other teams
The governance team ensures consistency and adherence to a set of common policies. Those policies come from an ongoing alignment with other teams.
Before it establishes policies or automated cloud governance, the cloud governance team should meet with other teams that are identified in the RACI template. This will help ensure alignment on critical topics, such as security, cost, performance, operations, and deployment. Steps 4 and 5 can help facilitate the alignment.
Deliverables:
- Discuss current-state implementation and ongoing adoption plans with each team.
Guidance to support deliverable completion:
- Review your company's strategy and plan template with members of the cloud strategy team to understand motivations, metrics, and strategy.
- Review your company's cloud adoption plan with members of the cloud adoption team to understand timelines and prioritization.
- Review the operation team's operations management workbook to understand the operational requirements and commitments that have been established with the business.
| Accountable team | Responsible and supporting teams |
|---|---|
Step 3: Establish a cadence with other teams
Cloud adoption generally comes in waves, or releases. A regular cadence that's aligned with those releases lets the cloud governance team look ahead and understand the risks that will be introduced in the next wave. Staying engaged with the strategy, adoption, and operations teams during planning and review also helps the governance team stay ahead of coming risks.
Deliverables:
- Establish a cadence with the supporting teams. If possible, align that cadence with release and planning cycles.
- Establish a separate cadence directly with the cloud strategy team (or various team members) to review risks that are associated with the next wave of adoption and gauge the team's level of tolerance for those risks.
Guidance to support deliverable completion:
- For more guidance on cadences for meetings, see Cloud governance functions.
| Accountable team | Responsible and supporting teams |
|---|---|
Step 4: Review the methodology
To help establish a future vision for governance and a working approach to that vision, review the Govern methodology of the Cloud Adoption Framework.
Deliverables:
- Gain an understanding of the methodology, approach, and implementation that supports the Govern methodology.
Guidance to support deliverable completion:
- Review the Govern methodology.
Accountable team:
- The cloud governance team is accountable for establishing a vision and approach to governance.
Step 5: Complete the governance benchmark
Governance is a broad topic. A short assessment can help the team understand where to get started.
Deliverables:
- Complete the governance benchmark assessment, based on conversations with various stakeholders. Or ask other teams to complete the assessment on their own.
Guidance to support deliverable completion:
- Use the governance benchmark to assess your governance needs and priorities.
Accountable team:
- The cloud governance team should understand the gaps that are identified in the governance benchmark and then provide direction on governance that helps address the gaps.
Step 6: Implement the initial governance best practice and configuration
The Govern methodology includes two approaches to an initial governance foundation. Review each approach, and implement the one that most closely matches your needs.
Deliverables:
- Deploy the basic governance tools and organization configurations that are required to govern the environment during the next few waves of adoption efforts.
Guidance to support deliverable completion:
- For guidance on configuration and implementation, review establish an initial cloud governance foundation.
Accountable team:
- The cloud governance team is accountable for the review and implementation of governance best practices and an initial governance foundation.
Step 7: Continuously improve governance maturity
Governance needs grow as additional cloud adoption efforts are completed. Stay aligned with the ongoing adoption plan to ensure that the governance approach can maintain the proper levels of governance and control.
Deliverables:
- Implement governance improvements to guard against changing risks and governance needs.
Guidance to support deliverable completion:
- To help improve the initial governance foundation, implement expanded governance scenarios.
Accountable team:
- The cloud governance team is accountable for aligning with ongoing adoption plans.
Step 8: Evaluate landing zone changes
As landing zones are deployed and expanded, new risks or governance violations might emerge. Periodically review landing zone configurations to identify any deviations from policy that aren't caught by the cloud-native governance tools. Ensure that each landing zone deployment adheres to guidelines for landing zone governance.
Deliverables:
- Help the cloud platform team develop improvements to the landing zone, which must comply with governance policies.
Guidance to support deliverable completion:
- Improve landing zone governance.
Accountable team:
- The cloud governance team should make sure that each landing zone deployment adheres to governance guidelines.
Step 9: Adoption handoffs
As new adoption efforts are completed, the cloud adoption team hands off operational responsibilities to the cloud operations team and cloud governance teams. Stay aligned with adoption release cadences to ensure proper documentation and policy alignment, and to help the team assume responsibility for the workloads.
Deliverables:
- Regularly review and accept handoffs from other cloud adoption teams.
Guidance to support deliverable completion:
- Establish a process for onboarding new workloads and resources.
| Accountable team | Responsible and supporting teams |
|---|---|
What's next
All companies are unique, and so are their governance needs. Choose the level of maturity that fits your organization, and use the Cloud Adoption Framework to guide the practices, processes, and tooling that can help you get there.
As cloud governance matures, teams are empowered to adopt the cloud at a faster pace. Continuous cloud adoption efforts tend to trigger maturity in IT operations. To ensure that governance is a part of operations development, either develop a cloud operations team or sync with your existing cloud operations team.
Feedback
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback.
Submit and view feedback for