multicloud
102 TopicsAnnouncing the Configuration Manager connector for Azure Arc (preview)
If you run Microsoft Configuration Manager, you already have one of the best records of your servers: what's deployed, which roles are running and which applications are installed. Until now, getting that picture into Azure meant installing the Azure Connected Machine agent on every machine. For many teams, that's a big job just to answer the question "what do we have?" Today we're excited to announce the public preview of the Configuration Manager connector for Azure Arc. The connector runs on-premises and brings inventory from your Configuration Manager-managed machines into Azure. You choose the device collections to include. The connector then uses their inventory data to show those machines in Azure, with no agent needed on each managed machine. Why we built it Customers keep telling us they want one view of their hybrid estate in Azure. They don't want to deploy agents across thousands of servers before they get any value. You've already invested in Configuration Manager, and that investment should carry forward. Configuration Manager stays the source of inventory and the management authority for those machines. Azure gets a connected view of them that you can query. How it works You deploy the connector once, on your Configuration Manager site server, not on each managed machine. The site server connects to Azure Arc using the Azure Connected Machine agent. You select device collections from the Configuration Manager console. The connector makes the selected machines and their inventory visible in Azure. Connected inventory includes server roles, services and applications, taken from the data already in Configuration Manager. What you can do with it See your Azure resources, Azure Arc-enabled servers and Configuration Manager machines in one inventory view. Query machines, roles, services and applications at scale with Azure Resource Graph. You don't need a Log Analytics workspace. Start with a pilot collection, check the results, then expand at your own pace. Use the inventory to decide which machines should be fully onboarded to Azure Arc next. Inventory today, full Azure management enabled by Azure Arc when you're ready The connector shows inventory as read-only. It doesn't move management of the machines to Azure, and it doesn't deploy the agent to them. When you want Azure Arc features that need an agent on each machine, such as update management, security, monitoring or Extended Security Updates, you can still use the existing Configuration Manager onboarding options: the PowerShell onboarding script a custom task sequence Getting started You'll need: An Azure subscription, a resource group and your Microsoft Entra tenant ID. Permission to connect the site server to Azure Arc and to manage connected inventory resources in the target resource group. Admin access to the site server, with rights to approve and install console extensions. Azure Connected Machine agent version 1.70 or later on the site server, plus Windows PowerShell 5.1. A small device collection for your first test. To set it up: In the Azure portal, open Azure Arc. Under Supported environments, select On-premises connectors, then Create. Download the onboarding script and run it as Administrator on the site server. Approve the console extension and choose your collections. Full guidance and sample queries: Configuration Manager connector for Azure Arc (preview) This is just the beginning Configuration Manager is a natural place to start, because it's where many of you keep the most complete picture of your servers. But it isn't the only system that knows your servers well. Our goal is simple: wherever your on-premises inventory lives today, Azure Arc should be able to see it, without asking you to start over. Keep an eye on this space. Tell us what you think This is a preview, and your feedback directly shapes what we do next. Try the connector with a pilot collection and tell us what works, what doesn't and what you'd like to see. Leave a comment below or use the feedback link in the Azure portal.597Views2likes1CommentGovern, Secure, and Operate Anywhere with Azure Arc
Over the past year, the way the world does work has shifted significantly. Agents have gone mainstream, infrastructure is being purpose-built for AI inferencing, and expectations around data sovereignty continue to grow. While the goals for our systems are evolving, one need remains constant: centralized visibility and control of your IT infrastructure, wherever your workloads run. Hybrid by default With geopolitical pressures and disaster risks rising, enterprises are increasingly choosing distributed infrastructure deliberately for strategic workloads to meet requirements for latency, data gravity, AI inferencing, resiliency, sovereignty, operational continuity, and regulation. Common drivers include: Unreliable connectivity: Remote sites and factory locations often operate with unreliable connections and high latency. Regulations: State, corporate, and industry rules on sovereignty and data mean some workloads must stay where they are. Acquisitions: Legacy systems and inherited environments from organic growth and team-level choices need to be integrated, not rebuilt. Optimization: Compute and power costs vary by location, so workloads need to be placed with economics in mind. As a result, many customers juggle multiple tools to manage on-premises, multicloud, and multi-OS environments, often from one central operations team. What those teams want most is consistency. One platform for your entire estate Azure Arc extends Azure management to servers and Kubernetes clusters wherever they run, so organizations can unify hybrid, multicloud, and edge estates on one platform for operations, innovation, and insights. That's where cloud-native innovation shows up. Beyond basic health and status monitoring, Azure Arc lets you collect richer operational, security, and configuration data and query it at massive scale. It also centralizes governance with consistent tags and unified identity and access management through RBAC. With centralized insights teams are able to close vulnerabilities faster, fix compliance drift, and maintain day-to-day operations, including modern patching, across hybrid and multicloud estates with better control. At Ignite 2026, we're expanding capabilities to help you see more, control more, and secure more, wherever your infrastructure runs. See Everything- Unify your distributed estate with Azure Arc You can't govern what you can't see, and full visibility used to mean deploying the Azure Arc agent to every machine first. However, at Ignite 2026 we are introducing Improved onboarding and discovery help you understand your estate and extend Azure management where it matters most. Onboarding and discovery: Google Cloud (GCP) connector (generally available): Multicloud shouldn't mean managing in silos. In addition to the AWS connector we announced last Ignite, we now support bringing all your Google Cloud resources into Azure for centralized visibility and control. Kubernetes Onboarding Solutions (Public Preview): Bring Kubernetes clusters running in Google Kubernetes Engine and Amazon EKS under Azure Arc through the Multicloud Connector. Clusters in Google Cloud and AWS join the same inventory and management as the rest of your estate, so platform teams can govern every cluster from one place. Microsoft Endpoint Configuration Manager (MECM) connector enabled by Azure Arc (preview): Bring years of Configuration Manager server inventory into Azure, with visibility into machines, software, and configuration without installing an agent on every machine. Then extend Arc management only where you need it. Visualize inventory and gain insights: Once machines are connected, the next question is what's running on them. Machine Inventory (preview): A central, Azure-native view of what's inside your Azure VMs and Arc-enabled servers, including applications, services, certificates, users, groups, and Windows OS details. Questions like "Which servers still run this app version?" or "Which certificates are about to expire?" no longer require scripts and spreadsheets. Azure Resource Manager MCP server (preview): AI agents are becoming a new way to manage Azure, and the ARM MCP server gives them a governed way to do it. Through the Model Context Protocol, agents can query resources, deploy ARM templates, create or update resources, inspect schemas, and analyze costs. And because Azure Arc-enabled resources appear in Azure Resource Manager, agents can query your hybrid estate the same way they query Azure, turning "Which on-premises servers are missing the latest agent?" into a natural-language request. And with the new Machine Configuration centralized UI (preview), users get a fleet-wide view of posture and compliance, guided setup for scenarios like custom policy and security baselines, and one-step enablement at the subscription scope. Simplify Operations- Manage, govern, operate, & secure Manage, govern and operate: Day-to-day operations are where hybrid estates take the most manual effort. New capabilities reduce that effort so teams can focus on innovation, not upkeep. Essential Machine Management, Day N operations (preview): Enable a subscription, and all its VMs and Arc-enabled servers are automatically enrolled and configured with curated management features, including monitoring, update management, security baseline auditing, and change tracking and inventory. Day N updates go beyond onboarding, with new dashboards that surface top issues at the subscription level and a central view of which subscriptions are onboarded to EMM. VM Applications for Azure Arc-enabled machines (preview): Package and deploy third-party and internal applications, agents, and middleware to Azure VMs and Arc-enabled servers without rebuilding images. Applications are stored centrally and versioned, so software deploys consistently across thousands of servers with less image management overhead. Azure Arc automatic agent upgrade (generally available): With this feature Microsoft automatically manages Azure Connected Machine agent updates, rolling them out in batches across regions during off-peak hours, with no server restart required. Turn it on across your estate with Azure Policy to keep your fleet current with no manual work. Upgrade Insights for Azure Arc-enabled Kubernetes (preview): Kubernetes version upgrades are a common cause of outages. Upgrade Insights checks clusters beforehand and flags deprecated APIs, compatibility issues, readiness problems, and configuration blockers, so platform teams can upgrade with confidence. DISA STIG audit (preview) and CIS Windows audit (generally available): Audit servers against Defense Information Systems Agency Security Technical Implementation Guides (DISA STIGs), and Windows Server 2022 and 2025 against CIS benchmarks, with hybrid support through Azure Arc. Defense, public sector, and other regulated organizations can verify compliance with the standards they're measured against, using one consistent assessment across on-premises, Azure, and other clouds. Secure and remediate: Security has to cover the whole estate, from the hardware up. These announcements strengthen identity, close compliance gaps, and speed recovery when things go wrong. TPM-backed identity for Azure Arc-enabled servers (preview): Instead of storing managed identity credentials on local disk, the Azure Connected Machine agent can now use the machine's physical TPM or virtual TPM (vTPM) as a hardware-backed root of trust. Credentials are protected against exfiltration, including by privileged users, which matters most in regulated and high-security environments. User-assigned managed identity (UAMI) for Azure Arc-enabled machines (preview): Create one identity, grant it access once, and assign it across many machines, instead of relying on per-machine system-assigned identities. This simplifies access management at scale and matches how customers already manage identity for Azure VMs. Microsoft Defender for Cloud + CIS Benchmark remediation (preview): Azure Policy and Machine Configuration assess Windows and Linux servers against CIS benchmarks and Azure security baselines, with findings and remediation in Azure Policy and Defender for Cloud. Azure Arc applies the same assessment on-premises and in other clouds, so you can audit and remediate consistently across your hybrid estate. Windows Recovery Environment (WinRE) with Quick Machine Recovery (preview): When a server can't boot, every minute offline counts, and remote sites are hard to reach. One Azure Policy now turns on WinRE and QMR across eligible Windows Server 2025 Arc-enabled servers, so they can self-repair startup problems and get critical workloads back online faster. A new Windows Recovery tab in the portal shows which servers are protected or recovering. For widespread boot issues, QMR can apply a Microsoft-provided fix through Windows Update. Recovery is best effort, so not every failure has an automated fix. Hotpatch enabled by Azure Arc is now free for Windows Server 2025: Patching shouldn't force a choice between security and uptime. Hotpatch applies updates without restarts, cutting reboots on Windows Server 2025 from roughly monthly to about four planned reboots per year (the quarterly baselines), while security content lands continuously in between. There's no separate SKU and no premium tier, just the Azure Arc onboarding step. Run Apps and Data anywhere- Consistent deployment across boundaries GitOps-based deployments with Azure Kubernetes Fleet Manager and Flux extension (preview): Fleet Manager now integrates with the Flux extension, so platform teams can roll out applications and configurations through GitOps to AKS and Arc-enabled Kubernetes clusters across Azure, on-premises, AWS, and Google Cloud. Manage Kubernetes at scale from a single control plane, with safe upgrades and multi-cluster operations. All centralized for scale Each capability is useful on its own. Together, they let you manage your whole estate the same way, at any size. Azure Arc projects every server, cluster, and cloud resource into Azure Resource Manager, so the same tools work everywhere: Azure Policy, Defender for Cloud, Machine Configuration, Update Manager, and now AI agents through MCP. That holds whether you manage ten servers or a hundred thousand, in a factory, a sovereign datacenter, or a third-party cloud. Hybrid by default doesn't have to mean complex by default. With Azure Arc, you can govern, secure, and operate anywhere, all from a single pane of glass. Want to learn more? Join the Arc Monthly Customer Forum Connect with the Azure Arc product team and hear from other customers on how they use Azure Arc. Azure Arc on Microsoft Learn: Explore documentation, tutorials, and technical guidance. Azure Arc Tech Community blog: Stay up to date on product news and announcements. Azure Arc on Microsoft Azure: Discover how Azure Arc helps simplify hybrid, multicloud, and edge management. FULL SCHEDULE: Explore Azure Arc sessions at Ignite Tuesday, November 17 3:45–5:00 PM | LAB724: Govern your estate with Azure Arc and Azure Resource Manager MCP 4:10–4:55 PM | TT1691: Audit-ready everywhere: Governance for hybrid and edge AI Wednesday, November 18 9:00–9:45 AM | TT1694: Discover everything: Unified hybrid and edge AI asset inventory 10:15–11:00 AM | BRK421: Operate a global AKS fleet across regions, edge, and sovereign clouds 12:00–1:15 PM | LAB724: Govern your estate with Azure Arc and Azure Resource Manager MCP Thursday, November 19 10:45 AM-12:00 PM | LAB724: Govern your estate with Azure Arc and Azure Resource Manager MCP 1:30–2:15 PM | BRK413: Govern, secure, and operate anywhere with Azure Arc (News from Azure Arc) Friday, November 20 9:00–10:15 AM | LAB724: Govern your estate with Azure Arc and Azure Resource Manager MCP356Views1like0CommentsAnnouncing General Availability of GCP support in the Azure Arc Multicloud Connector
We're excited to announce the general availability of Google Cloud Platform (GCP) support in the Multicloud Connector enabled by Azure Arc! For teams that have been evaluating the GCP connector in Public Preview, you can build on the experience you already know: discover supported Google Cloud resources, maintain a shared inventory in Azure, and onboard eligible virtual machines to Azure Arc without moving your workloads. Integrated Azure Cloud Shell support also simplifies connector setup by letting you authenticate to Google Cloud and run setup commands directly from the Azure portal, reducing context switching and the need to prepare a separate execution environment. Build on your existing Multicloud management experience The core workflow remains familiar: connect your Google Cloud environment, choose your solutions, and define the scope of resources you want to discover and onboard. The Inventory solution maintains Azure representations of supported Google Cloud resources through periodic synchronization. Teams can query those resources alongside Azure and AWS resources through Azure Resource Graph, using imported metadata to understand their connected environments. Azure tags and Azure policies can also be applied to those representations to help organize and govern inventory. With Arc VM onboarding, eligible Google Cloud VMs are connected to Azure Arc through installation of the Azure Connected Machine agent. Supported region and GCP label filters help teams control onboarding scope, while periodic synchronization allows newly discovered machines that meet the prerequisites and configured filters to be onboarded automatically. For Kubernetes workloads, Arc GKE onboarding (Public Preview) is also available now, bringing discovery and Azure Arc onboarding together for eligible Google Kubernetes Engine clusters. Choose the solutions that match your workloads The following Multicloud Connector solutions are available for GCP, covering resource inventory, Azure Arc onboarding, security configuration assessment, licensing, and Extended Security Updates. Supported solution What it enables Inventory View supported Google Cloud resources in a shared inventory and query their Azure representations through Azure Resource Graph. Arc VM onboarding Connect eligible GCP VMs to Azure Arc, enabling access to services such as Azure Monitor and Microsoft Defender for Cloud when configured. Arc GKE onboarding (preview) Discover and connect eligible GKE clusters to Azure Arc-enabled Kubernetes. Security Baselines (preview) Audit connected machines against security baselines, including CIS Benchmarks and the Azure security baseline, powered by Machine Configuration. SQL Server licensing and ESU Manage SQL Server licensing and subscribe to Extended Security Updates for eligible SQL Server instances. Windows Server ESU Attach an Extended Security Updates license to eligible Azure Arc-enabled Windows Server machines. Security Baselines, SQL Server licensing and ESU, and Windows Server ESU require Arc VM onboarding, along with applicable configuration, eligibility, and licensing requirements. For more information about these solutions, their prerequisites, and how to get started, see our companion article: Expanding Multicloud Management with Azure Arc | Microsoft Community Hub. Take the next step Ready to get started? Follow the Multicloud Connector setup documentation to connect your Google Cloud environment.89Views0likes0CommentsExpanding Multicloud Management with Azure Arc
For many organizations, applications run across Azure, AWS, and Google Cloud. Across that environment, teams face familiar questions: What resources do we have? Are they connected to our management tools? How do we assess their security configuration? And how do we take action without constantly switching consoles? The Azure Arc Multicloud Connector was designed to help with these scenarios. For the Multicloud Connector, we’re very excited to introduce six new solutions: Google Kubernetes Engine (GKE) onboarding, Amazon Elastic Kubernetes Service (EKS) onboarding, Windows Server Extended Security Updates (ESU), SQL Server ESU, Security Baselines, and Power Cycle Management. Building on the connector’s existing inventory and server onboarding capabilities, these solutions help organizations move from discovering their multicloud resources to managing them - with workloads staying in the clouds where they run. GKE onboarding (preview): Bring Google Cloud Kubernetes into Azure Arc The new GKE onboarding solution helps organizations discover eligible Kubernetes clusters in Google Cloud and connect them to Azure Arc-enabled Kubernetes through the multicloud connector. For platform teams, this reduces the manual work required to bring clusters into a shared management estate. Onboarding filters help scope the rollout to the intended workloads, while periodic discovery helps teams keep pace as their Kubernetes environment evolves. Once onboarded, supported clusters can use Azure Arc-enabled Kubernetes capabilities, including GitOps configuration management and applicable governance and monitoring services. EKS onboarding (preview): Connect AWS Kubernetes through the same workflow The new EKS onboarding solution brings a similar experience to Kubernetes clusters running in AWS. Teams can discover supported EKS clusters and onboard them to Azure Arc-enabled Kubernetes through the connector, using region and tag filters to align onboarding with their operational requirements. Together, EKS and GKE onboarding help organizations bring their Kubernetes fleets into a more consistent management model. Platform teams can establish a shared foundation for connected clusters while application teams retain their existing cloud platforms and deployment choices. The benefit is less repetitive onboarding work and a clearer path to applying supported Azure Arc management capabilities across cloud environments. Windows Server ESU: Support legacy workloads while modernization moves forward Modernization takes planning. The new Windows Server ESU solution brings Extended Security Updates enablement into the multicloud connector experience, helping organizations connect eligible servers with Azure Arc-enabled ESU capabilities. For qualifying workloads within an active ESU coverage period, organizations can continue receiving applicable security updates while completing their upgrade or migration plans. Bringing this workflow closer to resource discovery and onboarding helps teams address legacy server needs as part of their broader multicloud management strategy. ESU eligibility, licensing, and coverage requirements continue to apply. SQL Server ESU: Address database lifecycle needs alongside infrastructure An application’s operating system and database can reach end of support on different schedules. Protecting the server does not automatically address the database running on it. The new SQL Server ESU solution adds a database-focused workflow to the multicloud connector, helping organizations enable Azure Arc-based Extended Security Updates for eligible SQL Server workloads. This helps teams address qualifying database security-update needs while preparing to upgrade or migrate. It also brings SQL Server lifecycle management closer to the infrastructure workflows already used to discover and connect multicloud servers. Security Baselines (preview): Powered by Machine Configuration Visibility is the starting point for multicloud management. Understanding whether connected machines meet your security configuration standards is the next step. The new Security Baselines (preview) solution, powered by Azure Machine Configuration, helps organizations audit connected machines against security baselines, including CIS Benchmarks and the Azure security baseline. By bringing baseline auditing into the multicloud connector experience, teams can assess configuration against their selected standards and use the findings to identify gaps and prioritize remediation. This gives infrastructure and security teams a shared foundation for improving security posture across connected machines. Power cycle management (preview): Take action on AWS compute from Azure Sometimes the next operational step is not another assessment. It is starting a stopped instance, stopping a running one, or restarting a machine. The new Power Cycle management solution enables these actions for supported AWS EC2 instances directly from Azure. Teams can act on discovered resources without switching to the AWS console for each routine power operation. The solution supports AWS EC2 instances discovered by the connector, whether inventory-only or onboarded to Azure Arc, with the required permissions and connector configuration in place. This extends the connector’s value beyond onboarding: discovered resources can become actionable even when they have not been connected to Azure Arc. The scope is focused on starting, stopping, and restarting AWS EC2 instances. Take the next step with the Azure Arc multicloud connector With these new solutions, the multicloud connector brings more of your day-to-day operations into Azure - from connecting Kubernetes clusters and enabling eligible security updates to auditing machine configurations and taking action on AWS compute. Your workloads stay where they belong, while your teams gain a more consistent way to manage them. For solution details, prerequisites, and setup guidance, explore the Azure Arc multicloud connector documentation on Microsoft Learn.157Views0likes0CommentsAzure Arc at Microsoft Ignite 2026: Sessions, hands-on labs, and ways to connect
Microsoft Ignite 2026 is almost here! Join us November 17–20 in San Francisco or online to explore the latest innovations across Microsoft. As organizations operate across increasingly distributed environments, consistent visibility, governance, and management are more important than ever. Azure Arc extends Azure to help organizations discover, govern, secure, and operate infrastructure anywhere. This year at Ignite, we're bringing Azure Arc to life through breakout sessions, interactive table talks, and hands-on labs focused on unifying and simplifying operations across your distributed estate. Here's where to find us! Explore Azure Arc sessions at Ignite Looking to strengthen governance, simplify hybrid management, or discover what's new in onboarding and inventory? We've got sessions for you. In Breakout Session 413, explore how Azure Arc brings consistent management, security, and governance to servers, Kubernetes, databases, and applications across distributed environments. Discover how to reduce security gaps, optimize costs, and streamline operations, with a closer look at managing Arc-enabled SQL Server instances through Database Hub in Microsoft Fabric. FULL SCHEDULE: Tuesday, November 17 3:45–5:00 PM | LAB724: Govern your estate with Azure Arc and Azure Resource Manager MCP 4:10–4:55 PM | TT1691: Audit-ready everywhere: Governance for hybrid and edge AI Wednesday, November 18 9:00–9:45 AM | TT1694: Discover everything: Unified hybrid and edge AI asset inventory 10:15–11:00 AM | BRK421: Operate a global AKS fleet across regions, edge, and sovereign clouds 12:00–1:15 PM | LAB724: Govern your estate with Azure Arc and Azure Resource Manager MCP Thursday, November 19 10:45 AM-12:00 PM | LAB724: Govern your estate with Azure Arc and Azure Resource Manager MCP 1:30–2:15 PM | BRK413: Govern, secure, and operate anywhere with Azure Arc (News from Azure Arc) Friday, November 20 9:00–10:15 AM | LAB724: Govern your estate with Azure Arc and Azure Resource Manager MCP All times are Pacific. Get hands-on with Azure Arc Looking to put your knowledge into practice? Join LAB724: Govern your estate with Azure Arc and Azure Resource Manager MCP to explore practical approaches to managing and governing distributed infrastructure. With four opportunities to participate throughout the week, be sure to add the lab to your Ignite schedule. Join us online Can't make it to San Francisco? You can still participate in Microsoft Ignite through the free digital experience. Explore the Microsoft Ignite session catalog to discover sessions and build your schedule. Stay connected with Azure Arc The learning doesn't stop at Ignite! Explore these resources to continue your Azure Arc journey: Azure Arc-enabled Servers Customer Forum: Connect with the Azure Arc product team and share feedback. Azure Arc on Microsoft Learn: Explore documentation, tutorials, and technical guidance. Azure Arc Tech Community blog: Stay up to date on product news and announcements. Azure Arc on Microsoft Azure: Discover how Azure Arc helps simplify hybrid, multicloud, and edge management. See you at Ignite!631Views1like0CommentsIntroducing Azure Copilot for Azure Local: AI-powered operations for distributed infrastructure
Managing distributed infrastructure can be complex. When an issue occurs, operators may need to navigate multiple tools, review health signals and diagnostics, interpret logs, and determine the right troubleshooting steps before they can move toward resolution. Azure Copilot for Azure Local helps bring an AI-powered, agentic experience to Azure Local operations, designed to make managing and troubleshooting infrastructure simpler and more intuitive. With Azure Copilot for Azure Local, operators can start with a natural-language question, such as: “Why is my Azure Local cluster disconnected?” “Is this node healthy?” “Why did my deployment fail?” “Is my environment ready for an update?” “Check my network configuration” Azure Copilot for Azure Local translates the operator’s intent into a troubleshooting workflow, bringing together infrastructure context, diagnostics, and relevant troubleshooting knowledge to help operators understand what is happening and determine the appropriate next steps for their infrastructure. Start troubleshooting with natural language Infrastructure problems rarely begin with a clearly identified root cause. An administrator may simply know that an update failed, a node is unhealthy, connectivity was lost, or a deployment cannot continue. Azure Copilot for Azure Local provides a natural language starting point for these investigations. Rather than first determining which command to run, which diagnostic tool to open, or which troubleshooting guide to follow, operators can describe the problem they are trying to understand. Copilot can help gather relevant information, analyze the results, explain findings, and guide the operator toward potential next steps. This provides operators with a more intuitive troubleshooting experience that helps bridge the gap between observing a problem and knowing what to investigate next. Guided, multi-step troubleshooting Azure Copilot for Azure Local is designed to go beyond simply answering questions. For supported scenarios, the experience can orchestrate multiple steps of an investigation, using infrastructure context, diagnostic capabilities, and troubleshooting knowledge to help operators work through a problem. The troubleshooting journey becomes: Ask a question → Gather context → Run diagnostics → Analyse findings → Recommend next steps The operator remains in control while Copilot helps with the investigative work required to understand the issue and identify a path forward. Designed for real Azure Local operational scenarios Azure Copilot for Azure Local can assist operators across common infrastructure management and troubleshooting scenarios, including: Infrastructure health Understand the health of an Azure Local system or individual node and identify areas that may require further investigation. Connectivity troubleshooting Investigate why an Azure Local system or machine is disconnected and surface information that can help narrow down the issue. Network configuration Investigate network-related conditions and help identify configuration issues affecting the environment. Deployment troubleshooting Investigate failed deployments and help operators understand potential blockers and next steps. Update readiness Evaluate the environment before an update and identify conditions that may require attention. Diagnostics and log collection Guide diagnostic collection when deeper troubleshooting or additional evidence is required. Helping operators move from questions to outcomes Troubleshooting infrastructure often involves connecting information spread across configuration, health signals, diagnostics, logs, and troubleshooting documentation. Azure Copilot for Azure Local is evolving toward an operator-focused experience where AI agents can help connect these pieces as part of a guided investigation. The goal is simple: reduce the effort required to understand what is happening and help operators get to the right next step faster. By combining natural-language interaction with agentic troubleshooting workflows, Azure Copilot for Azure Local can help make complex diagnostic information easier to understand and help operators navigate investigations while keeping them in control of applicable actions. Public preview planned for early 2027 Azure Copilot for Azure Local is planned to enter public preview in early 2027. Once available, customers can explore the agentic experience in their Azure Local environments, evaluate real operational scenarios, and provide feedback that helps shape future capabilities. For more details, reach out to us at AzureLocalCopilotTeam@microsoft.com891Views0likes0CommentsAzure Local Storage: Choose the Architecture That Fits Your Business
Organizations modernize infrastructure in different ways. Some prioritize a simple, integrated platform; others need to preserve SAN investments, scale storage independently, or support workloads with different storage requirements. In this post, we'll explore the storage options available in Azure Local, when to use each one, and the business benefits they unlock. One Platform, Multiple Storage Architectures Azure Local brings multiple storage choices into a consistent, cloud-connected platform experience. Hyperconverged Infrastructure (Storage Spaces Direct) Storage Spaces Direct (S2D) provides a hyperconverged architecture where compute and storage are integrated into the same cluster. This model is ideal for customers looking for streamlined deployment experience, with infrastructure managed as a single platform and fewer organizational dependencies. Disaggregated Architecture (SAN Only) Azure Local supports validated external storage arrays connected through Fibre Channel or iSCSI. This architecture enables organizations to leverage existing storage investments and advanced storage services while independently scaling compute to support higher-capacity requirements. This gives customers the flexibility to work with supported storage vendors—including Dell, HPE, Hitachi, Lenovo, NetApp, and Everpure—while using the Fibre Channel or iSCSI connectivity already supported by Azure Local. Hybrid Architecture (Storage Spaces Direct + SAN) Customers can also combine Storage Spaces Direct and external storage to support different workload requirements within the same environment. This approach offers maximum flexibility, allowing organizations to align storage choices with application needs. Which Storage Option Should You Choose? If your goal is... Consider Simple integrated infrastructure Hyperconverged Expand an existing Azure Local cluster storage capacity Hybrid Reuse existing storage investments Hybrid or Disaggregated Independent compute and storage scaling Disaggregated Consolidate storage across workloads Disaggregated Advanced storage efficiency capabilities Disaggregated Flexible workload placement Hybrid Traditional three-tier architecture modernization Disaggregated Minimize infrastructure replacement Disaggregated Higher-scale compute clusters with more than 16 nodes Disaggregated Ready to size your solution? Use ODIN for Azure Local to translate workload, resiliency, growth, compute, and storage requirements into an example solution design. Use ODIN as a planning aid and validate the proposed configuration against official Azure Local documentation and with your preferred hardware and storage partners. Before finalizing your design, review External storage support for Azure Local for supported architectures and protocols, and Supported SAN solutions on Azure Local for validated storage partners and configurations. Use the comparison above to identify the most suitable architecture, then use ODIN, official Azure Local documentation, and partner guidance to validate workload sizing, supported configurations, and operational requirements. Modern Infrastructure Demands More Storage Flexibility Storage architecture decisions increasingly depend on more than capacity and performance. Organizations must also account for operational processes, maintenance planning, existing infrastructure, efficiency services, resiliency, and expected growth. These priorities influence whether an organization chooses an integrated, disaggregated, or hybrid architecture—and which benefits matter most in its environment. The following benefits explain where external storage can add value within that decision. Benefits of External Storage with Azure Local Protect Existing Investments Many organizations already operate enterprise storage platforms that support critical business applications. Azure Local enables customers to modernize compute infrastructure while continuing to leverage existing storage investments, operational expertise, backup strategies, and storage management processes. Get More Value from Every Terabyte Storage efficiency is becoming increasingly important as organizations scale virtualized environments, desktop infrastructure, databases, and application workloads. Many enterprise storage platforms offer advanced services such as compression, deduplication, thin provisioning, and capacity optimization. Organizations can leverage these capabilities while maintaining consistent Azure Local management experience. Spend Less Time Maintaining Infrastructure Operational efficiency is often just as important as infrastructure capabilities. Because compute and storage are separated in SAN-based architectures, organizations can independently manage storage and compute infrastructure. This can help simplify maintenance planning and reduce storage-related operational activities during maintenance events. Customers frequently cite more predictable maintenance windows, simplified update planning, mature storage monitoring practices, and reduced operational complexity. Scale on Your Terms One of the primary reasons organizations adopt external storage is flexibility. In hyperconverged environments, compute and storage typically scale together. With disaggregated storage, organizations can expand storage capacity independently from compute resources. This can be particularly valuable when storage growth outpaces CPU or memory requirements. Designed for Enterprise Resiliency Azure Local pairs cloud-connected infrastructure with the storage maturity Windows Server has refined over many generations. For external storage, that means working with the same well-understood technologies you already rely on—Fibre Channel and iSCSI connectivity, MPIO, dual fabrics, redundant controllers, and Cluster Shared Volumes—applied to the Azure Local platform. Because these are proven, standard building blocks, you have the flexibility to design highly available storage that fits your existing SAN investments and operational practices, rather than adapt to an unfamiliar model. For implementation requirements and configuration steps—including Fibre Channel, iSCSI, MPIO, array-side configuration, and presenting SAN-backed volumes as Cluster Shared Volumes see : Connect an external storage array to Azure Local. Real-World Scenarios Streamlined Infrastructure for Distributed Locations Retail stores, branch offices, and back-office environments can use a hyperconverged architecture to run applications on an integrated compute and storage platform. This approach simplifies deployment and day-to-day operations for locations that need consistent infrastructure without dedicated storage teams. Flexible Workload Placement Manufacturing and healthcare organizations can use a hybrid architecture when some workloads are best served by integrated Storage Spaces Direct and others require external SAN capacity or established storage services. This allows application teams to place workloads on the storage option that best meets their performance, resiliency, and operational requirements. Modernizing while Preserving SAN Investments A manufacturing organization, financial institution, or enterprise datacenter with established SAN platforms and processes can use a disaggregated architecture to modernize compute without redesigning storage operations, retraining teams, or immediately replacing proven infrastructure. Scaling Storage as Data Needs Grow Data-intensive environments—including manufacturing, fintech, and enterprise datacenters—may find that storage capacity grows faster than compute demand. A disaggregated architecture allows them to scale storage and compute independently, helping optimize infrastructure investments over time. Cost and Licensing Considerations Azure Local uses a monthly service fee based on the deployment configuration: Hyperconverged deployments (S2D only): Compute and storage are integrated in the same cluster using Storage Spaces Direct, with no external SAN storage. A monthly service fee of $10 per physical core/month applies. Disaggregated (SAN only), and hybrid storage configurations (S2D with SAN): Disaggregated deployments use external SAN storage instead of Storage Spaces Direct, while hybrid deployments with external storage combine Storage Spaces Direct with external SAN storage. Using external SAN storage has a monthly service fee of $20.1 per physical core/month applies. Prices are subjected to change. For current pricing details and applicable terms, visit Azure Local Pricing | Microsoft Azure. Choosing the Right Fit for Your Business Start with the operating model and workload requirements you need to support, then choose the architecture that best fits them. Azure Local provides a consistent platform experience across hyperconverged, disaggregated, and hybrid deployments. That consistency lets organizations modernize without treating storage architecture as a one-time, irreversible choice. The right storage strategy is the one that fits your workloads, operations, and growth plans. Learn more: Storage Spaces Direct overview; External storage support for Azure Local; Supported SAN solutions on Azure Local; Connect an external storage array to Azure Local; Azure Local pricing; and Azure Hybrid Benefit for Azure Local.804Views2likes3CommentsWorkload Orchestration in the Azure portal is now available: Deploy in minutes, scale with ease
Edge deployments rarely stay simple for long. What begins as an application running on a single Kubernetes cluster can quickly expand across stores, factories, branches, or other distributed locations, each having different configuration needs. That is exactly where workload orchestration for Azure Arc comes in. Workload orchestration helps teams manage that complexity by providing a centralized approach to consistently define, configure, and deploy applications across distributed cloud, on-premises, and edge environments, all while catering to custom configuration needs of individual sites and deployment targets. See the experience in action Evaluating a new deployment approach often starts slowly: study the documentation, package an application, complete the setup, and only then decide whether it fits. The Azure portal reverses that order with its jumpstart onboarding experience. Bring your Azure Arc-enabled Kubernetes cluster and deploy a pre-packaged application in minutes. Whether you are validating a proof of concept or introducing the product to your broader team, the new portal onboarding experience turns the end-to-end workflow into something you can quickly try on your own cluster. Scale from first deployment to production Once you have validated the first deployment, you can evolve the same approach for production. Onboard your infrastructure into workload orchestration, organize your deployment sites into hierarchies, and define shared configurations for all deployments – all without leaving the portal. This lets you expand from one cluster to a distributed fleet while retaining centralized governance, repeatability, and site-level flexibility. Ready to try it? Try now by deploying your first application with workload orchestration in the Azure portal. Explore the product documentation for the complete set of capabilities.533Views0likes0CommentsEpisode 1: Onboarding Azure Arc at Scale | The Azure Arc Check-In
Once a month the Azure Arc team will release an episode covering a variety of topics. To request a topic or view additional episodes please visit: aka.ms/the-azure-arc-check-in Episode 1: Onboarding Azure Arc at Scale Scenario: Imagine your organization has 1,000 Windows and Linux servers spread across multiple locations. You want them all in Azure Arc, but first you need to deploy the Azure Connected Machine agent at scale. Try now in Azure aka.ms/aaci-episode1 Why onboarding strategy matters Interactive sign-in works well for testing and proof-of-concepts, but it quickly becomes impractical when you’re onboarding large server estates. At scale, organizations need a deployment model that can: Automate onboarding across many machines Align with existing management tooling Apply consistent configuration and governance from day one Minimize manual effort and human error This episode focuses on using non-interactive authentication and automation to onboard large server fleets efficiently. One of the key recommendations is to use a dedicated authentication mechanism designed for scale rather than relying on interactive administrator sign-ins. Onboard a Linux fleet with Ansible The Ansible deployment begins with an Ansible node that is already connected to Azure Arc. The deployment uses the credential on the Ansible node to deploy the Azure Connected Machine agent to the Linux fleet. To enable this, the managed identity of the Ansible node has the Azure Connected Machine Onboarding role in Azure assigned. Below are the steps for role assignment in the Azure portal: Open the resource group where the servers will be deployed. In Access control, add a role assignment. Select the Azure Connected Machine Onboarding role. Choose managed identities, select Machine - Azure Arc, and find the Ansible node. Review and assign the role. Configure the Ansible playbook With the permissions in place, the deployment uses three files: inventory.ini: Represents the machines configured by the playbook. arc-vars.yml: Contains non-secret configuration, including the resource group name, subscription and tenant IDs, location, and tags. arc-onboard.yml: References arc-vars.yml and configures the playbook to use managed identity, or MSI, for authentication. After the playbook runs, Ansible deploys the Azure Connected Machine agent to the Linux fleet. You can return to the resource group, refresh the view, and verify that your Linux machines appear as Azure Arc connected servers. Onboard Windows machines with Group Policy For Windows Server environments joined to Active Directory, Group Policy remains one of the simplest and most scalable deployment mechanisms. The process includes: Creating the required onboarding identity Preparing a shared location for deployment assets Downloading the Azure Arc GPO deployment package Generating a Group Policy Object with the required settings Linking that GPO to the appropriate organizational unit (OU) Allowing targeted servers to automatically onboard during policy refresh cycles For organizations that already manage Windows Server through Active Directory, this approach enables onboarding at scale without introducing additional management infrastructure. FAQs What is the best way to onboard servers to Azure Arc at scale? For large Windows and Linux server environments, use automated deployment with non-interactive authentication rather than signing in interactively on each machine. This approach lets you deploy the Azure Connected Machine agent consistently across many servers while reducing manual effort and human error. Azure Connected Machine Agent Deployment Options - Azure Arc Can I use Ansible to onboard Linux servers to Azure Arc? Yes. You can use an Azure Arc-enabled Ansible node to deploy the Azure Connected Machine agent across a Linux server fleet. In the approach demonstrated here, the Ansible node uses its managed identity, which is assigned the Azure Connected Machine Onboarding role, to authenticate the deployment. Connect machines to Azure Arc at scale using Ansible - Azure Arc Can I use Group Policy to onboard Windows servers to Azure Arc? Yes. Group Policy can automate Azure Arc onboarding for Windows Server machines that are joined to Active Directory. The process uses a Group Policy Object linked to the appropriate organizational unit, allowing targeted servers to onboard automatically during Group Policy refresh cycles. Connect machines at scale using Group Policy with a PowerShell script - Azure Arc What files are needed to onboard Linux servers to Azure Arc with Ansible? The Ansible deployment shown in this episode uses three files: inventory.ini to identify the target machines, arc-vars.yml to store non-secret configuration such as subscription, tenant, resource group, location, and tags, and arc-onboard.yml to run the onboarding playbook using managed identity authentication. Should I use Ansible or Group Policy for Azure Arc onboarding? Use Ansible when onboarding Linux servers in an environment that already uses Ansible playbooks and automation. Use Group Policy when onboarding domain-joined Windows servers managed through Active Directory. Both approaches help organizations automate Azure Connected Machine agent deployment by using tools already present in their server-management environment. Additional options are available for onboarding servers at scale. See Azure Connected Machine Agent deployment options.789Views1like0CommentsAzure Arc Server June Forum
Please find the recording for the monthly Azure Arc Server Forum on YouTube! During the June 2026 Azure Arc Server Forum, we discussed: Arc Server AI Agent assists with onboarding and troubleshooting through an integrated LLM with plans for surfacing the experience through Azure Copilot and in Azure Portal. Azure Arc Multicloud Connector Updates focused on both the Public Preview of the Google Cloud Platform (GCP) Connector and Public Preview of Azure Arc-enablement of detected EKS Clusters. WS 2016 ESU Updates with planned changes versus WS 2012 ESUs and expected timelines anticipating the WS 2016 end-of-support date of January 2027. Note, WS 2012 ESUs will end in October 2026. SQL 2016 ESU Updates discussed enrollment processes, licensing basics, and overall guidance with end-of-support in July 2026. To sign up for the Azure Arc Server Forum and newsletter, please register with contact details at https://aka.ms/arcserverforumsignup/. For the latest agent release notes, check out What's new with Azure Connected Machine agent - Azure Arc | Microsoft Learn. We are skipping July and August, and will resume after summer holidays with the September forum to be held on Thursday, September 17 at 9:30 AM PST / 12:30 PM EST. Finally, I wanted to thank everyone for the attendance and community over the last few years, I will no longer be leading the community calls. Please stay in touch, and Mason Torres, Yunis Hussein, and Meagan McCrory from the Arc PM team will be taking the community forward. We look forward to you joining us, thank you!425Views1like0Comments