1. Why Hybrid Cloud?

Few enterprises are 100% cloud. Common drivers for hybrid architecture:

• Compliance & data sovereignty — regulations mandate data stays on-prem or in-country.
• Latency — factory floor, retail POS, or medical devices need sub-millisecond response.
• Migration timeline — lift-and-shift takes years; you need unified management during transition.
• Existing investment — hardware with years of depreciation remaining can't be abandoned overnight.

2. Azure Arc Overview

Azure Arc projects non-Azure resources into Azure Resource Manager (ARM). Once projected, you manage them with the same tools: Portal, CLI, Policy, RBAC, Monitor, and Defender for Cloud.

The Arc agent establishes an outbound HTTPS connection — no inbound firewall rules needed. Resources appear as ARM objects with resource IDs, tags, and location metadata.

3. Arc-Enabled Servers

Install the Connected Machine agent on Windows or Linux to project physical or virtual servers into Azure.

• Onboarding — single script, at-scale via service principal, or Configuration Manager / Ansible.
• Guest Configuration (Machine Configuration) — audit and enforce OS settings (password policy, installed software) using Azure Policy.
• Extensions — deploy Log Analytics agent, Dependency agent, Custom Script, Key Vault for certificates.
• Azure Policy — apply the same compliance policies to on-prem servers as to Azure VMs.
• Microsoft Defender for Servers — threat detection on Arc-enabled machines.

4. Arc-Enabled Kubernetes

Connect any CNCF-conformant cluster — on-prem, EKS, GKE, Rancher — to Azure.

• Azure RBAC — grant Azure AD identities access to namespaces without managing kubeconfig.
• GitOps (Flux v2) — declare cluster configuration in Git; Arc reconciles automatically.
• Azure Policy for K8s — enforce pod security, image registries, resource limits via Gatekeeper.
• Cluster Extensions — deploy Azure Monitor Container Insights, Defender, Open Service Mesh.
• App Services / ML on Arc — run App Service, Functions, Logic Apps, or ML inference on your own cluster.

5. Arc-Enabled Data Services

Run Azure-managed database engines on any Kubernetes infrastructure with Azure billing and evergreen updates.

• SQL Managed Instance (Arc) — full SQL MI feature set running on your K8s cluster, with automated patching.
• Azure Arc-enabled PostgreSQL — Hyperscale PostgreSQL on any infrastructure.
• Connectivity modes — Directly connected (real-time telemetry) or Indirectly connected (air-gapped, periodic upload).
• Billing — pay-as-you-go or SQL Server license with Software Assurance; metered through Azure.

6. Azure Stack Family

• Azure Stack HCI — hyper-converged on-prem cluster; run Azure VMs, AKS, and Azure Virtual Desktop locally with Azure billing.
• Azure Stack Hub — fully disconnected Azure environment for sovereignty, submarine, or classified workloads.
• Azure Stack Edge — Microsoft-managed appliance for edge compute, ML inference, and data transfer.

7. Multi-Cloud Patterns

Azure Arc treats AWS and GCP resources as first-class Azure objects:

• Unified inventory — see all EC2 instances, GKE clusters in the Azure portal alongside Azure resources.
• Consistent governance — one Azure Policy definition enforces tagging, allowed regions, and security baselines everywhere.
• Single pane monitoring — Azure Monitor and Defender aggregate metrics/alerts from all clouds.
• Cost visibility — while native billing stays per-cloud, Azure Resource Graph queries span all projected resources for governance.

Pattern: Use Arc for governance & compliance; keep workloads running natively in each cloud to avoid re-platforming.

8. Arc vs Azure Stack HCI vs Native Azure

9. Real-World: Unified Factory Management

10. Exam Tip

11. Knowledge Check