Merge branch 'MicrosoftDocs:release-local-disconnectednew' into release-local-disconnectednew

Author: haraldfianbakken

azure-local/TOC.yml

@@ -570,6 +570,8 @@ items:
         href: migrate/migrate-enable-guest-management.md
     - name: Maintain static IP addresses
       href: migrate/migrate-maintain-ip-addresses.md
+    - name: Monitor Azure Local migrations
+      href: migrate/monitor-migration.md
     - name: FAQ
       href: migrate/migrate-faq.yml
     - name: Troubleshoot

azure-local/deploy/deployment-azure-resource-manager-template.md

@@ -3,7 +3,7 @@ title: Release notes with fixed and known issues in Azure Local
 description: Read about the known issues and fixed issues in Azure Local.
 author: alkohli
 ms.topic: conceptual
-ms.date: 07/30/2025
+ms.date: 08/01/2025
 ms.author: alkohli
 ms.reviewer: alkohli
 ---
@@ -51,7 +51,12 @@ The following table lists the fixed issues in this release:
 
 ## Known issues
 
-Microsoft isn't aware of any known issues in this release.
+The following is a known issue with this release.
+
+|Feature  |Issue  |Workaround  |
+|---------|---------|---------|
+| Update | When installing cumulative updates using Azure Update Manager, only the latest update for version 2507 is installed. If earlier update options (for versions 2505, 2506) are selected, they are not installed. | There's no workaround in this release. |
+
 
 ## Known issues from previous releases
 

azure-local/known-issues.md

@@ -4,7 +4,7 @@ description: Manage Azure Kubernetes Service (AKS) Arc for Azure Local with disc
 ms.topic: how-to
 author: ronmiab
 ms.author: robess
-ms.date: 06/20/2025
+ms.date: 08/06/2025
 ai-usage: ai-assisted
 ---
 

azure-local/manage/disconnected-operations-aks.md

@@ -4,7 +4,7 @@ description: Learn how to manage Azure Local VMs running disconnected (preview).
 ms.topic: concept-article
 author: ronmiab
 ms.author: robess
-ms.date: 06/20/2025
+ms.date: 08/06/2025
 ai-usage: ai-assisted
 ---
 
@@ -36,37 +36,30 @@ Azure Local VMs running disconnected operations have the following limitations:
 
 ### VM images
 
-- Create VM images only from a local share.
-- Create VM images only using Azure Command Line (CLI). This release doesn't support image creation in the Azure portal.
 - Marketplace, Azure storage account, and images from an existing Azure Local VM aren't supported.
+- Create VM images only from a local share.
 
 ### Network interfaces
 
 Create network interfaces only in CLI. This release doesn't support network interface creation in the Azure portal.
 
 ### Storage paths
 
-- Create storage paths only in CLI. This release doesn't support storage path creation in the Azure portal.
-- Don't delete storage paths using CLI or the portal if they're connected to an Azure Local VM or VM image. First, delete the Azure Local VM and image using that storage path.
+To delete storage paths from CLI or Portal, first delete any resources (VMs, images, disks) that are on the storage path.
 
 ### Logical networks
 
-- Create logical networks only in CLI; the portal isn't supported.
-- You can see and use logical networks, but they might not fully load in the portal.
-- Deleting a logical network used by a network interface doesn't fail as expected. It deletes the network and results in a **Failed** state. To recover, recreate the logical network.
+You can see and use logical networks, but they might not fully load in the portal.
 
 ### Proxy servers
 
 Proxy servers aren't supported for outbound internet connections.
 
-### Machine creation
+### VM creation
 
-- Create a VM in the portal by selecting **Azure Arc** > **Machines** > **Add/Create** > **Create a machine in a connected host environment**. For more information, see step 7 under the Create Azure Local VMs section.
+Create a VM in the portal by selecting **Azure Arc** > **Machines** > **Add/Create** > **Create a machine in a connected host environment**. For more information, see step 7 under the Create Azure Local VMs section.
 
-    :::image type="content" source="./media/disconnected-operations/arc-vms/create-arc-vms.png" alt-text="Screenshot showing how create an Azure Local VM from the portal." lightbox=" ./media/disconnected-operations/arc-vms/create-arc-vms.png":::
-
-    > [!NOTE]
-    > Don't use the **Create** button in the Virtual Machines section of the Azure Local resource on the portal to create a machine.
+:::image type="content" source="./media/disconnected-operations/arc-vms/create-arc-vms.png" alt-text="Screenshot showing how to create an Azure Local VM from the portal." lightbox=" ./media/disconnected-operations/arc-vms/create-arc-vms.png":::
 
 ## Create Azure Local VMs with disconnected operations
 
@@ -75,7 +68,7 @@ Follow these steps to create Azure Local VMs running disconnected operations.
 1. [Review prerequisites](../manage/azure-arc-vm-management-prerequisites.md).
 
     - [Install the Azure CLI](disconnected-operations-cli.md#install-azure-cli) version AzCLI 2.60.0.
-    - Install the Azure Local extension **stack-hci-vm** version v1.3.0.
+    - [Install the latest Azure Local extension **stack-hci-vm** version](disconnected-operations-cli.md#extensions-for-azure-cli).
     - [Sign into Azure interactively using the Azure CLI](/cli/azure/authenticate-azure-cli-interactively).
 
 2. [Assign role-based access control (RBAC) roles](../manage/assign-vm-rbac-roles.md).
@@ -202,11 +195,11 @@ Follow these steps to create Azure Local VMs running disconnected operations.
 
 To manage Azure Local VMs using CLI, see [Azure Local VMs using the Azure CLI](/azure/azure-local/manage/manage-arc-virtual-machines?view=azloc-24112&tabs=windows&preserve-view=true). To check the status of the VM, see [Status of the VM](../manage/manage-arc-virtual-machines.md#status-displayed-as-connecting).
 
-For Azure Local VM resources:
+<!--For Azure Local VM resources:
 
 - If you remove a data disk interface used by a VM, the command doesn't fail as expected. Instead, it deletes the data disk interface and sets the provisioning state as **Failed**.
 
-- To restore the provisioning state to **Succeeded**, recreate the data disk.
+- To restore the provisioning state to **Succeeded**, recreate the data disk.-->
 
 ## Manage VM extensions
 
@@ -216,6 +209,8 @@ To manage VM extensions, see [Manage VM extensions](../manage/virtual-machine-ma
 
 ## Related content
 
+- [Manage Azure Local VMs enabled by Azure Arc](../manage/manage-arc-virtual-machines.md)
+
 - [Collect log files for Azure Local VMs](../manage/collect-log-files-arc-enabled-vms.md)
 
 - [Troubleshoot Azure Local VM management](../manage/troubleshoot-arc-enabled-vms.md)

azure-local/manage/disconnected-operations-arc-vm.md

@@ -4,7 +4,7 @@ description: Learn how to deploy and manage Azure Container Registry with discon
 ms.topic: how-to
 author: ronmiab
 ms.author: robess
-ms.date: 06/20/2025
+ms.date: 08/06/2025
 ai-usage: ai-assisted
 ---
 
@@ -45,7 +45,7 @@ Key features of Azure Container Registry on disconnected operations include:
 - Make sure that the disconnected operations virtual machine is deployed.
 - Check that you can access the disconnected operations portal.
 - Register the *Microsoft.ContainerRegistry* resource provider with disconnected operations.
-- [Install the Azure CLI](disconnected-operations-cli.md#install-azure-cli) (supported up to version 2.54.0.).
+- [Install the Azure CLI](disconnected-operations-cli.md#install-azure-cli) (supported up to version 2.54.0).
 - (Optional) [Install Docker Desktop](https://www.docker.com/get-started/) on your disconnected operations host or client machine for testing.
 
 ## Deploy Azure Container Registry for disconnected operations

azure-local/manage/disconnected-operations-azure-container-registry.md

@@ -4,7 +4,7 @@ description:  Learn how to use the Azure Command-Line Interface (CLI) for discon
 ms.topic: how-to
 author: ronmiab
 ms.author: robess
-ms.date: 06/20/2025
+ms.date: 08/06/2025
 ai-usage: ai-assisted
 ---
 
@@ -51,7 +51,7 @@ For disconnected operations:
 1. Understand [public key infrastructure (PKI) for Azure Local with disconnected operations (preview)](disconnected-operations-pki.md)
 2. Set up and configure the certificate trusts for Azure CLI using PowerShell.
 
-    Here's an example script you can run in Powershell:
+    Here's an example script you can run in PowerShell:
 
     ```powershell    
         # Define the helper method
@@ -220,9 +220,9 @@ The following table lists the CLI extensions supported on Azure Local disconnect
 |----------------------------------|------------|------------------------------------|--------------------------|  
 | Arc-enabled servers              | az connectedmachine | 1.1.0 | [az connectedmachine](/cli/azure/connectedmachine?view=azure-cli-latest&preserve-view=true)  |
 | Azure Arc-enabled Kubernetes clusters  | az connectedk8s <br></br> az k8s-extension <br></br> az k8s-configuration <br></br> az customlocation | connectedk8s: 1.6.2 <br></br> k8s-extension: 1.4.5 <br></br> k8sconfiguration: 2.0.0 <br></br> customlocation: 0.1.4 | [az connectedk8s](/cli/azure/connectedk8s?view=azure-cli-latest&preserve-view=true) <br></br> [az k8s-extension](/cli/azure/k8s-extension?view=azure-cli-latest&preserve-view=true) <br></br> [az k8s-configuration flux](/cli/azure/k8s-configuration/flux?view=azure-cli-latest&preserve-view=true) <br></br> [az customlocation](/cli/azure/customlocation?view=azure-cli-latest&preserve-view=true)  |
-| Azure Local VMs enabled by Azure Arc    | az arcappliance <br></br> az k8s-extension <br></br> az customlocation <br></br> az stack-hci-vm | arcappliance: 1.4.1 <br> k8s-extension: 1.4.5  <br></br> customlocation: 0.1.4 <br></br> stack-hci-vm: 1.9.1 | [Enable Azure VM extensions using CLI](/azure/azure-arc/servers/manage-vm-extensions-cli) <br></br> [Troubleshoot Arc-enabled servers VM extension issues](/azure/azure-arc/servers/troubleshoot-vm-extensions)  |
-| AKS Arc on Azure Local | az arcappliance <br></br> az k8s-extension <br></br> az customlocation <br></br> az stack-hci-vm <br></br> az aksarc | arcappliance: 1.4.1 <br></br>  <br></br> k8s-extension: 1.4.5 <br></br> customlocation: 0.1.4 <br></br> stack-hci-vm: 1.9.1 <br></br> aksarc: 1.2.23 | [Create Kubernetes clusters using Azure CLI](/azure/aks/aksarc/aks-create-clusters-cli) |
-| Azure Local Resource Provider          | Arcappliance <br></br> k8s-extension <br></br> customlocation <br></br> stack-hci-vm <br></br> connectedk8s <br></br> stack-hci | arcappliance: 1.4.1 <br></br>  <br></br> k8s-extension: 1.4.5 <br></br> customlocation: 0.1.4 <br></br> stack-hci-vm: 1.9.1 <br></br> connectedk8s: 1.6.2 <br></br> stack-hci: 1.1.0 | [How to install and manage Azure CLI extensions](/cli/azure/azure-cli-extensions-overview) |
+| Azure Local VMs enabled by Azure Arc    | az arcappliance <br></br> az k8s-extension <br></br> az customlocation <br></br> az stack-hci-vm | arcappliance: 1.4.1 <br></br> k8s-extension: 1.4.5 <br></br> customlocation: 0.1.4 <br></br> stack-hci-vm: 1.9.1 | [Enable Azure VM extensions using CLI](/azure/azure-arc/servers/manage-vm-extensions-cli) <br></br> [Troubleshoot Arc-enabled servers VM extension issues](/azure/azure-arc/servers/troubleshoot-vm-extensions)  |
+| AKS Arc on Azure Local | az arcappliance <br></br> az k8s-extension <br></br> az customlocation <br></br> az stack-hci-vm <br></br> az aksarc | arcappliance: 1.4.1 <br></br> k8s-extension: 1.4.5 <br></br> customlocation: 0.1.4 <br></br> stack-hci-vm: 1.9.1 <br></br> aksarc: 1.2.23 | [Create Kubernetes clusters using Azure CLI](/azure/aks/aksarc/aks-create-clusters-cli) |
+| Azure Local Resource Provider          | Arcappliance <br></br> k8s-extension <br></br> customlocation <br></br> stack-hci-vm <br></br> connectedk8s <br></br> stack-hci | arcappliance: 1.4.1 <br></br> k8s-extension: 1.4.5 <br></br> customlocation: 0.1.4 <br></br> stack-hci-vm: 1.9.1 <br></br> connectedk8s: 1.6.2 <br></br> stack-hci: 1.1.0 | [How to install and manage Azure CLI extensions](/cli/azure/azure-cli-extensions-overview) |
 | Azure Container Registry | Built-in      |    |  |
 | Azure Policy | Built-in      |    | [Quickstart: Create a policy assignment to identify noncompliant resources using Azure CLI](/azure/governance/policy/assign-policy-azurecli) |
 | Azure Key Vault | Built-in      |    | [Quickstart: Create a key vault using Azure CLI](/azure/key-vault/general/quick-create-cli) |

azure-local/manage/disconnected-operations-cli.md

@@ -4,7 +4,7 @@ description: Learn how to deploy disconnected operations for Azure Local in your
 ms.topic: how-to
 author: ronmiab
 ms.author: robess
-ms.date: 06/20/2025
+ms.date: 08/06/2025
 ai-usage: ai-assisted
 ---
 
@@ -105,8 +105,8 @@ To prepare each machine for the disconnected operations appliance, follow these
 
 1. [Rename each node](/powershell/module/microsoft.powershell.management/rename-computer?view=powershell-7.4&preserve-view=true) according to your environments naming conventions. For example, azlocal-n1, azlocal-n2, and azlocal-n3.  
 
- 1. Check and make sure you have sufficient disk space for disconnected operations deployment.
- 
+1. Check and make sure you have sufficient disk space for disconnected operations deployment.
+
     Make sure you have at least 600 GB of free space on the drive you plan to use for deployment. If your drive has less space, use a data disk on each node and initialize it so each node has the same available data disks for deployment.
 
     Here’s how to initialize a disk on the nodes and format it for a D partition: 
@@ -145,11 +145,10 @@ To prepare each machine for the disconnected operations appliance, follow these
     > [!NOTE]
     > If you use a different root for the management certificate, repeat the process and import the key on each node.
 
-
 1. [Install and configure the CLI](disconnected-operations-cli.md) with your local endpoint on each node.
-   
+
 1. Set the environment variable to support disconnected operations
-   
+
     ```powershell
     [Environment]::SetEnvironmentVariable("DISCONNECTED_OPS_SUPPORT", $true, [System.EnvironmentVariableTarget]::Machine)
     ```
@@ -173,9 +172,9 @@ To prepare the first machine for the disconnected operations appliance, follow t
 1. Modify your path to correct location. 
 
     If you initialized a data disk or are using a different path than C: modify the `$applianceConfigBasePath`.
-    
+
     Here's an example:
-    
+
     ```powershell
     $applianceConfigBasePath = 'C:\AzureLocalDisconnectedOperations'
     ```
@@ -333,7 +332,6 @@ Populate the required parameters based on your deployment planning. Modify the e
     copy-item AzureLocal.DisconnectedOperations.Manifest.json $applianceConfigBasePath\AzureLocal.DisconnectedOperations.manifest.json
     ```  
 
-
 ## Install and configure the appliance  
 
 To install and configure the appliance on the first machine (seed node), use the following command. Point the `AzureLocalInstallationFile` to a path that contains the **IRVM01.zip**.
@@ -463,10 +461,10 @@ Wait until all resource providers are in the state **Registered**. Here's a samp
 
 ```azurecli  
     az provider list -o table
-``` 
+```
 
-> [!NOTE] 
-> You can also register or view resource provider statuses in the local portal. To do this, go to your **Subscription**, click the dropdown arrow for **Settings**, and select **Resource providers**. 
+> [!NOTE]
+> You can also register or view resource provider statuses in the local portal. To do this, go to your **Subscription**, click the dropdown arrow for **Settings**, and select **Resource providers**.
 
 ### Create resource group SPN for cluster  
 
@@ -502,7 +500,6 @@ Use the operator account to create an SPN for Arc initialization of each Azure L
     >
     > Don't place the cluster resource in the operator subscription, unless you plan to restrict this to only operators with full access to other operations. You can create more subscriptions or place it in the starter subscription.
 
-
 ### Initialize each node
 
 To initialize each node, follow these steps. Modify where necessary to match your environment details:
@@ -594,7 +591,7 @@ To initialize each node, follow these steps. Modify where necessary to match you
     > Nodes appear in the local portal shortly after you run the steps, and the extensions appear on the nodes a few minutes after installation.  
     >
     > You can also use the [Configurator App](../deploy/deployment-arc-register-configurator-app.md?view=azloc-2506&preserve-view=true) to initialize each node.
-    
+
 ### For fully air-gapped or disconnected deployments (where nodes have no line of sight to internet connection)
 
 To enable Azure Local to be air-gapped or deployed fully disconnected, you must do the following on each node:
@@ -640,7 +637,7 @@ Follow these steps to create an Azure Local instance (cluster):
 
   > [!NOTE]
   > If you create Azure Key Vault during deployment, wait about 20 minutes for RBAC permissions to take effect.
-  > 
+  >
   > If you see a validation error, it’s a known issue. Permissions might still be propagating. Wait a bit, refresh your browser, and redeploy the cluster.
 
 ## Tasks after deploying disconnected operations