M365Con 2027 – free online conference · 11–22 Jan 2027 · 120 sessions m365con.net

Azure Connected Machine agent

Product

The lightweight agent installed on servers outside Azure to connect them to Azure Arc. It connects outbound over HTTPS, handles extensions and reports inventory so the machine appears as an Azure resource.

◆ PRODUCTAzure Connected MachineagentM365.FM
Title graphic: Azure Connected Machine agent (Product)

Relationships

Azure Connected Machine agent is a product and part of Microsoft Azure.

Description

The Azure Connected Machine agent is the software installed on Windows and Linux machines that run outside Azure so they can be managed from Azure through Azure Arc. These machines may sit in a corporate network or at another cloud provider. Once the agent is installed and connected, the server becomes an Azure Arc-enabled server and is projected into Azure's control plane as an Azure resource. The agent is part of Microsoft Azure and is described in Microsoft documentation as a lightweight component.

The agent is built from several parts. The Hybrid Instance Metadata Service handles the connection to Azure and the machine's identity. A machine configuration agent checks and enforces policy compliance on the server. An extension agent installs, removes and updates VM extensions. An Azure Arc proxy bundles the network traffic of these services. According to the documentation, the agent also reports inventory: collected metadata covers the operating system, computer name, hardware details, network interfaces and detected database software, and the documentation states that no personal data is collected.

On the network side, the agent connects outbound over HTTPS, using TCP port 443, with options for proxy configuration. The episode "Azure Arc - Simply Explained" lists this outbound communication on port 443 as a requirement before servers can be connected, and names supported Linux distributions such as Red Hat Enterprise Linux versions 7 to 9, along with others like CentOS, Debian and Oracle Linux. Because the connection is initiated from the server toward Azure, the approach does not depend on opening inbound access to the machine.

Installation differs by platform. On Windows the agent is delivered as an MSI package. On Linux it is installed from an rpm or deb package or through a script. After installation the agent sends a heartbeat to Azure every five minutes. The documentation notes that a gap longer than fifteen minutes can indicate that the server is offline or that the connection is blocked, which makes the heartbeat a practical starting point when troubleshooting a machine that no longer reports in.

Typical decisions around the agent involve version currency and resource use. Only agent versions not older than one year are supported, so environments with many connected servers need a process for keeping the agent updated. CPU limits apply to the machine configuration and extension services, and from version 1.39 these limits can be adjusted. The documentation also points out that the Azure Monitor Agent is a separate agent and does not replace the Connected Machine agent; the two serve different purposes, and the Connected Machine agent is the one that establishes the Azure Arc connection.

The agent is what makes the unified management model of Azure Arc possible. The episode "Azure Arc - Simply Explained" says that installing the Azure Connected Machine Agent transforms a server into an Azure Arc-enabled server, integrating it into Azure's control plane. From there, servers can be managed through a single interface, with consistent policies and governance applied across on-premises and multi-cloud environments. In that framing, the agent is the entry point: without it, a server outside Azure remains outside Azure Arc management.

Overview compiled with AI from M365.FM episodes and the facts on this page. You can improve it with the edit button below.

TypeProduct
DocumentationAzure Connected Machine agent – Microsoft Learn learn.microsoft.com

Episodes about Azure Connected Machine agent

Episodes in which Azure Connected Machine agent is discussed:

Azure Arc - Simply Explained

2026-07-16 · YouTube: Azure Arc - Simply Explained

Azure Arc extends Azure's management, security, and governance capabilities beyond the Azure cloud, allowing you to manage servers, Kubernetes clusters, databases, and other resources running on-premises, at the edge, or in other cloud providers from a single…

Frequently asked questions

Questions marked with AI were written with AI from the facts on this page.

What does the Azure Connected Machine agent do? (AI)

It connects Windows and Linux machines running outside Azure to Azure Arc, handles the machine's identity, enforces policy compliance, manages VM extensions and reports inventory so the server appears as an Azure resource.

What network access does the agent need? (AI)

It connects outbound over HTTPS on TCP port 443, with options for proxy configuration. The episode "Azure Arc - Simply Explained" lists this as a requirement for connecting servers.

Does the Azure Monitor Agent replace the Azure Connected Machine agent? (AI)

No. According to the Microsoft documentation, the Azure Monitor Agent is a separate agent and does not replace the Connected Machine agent.

Related topics in brief

Topics linked to Azure Connected Machine agent, each briefly explained:

All relationships of Azure Connected Machine agent, grouped by type of relationship:

Part of

Offerings of which Azure Connected Machine agent is a part:

Glossary

Community wiki

Short info above, community knowledge below: add practical tips, examples or corrections. New contributions are reviewed first; trusted members publish directly.

Experts and companies for this topic

Nobody has listed this topic yet. Add it to your profile.

Experts on related topics

Experts on topics related to Azure Connected Machine agent, each with the topic that connects them:

Sources

Maintained by Mirko Peters (Microsoft MVP) · Last updated: