Read a sample: 1. The Exception You Can Explain
The request arrives on a Tuesday morning: an application team needs to keep a business-critical Azure resource running, but the resource does not meet an assigned policy. The team cannot complete the required change immediately, and the next release window is weeks away.
The technical response might seem straightforward. An administrator could create an Azure Policy exemption and move on. But an exemption is not a repair, an approval in itself, or proof that the risk has disappeared. It is a way to make a governance decision visible in relation to a policy assignment. The decision still needs a reason, a boundary, an owner, and a path to closure.
This chapter introduces a hypothetical organization and a request that will follow us through the book. The example is deliberately ordinary: the interesting work is not discovering an obscure setting, but deciding what the organization is willing to accept while a real constraint is addressed.
Northstar Logistics operates a shipment-tracking application used by its customer service teams. The application stores operational records in an Azure storage account named stnorthstarops. The account sits in the rg-tracking-prod resource group within the production subscription.
Northstar has assigned a policy requiring storage accounts to disable public network access. Its objective is to reduce exposure by directing approved access through private networking. The assignment applies to the production subscription and therefore reaches the storage account.
The application team reports that stnorthstarops still needs public network access because an older integration sends shipment updates from an external partner. The partner is preparing a private connectivity solution, but the change requires coordination, testing, and a scheduled release. Disabling public network access immediately would interrupt the integration before the replacement path is ready.
The team asks for a temporary exception for the storage account. It proposes an end date of September 30 and a review at the end of each month. The year is not important to the governance pattern; in a real request, the date must be a complete, unambiguous date and time appropriate to the organization’s process.
That request raises several questions before anyone opens the Azure portal:
- Does the assigned policy actually apply to this account, and what does its effect do?
- Is the external integration genuinely dependent on the current access path?
- Can the exposure be reduced while remediation is underway?
- Who can accept the residual risk, and who must approve the business interruption that an immediate change might cause?
- Is the requested scope limited to the affected resource?
- What evidence will show that the exception is still needed, and what will close it?
The answers may support an exemption, a different technical approach, or a decision to enforce the policy without an exception. The existence of a difficult business constraint does not predetermine the outcome.
A policy expresses an intended standard. In Northstar’s case, the standard says that storage accounts within the assignment’s reach should not permit public network access. That standard has a purpose: to limit exposure and encourage a controlled network design.
The application team’s request introduces a competing concern. An abrupt change may disrupt shipment updates and affect customer operations. The team is not necessarily arguing that the standard is wrong; it is saying that this particular resource cannot meet it immediately without an unacceptable operational consequence.
The governance problem is to decide whether the temporary deviation is justified and, if so, to manage it without losing sight of the original standard.
That distinction matters because an exception can easily become a substitute for a plan. “The application needs it” describes a dependency, but it does not explain why the dependency remains, how much risk it creates, or when it will end. Conversely, “the policy requires it” does not by itself establish that disabling access today is the best operational decision. A useful review examines both the risk of continuing the deviation and the risk of changing the resource too quickly.
Azure Policy provides mechanisms for expressing and reporting governance decisions. An exemption can associate an exception with a policy assignment at an applicable scope. It does not rewrite the policy definition, remove the assignment, or make the resource’s configuration conform to the standard. If the account continues to allow public network access, that technical fact remains true even when an exemption applies.
An exemption also is not a substitute for authorization within Northstar. An administrator’s ability to create one in Azure does not automatically mean that the administrator has the business authority to accept the associated risk. The organization must determine who approves the decision and what evidence is required.
Before evaluating the business case, the cloud administrator should confirm the technical situation. Requests often begin with a summary such as “the storage policy is blocking us.” That might describe several different conditions.
The resource may be reported as noncompliant under an audit-oriented policy. A policy with a deny effect may be preventing a proposed create or update operation. An initiative may contain several policy definitions, only one of which relates to the reported problem. Or the team may be looking at a different assignment from the one it expects.
For Northstar’s request, the administrator gathers the following:
- The exact resource ID of stnorthstarops, its subscription, and resource group. - The relevant policy assignment and the scope at which it was assigned. - The policy definition or initiative member concerned with public network…