Microsoft announced the preview on its Azure Arc Blog. The setup is short: the connector runs on the Configuration Manager site server, you pick device collections in the Configuration Manager console, and those machines appear in Azure with their roles, services and applications.
Before anyone emails the change advisory board, note one limit. This is inventory, not management. The rest of this piece explains what the connector does, what it doesn't do, and how to run a pilot.
What the connector actually does
For years, an organisation that wanted Azure to know about its on-premises servers had one main option: onboard each machine as an Azure Arc-enabled server, which means installing the Connected Machine agent on that machine. Configuration Manager already helps with that. Microsoft Learn documents how admins can use Configuration Manager to run a PowerShell script that automates at-scale onboarding to Azure Arc-enabled servers. The agent still ends up on every target machine, though.
The new connector reverses that model. Microsoft's announcement describes it like this:
- One install, on the site server. The connector is deployed once, on the Configuration Manager site server. The managed machines don't get anything new.
- The site server becomes the bridge. Microsoft Learn's preview documentation says the Configuration Manager site server connects to Azure Arc using the Azure Connected Machine agent.
- You choose the scope by collection. Admins pick device collections in the Configuration Manager console. Machines outside those collections stay out of Azure.
- Existing data is reused. The inventory comes from data Configuration Manager already holds, including server roles, services and installed applications.
The Azure Governance and Management blog's Machine Inventory preview post confirms the scope. It says publishing collections through the connector creates read-only Azure representations of the selected servers without installing agents on each managed server. The same post names the resource type behind collection membership as microsoft.guestconfiguration/devicecollections, which helps if you plan to write queries.
In short: you install one agent on one site server, choose collections in the console, and Azure gets a read-only view of the servers Configuration Manager already knows about.
The fine print: read-only means read-only
Microsoft is clear about the boundary, and admins should be too. The Learn documentation says the Configuration Manager connector provides a read-only inventory view. It does not hand management of the selected machines over to Azure, nor does it deploy the Connected Machine Agent to them.
In practice:
- Configuration Manager stays in charge. It remains the source of inventory and the management authority for those machines.
- Seeing a machine in Azure doesn't make it an Arc-enabled server. Agent-based features still need the agent on that machine. Microsoft lists update management, security, monitoring and Extended Security Updates as examples.
- Full onboarding uses the existing methods. Microsoft points admins to the PowerShell onboarding script or a custom task sequence. Both are long-standing options. Microsoft's deployment options page lists connect machines by running PowerShell scripts with Configuration Manager and connect machines with a Configuration Manager custom task sequence as at-scale Windows methods.
So the connector doesn't replace Arc onboarding. Microsoft positions it as the first step: see the whole estate, then decide which servers need full Arc management.
What you can do with the inventory
According to Microsoft's announcement, the connector gives you:
- One inventory view. Azure resources, Arc-enabled servers and Configuration Manager machines appear together.
- Queries at scale through Azure Resource Graph. You can query machines, roles, services and applications without a Log Analytics workspace, so there's no workspace to set up or pay for before the first query.
- Gradual expansion. Start with a pilot collection, check the results, then add more.
- A shortlist for onboarding. The inventory can show which machines should be fully onboarded to Azure Arc next.
The Machine Inventory preview post describes the connector as one of several data sources. Azure VMs and Arc-enabled servers use built-in Azure policies through Machine Configuration, while servers managed through Configuration Manager use the connector. It also positions Azure Resource Graph as the place to query the inventory, with the portal as a starting point. In short, Microsoft wants to merge agent-based and agentless inventory into one queryable dataset.
Prerequisites
Microsoft's announcement lists these requirements:
| Requirement | Detail |
|---|---|
| Azure basics | An Azure subscription, a resource group and your Microsoft Entra tenant ID |
| Azure permissions | Rights to connect the site server to Azure Arc and to manage connected inventory resources in the target resource group |
| Site server access | Admin access, including rights to approve and install console extensions |
| Agent version | Azure Connected Machine agent 1.70 or later on the site server |
| Scripting runtime | Windows PowerShell 5.1 |
| Pilot scope | A small device collection for the first test |
The Learn documentation repeats the agent requirement: Azure Connected Machine agent version 1.70 or later on the Configuration Manager site server.
One caution. The older script-based onboarding guide requires Configuration Manager version 1706 or higher and specific SMS Scripts permissions. Those requirements apply to the per-machine agent workflow. Don't assume they apply to the connector until its own documentation says so.
Setting up a pilot, step by step
The portal workflow in Microsoft's announcement is short:
- In the Azure portal, open Azure Arc.
- Under Supported environments, select On-premises connectors, then Create.
- Download the generated onboarding script and run it as Administrator on the site server.
- Approve the console extension, then choose your collections.
Microsoft Learn's preview documentation explains what the script does. It installs the Azure Connected Machine agent, discovers the Configuration Manager site code, connects the site server as the Configuration Manager connector, and enables automatic agent upgrade. It also installs Az.Accounts as needed, disables Arc VM extension deployment on the site server, and publishes the Configuration Manager console extension.
Two points matter for change control:
- Extension deployment is turned off on the site server. Your site server's Arc resource is set up as a connector, not as a general-purpose Arc server. If you expected to push other Arc VM extensions to it, check this first.
- Agent auto-upgrade is turned on. Some organisations pin agent versions on infrastructure servers. Make sure that policy fits.
After the script runs, the documentation says to approve the Azure Arc console extension if your hierarchy settings require approval. In the console, it directs admins to Administration > Overview > Cloud Services, then to the Azure Arc devices node. There you select Arc Connected Devices from the ribbon or context menu, finish the wizard, and check the refreshed workspace. That workspace shows the inventory status of each device collection.
What success looks like
- The Azure Arc devices workspace in the console shows your pilot collection with a published inventory status.
- The selected machines appear in Azure as read-only resources in the target resource group.
- Azure Resource Graph queries return the machines with their roles, services and applications. Microsoft's documentation includes sample queries. One sample asks you to replace <site-server-resource-id> with the Azure resource ID of the Configuration Manager site server, which lets you filter results by the connector they came from.
If it doesn't work
Microsoft hasn't published connector-specific troubleshooting yet, so these are general checks rather than documented fixes:
- Agent version: run
azcmagent versionon the site server and confirm it's 1.70 or later. - Elevation: the script must run as Administrator.
- Approval: if the console extension is waiting for hierarchy approval, collection selection can't continue.
- Permissions: the account needs rights to connect the site server and to manage connected inventory resources in the target resource group.
Analysis: why this matters, and what to watch
This is a sensible move by Microsoft. Many Configuration Manager estates are large and slow to change. Asking teams to deploy an agent to thousands of servers just to see what's there has always been a hard sell, especially for servers that will never need Azure management. The connector reuses data Configuration Manager already collects.
There are trade-offs:
- Preview status. Microsoft's announcement doesn't state a sync interval, machine limits, pricing, supported regions or a general availability date. Treat the connector as a pilot tool for now, not a compliance source.
- Data freshness. The Azure view can only be as current as Configuration Manager's own hardware and software inventory cycles. If clients haven't reported in weeks, Azure will show the same stale data.
- A single point of failure. One site server now carries Azure connectivity for the whole published scope. That is easier to secure than thousands of agents, but it's also a single dependency.
- Microsoft's direction. The announcement says Configuration Manager is "a natural place to start" and that Azure Arc should eventually see inventory wherever it lives. That's a stated goal, not a roadmap, and no other inventory sources are announced.
Some readers will note that Microsoft keeps finding ways to bring on-premises estates into Azure. That's true, and Microsoft clearly wants to bring those servers into Azure. Still, a read-only, opt-in, collection-scoped preview is about as low-risk as these offers get. You can try it on a lab collection, run a few Resource Graph queries, and decide whether it's useful.
Bottom line: if your server inventory lives in Configuration Manager and leadership keeps asking for one view of the hybrid estate, a small pilot collection is a cheap way to test this. Just remember that the connector shows your servers in Azure but doesn't manage them.
References
- Announcing the Configuration Manager connector for Azure Arc (preview) Azure Arc Blog · 2026-11-17T18:52:52+00:00
- Announcing the Configuration Manager connector for Azure Arc (preview) | Microsoft Community Hub techcommunity.microsoft.com
- Connect machines at scale by running PowerShell scripts with Configuration Manager - Azure Arc | Microsoft Learn learn.microsoft.com