This chapter covers Azure Arc, a service that extends Azure management capabilities to resources outside of Azure. AZ-900 tests this under objective 3.4, connecting to broader hybrid and multi-cloud concepts.
Jump to a section
A simple way to picture Azure Arc
A universal remote control lets you manage devices from different manufacturers — a TV, a sound system, a streaming box — using one consistent interface, even though the devices themselves are quite different underneath. Azure Arc works similarly: it extends Azure's management tools to resources running outside of Azure entirely — on-premises servers, other clouds, or edge devices — letting an organization manage all of them through consistent Azure tools, even though the underlying infrastructure isn't actually running in Azure.
What Azure Arc does
Azure Arc extends Azure's management capabilities — like Azure Policy, RBAC, and monitoring — to resources that aren't actually running in Azure, including on-premises servers, resources in other clouds, and edge devices. This lets an organization manage a mixed environment consistently, using the same Azure tools regardless of where a resource physically runs.
Why this matters for hybrid and multi-cloud organizations
Many organizations don't run everything in Azure — some infrastructure remains on-premises, or some workloads run in other cloud providers. Without a tool like Azure Arc, managing that mixed environment would typically require entirely separate tools for each location. Azure Arc lets Azure's governance and management tools extend to cover that broader environment.
What can be connected through Azure Arc
Azure Arc supports connecting various resource types, including servers, Kubernetes clusters, and certain data services, running outside of Azure, representing them within Azure's management tools as if they were Azure resources for management purposes (though they continue running in their original location).
How this connects to earlier concepts
Once a non-Azure resource is connected through Azure Arc, tools like Azure Policy and RBAC (covered in earlier chapters) can be applied to it, extending the same governance and access control practices used for Azure resources to this broader, hybrid environment.
Identify resources outside of Azure
Non-Azure resources — on-premises servers, resources in other clouds, or edge devices — are identified as candidates for connecting through Azure Arc.
Connect them through Azure Arc
Those resources are connected to Azure Arc, representing them within Azure's management tools even though they continue running in their original location.
Apply consistent governance and management
Once connected, tools like Azure Policy and RBAC can be applied to these resources, extending consistent governance practices across the whole mixed environment.
Manage the broader environment centrally
The organization gains a more unified management experience across Azure and non-Azure resources, rather than needing entirely separate tools for each location.
A company with a mix of on-premises servers and Azure resources uses Azure Arc to connect those on-premises servers to Azure's management tools, allowing them to apply the same security policies and monitoring practices across both environments, rather than maintaining entirely separate governance approaches for each.
A separate organization running Kubernetes clusters both in Azure and in another cloud provider uses Azure Arc to manage all of those clusters consistently through Azure's tools, reducing the operational complexity of switching between different management approaches for each cloud.
Objective 3.4 expects a general, conceptual understanding of Azure Arc's role in extending Azure management to non-Azure resources — implementation-level detail isn't required at this level.
A common wrong answer is assuming Azure Arc moves or migrates resources into Azure — it doesn't; connected resources continue running in their original location, but become manageable through Azure's tools. Another common trap is assuming Azure Arc only works with servers — it can also extend to Kubernetes clusters and certain data services.
Stable terms: Azure Arc, hybrid, multi-cloud. Recognizing Azure Arc's role in extending consistent management to resources outside of Azure, without physically moving them, is the core exam-relevant idea.
Memory trick: Azure Arc doesn't move your resources into Azure — it extends Azure's management tools out to wherever your resources already are.
Azure Arc extends Azure's management capabilities — like Policy, RBAC, and monitoring — to resources running outside of Azure.
Connected resources continue running in their original location; Azure Arc doesn't migrate or move them into Azure.
Azure Arc supports connecting servers, Kubernetes clusters, and certain data services running on-premises, in other clouds, or at the edge.
Azure Arc helps organizations with hybrid or multi-cloud environments manage resources consistently through Azure's tools.
These come up on the exam all the time. Here's how to tell them apart.
Resources Running in Azure
Physically run on Azure's infrastructure
Natively managed through Azure tools
No additional connection step needed
Resources Connected via Azure Arc
Physically run outside Azure (on-premises, other clouds, edge)
Managed through Azure tools after being connected
Requires connecting the resource to Azure Arc first
Mistake
Azure Arc moves or migrates non-Azure resources into Azure.
Correct
Connected resources continue running in their original location — on-premises, another cloud, or the edge. Azure Arc extends Azure's management tools to them without physically relocating anything.
Mistake
Azure Arc only works with servers.
Correct
It can also extend to other resource types, including Kubernetes clusters and certain data services running outside of Azure, not just servers alone.
Mistake
Azure Arc is only useful for very large, complex organizations.
Correct
Any organization with resources split between on-premises, other clouds, or the edge alongside Azure can benefit from the consistent management Azure Arc provides, regardless of overall size.
It's a service that extends Azure's management capabilities — like Azure Policy, RBAC, and monitoring — to resources running outside of Azure, including on-premises servers, resources in other clouds, and edge devices.
No — resources connected through Azure Arc continue running in their original location. Azure Arc extends Azure's management tools to them, representing them within Azure for management purposes, without physically relocating them.
It supports various resource types, including servers, Kubernetes clusters, and certain data services running outside of Azure, not just a single resource type.
You've just covered Azure Arc — now see how well it sticks with free AZ-900 practice questions. Full explanations included, no account needed.
Done with this chapter?