Cloud Resource Governance?
In How does Azure work?, you learned that Azure is a collection of servers and networking hardware running virtualized hardware and software on behalf of users. Azure enables your organization's application development and IT departments to be agile by making it easy to create, read, update, and delete resources as needed.
However, while unrestricted to resources can make developers more agile, it can also lead to unexpected costs. For example, a development team might be approved to deploy a set of resources for testing but forget to delete them when testing is complete. These resources will continue to accrue costs even though they are no longer approved or necessary.
The solution is resource access governance. Governance is the ongoing process of managing, monitoring, and auditing the use of Azure resources to meet the goals and requirements of your organization.
These requirements are unique to each organization, so a one-size-fits-all approach to governance isn't helpful. Instead, it's up to each organization to design their governance model using Azure's two primary governance tools: role-based access control (RBAC), and resource policy.
RBAC defines roles, and roles define the operations allowed for each user assigned to that role. For example, the owner role allows all operations (create, read, update, and delete) on a resource, while the reader role allows only read operations. Roles can be defined broadly and applied to many resource types, or defined more narrowly and applied to just a few resource types.
Resource policies define rules for resource creation. For example, a resource policy can limit the SKU of a virtual machine to a particular preapproved size. Another resource policy could enforce the application of a tag for an assigned cost center when the request is made to create the resource.
When configuring these tools, it is important to balance governance and organizational agility. The more restrictive your governance policy, the less agile your developers and IT workers will be. A restrictive governance policy may require more manual steps like requiring a developer to fill out a form or send an email to a member of the governance team to manually create a resource. The governance team has finite capacity and may become a bottleneck, resulting in development teams waiting unproductively for their resources to be created, or unneeded resources accruing costs before they are deleted.
Now that you understand the concept of cloud resource governance, learn more about how resource access is managed in Azure.