Microsoft Expands Azure Arc Multicloud Connector with GCP Integration and Automated EKS Discovery

Microsoft has expanded the capabilities of the Azure Arc Multicloud Connector, adding public preview support for Google Cloud Platform (GCP) alongside existing Amazon Web Services (AWS) integrations. The multicloud connector provides agentless inventory discovery, auto-discovering compute resources across AWS EC2, GCP virtual machines, and Amazon Elastic Kubernetes Service (EKS) clusters. By syncing metadata directly into Azure Resource Graph and leveraging OpenID Connect (OIDC) federation, the mechanism allows operators to query, tag, and attach governance policies to multi-cloud workloads from a central Azure management plane without storing long-lived third-party credentials. For DevOps and infrastructure practitioners, running workloads across multiple public clouds has historically meant managing bifurcated operational stacks. Teams often replicate monitoring configurations, security baselines, and tagging conventions across each cloud provider's native consoles or invest heavily in custom abstraction software. By projecting external cloud metadata natively into Azure Resource Manager, platform teams can enforce unified compliance benchmarks and automate the deployment of Azure Connected Machine agents across external VMs and EKS nodes from day zero. This significantly cuts operational toil and lowers the risk of shadow infrastructure escaping standard vulnerability management cycles. This release reflects a broader strategic realignment among major hyperscalers, transitioning from walled-garden lock-in toward federated control planes. As enterprise multi-cloud adoption matures beyond mere redundancy and into workload specialization, managing cross-cloud drift has become a critical reliability vulnerability. Solutions like Google Cloud's Cross-Cloud Network and Microsoft's Azure Arc Multicloud Connector illustrate that the battleground for public cloud dominance is shifting from raw compute pricing to control plane stewardship, where vendors seek to become the authoritative management layer for assets running on competing infrastructure. In practice, engineering teams should evaluate the Multicloud Connector to streamline compliance audits and standardize tagging taxonomies across AWS and GCP environments. However, practitioners must account for the trade-offs of centralized governance: relying on a single provider's control plane introduces operational dependency on Azure APIs for managing multi-cloud health. Teams should test agent auto-onboarding workflows in non-production environments to evaluate performance overhead and verify that OIDC credential exchange adheres to their least-privilege identity architecture.