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
This article lists the requirements and prerequisites for Azure Arc VM management on Azure Local. We recommend that you review the requirements and complete the prerequisites before you manage your Arc VMs.
16
+
This article lists the requirements and prerequisites for Azure Local VMs enabled by Azure Arc. We recommend that you review the requirements and complete the prerequisites before you manage your Azure Local VMs.
17
17
18
18
## Azure requirements
19
19
20
20
The Azure requirements include:
21
21
22
-
- To provision Arc VMs and VM resources such as virtual disks, logical network, network interfaces, and VM images through the Azure portal, you must have access to an Azure subscription with the appropriate RBAC role and permissions assigned. For more information, see [RBAC roles for Azure Local Arc VM management](./assign-vm-rbac-roles.md#about-builtin-rbac-roles).
22
+
- To provision Azure Local VMs and VM resources such as virtual disks, logical network, network interfaces, and VM images through the Azure portal, you must have access to an Azure subscription with the appropriate RBAC role and permissions assigned. For more information, see [RBAC roles for Azure Local VMs](./assign-vm-rbac-roles.md#about-builtin-rbac-roles).
23
23
24
-
-Arc VM management infrastructure is supported in the regions documented in the [Azure requirements](../concepts//system-requirements-23h2.md#azure-requirements). For Arc VM management on Azure Local, all entities must be registered, enabled, or created in the same region.
24
+
-Azure Local VM infrastructure is supported in the regions documented in the [Azure requirements](../concepts//system-requirements-23h2.md#azure-requirements). For Azure Local VMs, all entities must be registered, enabled, or created in the same region.
25
25
26
-
The entities include your Azure Local instance, Arc Resource Bridge, Custom Location, VM operator, virtual machines created from Arc and Azure Arc for Servers guest management. These entities can be in different or same resource groups as long as all resource groups are in the same region.
26
+
The entities include your Azure Local instance, Azure Arc resource bridge, Custom Location, VM operator, virtual machines created from Arc and Azure Arc for Servers guest management. These entities can be in different or same resource groups as long as all resource groups are in the same region.
27
27
28
28
29
29
## Azure Local requirements
30
30
31
-
- You have access to an Azure Local instance that is deployed, has an Arc Resource Bridge, and a custom location.
31
+
- You have access to an Azure Local instance that is deployed, has an Azure Arc resource bridge, and a custom location.
32
32
33
-
- Go to the **Overview > Server** page in the Azure Local resource. Verify that **Azure Arc** shows as **Connected**. You should also see a custom location and an Arc Resource Bridge for your system.
33
+
- Go to the **Overview > Server** page in the Azure Local resource. Verify that **Azure Arc** shows as **Connected**. You should also see a custom location and an Azure Arc resource bridge for your system.
34
34
35
35
:::image type="content" source="./media/azure-arc-vm-management-prerequisites/azure-arc-connected.png" alt-text="Screenshot of the Overview page in the Azure Local resource showing Azure Arc as connected." lightbox="./media/azure-arc-vm-management-prerequisites/azure-arc-connected.png":::
36
36
@@ -58,7 +58,7 @@ For information on Azure CLI commands for Azure Local VMs, see [az stack-hci-vm]
58
58
59
59
If you're accessing your Azure Local directly, no steps are needed on your part.
60
60
61
-
During the system deployment, an Arc Resource Bridge is created and the Azure CLI extension `stack-hci-vm` is installed on the system. You can connect to and manage the system using the Azure CLI extension.
61
+
During the system deployment, an Azure Arc resource bridge is created and the Azure CLI extension `stack-hci-vm` is installed on the system. You can connect to and manage the system using the Azure CLI extension.
62
62
63
63
### Connect to the system remotely
64
64
@@ -103,4 +103,4 @@ If you're accessing your Azure Local remotely, the following requirements must b
103
103
104
104
## Next steps
105
105
106
-
- [Assign RBAC role for Arc VM management](./assign-vm-rbac-roles.md).
106
+
- [Assign RBAC role for Azure Local VMs](./assign-vm-rbac-roles.md).
This article describes how to create an Arc virtual machine (VM) starting with the VM images that you created on your Azure Local instance. You can create Arc VMs using the Azure CLI, Azure portal, or Azure Resource Manager template.
17
+
This article describes how to create Azure Local virtual machines (VMs) starting with the VM images that you created on your Azure Local instance. You can create Azure Local VMs using the Azure CLI, Azure portal, or Azure Resource Manager template.
18
18
19
19
## About Azure Local resource
20
20
21
21
Use the [Azure Local resource page](https://portal.azure.com/#blade/HubsExtension/BrowseResource/resourceType/Microsoft.AzureStackHCI%2Fclusters) for the following operations:
22
22
23
-
- Create and manage Arc VM resources such as VM images, disks, network interfaces.
24
-
- View and access Azure Arc Resource Bridge and Custom Location associated with the Azure Local instance.
25
-
- Provision and manage Arc VMs.
23
+
- Create and manage Azure Local VM resources such as VM images, disks, network interfaces.
24
+
- View and access Azure Arc resource bridge and custom location associated with the Azure Local instance.
25
+
- Provision and manage VMs.
26
26
27
-
The procedure to create Arc VMs is described in the next section.
27
+
The procedure to create VMs is described in the next section.
28
28
29
29
## Prerequisites
30
30
31
-
Before you create an Azure Arc-enabled VM, make sure that the following prerequisites are completed.
31
+
Before you create an Azure Local VM, make sure that the following prerequisites are completed.
32
32
33
33
# [Azure CLI](#tab/azurecli)
34
34
@@ -78,9 +78,9 @@ Before you create an Azure Arc-enabled VM, make sure that the following prerequi
78
78
79
79
---
80
80
81
-
## Create Arc VMs
81
+
## Create Azure Local VMs
82
82
83
-
Follow these steps to create an Arc VM on your Azure Local.
83
+
Follow these steps to create a VM on your Azure Local.
84
84
85
85
# [Azure CLI](#tab/azurecli)
86
86
@@ -138,7 +138,7 @@ Here we create a VM that uses specific memory and processor counts on a specifie
138
138
139
139
1. Run the following commands to create the applicable VM.
140
140
141
-
**To create a Trusted launch Arc VM:**
141
+
**To create a Trusted launch Azure Local VM:**
142
142
143
143
1. Specify additional flags to enable secure boot, enable virtual TPM, and choose security type. Note, when you specify security type as Trusted launch, you must enable secure boot and vTPM, otherwise Trusted launch VM creation will fail.
144
144
@@ -162,7 +162,7 @@ Here we create a VM that uses specific memory and processor counts on a specifie
@@ -171,18 +171,18 @@ Here we create a VM that uses specific memory and processor counts on a specifie
171
171
The VM is successfully created when the `provisioningState` shows as `succeeded`in the output.
172
172
173
173
> [!NOTE]
174
-
> The VM created has guest management enabled by default. If for any reason guest management fails during VM creation, you can follow the steps in [Enable guest management on Arc VM](./manage-arc-virtual-machines.md#enable-guest-management) to enable it after the VM creation.
174
+
> The VM created has guest management enabled by default. If for any reason guest management fails during VM creation, you can follow the steps in [Enable guest management on Azure Local VM](./manage-arc-virtual-machines.md#enable-guest-management) to enable it after the VM creation.
175
175
176
176
In this example, the storage path was specified using the `--storage-path-id` flag and that ensured that the workload data (including the VM, VM image, non-OS data disk) is placed in the specified storage path.
177
177
178
178
If the flag isn't specified, the workload (VM, VM image, non-OS data disk) is automatically placed in a high availability storage path.
179
179
180
180
### Additional parameters for Windows Server 2012 and Windows Server 2012 R2 images
181
181
182
-
When creating an Arc VM using Windows Server 2012 and Windows Server 2012 R2 images, specify the following additional parameters to create the VM:
182
+
When creating a VM using Windows Server 2012 and Windows Server 2012 R2 images, specify the following additional parameters to create the VM:
183
183
184
-
-`--enable-agent`: Set this parameter to `true` to onboard the Azure Connected Machine agent on Arc VMs.
185
-
-`--enable-vm-config-agent`: Set this parameter to `false` to prevent the onboarding of the VM agent on the VM from the host via Hyper-V sockets channel. Windows Server 2012 and Windows Server 2012 R2 don't support Hyper-V sockets. In the newer image versions that support Hyper-V sockets, the VM agent is used to onboard the Azure Connected Machine agent on Arc VMs. For more information on Hyper-V sockets, see [Make your own integration services](/virtualization/hyper-v-on-windows/user-guide/make-integration-service).
184
+
-`--enable-agent`: Set this parameter to `true` to onboard the Azure Connected Machine agent on VMs.
185
+
-`--enable-vm-config-agent`: Set this parameter to `false` to prevent the onboarding of the VM agent on the VM from the host via Hyper-V sockets channel. Windows Server 2012 and Windows Server 2012 R2 don't support Hyper-V sockets. In the newer image versions that support Hyper-V sockets, the VM agent is used to onboard the Azure Connected Machine agent on VMs. For more information on Hyper-V sockets, see [Make your own integration services](/virtualization/hyper-v-on-windows/user-guide/make-integration-service).
186
186
187
187
### Create a Linux VM
188
188
@@ -199,7 +199,7 @@ To create a Linux VM, use the same command that you used to create the Windows V
199
199
200
200
Use this optional parameter **proxy-configuration** to configure a proxy server for your VM.
201
201
202
-
Proxy configuration for Arc VMs is applied only to the onboarding of the Azure connected machine agent and set as environment variables within the guest VM operating system. Browsers and applications on the VM aren't necessarily all enabled with this proxy configuration.
202
+
Proxy configuration for VMs is applied only to the onboarding of the Azure connected machine agent and set as environment variables within the guest VM operating system. Browsers and applications on the VM aren't necessarily all enabled with this proxy configuration.
203
203
204
204
As such, you may need to specifically set the proxy configuration for your applications if they don't reference the environment variables set within the VM.
For proxy authentication, you can pass the username and password combined in a URL as follows:`"http://username:[email protected]:3128"`.
230
230
231
-
<!--Depending on the PowerShell version you're running on your VM, you may need to enable the proxy settings for your VM.
232
-
233
-
- For Windows VMs running PowerShell version 5.1 or earlier, sign in to the VM after the creation. Run the following command to enable proxy:
234
-
235
-
```powershell
236
-
netsh winhttp set proxy proxy-server="http=myproxy;https=sproxy:88" bypass-list="*.foo.com"
237
-
```
238
-
239
-
After the proxy is enabled, you can then [Enable guest management](./manage-arc-virtual-machines.md#enable-guest-management).
240
-
241
-
- For Windows VMs running PowerShell version later than 5.1, proxy settings passed during VM creation are only used for enabling Arc guest management. After the VM is created, sign in to the VM and run the above command to enable proxy for other applications.-->
242
231
243
232
# [Azure portal](#tab/azureportal)
244
233
@@ -297,12 +286,12 @@ Follow these steps in Azure portal for your Azure Local.
297
286
298
287
> [!NOTE]
299
288
> - Add at least one network interface through the **Networking** tab to complete guest management setup.
300
-
> - The network interface that you enable, must have a valid IP address and internet access. For more information, see [Arc VM management networking](../manage/azure-arc-vm-management-networking.md#arc-vm-virtual-network).
289
+
> - The network interface that you enable, must have a valid IP address and internet access. For more information, see [Azure Local VM management networking](../manage/azure-arc-vm-management-networking.md#arc-vm-virtual-network).
301
290
302
-
1. In the VM proxy configuration section, to configure a proxy for your Arc VM, input the following parameters:
291
+
1. In the VM proxy configuration section, to configure a proxy for your VM, input the following parameters:
303
292
304
293
> [!NOTE]
305
-
> Proxy configuration for Arc VMs is applied only to the onboarding of the Azure connected machine agent and set as environment variables within the guest VM operating system. Browsers and applications on the VM aren't necessarily all enabled with this proxy configuration. As such, you may need to specifically set the proxy configuration for your applications if they don't reference the environment variables set within the VM.
294
+
> Proxy configuration for VMs is applied only to the onboarding of the Azure connected machine agent and set as environment variables within the guest VM operating system. Browsers and applications on the VM aren't necessarily all enabled with this proxy configuration. As such, you may need to specifically set the proxy configuration for your applications if they don't reference the environment variables set within the VM.
306
295
307
296
:::image type="content" source="./media/create-arc-virtual-machines/arc-vm-proxy-configuration.png" alt-text="Screenshot of local VM administrator on Basics tab." lightbox="./media/create-arc-virtual-machines/arc-vm-proxy-configuration.png":::
308
297
@@ -388,7 +377,7 @@ Follow these steps to deploy the Resource Manager template:
388
377
389
378
1. Replace the blank template with the template that you downloaded during the prerequisites step.
390
379
391
-
This template creates an Arc VM. First, a virtual network interface is created. You can optionally enable domain-join and attach a virtual disk to the VM you create. Finally, the VM is created with the guest management enabled.
380
+
This template creates an Azure Local VM. First, a virtual network interface is created. You can optionally enable domain-join and attach a virtual disk to the VM you create. Finally, the VM is created with the guest management enabled.
392
381
393
382
```json
394
383
{
@@ -701,17 +690,17 @@ You can use the Azure Verified Module (AVM) that contains the Terraform template
701
690
702
691
---
703
692
704
-
## Use managed identity to authenticate Arc VMs
693
+
## Use managed identity to authenticate Azure Local VMs
705
694
706
-
When the Arc VMs are created on your Azure Local via Azure CLI or Azure portal, a system-assigned managed identity is also created that lasts for the lifetime of the Arc VMs.
695
+
When the VMs are created on your Azure Local via Azure CLI or Azure portal, a system-assigned managed identity is also created that lasts for the lifetime of the VMs.
707
696
708
-
The Arc VMs on Azure Local are extended from Arc-enabled servers and can use system-assigned managed identity to access other Azure resources that support Microsoft Entra ID-based authentication. For example, the Arc VMs can use a system-assigned managed identity to access the Azure Key Vault.
697
+
The VMs on Azure Local are extended from Arc-enabled servers and can use system-assigned managed identity to access other Azure resources that support Microsoft Entra ID-based authentication. For example, the VMs can use a system-assigned managed identity to access the Azure Key Vault.
709
698
710
699
For more information, see [system-assigned managed identities](/entra/identity/managed-identities-azure-resources/overview#managed-identity-types) and [Authenticate against Azure resource with Azure Arc-enabled servers](/azure/azure-arc/servers/managed-identity-authentication).
![prmerger-automator[bot]](https://avatars.githubusercontent.com/u/22479449?v=4&size=40){kind=avatar}
0 commit comments