Merge pull request #18574 from NeilBird/users/nebird/cluster-performance-history

Azure Local | Minor improvements to Cluster performance history and sideloading updates articles

Author: prmerger-automator[bot]

azure-local/manage/health-service-cluster-performance-history.md

@@ -4,7 +4,7 @@ title: Cluster performance history
 ms.author: alkohli
 ms.topic: how-to
 author: alkohli
-ms.date: 01/16/2025
+ms.date: 07/30/2025
 ---
 
 # Get cluster performance history
@@ -13,6 +13,8 @@ ms.date: 01/16/2025
 
 The Health Service reduces the work required to get live performance and capacity information from your Storage Spaces Direct cluster. One cmdlet provides a curated list of essential metrics, which are collected efficiently and aggregated dynamically across nodes, with built-in logic to detect cluster membership. All values are real-time and point-in-time only.
 
+For additional information, see [Performance history for Storage Spaces Direct](/windows-server/storage/storage-spaces/performance-history).
+
 ## Usage in PowerShell
 Use the following cmdlet to get metrics for the entire Storage Spaces Direct cluster:
 
@@ -31,6 +33,8 @@ Get-Volume -FileSystemLabel <Label> | Get-ClusterPerformanceHistory
 Get-StorageNode -Name <Name> | Get-ClusterPerformanceHistory
 ```
 
+<br>For additional information on how to access performance history data using PowerShell, see [Scripting with PowerShell and Storage Spaces Direct performance history](/windows-server/storage/storage-spaces/performance-history-scripting).
+
 ## Usage in .NET and C#
 This sections shows how to connect to the Health Service, use discover objects, and implement an Observer to begin streaming metrics.
 

azure-local/update/import-discover-updates-offline-23h2.md

@@ -16,7 +16,9 @@ ms.date: 07/25/2025
 
 [!INCLUDE [azure-local-end-of-support-banner-23h2](../includes/azure-local-end-of-support-banner-23h2.md)]
 
-This article explains how to discover and import update packages for Azure Local with limited connectivity. Starting with version 2503, the OS update components for Azure Local are distributed as a static payload, so you can import the update payload and install updates with limited connectivity to Azure.
+This article explains how to discover and import solution update packages for Azure Local deployed in sites with limited bandwidth connections to Azure. Beginning with version 2503, Azure Local solution updates can be optionally downloaded as static payloads. You can download the payload once, copy or transfer to multiple instances and import using PowerShell. Performing these actions prior to starting an update, reduces the amount of data that is downloaded during an update.
+
+The static payload for a solution update includes the OS security update, extensions, and core agents, all of which are installed during the update process. Updated container images required for the Azure Resource Bridge component and Azure Kubernetes Service on Azure Local are not included in the static payload. These images are downloaded automatically during the update process.
 
 <!--To install updates online via PowerShell, see [Update Azure Local via PowerShell](./update-via-powershell-23h2.md).-->