Merge pull request #18310 from MicrosoftDocs/main

Merged by Learn.Build PR Management system

Author: learn-build-service-prod[bot]

AKS-Arc/aks-troubleshoot.md

@@ -3,7 +3,7 @@ title: Troubleshoot common issues in AKS enabled by Azure Arc
 description: Learn about common issues and workarounds in AKS enabled by Arc.
 ms.topic: how-to
 author: sethmanheim
-ms.date: 06/18/2025
+ms.date: 06/27/2025
 ms.author: sethm 
 ms.lastreviewed: 04/01/2025
 ms.reviewer: abha
@@ -16,7 +16,7 @@ This section describes how to find solutions for issues you encounter when using
 
 ## Open a support request
 
-To open a support request, see the [Get support](/azure/aks/hybrid/help-support) article for information about how to use the Azure portal to get support or open a support request for AKS Arc.
+To open a support request, see the [Get support](help-support.md) article for information about how to use the Azure portal to get support or open a support request for AKS Arc.
 
 ## Known issues
 
@@ -42,9 +42,10 @@ The following sections describe known issues for AKS enabled by Azure Arc:
 | Create validation      | [KubeAPIServer unreachable error](kube-api-server-unreachable.md) |
 | Network configuration issues | [Use diagnostic checker](aks-arc-diagnostic-checker.md) |
 | Kubernetes steady state   | [Resolve issues due to out-of-band deletion of storage volumes](delete-storage-volume.md) |
+| Kubernetes steady state   | [Repeated Entra authentication prompts when running kubectl with Kubernetes RBAC](entra-prompts.md) | 
 | Release validation     | [Azure Advisor upgrade recommendation message](azure-advisor-upgrade.md) |
 | Network validation | [Network validation error due to .local domain](network-validation-error-local.md) |
-| BGP with FRR not working | [Troubleshoot BGP with FRR in AKS Arc environments](connectivity-troubleshoot.md) |
+| Network validation | [Troubleshoot BGP with FRR in AKS Arc environments](connectivity-troubleshoot.md) |
 
 ## Next steps
 

azure-local/faq.yml

@@ -44,7 +44,7 @@ sections:
           
       - question: Are there bandwidth or latency requirements between Azure Local and the cloud?
         answer: |
-          No. Limited-bandwidth connections like rural T1 lines or satellite/cellular connections are adequate for Azure Local to sync. The minimum required connectivity is several kilobytes per day. More services might require extra bandwidth, especially to replicate or back up whole VMs, download large software updates, or upload verbose logs for analysis and monitoring in the cloud.
+          Yes. Limited-bandwidth connections like rural T1 lines or satellite/cellular connections are adequate for Azure Local to sync. The minimum required connectivity is 10 Mb per day. More services might require extra bandwidth, especially to replicate or back up whole VMs, download large software updates, or upload verbose logs for analysis and monitoring in the cloud.
 
       - question: Does Azure Local require continuous connectivity to the cloud?
         answer: |

azure-local/manage/add-server.md

@@ -4,7 +4,7 @@ description: Learn how to manage capacity on your Azure Local, version 23H2 syst
 ms.topic: how-to
 author: alkohli
 ms.author: alkohli
-ms.date: 06/25/2025
+ms.date: 06/26/2025
 ---
 
 # Add a node on Azure Local
@@ -110,19 +110,13 @@ On the new node that you plan to add, follow these steps.
 
 3. Assign the following permissions to the newly added nodes:
 
-    - Azure Local Device Management Role
+    - Azure Stack HCI Device Management Role
     - Key Vault Secrets User
     For more information, see [Assign permissions to the node](../deploy/deployment-arc-register-server-permissions.md).
 
 On a node that already exists on your system, follow these steps:
 
-1. Sign in with the domain user credentials (AzureStackLCMUser or another user with equivalent permissions) that you provided during the deployment of the system. 
-
-1. (Optional) Before you add the node, make sure to get an updated authentication token. Run the following command:
-
-    ```powershell
-    Update-AuthenticationToken 
-    ```
+1. Sign in with the domain user credentials (AzureStackLCMUser or another user with equivalent permissions) that you provided during the deployment of the system.
 
 1. Run the following command to add the new incoming node using a local administrator credential for the new node:
 

azure-local/manage/repair-server.md

@@ -4,7 +4,7 @@ description: Learn how to repair a node on your Azure Local, version 23H2 system
 ms.topic: how-to
 author: alkohli
 ms.author: alkohli
-ms.date: 06/25/2025
+ms.date: 06/26/2025
 ---
 
 # Repair a node on Azure Local
@@ -134,7 +134,7 @@ Follow these steps on the node you're trying to repair.
 
 1. Assign the following permissions to the repaired node:
 
-    - Azure Local Device Management Role
+    - Azure Stack HCI Device Management Role
     - Key Vault Secrets User
     For more information, see [Assign permissions to the node](../deploy/deployment-arc-register-server-permissions.md).
 

azure-local/migrate/migrate-vmware-requirements.md

@@ -3,7 +3,7 @@ title: Review requirements for VMware VM migration to Azure Local using Azure Mi
 description: Learn the system requirements for VMware migration to Azure Local using Azure Migrate (preview).
 author: alkohli
 ms.topic: how-to
-ms.date: 05/16/2025
+ms.date: 06/19/2025
 ms.author: alkohli
 ms.custom: references_regions
 ---
@@ -67,8 +67,6 @@ For any subscriptions hosting resources used in migration, such as Azure Migrate
 
 - Ensure that vCenter Server permission requirements are met. For more information, see [VMware vSphere requirements (agentless)](/azure/migrate/migrate-support-matrix-vmware-migration#agentless-migration).
 
-- In this release, you can only migrate VMs that have disks attached to the VMFS Datastores. If the VM disks aren't attached to the VMFS Datastore, the disks can’t be migrated.
-
 - Before you begin, for all VMware VMs, bring all the disks online and persist the drive letter. For more information, see how to [configure a SAN policy](/azure/migrate/prepare-for-migration#configure-san-policy) to bring the disks online.
 
 - The VMware source environment must be able to initiate a network connection with the target Azure Local instance, either by being on the same on-premises network or by using a VPN.

azure-stack/includes/app-service-hub-update-banner.md

@@ -3,7 +3,7 @@ author: apwestgarth
 ms.author: anwestg
 ms.service: azure-stack
 ms.topic: include
-ms.date: 01/31/2025
+ms.date: 06/25/2025
 ms.reviewer: sethm
 ms.lastreviewed: 10/28/2020
 ---
@@ -13,4 +13,4 @@ ms.lastreviewed: 10/28/2020
 >
 > | Supported minimum Azure Stack Hub version | App Service RP version |
 > |-----|---|
-> | 2311 and later | 24R1 [Installer](https://aka.ms/appsvcupdate24R1installer) ([release notes](../operator/app-service-release-notes-2024R1.md)) |
+> | 2311 and later | 25R1 [Installer](https://aka.ms/appsvcupdate25R1installer) 25R1 [Offline Package](https://aka.ms/appsvcupdate25R1offline) ([release notes](../operator/app-service-release-notes-2025R1.md)) |

azure-stack/operator/TOC.yml

@@ -386,16 +386,10 @@
           href: app-service-migrate-sql-server.md
       - name: Release notes
         items:
+        - name: 25R1 release notes [June 2025]
+          href: app-service-release-notes-2025R1.md
         - name: 24R1 release notes [December 2024]
           href: app-service-release-notes-2024R1.md
-        - name: 2302 release notes [February 2023]
-          href: app-service-release-notes-2302.md
-        - name: 2022 H1 release notes [October 2022]
-          href: app-service-release-notes-2022-h1.md
-        - name: 2021 Q3 release notes [December 2021]
-          href: app-service-release-notes-2021-Q3.md
-        - name: 2021 Q1 release notes [June 2021]
-          href: app-service-release-notes-2021-Q1.md
     - name: Azure Container Registry
       items:
       - name: Overview