You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -36,7 +36,7 @@ The following prerequisites must be met prior to installing the Azure Monitor ag
36
36
| Any role that includes the action *Microsoft.Resources/deployments/**| <ul><li>Subscription and/or</li><li>Resource group and/or </li></ul> | To deploy ARM templates |
37
37
-**Non-Azure**: For installing the agent on physical servers and virtual machines hosted *outside* of Azure (i.e. on-premises) or in other clouds, you must [install the Azure Arc Connected Machine agent](../../azure-arc/servers/agent-overview.md) first (at no added cost)
38
38
-**Authentication**: [Managed identity](../../active-directory/managed-identities-azure-resources/overview.md) must be enabled on Azure virtual machines. Both system-assigned and user-assigned managed identities are supported.
39
-
-**User-assigned**: This is recommended for largescale deployments, configurable via [built-in Azure policies](#using-azure-policy). It can be created once and shared across multiple VMs, and is thus more scalable than system-assigned. If User-assigned managed identity is used, you must pass the managed identity details to Azure Monitor agent via extension settings:
39
+
-**User-assigned**: This is recommended for large-scale deployments, configurable via [built-in Azure policies](#using-azure-policy). You can create a user-assigned managed identity once and share it across multiple VMs, and is thus more scalable than a system-assigned managed identity. If you use a user-assigned managed identity, you must pass the managed identity details to Azure Monitor Agent via extension settings:
40
40
```json
41
41
{
42
42
"authentication": {
@@ -47,7 +47,7 @@ The following prerequisites must be met prior to installing the Azure Monitor ag
47
47
}
48
48
}
49
49
```
50
-
We recommend using `mi_res_id` as the `identifier-name`, and the below sample commands will only show usage with `mi_res_id` for the sake of brevity. For more details on `mi_res_id`, `object_id`, and `client_id`, visit the [managed identity docs](../../active-directory/managed-identities-azure-resources/how-to-use-vm-token.md#get-a-token-using-http).
50
+
We recommend using `mi_res_id` as the `identifier-name`. The sample commands below only show usage with `mi_res_id` for the sake of brevity. For more details on `mi_res_id`, `object_id`, and `client_id`, see the [managed identity documentation](../../active-directory/managed-identities-azure-resources/how-to-use-vm-token.md#get-a-token-using-http).
51
51
- **System-assigned**: This is suited for initial testing or small deployments. When used at scale (for example, for all VMs in a subscription) it results in substantial number of identities created (and deleted) in Azure AD (Azure Active Directory). To avoid this churn of identities, it is recommended to use user-assigned managed identities instead. **For Arc-enabled servers, system-assigned managed identity is enabled automatically** (as soon as you install the Arc agent) as it's the only supported type for Arc-enabled servers.
52
52
- This is not required for Azure Arc-enabled servers. The system identity will be enabled automatically if the agent is installed via [creating and assigning a data collection rule using the Azure portal](data-collection-rule-azure-monitor-agent.md#create-data-collection-rule-and-association).
53
53
- **Networking**: The [AzureResourceManager service tag](../../virtual-network/service-tags-overview.md) must be enabled on the virtual network for the virtual machine. Additionally, the virtual machine must have access to the following HTTPS endpoints:
Copy file name to clipboardExpand all lines: articles/azure-monitor/agents/resource-manager-agent.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,13 +18,13 @@ This article includes sample [Azure Resource Manager templates](../../azure-reso
18
18
19
19
The samples in this section install the Azure Monitor agent on Windows and Linux virtual machines and Azure Arc-enabled servers.
20
20
21
-
> [!IMPORTANT]
22
-
> The below templates do not perform the prerequisite [creation](../../active-directory/managed-identities-azure-resources/how-manage-user-assigned-managed-identities.md?pivots=identity-mi-methods-arm#create-a-user-assigned-managed-identity-3) and [assignment](../../active-directory/managed-identities-azure-resources/qs-configure-template-windows-vm.md#user-assigned-managed-identity) of a user-assigned managed identity or [enablement](../../active-directory/managed-identities-azure-resources/qs-configure-template-windows-vm.md#system-assigned-managed-identity) of system-assigned managed identity. A managed identity is required for Azure Monitor agent to collect and publish data. User-assigned managed identities are _strongly recommended_ over system-assigned managed identities due to their ease of management at scale.
21
+
### Prerequisites
23
22
24
-
> [!IMPORTANT]
25
-
> To configure data collection for these agents, you must also deploy [Resource Manager templates data collection rules and associations](./resource-manager-data-collection-rules.md).
23
+
To use the templates below, you'll need:
24
+
- To [create a user-assigned managed identity](../../active-directory/managed-identities-azure-resources/how-manage-user-assigned-managed-identities.md?pivots=identity-mi-methods-arm#create-a-user-assigned-managed-identity-3) and [assign the user-assigned managed identity](../../active-directory/managed-identities-azure-resources/qs-configure-template-windows-vm.md#user-assigned-managed-identity), or [enable a system-assigned managed identity](../../active-directory/managed-identities-azure-resources/qs-configure-template-windows-vm.md#system-assigned-managed-identity). A managed identity is required for Azure Monitor agent to collect and publish data. User-assigned managed identities are _strongly recommended_ over system-assigned managed identities due to their ease of management at scale.
25
+
- To configure data collection for Azure Monitor Agent, you must also deploy [Resource Manager template data collection rules and associations](./resource-manager-data-collection-rules.md).
26
26
27
-
## Permissions required
27
+
###Permissions required
28
28
29
29
| Built-in Role | Scope(s) | Reason |
30
30
|:---|:---|:---|
@@ -33,7 +33,7 @@ The samples in this section install the Azure Monitor agent on Windows and Linux
33
33
34
34
### Azure Windows virtual machine
35
35
36
-
The following sample installs the Azure Monitor agent on an Azure Windows virtual machine. Based on your desired authentication method, choose the appropriate template below.
36
+
The following sample installs the Azure Monitor agent on an Azure Windows virtual machine. Use the appropriate template below based on your chosen authentication method.
The following sample installs the Azure Monitor agent on a Azure Linux virtual machine. Based on your desired authentication method, choose the appropriate template below.
209
+
The following sample installs the Azure Monitor agent on an Azure Linux virtual machine. Use the appropriate template below based on your chosen authentication method.
0 commit comments