Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
This article explains how to register disconnected operations for Azure Local after deploying your management cluster with the control plane. Learn how to ensure compliance with Azure Local requirements through proper registration.
Get the registration file
The registration file contains data about your Azure Local deployment, which is required to complete the registration process in the Azure portal.
To register disconnected operations for Azure Local, first generate a registration file from your management cluster.
Note
Certain compliance regulations prohibit copying data from air-gapped environments. If these restrictions prevent copying the registration file, use the self-attestation flow.
Follow these steps to create and export the registration file:
On your management cluster, sign in to the seed node by using local administrator credentials.
Import the operations module and initialize the management context:
# Replace with your actual values. $applianceConfigBasePath = 'C:\AzureLocalDisconnectedOperations' Import-Module "$applianceConfigBasePath\OperationsModule\Azure.Local.DisconnectedOperations.psd1" -Force $password = ConvertTo-SecureString 'RETRACTED' -AsPlainText -Force $context = Set-DisconnectedOperationsClientContext -ManagementEndpointClientCertificatePath "${env:localappdata}\AzureLocalOpModuleDev\certs\ManagementEndpoint\ManagementEndpointClientAuth.pfx" -ManagementEndpointClientCertificatePassword $password -ManagementEndpointIpAddress "169.254.53.25"Export the appliance registration data file by using the following command:
$file = 'AzureLocal-managementCluster.reg' Export-ApplianceRegistrationData -File $fileCopy this file to a machine that you can use to connect to the internet.
Complete the registration
To finalize the registration process for disconnected operations, follow these steps in the Azure portal.
- On an internet connected machine, navigate to the Azure portal.
- Navigate to your disconnected operations resource.
- Check for a banner that indicates that your disconnected operations resource isn't registered.
- Select the Register button, and then upload the registration file.
- Confirm the registration details and select Register.
- After the operation completes, the Registration status changes to Registered.
Registration using self-attestation flow
If you can't register Azure Local disconnected operations using the registration file flow, use the self-attestation flow instead.
On a machine with internet access, ensure that Azure CLI and Azure PowerShell are installed.
Copy the provided function from PowerShell.
function New-AzureLocalDisconnectedOperationsSelfAttestation {
<#
.SYNOPSIS
Registers your disconnected operations resource using a self-attestation flow.
#>
[CmdletBinding()]
param(
[Parameter(Mandatory)]
[ValidateSet('AzureCloud', 'AzureUSGovernment']
[string]$Cloud,
[Parameter(Mandatory)]
[string]$SubscriptionId,
[Parameter(Mandatory)]
[string]$ResourceGroup,
[Parameter(Mandatory)]
[string]$ResourceName,
[Parameter(Mandatory)]
[int]$TotalCores,
[Parameter(Mandatory)]
[int]$DiskSpaceInGb,
[Parameter(Mandatory)]
[int]$MemoryInGb,
[Parameter(Mandatory)]
[string]$Oem,
[Parameter(Mandatory)]
[string]$HardwareSku,
[Parameter(Mandatory)]
[int]$Nodes,
[Parameter(Mandatory)]
[string]$VersionAtRegistration,
[Parameter(Mandatory)]
[string]$SolutionBuilderExtension,
[Parameter(Mandatory)]
[string]$DeviceId,
[string]$ApiVersion = '2026-03-01-preview',
[switch]$SkipLogin
)
if (-not $SkipLogin) {
Connect-AzureForCloud -Cloud $Cloud
}
$baseEndpoint = switch ($Cloud) {
'AzureCloud' { 'management.azure.com' }
'AzureUSGovernment' { 'management.usgovcloudapi.net' }
'AzureChinaCloud' { 'management.chinacloudapi.cn' }
}
$token = Get-BearerToken
$uri = "https://$baseEndpoint/subscriptions/$SubscriptionId/resourceGroups/$ResourceGroup/providers/Microsoft.Edge/disconnectedOperations/$ResourceName/hardwareSettings/default?api-version=$ApiVersion"
$body = @{
properties = @{
totalCores = $TotalCores
diskSpaceInGb = $DiskSpaceInGb
memoryInGb = $MemoryInGb
oem = $Oem
hardwareSku = $HardwareSku
nodes = $Nodes
versionAtRegistration = $VersionAtRegistration
solutionBuilderExtension = $SolutionBuilderExtension
deviceId = $DeviceId
}
} | ConvertTo-Json -Depth 5
Write-Host "Creating HardwareSetting for '$ResourceName'..." -ForegroundColor Cyan
Write-Host " PUT $uri" -ForegroundColor DarkGray
$response = Invoke-RestMethod -Method Put -Uri $uri -Headers @{
Authorization = $token
'Content-Type' = 'application/json'
} -Body $body
Write-Host "HardwareSetting created successfully." -ForegroundColor Green
$response | ConvertTo-Json -Depth 10
}
Register your Azure Local disconnected operations
# Modify these to fit your disconnected operations resource.
$params = @{
Cloud = 'AzureCloud'
SubscriptionId = ''
ResourceGroup = ''
ResourceName = ''
TotalCores = 320 # Total cores managed by Azure Local disconnected operations
DiskSpaceInGb = 2000 # Management cluster total disk capacity
MemoryInGb = 2000 # Total memory
Oem = '' # E.g. Dell / Lenovo / HPE etc.
HardwareSku = '' # E.g. AX-760 / MX 655
Nodes = 10
VersionAtRegistration = '2602.2.32510'
SolutionBuilderExtension = 'x.y.z'
DeviceId = '' # Copy your device id from portal
ApiVersion = '2026-03-01-preview'
}
New-AzureLocalDisconnectedOperationsSelfAttestation @params
Related content
This feature is available only in Azure Local 2602 or later.