Azure Arc-enabled servers prerequisites
Microsoft's edit ·
Microsoft's commit message in MicrosoftDocs/azure-management-docs · commit be82c0b · +11 −9 lines · also on GitHub
11
---
22
title: Connected Machine agent prerequisites
33
description: Learn about the prerequisites for installing the Connected Machine agent for Azure Arc-enabled servers.
4
−ms.date: 11/26/2024
4
+ms.date: 01/24/2025
55
ms.topic: conceptual
66
ms.custom: devx-track-azurepowershell
77
---
⋯ 2 unchanged lines
1010
1111
This article describes the basic requirements for installing the Connected Machine agent to onboard a physical server or virtual machine to Azure Arc-enabled servers. Some [onboarding methods](deployment-options.md) may have more requirements.
1212
13
+The prerequisites for the Connected Machine agent are:
14
+
15
+- [Ensure supported environments are used](#supported-environments).
16
+- [Ensure supported operating systems and architectures are used](#supported-operating-systems).
17
+- [Verify necessary software requirements are met](#software-requirements).
18
+- [Confirm required permissions and Azure roles are assigned](#required-permissions).
19
+- [Register required Azure resource providers](#azure-resource-providers).
20
+
1321
## Supported environments
1422
1523
Azure Arc-enabled servers support the installation of the Connected Machine agent on physical servers and virtual machines hosted outside of Azure, including on platforms like:
⋯ 117 unchanged lines
133141
For Linux, the relevant package repository will only contain releases that are applicable, so no special considerations are required.
134142
135143
136
−### Client operating system guidance
144
+## Client operating system guidance
137145
138146
The Azure Arc service and Azure Connected Machine Agent are supported on Windows 10 and 11 client operating systems only when using those computers in a server-like environment. That is, the computer should always be:
139147
⋯ 3 unchanged lines
143151
144152
For example, a computer running Windows 11 that's responsible for digital signage, point-of-sale solutions, and general back office management tasks is a good candidate for Azure Arc. End-user productivity machines, such as a laptop, which may go offline for long periods of time, shouldn't use Azure Arc and instead should consider [Microsoft Intune](/mem/intune) or [Microsoft Configuration Manager](/mem/configmgr).
145153
146
−### Short-lived servers and virtual desktop infrastructure
154
+## Short-lived servers and virtual desktop infrastructure
147155
148156
Microsoft doesn't recommend running Azure Arc on short-lived (ephemeral) servers or virtual desktop infrastructure (VDI) VMs. Azure Arc is designed for long-term management of servers and isn't optimized for scenarios where you are regularly creating and deleting servers. For example, Azure Arc doesn't know if the agent is offline due to planned system maintenance or if the VM was deleted, so it won't automatically clean up server resources that stopped sending heartbeats. As a result, you could encounter a conflict if you re-create the VM with the same name and there's an existing Azure Arc resource with the same name.
149157
⋯ 32 unchanged lines
182190
* To read, modify, and delete a machine, you must have the [Azure Connected Machine Resource Administrator](/azure/role-based-access-control/built-in-roles#azure-connected-machine-resource-administrator) role for the resource group.
183191
* To select a resource group from the drop-down list when using the **Generate script** method, you'll also need the [Reader](/azure/role-based-access-control/built-in-roles#reader) role for that resource group (or another role that includes **Reader** access).
184192
* When associating a Private Link Scope with an Arc Server, you must have Microsoft.HybridCompute/privateLinkScopes/read permission on the Private Link Scope Resource.
185
−
186
−## Azure subscription and service limits
187
−
188
−There are no limits to the number of Azure Arc-enabled servers you can register in any single resource group, subscription, or tenant.
189
−
190
−Each Azure Arc-enabled server is associated with a Microsoft Entra object and counts against your directory quota. See [Microsoft Entra service limits and restrictions](/azure/active-directory/enterprise-users/directory-service-limits-restrictions) for information about the maximum number of objects you can have in a Microsoft Entra directory.
191193
192194
## Azure resource providers
193195
⋯ 37 unchanged lines
Microsoft's Markdown source from MicrosoftDocs/azure-management-docs, © Microsoft Corporation, under CC BY 4.0. Changed lines with up to 3 unchanged lines around each; ChangeIntel kept this copy 9 Oct 22:05 UTC. The commit date is when the source changed, which can be hours or days before Learn published it.