Register Azure Local with Azure Arc

This article details how to register Azure Local machines with Azure Arc without using an Arc gateway and with proxy configuration enabled. The proxy configuration can be done via an Arc script or via the Configurator app for Azure Local.

Configure with a script: You can use an Arc script to configure registration settings.
Set up via the Configurator app (Preview): Using this method, you can configure Azure Local registration via a user interface. This method is useful if you prefer not to use scripts or if you want to configure the settings interactively.

For instructions on registering Azure Local machines with Azure Arc using an Arc gateway and with proxy configuration enabled, see Register Azure Local with Azure Arc using Arc gateway.

Via Arc script
Via Configurator app (Preview)

Prerequisites

Make sure the following prerequisites are met before proceeding:

You have access to Azure Local machines running release 2505 or later.
You have assigned the appropriate permissions to the subscription used for registration. For more information, see Assign required permissions for Azure Local deployment.

Important

Run these steps as a local administrator on every Azure Local machine that you intend to cluster.

Step 1: Review script parameters

Review the parameters used in the script:

Parameters	Description
`TenantID`	The tenant ID used to register your machines with Azure Arc. Go to your Microsoft Entra ID and copy the tenant ID property.
`SubscriptionID`	The ID of the subscription used to register your machines with Azure Arc.
`ResourceGroup`	The resource group precreated for Arc registration of the machines. A resource group is created if one doesn't exist.
`Region`	The Azure region used for registration. See the Supported regions that can be used.
`ProxyServer`	Optional parameter. Proxy Server address when required for outbound connectivity.

Step 2: Set parameters

Set the parameters required for the registration script.

Here's an example of how you should change these parameters for the Invoke-AzStackHciArcInitialization initialization script. Once the registration is complete, the Azure Local machines are registered in Azure Arc:

#Define the tenant you will use to register your machine as Arc device
$Tenant = "YourTenantID"

#Define the subscription where you want to register your Azure Local machine with Arc.
$Subscription = "YourSubscriptionID"

#Define the resource group where you want to register your Azure Local machine with Arc.
$RG = "YourResourceGroupName"

#Define the region to use to register your server as Arc device
#Do not use spaces or capital letters when defining region
$Region = "eastus"

#Define the proxy address for your Azure Local deployment to access the internet via proxy.
$ProxyServer = "http://proxyaddress:port"

#Define the bypass list for the proxy. Use comma to separate each item from the list.  
# Parameters must be separated with a comma `,`.
# Use "localhost" instead of <local> 
# Use specific IPs such as 127.0.0.1 without mask 
# Use * for subnets allowlisting. 192.168.1.* for /24 exclusions. Use 192.168.*.* for /16 exclusions. 
# Append * for domain names exclusions like *.contoso.com 
# DO NOT INCLUDE .svc on the list. The registration script takes care of Environment Variables configuration. 
# At least the IP address of each Azure Local machine.
# At least the IP address of the Azure Local cluster.
# At least the IPs you defined for your infrastructure network. Arc resource bridge, Azure Kubernetes Service (AKS), and future infrastructure services using these IPs require outbound connectivity.
# NetBIOS name of each machine.
# NetBIOS name of the Azure Local cluster.

$ProxyBypassList = "localhost,127.0.0.1,*.contoso.com,machine1,machine2,machine3,machine4,machine5,192.168.*.*,AzureLocal-1"

Expand this section to see an example output.

PS C:\Users\SetupUser> $Subscription = "Subscription ID"
PS C:\Users\SetupUser> $RG = "myashcirg"
PS C:\Users\SetupUser> $Region = "eastus"
PS C:\Users\SetupUser> $Tenant = "Tenant ID"
PS C:\Users\SetupUser> $ProxyServer = "http://192.168.10.10:8080"
PS C:\Users\SetupUser> $ProxyBypassList = "localhost,127.0.0.1,*.contoso.com,machine1,machine2,machine3,machine4,machine5,192.168.*.*,AzureLocal-1"

Step 3: Run registration script

Note

If your Azure Local system is preinstalled with an Original Equipment Manufacturer (OEM) image that's outdated or unsupported, an update is triggered automatically. The update typically takes 40-45 minutes to complete and includes a system reboot. After the reboot, rerun the cmdlet to continue. For more instructions about the update flow, see Azure Arc registration workflow for systems with OEM images.

Run the Arc registration script. The script takes a few minutes to run.

#Invoke the registration script. Use a supported region.
Invoke-AzStackHciArcInitialization -TenantId $Tenant -SubscriptionID $Subscription -ResourceGroup $RG -Region $Region -Cloud "AzureCloud" -Proxy $ProxyServer -ProxyBypass $ProxyBypassList

For a list of supported Azure regions, see Azure requirements.

Expand this section to see an example output.

Here's a sample output of a successful registration of your machines:

PS C:\Users\Administrator> Invoke-AzStackHciArcInitialization -TenantId $Tenant -SubscriptionID $Subscription -ResourceGroup $RG -Region $Region -Cloud "AzureCloud" -Proxy $ProxyServer
>>
Configuration saved to: C:\Users\ADMINI~1\AppData\Local\Temp\bootstrap.json
Triggering bootstrap on the device...
Waiting for bootstrap to complete... Current Status: InProgress
=========SNIPPED=========SNIPPED=============
Waiting for bootstrap to complete... Current Status: InProgress
Waiting for bootstrap to complete... Current Status: Succeeded
Bootstrap succeeded.

Triggering bootstrap log collection as a best effort.
Version Response                                                    
------- --------                                                    
V1      Microsoft.Azure.Edge.Bootstrap.ServiceContract.Data.Response
V1      Microsoft.Azure.Edge.Bootstrap.ServiceContract.Data.Response


PS C:\Users\Administrator>

During the Arc registration process, you must authenticate with your Azure account. The console window displays a code that you must enter in the URL, displayed in the app, in order to authenticate. Follow the instructions to complete the authentication process.

Once the registration is complete, the Azure Local machines are registered in Azure Arc.

Step 4: Verify the setup is successful

After the script completes successfully on all the machines, verify that your machines are registered with Arc.

Go to the Azure portal.
Go to the resource group associated with the registration. The machines appear within the specified resource group as Machine - Azure Arc type resources.

Note

If the Azure Local machine fails to register, you can deregister and then register your cluster again. For detailed instructions, see Re-register Azure Local machines.

If you plan to deploy a few machines per site, use the Configurator app to register your Azure Local machines with Azure Arc.

Important

This feature is currently in PREVIEW. See the Supplemental Terms of Use for Microsoft Azure Previews for legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.

Prerequisites

Before you begin, make sure that you complete the following prerequisites:

Azure Local machine prerequisites

Download the Configurator App for Azure Local on a client machine that is connected to the same network as the Azure Local machines..
Note down:
- The serial number for each machine.
- Local administrator credentials to sign into each machine.

Azure prerequisites

Make sure you have the required permissions to register Azure Local machines with Azure Arc. For more information, see Assign required permissions for Azure Local deployment.

Step 1: Configure the network and connect to Azure

Follow these steps to configure network settings and connect the machines to Azure. Start this action a few minutes after you turn on the machine.

Open the Configurator app. Right-click the Configurator app exe and run as administrator. Wait a few minutes for the app to open up.
Enter the machine serial number and select Next.
Sign in to the machine with local administrator credentials.

Prerequisites tab

On the Prerequisites tab, verify that the minimum requirements are met and then select Next.

If a requirement isn't met, the app displays a warning or errors. You can't proceed if there are errors though warnings are ignored. Resolve the errors before you proceed. For more information, see Troubleshooting registration issues.

Basics tab

On the Basics tab, configure one network interface that is connected to the internet. Select the Pencil icon to modify network interface settings.
Provide the interface name, IP allocation as static or DHCP, IP address, subnet, gateway, and preferred DNS servers. Optionally, enter an alternate DNS server.

Important

Make sure that the IPs you assign are free and not in use.
To specify more details, select Enter additional details.
On the Additional details page, provide the following inputs and then select Apply.
1. Select ON to enable Remote desktop protocol. Remote desktop protocol is disabled by default.
2. Select Proxy server as the connectivity method. Provide the proxy URL and the bypass list. The bypass list is required and can be provided in a comma separated format.
  
  When defining your proxy bypass string, make sure you meet the following conditions:
  - Include at least the IP address of each Azure Local machine.
  - Include at least the IP address of the Azure Local cluster.
  - Include at least the IPs you defined for your infrastructure network. Arc resource bridge, Azure Kubernetes Service (AKS), and future infrastructure services using these IPs require outbound connectivity.
  - Or you can bypass the entire infrastructure subnet.
  - Provide the NetBIOS name of each machine.
  - Provide the NetBIOS name of the Azure Local cluster.
  - Domain name or domain name with asterisk * wildcard at the beginning to include any host or subdomain. For example, 192.168.1.* for subnets or *.contoso.com for domain names.
  - Parameters must be separated with a comma ,.
  - Classless Inter-Domain Routing (CIDR) notation to bypass subnets isn't supported.
  - The use of <local> strings isn't supported in the proxy bypass list.
3. Select a time zone.
4. Specify a preferred and an alternate NTP server to act as a time server or accept the Default. The default is time.windows.com.
5. Set the hostname for your machine to what you specified during the preparation of Active Directory. Changing the hostname automatically reboots the system.
Select Next on the Basics tab.

Arc agent setup tab

On the Arc agent setup tab, provide the following inputs:
1. The Cloud type is populated automatically as Azure.
2. Enter a Subscription ID to register the machine.
3. Provide a Resource group name. This resource group contains the machine and system resources that you create.
4. Specify the Region where you want to create the resources. The region should be the same as the region where you want to deploy the Azure Local instance.
  
  Important
  
  Specify the region with spaces removed. For example, specify the East US region as EastUS.
5. Skip the Tenant ID.
6. Skip the Arc gateway ID.
Important

Make sure to verify all the inputs before you proceed. Any incorrect inputs here might result in a setup failure.
Select Next.

Review and apply tab

On the Review and apply tab, verify machine details. To modify any settings, go back. If satisfied with the current settings, select Finish. If you changed the hostname, your machines boot up automatically at this point and you must sign in again.

Step 2: Complete registration of machines to Azure

Wait for the configuration to complete. First, machine is configured with the basic details followed by registration of the machines to Azure.
During the Arc registration process, you must authenticate with your Azure account. The app displays a code that you must enter in the URL, displayed in the app, in order to authenticate. Follow the instructions to complete the authentication process.
Once the configuration is complete, status for Arc configuration should display Success (Open in Azure portal).
Repeat all steps on the other machines until the Arc configuration succeeds. Select the Open in Azure portal link.

Step 3: Verify machines are connected to Arc

In the Azure portal, go to the resource group that you used for bootstrapping.
On the resource group used to bootstrap, you should see your Arc-enabled machines. In this example, you see a single machine.

This article describes how to register Azure Local machines with Azure Arc without using an Arc gateway and without proxy configuration enabled. You can register via the Arc script or the Configurator app.

Configure with a script: Using this method, configure the registration settings via a script.
Set up via the Configurator app: Configure Azure Arc gateway via a user interface. This method is useful if you prefer not to use scripts or if you want to configure the registration settings interactively.

For instructions on registering Azure Local machines with Azure Arc using an Arc gateway without proxy configuration enabled, see Register Azure Local with Azure Arc using Arc gateway.

Via Arc script
Via Configurator app (Preview)

Prerequisites

Make sure the following prerequisites are met before proceeding:

You have access to Azure Local machines running release 2505 or later.
You have assigned the appropriate permissions to the subscription used for registration. For more information, see Assign required permissions for Azure Local deployment.

Important

Run these steps as a local administrator on every Azure Local machine that you intend to cluster.

Step 1: Review script parameters

Review the parameters used in the script:

Parameters	Description
`TenantID`	The tenant ID used to register your machines with Azure Arc. Go to your Microsoft Entra ID and copy the tenant ID property.
`SubscriptionID`	The ID of the subscription used to register your machines with Azure Arc.
`ResourceGroup`	The resource group precreated for Arc registration of the machines. A resource group is created if one doesn't exist.
`Region`	The Azure region used for registration. See the Supported regions that can be used.

Step 2: Set parameters

Set the parameters.

#Define the tenant you will use to register your machine as Arc device
$Tenant = "YourTenantID"

#Define the subscription where you want to register your machine as Arc device
$Subscription = "YourSubscriptionID"

#Define the resource group where you want to register your machine as Arc device
$RG = "YourResourceGroupName"

#Define the region to use to register your server as Arc device
#Do not use spaces or capital letters when defining region
$Region = "eastus"

Expand this section to see an example output.

PS C:\Users\SetupUser> $Tenant = "Your tenant ID"
PS C:\Users\SetupUser> $Subscription = "Subscription ID"
PS C:\Users\SetupUser> $RG = "myashcirg"
PS C:\Users\SetupUser> $Region = "eastus"

Step 3: Run registration script

Note

Run the Arc registration script. The script takes a few minutes to run.

#Invoke the registration script. Use a supported region.
Invoke-AzStackHciArcInitialization -TenantId $Tenant -SubscriptionID $Subscription -ResourceGroup $RG -Region $Region -Cloud "AzureCloud"

For a list of supported Azure regions, see Azure requirements.

Expand this section to see an example output.

PS C:\Users\Administrator> Invoke-AzStackHciArcInitialization -TenantId $Tenant -SubscriptionID $Subscription -ResourceGroup $RG -Region $Region -Cloud "AzureCloud"
>>
Configuration saved to: C:\Users\ADMINI~1\AppData\Local\Temp\bootstrap.json
Triggering bootstrap on the device...
Waiting for bootstrap to complete... Current Status: InProgress
=========SNIPPED=========SNIPPED=============
Waiting for bootstrap to complete... Current Status: InProgress
Waiting for bootstrap to complete... Current Status: Succeeded
Bootstrap succeeded.

Triggering bootstrap log collection as a best effort.
Version Response                                                    
------- --------                                                    
V1      Microsoft.Azure.Edge.Bootstrap.ServiceContract.Data.Response
V1      Microsoft.Azure.Edge.Bootstrap.ServiceContract.Data.Response


PS C:\Users\Administrator>

During the Arc registration process, you must authenticate with your Azure account. The console window displays a code that you must enter in the URL, displayed in the app, in order to authenticate. Follow the instructions to complete the authentication process.

Step 4: Verify the setup is successful

Go to the Azure portal.
Go to the resource group associated with the registration. The machines appear within the specified resource group as Machine - Azure Arc type resources.

Note

Once an Azure Local machine is registered with Azure Arc, the only way to undo the registration is to install the operating system again on the machine.

If you plan to deploy a few machines per site, use the Configurator app to register your Azure Local machines with Azure Arc.

Important

Prerequisites for registration without proxy configuration

Before you begin, make sure that you complete the following prerequisites:

Azure Local machine prerequisites

Download the Configurator App for Azure Local on a client machine that is connected to the same network as the Azure Local machines..
Note down:
- The serial number for each machine.
- Local administrator credentials to sign into each machine.

Azure prerequisites

Make sure you have the required permissions to register Azure Local machines with Azure Arc. For more information, see Assign required permissions for Azure Local deployment.

Configure the network and connect to Azure

Follow these steps to configure network settings and connect the machines to Azure. Start this action a few minutes after you turn on the machine.

Open the Configurator app. Right-click the Configurator app exe and run as administrator. Wait a few minutes for the app to open up.
Enter the machine serial number and select Next.
Sign in to the machine with local administrator credentials.

Prerequisites tab

On the Prerequisites tab, verify that the minimum requirements are met and then select Next.

If a requirement isn't met, the app displays a warning or errors. You can't proceed if there are errors though warnings are ignored. Resolve the errors before you proceed. For more information, see Troubleshooting registration issues.

Basics tab

On the Basics tab, configure one network interface that is connected to the internet. Select the Pencil icon to modify network interface settings.
Provide the interface name, IP allocation as static or DHCP, IP address, subnet, gateway, and preferred DNS servers. Optionally, enter an alternate DNS server.

Important

Make sure that the IPs you assign are free and not in use.
To specify more details, select Enter additional details.
On the Additional details page, provide the following inputs and then select Apply.
1. Select ON to enable Remote desktop protocol. Remote desktop protocol is disabled by default.
2. Select Public endpoint as the connectivity method.
3. Select a time zone.
4. Specify a preferred and an alternate NTP server to act as a time server or accept the Default. The default is time.windows.com.
5. Set the hostname for your machine to what you specified during the preparation of Active Directory. Changing the hostname automatically reboots the system.
Select Next on the Basics tab.

Arc agent setup tab

On the Arc agent setup tab, provide the following inputs:
1. The Cloud type is populated automatically as Azure.
2. Enter a Subscription ID to register the machine.
3. Provide a Resource group name. This resource group contains the machine and system resources that you create.
4. Specify the Region where you want to create the resources. The region should be the same as the region where you want to deploy the Azure Local instance.
  
  Important
  
  Specify the region with spaces removed. For example, specify the East US region as EastUS.
5. Skip the Tenant ID.
6. Skip the Arc gateway ID.
Important

Make sure to verify all the inputs before you proceed. Any incorrect inputs here might result in a setup failure.
Select Next.

Review and apply tab

On the Review and apply tab, verify machine details. To modify any settings, go back. If satisfied with the current settings, select Finish. If you changed the hostname, your machines boot up automatically at this point and you must sign in again.

Complete registration of machines to Azure

Wait for the configuration to complete. First, machine is configured with the basic details followed by registration of the machines to Azure.
During the Arc registration process, you must authenticate with your Azure account. The app displays a code that you must enter in the URL, displayed in the app, in order to authenticate. Follow the instructions to complete the authentication process.
Once the configuration is complete, status for Arc configuration should display Success (Open in Azure portal).
Repeat all steps on the other machines until the Arc configuration succeeds. Select the Open in Azure portal link.

Verify machines are connected to Arc

In the Azure portal, go to the resource group that you used for bootstrapping.
On the resource group used to bootstrap, you should see your Arc-enabled machines. In this example, you see a single machine.

Next steps

Troubleshoot registration issues with Configurator app
After your machines are registered with Azure Arc, proceed to deploy your Azure Local instance via one of the following options:
- Deploy via Azure portal
- Deploy via Azure Resource Manager (ARM) template

This feature is available only in Azure Local 2503 or later. The following content applies specifically to release 2503 or 2504.

This article details how to register Azure Local machines with Azure Arc and with proxy configuration. The proxy configuration can be done via an Arc script or via the Configurator app for Azure Local.

Configure with a script: You can use an Arc script to configure registration settings.
Set up via the Configurator app (Preview): Using this method, you can configure Azure Local registration via a user interface. This method is useful if you prefer not to use scripts or if you want to configure the settings interactively.

Via Arc script
Via Configurator app (Preview)

Prerequisites for registration with proxy configuration

Make sure the following prerequisites are met before proceeding:

You have access to Azure Local machines running release 2503 or 2504.
You have assigned the appropriate permissions to the subscription used for registration. For more information, see Assign required permissions for Azure Local deployment.

Important

Run these steps as a local administrator on every Azure Local machine that you intend to cluster.

Review script parameters

Review the parameters used in the script:

Parameters	Description
`TenantID`	The tenant ID used to register your machines with Azure Arc. Go to your Microsoft Entra ID and copy the tenant ID property.
`SubscriptionID`	The ID of the subscription used to register your machines with Azure Arc.
`ResourceGroup`	The resource group precreated for Arc registration of the machines. A resource group is created if one doesn't exist.
`Region`	The Azure region used for registration. See the Supported regions that can be used.
`ProxyServer`	Optional parameter. Proxy Server address when required for outbound connectivity.
`AccountID`	The user who registers and deploys the instance.
`DeviceCode`	The device code displayed in the console at `https://microsoft.com/devicelogin` and is used to sign in to the device.

Set parameters

Set the parameters required for the registration script.

#Define the tenant you will use to register your machine as Arc device
$Tenant = "YourTenantID"

#Define the subscription where you want to register your machine as Arc device
$Subscription = "YourSubscriptionID"

#Define the resource group where you want to register your machine as Arc device
$RG = "YourResourceGroupName"

#Define the region to use to register your server as Arc device, do not use spaces or capital letters when defining region
$Region = "eastus"

#Define the proxy address if your Azure Local deployment accesses the internet via proxy
$ProxyServer = "http://proxyaddress:port"

Expand this section to see an example output.

PS C:\Users\SetupUser> $Tenant = "<Tenant ID>"
PS C:\Users\SetupUser> $Subscription = "<Subscription ID>"
PS C:\Users\SetupUser> $RG = "myashcirg"   PS C:\Users\SetupUser> $Region = "eastus"
PS C:\Users\SetupUser> $ProxyServer = "<http://proxyserver:tcpPort>"

Connect to your Azure account and set the subscription. Open a browser on the client that you're using to connect to the machine and open this page: https://microsoft.com/devicelogin and enter the provided code in the Azure CLI output to authenticate. Get the access token and account ID for the registration.

#Connect to your Azure account and Subscription
Connect-AzAccount -TenantId $Tenant -SubscriptionId $Subscription -DeviceCode

#Get the Access Token for the registration
$ARMtoken = (Get-AzAccessToken -WarningAction SilentlyContinue).Token

#Get the Account ID for the registration
$id = (Get-AzContext).Account.Id

Expand this section to see an example output.

PS C:\Users\SetupUser> Connect-AzAccount -TenantId $Tenant -SubscriptionId $Subscription -DeviceCode
WARNING: To sign in, use a web browser to open the page https://microsoft.com/devicelogin and enter the code A44KHK5B5
to authenticate.

Account               SubscriptionName      TenantId                Environment
-------               ----------------      --------                ----------- 
guspinto@contoso.com AzureLocal_Content  <Tenant ID>             AzureCloud

PS C:\Users\SetupUser> $ARMtoken = (Get-AzAccessToken).Token
PS C:\Users\SetupUser> $id = (Get-AzContext).Account.Id

Run registration script

Finally run the Arc registration script. The script takes a few minutes to run.

#Invoke the registration script. Use a supported region.
Invoke-AzStackHciArcInitialization -TenantID $Tenant -SubscriptionID $Subscription -ResourceGroup $RG -Region $Region -Cloud "AzureCloud" -ArmAccessToken $ARMtoken -AccountID $id -Proxy $ProxyServer -ProxyBypass $ProxyBypassList

For a list of supported Azure regions, see Azure requirements.

Expand this section to see an example output.

PS C:\Users\Administrator> Invoke-AzStackHciArcInitialization -SubscriptionID $Subscription -ResourceGroup $RG -TenantID $Tenant -Region $Region -Cloud "AzureCloud" -ArmAccessToken $ARMtoken -AccountID $id
>>
Configuration saved to: C:\Users\ADMINI~1\AppData\Local\Temp\bootstrap.json
Triggering bootstrap on the device...
Waiting for bootstrap to complete... Current Status: InProgress
=========SNIPPED=========SNIPPED=============
Waiting for bootstrap to complete... Current Status: InProgress
Waiting for bootstrap to complete... Current Status: Succeeded
Bootstrap succeeded.

Triggering bootstrap log collection as a best effort.
Version Response                                                    
------- --------                                                    
V1      Microsoft.Azure.Edge.Bootstrap.ServiceContract.Data.Response
V1      Microsoft.Azure.Edge.Bootstrap.ServiceContract.Data.Response

PS C:\Users\Administrator>

Verify the setup is successful

After the script completes successfully on all the machines, verify that your machines are registered with Arc.

Go to the Azure portal.
Go to the resource group associated with the registration. The machines appear within the specified resource group as Machine - Azure Arc type resources.

Note

Once an Azure Local machine is registered with Azure Arc, the only way to undo the registration is to install the operating system again on the machine.

If you plan to deploy a few machines per site, use the Configurator app to register your Azure Local machines with Azure Arc.

Important

Prerequisites for registration with proxy configuration

Before you begin, make sure that you complete the following prerequisites:

Azure Local machine prerequisites

Download the Configurator App for Azure Local on a client machine that is connected to the same network as the Azure Local machines..
Note down:
- The serial number for each machine.
- Local administrator credentials to sign into each machine.

Azure prerequisites

Make sure you have the required permissions to register Azure Local machines with Azure Arc. For more information, see Assign required permissions for Azure Local deployment.

Configure the network and connect to Azure

Follow these steps to configure network settings and connect the machines to Azure. Start this action a few minutes after you turn on the machine.

Open the Configurator app. Right-click the Configurator app exe and run as administrator. Wait a few minutes for the app to open up.
Enter the machine serial number and select Next.
Sign in to the machine with local administrator credentials.

Prerequisites tab

On the Prerequisites tab, verify that the minimum requirements are met and then select Next.

If a requirement isn't met, the app displays a warning or errors. You can't proceed if there are errors though warnings are ignored. Resolve the errors before you proceed. For more information, see Troubleshooting registration issues.

Basics tab

On the Basics tab, configure one network interface that is connected to the internet. Select the Pencil icon to modify network interface settings.
Provide the interface name, IP allocation as static or DHCP, IP address, subnet, gateway, and preferred DNS servers. Optionally, enter an alternate DNS server.

Important

Make sure that the IPs you assign are free and not in use.
To specify more details, select Enter additional details.
On the Additional details page, provide the following inputs and then select Apply.
1. Select ON to enable Remote desktop protocol. Remote desktop protocol is disabled by default.
2. Select Proxy server as the connectivity method. Provide the proxy URL and the bypass list. The bypass list is required and can be provided in a comma separated format.
  
  When defining your proxy bypass string, make sure you meet the following conditions:
  - Include at least the IP address of each Azure Local machine.
  - Include at least the IP address of the Azure Local cluster.
  - Include at least the IPs you defined for your infrastructure network. Arc resource bridge, Azure Kubernetes Service (AKS), and future infrastructure services using these IPs require outbound connectivity.
  - Or you can bypass the entire infrastructure subnet.
  - Provide the NetBIOS name of each machine.
  - Provide the NetBIOS name of the Azure Local cluster.
  - Domain name or domain name with asterisk * wildcard at the beginning to include any host or subdomain. For example, 192.168.1.* for subnets or *.contoso.com for domain names.
  - Parameters must be separated with a comma ,.
  - Classless Inter-Domain Routing (CIDR) notation to bypass subnets isn't supported.
  - The use of <local> strings isn't supported in the proxy bypass list.
3. Select a time zone.
4. Specify a preferred and an alternate NTP server to act as a time server or accept the Default. The default is time.windows.com.
5. Set the hostname for your machine to what you specified during the preparation of Active Directory. Changing the hostname automatically reboots the system.
Select Next on the Basics tab.

Arc agent setup tab

On the Arc agent setup tab, provide the following inputs:
1. The Cloud type is populated automatically as Azure.
2. Enter a Subscription ID to register the machine.
3. Provide a Resource group name. This resource group contains the machine and system resources that you create.
4. Specify the Region where you want to create the resources. The region should be the same as the region where you want to deploy the Azure Local instance.
  
  Important
  
  Specify the region with spaces removed. For example, specify the East US region as EastUS.
5. Skip the Tenant ID.
6. Skip the Arc gateway ID.
Important

Make sure to verify all the inputs before you proceed. Any incorrect inputs here might result in a setup failure.
Select Next.

Review and apply tab

On the Review and apply tab, verify machine details. To modify any settings, go back. If satisfied with the current settings, select Finish. If you changed the hostname, your machines boot up automatically at this point and you must sign in again.

Complete registration of machines to Azure

Wait for the configuration to complete. First, machine is configured with the basic details followed by registration of the machines to Azure.
During the Arc registration process, you must authenticate with your Azure account. The app displays a code that you must enter in the URL, displayed in the app, in order to authenticate. Follow the instructions to complete the authentication process.
Once the configuration is complete, status for Arc configuration should display Success (Open in Azure portal).
Repeat all steps on the other machines until the Arc configuration succeeds. Select the Open in Azure portal link.

Verify machines are connected to Arc

In the Azure portal, go to the resource group that you used for bootstrapping.
On the resource group used to bootstrap, you should see your Arc-enabled machines. In this example, you see a single machine.

This article details how to register using Azure Arc gateway on Azure Local without the proxy configuration. You can register via the Arc script or the Configurator app.

Configure with a script: Using this method, configure the registration settings via a script.
Set up via the Configurator app: Configure Azure Arc gateway via a user interface. This method is useful if you prefer not to use scripts or if you want to configure the registration settings interactively.

Via Arc script
Via Configurator app (Preview)

Prerequisites for registration without proxy configuration

Make sure the following prerequisites are met before proceeding:

You have access to Azure Local machines running release 2503 or 2504.
You have assigned the appropriate permissions to the subscription used for registration. For more information, see Assign required permissions for Azure Local deployment.

Important

Run these steps as a local administrator on every Azure Local machine that you intend to cluster.

Review script parameters

Review the parameters used in the script:

Parameters	Description
`TenantID`	The tenant ID used to register your machines with Azure Arc. Go to your Microsoft Entra ID and copy the tenant ID property.
`SubscriptionID`	The ID of the subscription used to register your machines with Azure Arc.
`ResourceGroup`	The resource group precreated for Arc registration of the machines. A resource group is created if one doesn't exist.
`Region`	The Azure region used for registration. See the Supported regions that can be used.
`AccountID`	The user who registers and deploys the instance.
`DeviceCode`	The device code displayed in the console at `https://microsoft.com/devicelogin` and is used to sign in to the device.

Set parameters

Set the parameters.

#Define the tenant you will use to register your machine as Arc device
$Tenant = "YourTenantID"

#Define the subscription where you want to register your machine as Arc device
$Subscription = "YourSubscriptionID"

#Define the resource group where you want to register your machine as Arc device
$RG = "YourResourceGroupName"

#Define the region to use to register your server as Arc device, do not use spaces or capital letters when defining region
$Region = "eastus"

Expand this section to see an example output.

PS C:\Users\SetupUser> $Tenant = "<Tenant ID>"
PS C:\Users\SetupUser> $Subscription = "<Subscription ID>"
PS C:\Users\SetupUser> $RG = "myashcirg"
PS C:\Users\SetupUser> $Region = "eastus"

#Connect to your Azure account and Subscription
Connect-AzAccount -TenantId $Tenant -SubscriptionId $Subscription -DeviceCode

#Get the Access Token for the registration
$ARMtoken = (Get-AzAccessToken -WarningAction SilentlyContinue).Token

#Get the Account ID for the registration
$id = (Get-AzContext).Account.Id

Expand this section to see an example output.

PS C:\Users\SetupUser> Connect-AzAccount -TenantId $Tenant -SubscriptionId $Subscription -DeviceCode
WARNING: To sign in, use a web browser to open the page https://microsoft.com/devicelogin and enter the code A44KHK5B5
to authenticate.

Account               SubscriptionName      TenantId                Environment
-------               ----------------      --------                ----------- 
guspinto@contoso.com AzureStackHCI_Content  <Tenant ID>             AzureCloud

PS C:\Users\SetupUser> $ARMtoken = (Get-AzAccessToken).Token
PS C:\Users\SetupUser> $id = (Get-AzContext).Account.Id

Run registration script

Finally run the Arc registration script. The script takes a few minutes to run.

#Invoke the registration script. Use a supported region.
Invoke-AzStackHciArcInitialization -TenantID $Tenant -SubscriptionID $Subscription -ResourceGroup $RG -Region $Region -Cloud "AzureCloud" -ArmAccessToken $ARMtoken -AccountID $id

For a list of supported Azure regions, see Azure requirements.

Expand this section to see an example output.

PS C:\Users\Administrator> Invoke-AzStackHciArcInitialization -TenantID $Tenant -SubscriptionID $Subscription -ResourceGroup $RG -Region $Region -Cloud "AzureCloud" -ArmAccessToken $ARMtoken -AccountID $id
>>
Configuration saved to: C:\Users\ADMINI~1\AppData\Local\Temp\bootstrap.json
Triggering bootstrap on the device...
Waiting for bootstrap to complete... Current Status: InProgress
=========SNIPPED=========SNIPPED=============
Waiting for bootstrap to complete... Current Status: InProgress
Waiting for bootstrap to complete... Current Status: Succeeded
Bootstrap succeeded.

Triggering bootstrap log collection as a best effort.
Version Response                                                    
------- --------                                                    
V1      Microsoft.Azure.Edge.Bootstrap.ServiceContract.Data.Response
V1      Microsoft.Azure.Edge.Bootstrap.ServiceContract.Data.Response

PS C:\Users\Administrator>

Verify the setup is successful

Go to the Azure portal.
Go to the resource group associated with the registration. The machines appear within the specified resource group as Machine - Azure Arc type resources.

Note

Once an Azure Local machine is registered with Azure Arc, the only way to undo the registration is to install the operating system again on the machine.

If you plan to deploy a few machines per site, use the Configurator app to register your Azure Local machines with Azure Arc.

Important

Prerequisites for registration without proxy configuration

Before you begin, make sure that you complete the following prerequisites:

Azure Local machine prerequisites

Download the Configurator App for Azure Local on a client machine that is connected to the same network as the Azure Local machines..
Note down:
- The serial number for each machine.
- Local administrator credentials to sign into each machine.

Azure prerequisites

Make sure you have the required permissions to register Azure Local machines with Azure Arc. For more information, see Assign required permissions for Azure Local deployment.

Configure the network and connect to Azure

Follow these steps to configure network settings and connect the machines to Azure. Start this action a few minutes after you turn on the machine.

Open the Configurator app. Right-click the Configurator app exe and run as administrator. Wait a few minutes for the app to open up.
Enter the machine serial number and select Next.
Sign in to the machine with local administrator credentials.

Prerequisites tab

On the Prerequisites tab, verify that the minimum requirements are met and then select Next.

If a requirement isn't met, the app displays a warning or errors. You can't proceed if there are errors though warnings are ignored. Resolve the errors before you proceed. For more information, see Troubleshooting registration issues.

Basics tab

On the Basics tab, configure one network interface that is connected to the internet. Select the Pencil icon to modify network interface settings.
Provide the interface name, IP allocation as static or DHCP, IP address, subnet, gateway, and preferred DNS servers. Optionally, enter an alternate DNS server.

Important

Make sure that the IPs you assign are free and not in use.
To specify more details, select Enter additional details.
On the Additional details page, provide the following inputs and then select Apply.
1. Select ON to enable Remote desktop protocol. Remote desktop protocol is disabled by default.
2. Select Public endpoint as the connectivity method.
3. Select a time zone.
4. Specify a preferred and an alternate NTP server to act as a time server or accept the Default. The default is time.windows.com.
5. Set the hostname for your machine to what you specified during the preparation of Active Directory. Changing the hostname automatically reboots the system.
Select Next on the Basics tab.

Arc agent setup tab

On the Arc agent setup tab, provide the following inputs:
1. The Cloud type is populated automatically as Azure.
2. Enter a Subscription ID to register the machine.
3. Provide a Resource group name. This resource group contains the machine and system resources that you create.
4. Specify the Region where you want to create the resources. The region should be the same as the region where you want to deploy the Azure Local instance.
  
  Important
  
  Specify the region with spaces removed. For example, specify the East US region as EastUS.
5. Skip the Tenant ID.
6. Skip the Arc gateway ID.
Important

Make sure to verify all the inputs before you proceed. Any incorrect inputs here might result in a setup failure.
Select Next.

Review and apply tab

On the Review and apply tab, verify machine details. To modify any settings, go back. If satisfied with the current settings, select Finish. If you changed the hostname, your machines boot up automatically at this point and you must sign in again.

Complete registration of machines to Azure

Wait for the configuration to complete. First, machine is configured with the basic details followed by registration of the machines to Azure.
During the Arc registration process, you must authenticate with your Azure account. The app displays a code that you must enter in the URL, displayed in the app, in order to authenticate. Follow the instructions to complete the authentication process.
Once the configuration is complete, status for Arc configuration should display Success (Open in Azure portal).
Repeat all steps on the other machines until the Arc configuration succeeds. Select the Open in Azure portal link.

Verify machines are connected to Arc

In the Azure portal, go to the resource group that you used for bootstrapping.
On the resource group used to bootstrap, you should see your Arc-enabled machines. In this example, you see a single machine.

Troubleshoot registration issues with Configurator app
After your machines are registered with Azure Arc, proceed to deploy your Azure Local instance via one of the following options:
- Deploy via Azure portal
- Deploy via Azure Resource Manager (ARM) template

Feedback

Was this page helpful?

Last updated on 2025-11-18

Share via

Register Azure Local with Azure Arc

Prerequisites

Step 1: Review script parameters

Step 2: Set parameters

Step 3: Run registration script

Step 4: Verify the setup is successful

Prerequisites

Step 1: Review script parameters

Step 2: Set parameters

Step 3: Run registration script

Step 4: Verify the setup is successful

Next steps

Prerequisites for registration with proxy configuration

Review script parameters

Set parameters

Run registration script

Verify the setup is successful

Prerequisites for registration without proxy configuration

Review script parameters

Set parameters

Run registration script

Verify the setup is successful

Related steps

Feedback

Additional resources