Merge pull request #18448 from ronmiab/rb-do-july-upds

AnnaMHuff · web-flow · commit 00df0a9d0da2 · 2025-07-15T16:50:46.000-06:00
Updated the TOC for Disconnected operations
diff --git a/azure-local/TOC.yml b/azure-local/TOC.yml
@@ -665,7 +665,50 @@ items:
     - name: To same hardware
       href: migrate/migrate-cluster-same-hardware.md
     - name: To new hardware
-      href: migrate/migrate-cluster-new-hardware.md   
+      href: migrate/migrate-cluster-new-hardware.md 
+
+- name: Disconnected operations
+  items:
+  - name: Overview
+    href: manage/disconnected-operations-overview.md
+  - name: Known issues
+    href: manage/disconnected-operations-known-issues.md
+  - name: Plan
+    items:
+    - name: Network
+      href: manage/disconnected-operations-network.md
+    - name: Identity
+      href: manage/disconnected-operations-identity.md
+    - name: Security
+      href: manage/disconnected-operations-security.md
+    - name: Public key infrastructure
+      href: manage/disconnected-operations-pki.md
+  - name: Deploy
+    items:
+    - name: Set-up
+      href: manage/disconnected-operations-set-up.md
+    - name: Deployment
+      href: manage/disconnected-operations-deploy.md
+  - name: Manage
+    items:
+    - name: Azure CLI
+      href: manage/disconnected-operations-cli.md
+    - name: Azure Local VMs
+      href: manage/disconnected-operations-arc-vm.md
+    - name: Azure Kubernetes Service (AKS)
+      href: manage/disconnected-operations-aks.md
+    - name: Azure Container Registry
+      href: manage/disconnected-operations-azure-container-registry.md
+    - name: Azure Policy
+      href: manage/disconnected-operations-policy.md
+    - name: Azure monitor
+      href: manage/disconnected-operations-monitoring.md
+  - name: Troubleshoot
+    items:
+    - name: On-demand log collection
+      href: manage/disconnected-operations-on-demand-logs.md
+    - name: Fallback log collection
+      href: manage/disconnected-operations-fallback.md
 
 - name: Concepts
   items: 
diff --git a/azure-local/manage/disconnected-operations-deploy.md b/azure-local/manage/disconnected-operations-deploy.md
@@ -40,7 +40,7 @@ When deploying Azure Local with disconnected operations, consider the following
 
 For more information, see [Azure Local disconnected operations overview](disconnected-operations-overview.md).
 
-<!--For information on known issues identified with disconnected operations for Azure Local, see [Known issues for disconnected operations](known-issues-disconnected-operations.md)-->
+For information on known issues identified with disconnected operations for Azure Local, see [Known issues for disconnected operations](disconnected-operations-known-issues.md).
 
 ## Checklist for deploying disconnected operations
 
@@ -698,7 +698,8 @@ To enable Azure Local to be air-gapped or deployed fully disconnected, you must
 ```powershell
  [Environment]::SetEnvironmentVariable("NUGET_CERT_REVOCATION_MODE", "offline", [System.EnvironmentVariableTarget]::Machine)
 ```
-- Configure the timeserver to use your domain controller,for example. Modify the script and run it from PowerShell:
+
+- Configure the timeserver to use your domain controller, for example. Modify the script and run it from PowerShell:
 
 ```powershell
 w32tm /config /manualpeerlist:"dc.contoso.com" /syncfromflags:manual /reliable:yes /update
@@ -709,12 +710,15 @@ w32tm /resync /rediscover
 w32tm /query /peers
 ```
 
-Download (or copy) the following certificates and import them into the local trust store: 
+Download (or copy) the following certificates and import them into the local trust store:
+
 - [MicCodSigPCA2011](https://www.microsoft.com/pkiops/certs/MicCodSigPCA2011_2011-07-08.crt)
+
 - [DigiCertGlobalRootCA](https://cacerts.digicert.com/DigiCertGlobalRootCA.crt?utm_medium=organic&utm_source=msazure-visualstudio&referrer=https://msazure.visualstudio.com/&_gl=1*1c6vxin*_gcl_au*MTE2OTcyNDYyMy4xNzUyMTg0NDU5)
+
 - [DigiCertGlobalRootG2](https://cacerts.digicert.com/DigiCertGlobalRootG2.crt?utm_medium=organic&utm_source=msazure-visualstudio&referrer=https://msazure.visualstudio.com/&_gl=1*1c6vxin*_gcl_au*MTE2OTcyNDYyMy4xNzUyMTg0NDU5)
 
-Place them in a folder, e.g.C:\AzureLocalDisconnectedOperations\Certs\ 
+Place them in a folder, for example, C:\AzureLocalDisconnectedOperations\Certs\
 
 Import the certs by running the following:
 
diff --git a/azure-local/manage/disconnected-operations-known-issues.md b/azure-local/manage/disconnected-operations-known-issues.md
@@ -12,7 +12,7 @@ ms.reviewer: hafianba
 
 ::: moniker range=">=azloc-2506"
 
-<!--[!INCLUDE [IMPORTANT](../includes/disconnected-operations-preview.md)]-->
+[!INCLUDE [IMPORTANT](../includes/disconnected-operations-preview.md)]
 
 This article lists critical known issues and their workarounds in disconnected operations for Azure Local.
 
@@ -80,7 +80,7 @@ When attempting to initialize an Arc-enabled node, you may encounter error code
 
 **Cause**: Signing in with a service principal name (SPN) causes arc initialization to fail.
 
-**Mitigation**: Until the underlying issue is fixed, sign in to each Azure Local node by running `az login –use-device-code` instead of using a SPN.
+**Mitigation**: Until the underlying issue is fixed, sign in to each Azure Local node by running `az login –use-device-code` instead of using an SPN.
 
 ### Azure Local VMs (Arc VMs)
 
diff --git a/azure-local/manage/disconnected-operations-overview.md b/azure-local/manage/disconnected-operations-overview.md
@@ -30,7 +30,7 @@ Here are some scenarios for running Azure Local with disconnected operations:
 
 - **Data sovereignty and compliance**: In sectors like government, healthcare, and finance, there's a necessity to meet data residency or compliance requirements. When you run disconnected, data and control remain within your organization's boundaries.
 
-- **Remote or isolated locations**: In areas with limited network infrastructure, like remote or protected regions, disconnected operations lets you to use Azure Arc services and run workloads without relying on internet connectivity. For example, oil rigs and manufacturing sites.
+- **Remote or isolated locations**: In areas with limited network infrastructure, like remote or protected regions, disconnected operations lets you use Azure Arc services and run workloads without relying on internet connectivity. For example, oil rigs and manufacturing sites.
 
 - **Security**: For industries with strict security requirements, disconnected operations help reduce the attack surface by not exposing systems to external networks.
 
@@ -85,6 +85,7 @@ Here's the flow to deploy and manage Azure Local with disconnected operations:
 
 | Step | Description |
 |------------|------------------|
+| Review [Known issues for disconnected operations](disconnected-operations-known-issues.md). | Check known issues with disconnected operations for Azure Local. |
 | Review the [Preview participation criteria](#preview-participation-criteria) | Check the preview participation criteria before you get started. |
 | **Plan** |        |
 | Review [Network requirements for disconnected operations](disconnected-operations-network.md). | Configure the required network settings. |
