Read a sample: 1. Governance Before Configuration
On Monday morning, a small company decides to move an internal application to Azure. By lunchtime, someone is ready to create a subscription, invite colleagues, and begin building.
The enthusiasm is useful. The unanswered questions are just as important.
Who is allowed to approve the spending? Should a developer be able to change the production application, or only a test copy? If a contractor needs access for a month, who decides what that access includes and who checks that it is removed? If the company adds a second application, should it share the same organizational boundary as the first?
These are governance questions. They are not a reason to delay every technical task until an organization has produced a perfect plan. They are a reason to make a few important decisions deliberately, while the environment is still easy to understand.
Cloud governance is the practice of deciding how an organization directs and oversees its use of the cloud. It connects business needs with practical boundaries: what people may do, where they may do it, and who is responsible for the decisions. Azure provides tools that can support those choices, but the tools do not make the choices for you.
This chapter begins a running planning exercise for a fictional company called Northstar. You do not need an Azure account to take part. A piece of paper or a simple document is enough.
Imagine giving a new employee a key to an office. Before handing it over, someone needs to know which rooms the employee should enter, whether the key should work after hours, and who can approve a replacement. The lock enforces part of the arrangement, but the arrangement begins with a decision.
Cloud access works in a similar way. A role assignment can grant a person permission to take certain actions within a particular area of Azure. Before creating that assignment, an organization should understand why the person needs it, what area it should cover, and who is authorized to approve it.
Not every governance decision concerns access. A company may also need to decide:
- Who can approve a new cloud project.
- How spending will be monitored and discussed.
- How production work will be separated from experimentation.
- Which requirements apply to several teams rather than just one.
- How exceptions will be requested and reviewed.
- What should happen when a person changes jobs or leaves.
Some decisions are formal, while others begin as a short agreement between a few people. The important point is that an agreement should be clear enough for someone else to follow and revisit. “Ask the IT team” may work when everyone sits in the same room, but it becomes less useful when nobody knows which member of the team can approve a request.
Governance is not the same as preventing change. Good governance makes ordinary decisions easier by clarifying who can act and when a conversation is needed. A developer who knows where to experiment and whom to contact for production access can often move faster than one who must guess.
Throughout this book, you will see three related ideas: decisions, boundaries, and responsibilities.
A decision is a choice the organization needs to make. For example, Northstar may decide that production access requires approval from the person accountable for the application.
A boundary defines where a decision or arrangement applies. Northstar might distinguish a production environment from a testing environment because the consequences of a change are different in each. Azure also has technical boundaries, called scopes, where access and other governance settings can be applied.
A responsibility identifies who is expected to take part. One person might request access, another approve it, and a technical administrator implement it. In a small company, one person may perform more than one of those activities. The activities are still worth distinguishing.
These ideas fit together, but they are not interchangeable. Naming an application owner does not automatically give that person Azure access. Granting someone Azure access does not, by itself, make that person accountable for a business decision. And creating a boundary does not explain what rules or responsibilities should apply within it.
The rest of this chapter uses those distinctions to make a first, modest plan. Chapter 2 will look more closely at the people involved.
Northstar is a fictional company with a small office, a few internal systems, and a growing customer service team. It wants to place an internal scheduling application in Azure. The application helps staff coordinate appointments, and the company expects to improve it over time.
For the planning exercise, Northstar has four people involved:
- Maya, the operations manager, relies on the application for day-to-day business and can explain when interruptions would be especially disruptive.
- Leo, an IT administrator, will help organize the Azure environment and carry out approved technical changes.
- Priya, a developer, needs a place to build and test improvements.
- Sam, the finance lead, wants to understand and monitor the cloud spending associated with the application.
These descriptions give the team a starting point; they do not automatically determine anyone’s Azure role. Maya’s responsibility for the application does not necessarily mean she needs permission to change cloud resources. Priya’s need to test an update does not necessarily mean she needs the same access to production.
Northstar also expects that an external specialist may occasionally help with the application. The specialist…