Skip to main content

Nerdio is Microsoft’s 2026 Americas ISV Partner of the Year Get the story

Blog

Azure governance model: how to design one for a growing estate

Build an Azure governance model that scales with management groups, subscriptions, Azure Policy, RBAC, tagging, and cost attribution.

One host pool in one subscription was easy to govern. Then finance asks for bills split by business unit, a second region opens for data residency, and an acquisition brings another Entra ID tenant into scope. Each pressure lands on the same governance structures, and the structures either hold or they don't.

This guide is for cloud platform owners and the IT or GRC leaders responsible for a growing Azure desktop estate.

A durable Azure governance model rests on four structural components of Azure landing zones. Management groups and subscriptions organize the estate. Azure Policy and RBAC enforce the rules across it. Applied through subscription vending, these components ensure each new subscription inherits its management group's rules on arrival rather than after an audit finding.

What an Azure governance model covers

An Azure governance model is the set of structures that decide who can act on which resources and who pays for them.

Microsoft's Cloud Adoption Framework (CAF) describes the management group hierarchy as the layer that "organizes all of your Azure subscriptions and applies governance standards to those subscriptions" per the previously cited Azure landing zones guidance.

Policy and role assignments made at a management group flow down to every subscription and resource group beneath it, and a subscription owner cannot override a policy inherited from above.

For a desktop estate, that model has to span both halves of Windows Cloud, Microsoft's umbrella term for Windows 365 and Azure Virtual Desktop. Many enterprises run both products, and the two put governance in different places: 

  • Windows 365 Cloud PCs run on Microsoft-managed infrastructure and take their configuration from Microsoft Intune. Their costs follow a per-user-per-month license charge that stays separate from any Azure infrastructure costs allocated through Azure Cost Management.
  • Azure Virtual Desktop session hosts and FSLogix profile storage live in your own subscriptions under Azure Policy and Azure RBAC.

The CAF's Govern guidance frames governance as five ongoing steps. A cloud governance team gets built first, then that team assesses risks, documents policies, enforces them, and monitors compliance on a repeating cycle. The first structural decision the team makes is where each subscription sits in the hierarchy.

What an Azure governance model covers

An Azure governance model is the set of structures that decide who can act on which resources and who pays for them.

Microsoft's Cloud Adoption Framework (CAF) describes the management group hierarchy as the layer that "organizes all of your Azure subscriptions and applies governance standards to those subscriptions" per the previously cited Azure landing zones guidance.

Policy and role assignments made at a management group flow down to every subscription and resource group beneath it, and a subscription owner cannot override a policy inherited from above.

For a desktop estate, that model has to span both halves of Windows Cloud, Microsoft's umbrella term for Windows 365 and Azure Virtual Desktop. Many enterprises run both products, and the two put governance in different places: 

  • Windows 365 Cloud PCs run on Microsoft-managed infrastructure and take their configuration from Microsoft Intune. Their costs follow a per-user-per-month license charge that stays separate from any Azure infrastructure costs allocated through Azure Cost Management.
  • Azure Virtual Desktop session hosts and FSLogix profile storage live in your own subscriptions under Azure Policy and Azure RBAC.

The CAF's Govern guidance frames governance as five ongoing steps. A cloud governance team gets built first, then that team assesses risks, documents policies, enforces them, and monitors compliance on a repeating cycle. The first structural decision the team makes is where each subscription sits in the hierarchy.

Build the management group hierarchy before vending the next subscription

Every subscription in a management group inherits the policy and RBAC assignments above it, so the platform team has to build the tree before it vends the next subscription. That work breaks into three parts: laying out the reference hierarchy, keeping the tree flat, and vending each new subscription into the right place.

Lay out the CAF reference hierarchy

The CAF reference hierarchy places an intermediate root directly under the tenant root, with a Platform group and a Landing Zones group beneath it. Platform holds the shared subscriptions the whole estate depends on, while Landing Zones is organized by workload archetype rather than by team or environment.

The table below shows how the four common groups map to the subscriptions that sit under each one.

Management group

What sits under it

Platform

Management, Connectivity, Identity, and Security subscriptions

Landing Zones / Corp

Workloads needing corporate or hybrid connectivity, including Azure Virtual Desktop host pool subscriptions

Landing Zones / Online

Workloads requiring direct internet connectivity or no virtual network

Sandbox

Experimentation; still inherits every policy from above

 

Azure Virtual Desktop host pool subscriptions that use domain join and corporate-network FSLogix shares belong under Corp. Azure allows six levels below the root, and the CAF still recommends keeping the tree flat at three to four levels so it doesn't end up mirroring your org chart.

Vend new subscriptions into the tree

Once the tree is in place, new subscriptions should arrive through subscription vending. The platform team deploys each subscription into its management group with a budget already attached, then applies the RBAC and policy assignments. Nerdio Manager for Enterprise deploys into a subscription you own, so it sits inside the same subscription boundary you already govern.

Handle the Windows 365 network boundary

Windows 365 puts less infrastructure in your hands because Microsoft runs the Cloud PC fleet. When Cloud PCs use an Azure Network Connection, you create and own the virtual network they attach to.

That subnet needs an explicit outbound path before Azure retires default outbound access for newly created virtual networks on March 31, 2026. With every subscription in a fixed place, the platform team can enforce a consistent Azure Policy baseline at the tree level.

Assign Azure Policy where inheritance does the work

Your desktop baseline belongs at the management group that holds your Azure Virtual Desktop subscriptions, so the next subscription the platform team vends inherits it before its first session host exists. Teams can assign workload-specific controls at the Corp group or the desktop subscription and keep them off Platform subscriptions that will never run a session host.

The rest of the section covers the baseline definitions to start with, how to roll them out safely, and where Windows 365 sits inside this model.

Start with four built-in definitions

Use these four built-in definitions to cover much of the baseline:

  • "Azure Virtual Desktop hostpools should disable public network access," which can run in Deny mode.
  • "Allowed locations", which enforces data residency. The CAF suggests limiting desktop resources to the United States, Europe, United Kingdom, and Canada when residency rules apply.
  • "Allowed virtual machine size SKUs", which caps session host sizes for cost control.
  • A DeployIfNotExists policy that routes host pool diagnostic logs to Log Analytics. Each resource type needs its own definition, which is why large estates deploy policy from a repository with Enterprise Policy as Code (EPAC).

Session hosts belong in their own subnets, and teams should apply network security groups. Teams can assign the built-in initiatives to support alignment with CIS and NIST SP 800-53 requirements at the same management group, so CIS security baselines inherit the same way. Defender for Cloud's regulatory compliance dashboard is where a GRC lead reads the results.

Roll out policy safely and account for evaluation timing

Microsoft's Azure Policy safe deployment guidance is to assign at the highest scope with enforcementMode set to DoNotEnforce. After remediating what the audit surfaces, switch to Default.

Azure Policy evaluates compliance once every 24 hours, so a deleted session host can keep showing as Non-Compliant until the next cycle completes.

Handle Windows 365 through Intune

Windows 365 has no Cloud PC-specific built-in Azure Policy definitions. The Azure Policy baseline still governs the virtual network and any Azure resources Cloud PCs attach to, and Intune policies enforce Cloud PC configuration itself. That split shows up again in identity, because Intune runs a separate role system from Azure RBAC.

Scope RBAC to groups and separate platform from workload roles

Least privilege in a desktop estate comes down to group-scoped roles and a hard split between platform and workload scopes. Microsoft's 2024 State of Multicloud Security Risk Report examined 209 million cloud identities and found usage for only 2% of granted permissions, which is why broad standing assignments at management group scope are the expensive mistake.

Three moves keep RBAC manageable at scale. Start from the built-in Virtual Desktop roles, let team boundaries determine role scope, and plan a separate RBAC matrix for Windows 365.

Start with the narrow built-in Virtual Desktop roles

The built-in Virtual Desktop roles are narrow by design. Desktop Virtualization Session Host Operator covers drain mode and host removal for a help desk. Desktop Virtualization Application Group Contributor excludes user assignment, so admins have to pair it with User Access Administrator before anyone can publish a desktop to a group.

Match role scope to team boundary

Team boundaries determine role scope in this model:

  • Roles for your platform team sit at management group scope.
  • Roles for your workload team sit at subscription or resource group scope, with each landing zone keeping its own groups instead of one shared desktop admins group.
  • Role assignments attach to groups rather than users, because Azure caps role assignments at 5,000 per subscription and 500 per management group.

Microsoft's RBAC guidance recommends a maximum of three subscription owners, and puts Owner and User Access Administrator behind Microsoft Entra Privileged Identity Management (PIM) so elevation is time-bound. Eligible PIM assignments do not count toward the 5,000 limit.

Nerdio Manager adds a further layer here, with role-based access control and granular module permissions that separate help desk and desktop administration duties.

Plan a second RBAC matrix for Windows 365

Windows 365 uses a different plane. Cloud PC Administrator and Cloud PC Reader are Intune roles that only appear when the tenant holds a Windows 365 subscription, and an admin holding Azure's Desktop Virtualization Contributor role does not automatically carry Cloud PC permissions in Intune.

Your RBAC design therefore has two matrices, one in Azure and one in Intune. Identity decides who can create resources, and tagging decides whether anyone can say who is paying for them.

How do you make cost attribution work by default?

Cost attribution works by default when tags are enforced on every resource at creation and inheritance handles the rollup automatically. IDC estimates up to 30% of cloud spend is waste, and an ownership tag identifies who is accountable for closing the gap.

Resources do not inherit tags from their resource group or subscription. To close that gap, the built-in policy "Inherit a tag from the resource group if missing" (Modify effect) applies ownership tags to new resources, and a remediation task backfills the existing ones. With enforcement on creation and remediation for what's already there, teams can group session-host charges by host pool for reporting.

For Azure Virtual Desktop, cost management starts with the cm-resource-parent tag. Teams set it on session host VMs to the host pool's resource ID, which makes Cost Management group each host's charges under the parent host pool. Cost Management's tag inheritance setting then applies subscription and resource group tags to usage records within 24 hours, so attribution flows through automatically once the tag strategy is in place.

Nerdio Manager's User Cost Attribution feature (Premium edition) takes it a step further by allocating total Azure Virtual Desktop deployment cost to individual users in proportion to session duration.

Windows 365 attribution works differently because the license model is different. A fixed per-user license charge is predictable before the month starts, and those license charges stay separate from any Azure infrastructure costs Cloud PCs incur. Azure Cost Management allocation reassigns those Azure infrastructure costs from subscriptions, resource groups, or tags to the business units that own them.

Where Nerdio Manager fits in a Windows 365 and Azure Virtual Desktop governance model

Nerdio Manager adds a management and automation layer to the Azure hierarchy and policy assignments you control, though it does not certify or guarantee compliance with any framework.

Nerdio Manager deploys directly inside your Azure environment in a region you choose, with no third-party hosting. Its RBAC supports granular module permissions and policy automation. It also provides audit logging. The audit log records administrative activity to support internal control reviews without asking anyone to reconstruct who changed what.

Across Windows Cloud

Nerdio Manager manages Windows 365 and Microsoft Intune together. It also manages Azure Virtual Desktop across the Windows Cloud estate. Governing Cloud PCs means governing Intune, and Nerdio Manager extends native Intune with policy backup and restore, including recovery after someone deletes a policy.

Application deployment to Cloud PCs through Unified Application Management takes about 30 seconds, compared with up to 3 hours for native Intune delivery. Nerdio Advisor flags oversized Cloud PCs for right-sizing and identifies users whose shifts never overlap as Frontline license conversion candidates.

Nerdio Manager lets you select CIS Hardened Images when deploying Azure Virtual Desktop session hosts, so teams apply the hardened baseline at build time rather than discover it as a finding later. Syneos Health, a clinical research organization, reported 70% faster configuration changes after moving its virtual desktop change process onto Nerdio Manager.

City of Corona reported an improved security posture and greater IT operational efficiency with Nerdio Manager. Even with those improvements in place, the model itself has to change shape as the estate grows.

Frequently asked questions about Azure governance

Ready to get started?