Register Azure Local with Azure Arc using Arc gateway

This article details how to register Azure Local using Azure Arc gateway and with the proxy configuration enabled. Once you create an Arc gateway resource in your Azure subscription, you can enable the Arc gateway features. For an overview of the Arc gateway, see About Azure Arc gateway for Azure Local.

Note

The registration and environment variable configuration described in this article applies to initial deployment. For an existing Azure Local instance, use Update-AzureLocalProxy to make coordinated changes to proxy and bypass settings instead of updating environment variables or appliance settings individually. Existing AKS clusters don't automatically receive these changes. For instructions and limitations, see Update proxy settings after deployment.

• Configure proxy with a script: Using this method, you can configure Arc proxy with a script. This method is useful as you don't need to configure the Arc proxy across WinInet, WinHttp, or environment variables manually.

• Set up proxy via the Configurator app: Using this method, you can configure the Arc proxy via a user interface. This method is useful if you prefer not to use scripts or if you want to configure the proxy settings interactively.

Via Arc script

Prerequisites

• You have access to Azure Local machines running release 2506 or later. Earlier versions don't support this scenario.

• You have assigned the appropriate permissions to the subscription used for registration. For more information, see Assign required permissions for Azure Local deployment.

• An Arc gateway resource is created in the same subscription used to deploy Azure Local. For more information, see Create the Arc gateway resource in Azure.

• You have reviewed the supported and unsupported scenarios. For more information, see Supported and unsupported scenarios.

• Required endpoints are open in your firewall. For more information, see Azure Local endpoints not redirected.

Step 1: Get the Arc gateway ID

• Get Arc gateway ID. To create Azure Arc gateway, see Set up an Azure Arc gateway and get the resource ID of the Arc gateway. This is also referred to as the ArcGatewayID.

  1. In the Azure portal, go to the Arc gateway resource that you created.
  2. On the Overview page, copy the Resource ID. You use this Arc gateway ID later.

  

Step 2: 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.
ArcGatewayID	Define the Arc gateway resource ID from Azure.
ProxyServer	Optional. Proxy Server address when required for outbound connectivity.
ProxyBypass	Optional. Define the bypass list for the proxy. Use comma to separate each item from the list.
ArmAccessToken	Required if you choose to authenticate by using an Azure Resource Manager (ARM) access token. If you omit this parameter, the script prompts for device code authentication.
TargetSolutionVersion	Optional. The target Azure Local solution version to use for the initial deployment after Azure Arc registration. If you don't specify this optional parameter, you're prompted to select a version from the list of available versions. For example: 12.2602.1002.10

Step 3: 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.

#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 Arc gateway resource ID from Azure 
$ArcgwId = "/subscriptions/yoursubscriptionid/resourceGroups/yourResourceGroupName/providers/Microsoft.HybridCompute/gateways/yourArcGatewayName" 

#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" 

#Optional: Define the Azure Resource Manager access token.
# Required only if you want to use token-based authentication instead of device code authentication.
$armTokenResponse = Get-AzAccessToken

# Convert token to string for use in initialization
# Required because Get-AzAccessToken returns SecureString
$ArmAccessToken = [System.Net.NetworkCredential]::new("", $armTokenResponse.Token).Password

#Optional: The target Azure Local solution version for initial deployment after Azure Arc registration. If omitted, select a version from the available options.
$TargetSolutionVersion = "<solution-version>" 

Step 4: Run the registration script

Note

During Azure Arc registration, select a target Azure Local solution version for the initial deployment. Specify the version by using the optional TargetSolutionVersion parameter, or select a version when prompted.

To use the Arc gateway feature for Azure Local systems without a proxy, only use the ArcGatewayID parameter.

1. Run the initialization script as follows.

   Invoke-AzStackHciArcInitialization
   -TenantId $Tenant
   -SubscriptionID $Subscription
   -ResourceGroup $RG
   -Region $Region
   -Cloud "AzureCloud"
   -ArcGatewayID $ArcgwId
   # Optional: include only when using token-based authentication
   -ArmAccessToken $ArmAccessToken
   # Optional: The target Azure Local solution version for initial deployment after Azure Arc registration. If omitted, select a version from the available options.
   -TargetSolutionVersion $TargetSolutionVersion
   

   Note

   If using -ArmAccessToken, convert the token to a plain text string by using: $ArmAccessToken = [System.Net.NetworkCredential]::new("", $armTokenResponse.Token).Password.

2. 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, in order to authenticate. Follow the instructions to complete the authentication process.

   

3. If an update is required:

   • The update typically takes 40-45 minutes, followed by a reboot.
   • During the update, the registration status appears as Update: InProgress.
   • Rerun Invoke-AzStackHciArcInitialization cmdlet after reboot.

   

Monitor and complete registration

1. If registration times out or the machine reboots, reconnect and check the registration progress by running the following commands:

   $status = Get-ArcBootstrapStatus
   $status.Response.Status
   

2. Review the status value:

   • Succeeded: Registration completed successfully.
   • Failed: Rerun registration by using a new ARM token or device code flow.
   • If the issue persists, collect logs by running Collect-ArcBootstrapSupportLogs and share them for further troubleshooting.

3. After the reboot, rerun the Invoke-AzStackHciArcInitialization cmdlet to continue.

Step 5: Verify the Azure Arc gateway setup is successful

Once the registration is complete, follow these steps to verify that Azure Arc gateway setup is successful.

1. Connect to the first Azure Local machine from your system.

2. Open the Arc gateway log to monitor which endpoints are being redirected to the Arc gateway and which ones continue using your firewall or proxy. You can find the Arc gateway log at: c:\programdata\AzureConnectedMAchineAgent\Log\arcproxy.log.

   

3. To check the Arc agent configuration and verify that it's using the gateway, run the following command:

   C:\program files\AzureConnectedMachineAgent>.\azcmagent show
   

   The values displayed should be as follows:

   1. Agent version is 1.45 or later.

   2. Agent Status should show as Connected.

   3. Using HTTPS Proxy shows as http://localhost:40343when the Arc gateway is enabled.

   4. Upstream Proxy shows your enterprise proxy server and port.

   5. Azure Arc Proxy shows as running when the Arc gateway is enabled.

   

4. Additionally, to verify that the setup was done successfully, run the following command:

   C:\program files\AzureConnectedMachineAgent>.\azcmagent check
   

   The response should indicate that the connection.type is set to gateway, and the Reachable column should indicate true for all URLs.

   Here's an example of the Arc agent using the Arc gateway:

   

   You can also audit your gateway traffic by viewing the gateway router logs.

   To view gateway router logs on Windows, run the azcmagent logs command in PowerShell. In the resulting .zip file, the logs are located in the C:\ProgramData\Microsoft\ArcGatewayRouter folder.

Via Configurator app

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

Prerequisites

Azure Local machine prerequisites

• Download the Configurator App for Azure Local on a client machine that's connected to the same network as the Azure Local machines.

• Note down:

  • The serial number for each machine.
  • Local administrator credentials to sign in to each machine.

Azure prerequisites

• Create an Arc gateway resource in the same subscription that you use to deploy Azure Local. For more information, see Create the Arc gateway resource in Azure.

  1. In the Azure portal, go to the Arc gateway resource that you created.
  2. On the Overview page, copy the Resource ID. You use this Arc gateway ID during registration.

  

Register Azure Local by using the Configurator app

Use the Configurator app to configure machine settings and register Azure Local with Azure Arc.

Sign in to the Configurator app

1. On the client machine, launch the Configurator app.

2. On the Machine name page, enter the machine name, serial number, hostname, or IP address of the Azure Local machine, and then select Next.

   

3. Enter the local administrator password, and then select Sign in.

   

4. After authentication, review the configuration status and prerequisite validation results.

   

Configure machine settings

1. On the Basics page, review the following machine configuration:

   • Network settings
   • DNS configuration
   • Remote Desktop settings
   • Connectivity method
   • Time zone
   • Time server
   • Hostname

   

2. To modify network settings, select Edit network settings. Provide the interface name, IP allocation method, IP address, subnet, gateway, and preferred DNS server. Optionally, enter an alternate DNS server.

   

   Important

   Ensure that the IP addresses you assign are available and not in use.

3. To modify Remote Desktop, connectivity, time server, or hostname settings, select Edit settings.

   

4. Enter the following additional details:

   1. Select a time zone.

   2. Specify an NTP server or accept the default value, time.windows.com. Optionally, add an alternate NTP server.

   3. Enable Remote Desktop if required. Remote Desktop is disabled by default.

   4. Under Connectivity, select the option that uses a proxy server.

   5. Enter the proxy server URL.

   6. Configure the proxy bypass list. Observe the following requirements:

      • Include the IP address and NetBIOS name of each Azure Local machine.
      • Include the IP address and NetBIOS name of the Azure Local cluster.
      • Include the IP addresses that you defined for the infrastructure network, or bypass the entire infrastructure subnet. Arc resource bridge, Azure Kubernetes Service (AKS), and future infrastructure services that use these addresses require outbound connectivity.
      • Separate entries with commas.
      • To bypass a subnet, use a wildcard pattern such as 192.168.1.*. Classless Inter-Domain Routing (CIDR) notation isn't supported.
      • To bypass a domain and its subdomains, use a wildcard pattern such as *.contoso.com.
      • Don't use <local> in the proxy bypass list.

   7. Specify a hostname for the machine. Changing the hostname automatically restarts the machine.

   8. When you finish configuring the machine settings, continue to Arc agent setup.

Configure Azure Arc registration

1. On the Arc agent setup page, select Log in to Azure.

   

2. Sign in with an Azure account that has permissions to register Azure Local with Azure Arc.

3. Enter the following information:

   • Cloud type. This field is populated automatically as Azure.
   • Tenant ID. If you register by using an Arc gateway, enter the directory ID of your Microsoft Entra tenant. If you register without an Arc gateway, skip this field. To get the tenant ID, see Find your Microsoft Entra tenant.
   • Subscription. Enter a subscription ID to register the machine.
   • Resource group. The resource group for Azure Local resources. This resource group contains the machine and system resources that you create.
   • Region. The Azure region where you want to create resources. The region should be the same as the region where you want to deploy the Azure Local instance. Specify the region with spaces removed. For example, specify the East US region as EastUS.
   • Azure Arc gateway. This is the resource ID of the Arc gateway that you set up. If you register by using an Arc gateway, select the Arc gateway resource that you created earlier. If you register without an Arc gateway, skip this field. For more information, see About Azure Arc gateways.

4. Verify the information, and then select Next.

Review and apply configuration

1. On the Review and apply page, review the configuration.

   

2. Select Done to start the configuration and registration process.

3. Monitor the registration progress on the Configuration status page. Select View details when available to open the details pane on the right. The app might display the following states:

   • Registration not started.

     

   • Update available.

     

   • Configuration in progress.

     

   • Registration completed successfully.

     

Verify machines are connected to Azure Arc

1. In the Azure portal, go to the resource group that you used for bootstrapping.

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

Troubleshoot and collect support logs

Use the support and troubleshooting tools in the Configurator app to collect logs and diagnose issues.

1. Select the Support icon in the upper-right corner of the Configurator app.

2. Use the available options to:

   • Create a support log package.
   • Download a support log package.
   • Upload a support package to Microsoft.
   • Run diagnostic tests.

   The following example shows a support log package being created:

   

   The following example shows a completed support log package that is ready for download or upload:

   

Note

Use the generated support package when you work with Microsoft Support to troubleshoot Azure Arc registration or connectivity issues.

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. For an overview of the Arc gateway, see About Azure Arc gateway for Azure Local.

• 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

Prerequisites

• You have access to Azure Local machines running release 2506 or later. Earlier versions don't support this scenario.

• You have assigned the appropriate permissions to the subscription used for registration. For more information, see Assign required permissions for Azure Local deployment.

• An Arc gateway resource is created in the same subscription used to deploy Azure Local. For more information, see Create the Arc gateway resource in Azure.

• You have reviewed the supported and unsupported scenarios. For more information, see Supported and unsupported scenarios.

• Required endpoints are open in your firewall. For more information, see Azure Local endpoints not redirected.

Step 1: Get the Arc gateway ID

• Get Arc gateway ID. To create Azure Arc gateway, see Set up an Azure Arc gateway and get the resource ID of the Arc gateway. This is also referred to as the ArcGatewayID.

  1. In the Azure portal, go to the Arc gateway resource that you created.
  2. On the Overview page, copy the Resource ID. You use this Arc gateway ID later.

  

Step 2: 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.
ArcGatewayID	Define the Arc gateway resource ID from Azure.
ArmAccessToken	Optional. Required if you choose to authenticate by using an ARM access token. If you omit this parameter, the script prompts for device code authentication.
TargetSolutionVersion	Optional. The target Azure Local solution version to use for the initial deployment after Azure Arc registration. If you don't specify this optional parameter, you're prompted to select a version from the list of available versions. For example: 12.2602.1002.10.

Step 3: 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.

#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 Arc gateway resource ID from Azure 
$ArcgwId = "/subscriptions/yoursubscriptionid/resourceGroups/yourResourceGroupName/providers/Microsoft.HybridCompute/gateways/yourArcGatewayName" 

#Optional: Define the Azure Resource Manager access token.
# Required only if you want to use token-based authentication instead of device code authentication.
$armTokenResponse = Get-AzAccessToken

# Convert token to string for use in initialization
# Required because Get-AzAccessToken returns SecureString
$ArmAccessToken = [System.Net.NetworkCredential]::new("", $armTokenResponse.Token).Password

#Optional: The target Azure Local solution version for initial deployment after Azure Arc registration. If omitted, select a version from the available options.
$TargetSolutionVersion = "<solution-version>" 

Step 4: Run the registration script

Note

During Azure Arc registration, select a target Azure Local solution version for the initial deployment. Specify the version by using the optional TargetSolutionVersion parameter, or select a version when prompted.

To use the Arc gateway feature for Azure Local systems without a proxy, only use the ArcGatewayID parameter.

1. Run the initialization script as follows.

   Invoke-AzStackHciArcInitialization
   -TenantId $Tenant
   -SubscriptionID $Subscription
   -ResourceGroup $RG
   -Region $Region
   -Cloud "AzureCloud"
   -ArcGatewayID $ArcgwId
   # Optional: include only when using token-based authentication
   -ArmAccessToken $ArmAccessToken
   # Optional: The target Azure Local solution version for initial deployment after Azure Arc registration. If omitted, select a version from the available options.
   -TargetSolutionVersion $TargetSolutionVersion
   

   Note

   If using -ArmAccessToken, convert the token to a plain text string by using: $ArmAccessToken = [System.Net.NetworkCredential]::new("", $armTokenResponse.Token).Password.

2. 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, in order to authenticate. Follow the instructions to complete the authentication process.

   

3. If an update is required:

   • The update typically takes 40-45 minutes, followed by a reboot.
   • During the update, the registration status appears as Update: InProgress.
   • Rerun Invoke-AzStackHciArcInitialization cmdlet after reboot.

   

Monitor and complete registration

1. If registration times out or the machine reboots, reconnect and check the registration progress by running the following commands:

   $status = Get-ArcBootstrapStatus
   $status.Response.Status
   

2. Review the status value:

   • Succeeded: Registration completed successfully.
   • Failed: Rerun registration by using a new ARM token or device code flow.
   • If the issue persists, collect logs by running Collect-ArcBootstrapSupportLogs and share them for further troubleshooting.

3. After the reboot, rerun the Invoke-AzStackHciArcInitialization cmdlet to continue.

Step 5: Verify the setup is successful

Once the registration is complete, follow these steps to verify that Azure Arc gateway setup is successful.

1. Connect to the first Azure Local machine from your system.

2. Open the Arc gateway log to monitor the endpoints that are being redirected to the Arc gateway and which ones continue using your firewall. You can find the Arc gateway log at: c:\programdata\AzureConnectedMAchineAgent\Log\arcproxy.log.

   

3. To check the Arc agent configuration and verify that it's using the gateway, run the following command:

   C:\program files\AzureConnectedMachineAgent>.\azcmagent show
   

   The values displayed should be as follows:

   1. Agent version is 1.45 or later.

   2. Agent Status should show as Connected.

   3. Using HTTPS Proxy shows as http://localhost:40343when the Arc gateway is enabled.

   4. Upstream Proxy shows your enterprise proxy server and port.

   5. Azure Arc Proxy shows as running when the Arc gateway is enabled.

   The Arc agent using the Arc gateway:

   

4. Additionally, to verify that the setup was done successfully, run the following command:

   C:\program files\AzureConnectedMachineAgent>.\azcmagent check
   

   The response should indicate that the connection.type is set to gateway, and the Reachable column should indicate true for all URLs.

   The Arc agent using the Arc gateway:

   

   You can also audit your gateway traffic by viewing the gateway router logs.

   To view gateway router logs on Windows, run the azcmagent logs command in PowerShell. In the resulting .zip file, the logs are located in the C:\ProgramData\Microsoft\ArcGatewayRouter folder.

Via Configurator app

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

Prerequisites

Azure Local machine prerequisites

• Download the Configurator App for Azure Local on a client machine that's connected to the same network as the Azure Local machines.

• Note down:

  • The serial number for each machine.
  • Local administrator credentials to sign in to each machine.

Azure prerequisites

• Create an Arc gateway resource in the same subscription that you use to deploy Azure Local. For more information, see Create the Arc gateway resource in Azure.

  1. In the Azure portal, go to the Arc gateway resource that you created.
  2. On the Overview page, copy the Resource ID. You use this Arc gateway ID during registration.

  

Register Azure Local by using the Configurator app

Use the Configurator app to configure machine settings and register Azure Local with Azure Arc.

Sign in to the Configurator app

1. On the client machine, launch the Configurator app.

2. On the Machine name page, enter the machine name, serial number, hostname, or IP address of the Azure Local machine, and then select Next.

   

3. Enter the local administrator password, and then select Sign in.

   

4. After authentication, review the configuration status and prerequisite validation results.

   

Configure machine settings

1. On the Basics page, review the following machine configuration:

   • Network settings
   • DNS configuration
   • Remote Desktop settings
   • Connectivity method
   • Time zone
   • Time server
   • Hostname

   

2. To modify network settings, select Edit network settings. Provide the interface name, IP allocation method, IP address, subnet, gateway, and preferred DNS server. Optionally, enter an alternate DNS server.

   

   Important

   Ensure that the IP addresses you assign are available and not in use.

3. To modify Remote Desktop, connectivity, time server, or hostname settings, select Edit settings.

   

4. Enter the following details:
   1. Select a time zone.
   2. Specify an NTP server or accept the default value, time.windows.com. Optionally, add an alternate NTP server.
   3. Enable Remote Desktop if required. Remote Desktop is disabled by default.
   4. Under Connectivity, select Public endpoint.
   5. Specify a hostname for the machine. Changing the hostname automatically restarts the machine.
   6. When you finish configuring the machine settings, continue to Arc agent setup.

Configure Azure Arc registration

1. On the Arc agent setup page, select Log in to Azure.

   

2. Sign in with an Azure account that has permissions to register Azure Local with Azure Arc.

3. Enter the following information:

   • Cloud type. This field is populated automatically as Azure.
   • Tenant ID. If you register by using an Arc gateway, enter the directory ID of your Microsoft Entra tenant. If you register without an Arc gateway, skip this field. To get the tenant ID, see Find your Microsoft Entra tenant.
   • Subscription. Enter a subscription ID to register the machine.
   • Resource group. The resource group for Azure Local resources. This resource group contains the machine and system resources that you create.
   • Region. The Azure region where you want to create resources. The region should be the same as the region where you want to deploy the Azure Local instance. Specify the region with spaces removed. For example, specify the East US region as EastUS.
   • Azure Arc gateway. This is the resource ID of the Arc gateway that you set up. If you register by using an Arc gateway, select the Arc gateway resource that you created earlier. If you register without an Arc gateway, skip this field. For more information, see About Azure Arc gateways.

4. Verify the information, and then select Next.

Review and apply configuration

1. On the Review and apply page, review the configuration.

   

2. Select Done to start the configuration and registration process.

3. Monitor the registration progress on the Configuration status page. Select View details when available to open the details pane on the right. The app might display the following states:

   • Registration not started.

     

   • Update available.

     

   • Configuration in progress.

     

   • Registration completed successfully.

     

Verify machines are connected to Azure Arc

1. In the Azure portal, go to the resource group that you used for bootstrapping.

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

Troubleshoot and collect support logs

Use the support and troubleshooting tools in the Configurator app to collect logs and diagnose issues.

1. Select the Support icon in the upper-right corner of the Configurator app.

2. Use the available options to:

   • Create a support log package.
   • Download a support log package.
   • Upload a support package to Microsoft.
   • Run diagnostic tests.

   The following example shows a support log package being created:

   

   The following example shows a completed support log package that is ready for download or upload:

   

Note

Use the generated support package when you work with Microsoft Support to troubleshoot Azure Arc registration or connectivity issues.

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