Last few

Author: sethmanheim

azure-local/manage/azure-benefits.md

@@ -7,7 +7,7 @@ ms.topic: overview
 ms.custom:
   - devx-track-azurepowershell
 ms.reviewer: jlei
-ms.date: 11/28/2023
+ms.date: 02/21/2025
 ms.lastreviewed: 02/23/2024
 ---
 
@@ -18,11 +18,11 @@ ms.lastreviewed: 02/23/2024
 [!INCLUDE [azure-local-banner-22h2](../includes/azure-local-banner-22h2.md)]
 
 > [!NOTE]
-> This article is for Azure Stack HCI version 22H2 and earlier only. For a list of benefits associated with version 23H2 and later, see [Azure verification for VMs](../deploy/azure-verification.md).
+> This article is only for Azure Stack HCI version 22H2 and earlier. For a list of benefits associated with version 23H2 and later, see [Azure verification for VMs](../deploy/azure-verification.md).
 
 Microsoft Azure offers a range of differentiated workloads and capabilities that are designed to run only on Azure. Azure Stack HCI extends many of the same benefits you get from Azure, while running on the same familiar and high-performance on-premises or edge environments.
 
-*Azure Benefits* makes it possible for supported Azure-exclusive workloads to work outside of the cloud. You can enable Azure Benefits on Azure Stack HCI at no extra cost. If you have Windows Server workloads, we recommend turning it on. 
+*Azure Benefits* makes it possible for supported Azure-exclusive workloads to work outside of the cloud. You can enable Azure Benefits on Azure Stack HCI at no extra cost. If you have Windows Server workloads, we recommend turning it on.
 
 Take a few minutes to watch the introductory video on Azure Benefits:
 
@@ -56,12 +56,12 @@ Turning on Azure Benefits starts the service running on your Azure Stack HCI clu
    > [!NOTE]
    > Certificates are renewed every time the Azure Stack HCI cluster syncs with Azure, and each renewal is valid for 30 days. As long as you maintain the usual 30 day connectivity requirements for Azure Stack HCI, no user action is required.
 
-2. HciSvc exposes a private and non-routable REST endpoint, accessible only to VMs on the same server. To enable this endpoint, an internal vSwitch is configured on the Azure Stack HCI host (named *AZSHCI_HOST-IMDS_DO_NOT_MODIFY*). VMs then must have a NIC configured and attached to the same vSwitch (*AZSHCI_GUEST-IMDS_DO_NOT_MODIFY*).
+1. HciSvc exposes a private and non-routable REST endpoint, accessible only to VMs on the same server. To enable this endpoint, an internal vSwitch is configured on the Azure Stack HCI host (named **AZSHCI_HOST-IMDS_DO_NOT_MODIFY**). VMs then must have a NIC configured and attached to the same vSwitch (**AZSHCI_GUEST-IMDS_DO_NOT_MODIFY**).
 
    > [!NOTE]
    > Modifying or deleting this switch and NIC prevents Azure Benefits from working properly. If errors occur, disable Azure Benefits using Windows Admin Center or the PowerShell instructions that follow, and then try again.
 
-3. Consumer workloads (for example, Windows Server Azure Edition guests) request attestation. HciSvc then signs the response with an Azure certificate.
+1. Consumer workloads (for example, Windows Server Azure Edition guests) request attestation. HciSvc then signs the response with an Azure certificate.
 
    > [!NOTE]
    > You must manually enable access for each VM that needs Azure Benefits.
@@ -89,15 +89,15 @@ You can enable Azure Benefits on Azure Stack HCI using Windows Admin Center, Pow
 
 1. In Windows Admin Center, select **Cluster Manager** from the top drop-down menu, navigate to the cluster that you want to activate, then under **Settings**, select **Azure Benefits**.
 
-2. In the **Azure Benefits** pane, select **Turn on**. By default, the checkbox to turn on for all existing VMs is selected. You can deselect it and manually add VMs later.
+1. In the **Azure Benefits** pane, select **Turn on**. By default, the checkbox to turn on for all existing VMs is selected. You can deselect it and manually add VMs later.
 
-3. Select **Turn on** again to confirm setup. It may take a few minutes for servers to reflect the changes.
+1. Select **Turn on** again to confirm setup. It may take a few minutes for servers to reflect the changes.
 
-4. When Azure Benefits setup is successful, the page updates to show the Azure Benefits dashboard. To check Azure Benefits for the host:
+1. When Azure Benefits setup is successful, the page updates to show the Azure Benefits dashboard. To check Azure Benefits for the host:
    1. Check that **Azure Benefits cluster status** appears as **On**.
    2. Under the **Cluster** tab in the dashboard, check that Azure Benefits for every server shows as **Active** in the table.
 
-5. To check access to Azure Benefits for VMs: Check the status for VMs with Azure Benefits turned on. It's recommended that all of your existing VMs have Azure Benefits turned on; for example, 3 out of 3 VMs.
+1. To check access to Azure Benefits for VMs: Check the status for VMs with Azure Benefits turned on. It's recommended that all of your existing VMs have Azure Benefits turned on; for example, 3 out of 3 VMs.
 
 :::image type="content" source="media/azure-benefits/manage-benefits.gif" alt-text="Screenshot of Azure Benefits in Windows Admin Center.":::
 
@@ -115,7 +115,7 @@ You can enable Azure Benefits on Azure Stack HCI using Windows Admin Center, Pow
    Enable-AzStackHCIAttestation -AddVM
    ```
 
-2. When Azure Benefits setup is successful, you can view the Azure Benefits status. Check the cluster property **IMDS Attestation** by running the following command:
+1. When Azure Benefits setup is successful, you can view the Azure Benefits status. Check the cluster property **IMDS Attestation** by running the following command:
 
    ```powershell
    Get-AzureStackHCI
@@ -127,15 +127,16 @@ You can enable Azure Benefits on Azure Stack HCI using Windows Admin Center, Pow
    Get-AzureStackHCIAttestation [[-ComputerName] <string>]
    ```
 
-3. To check access to Azure Benefits for VMs, run the following command:
+1. To check access to Azure Benefits for VMs, run the following command:
 
    ```powershell
    Get-AzStackHCIVMAttestation
    ```
 
 ## [Azure portal](#tab/azureportal)
+
 1. In your Azure Stack HCI cluster resource page, navigate to the **Configuration** tab.
-2. Under the feature **Enable Azure Benefits**, view the host attestation status:
+1. Under the feature **Enable Azure Benefits**, view the host attestation status:
 
    :::image type="content" source="media/azure-benefits/attestation-status.png" alt-text="Screenshot of Azure Benefit Attestation status." lightbox="media/azure-benefits/attestation-status.png":::
 
@@ -145,7 +146,8 @@ Azure CLI is available to install in Windows, macOS, and Linux environments. It
 
 Launch [Azure Cloud Shell](https://shell.azure.com/) and use Azure CLI to configure Azure Benefits following these steps:
 
-1. Set up parameters from your subscription, resource group, and cluster name
+1. Set up parameters from your subscription, resource group, and cluster name:
+
     ```azurecli
     subscription="00000000-0000-0000-0000-000000000000" # Replace with your subscription ID
     resourceGroup="hcicluster-rg" # Replace with your resource group name
@@ -155,7 +157,8 @@ Launch [Azure Cloud Shell](https://shell.azure.com/) and use Azure CLI to config
     ```
 
 1. To view Azure Benefits status on a cluster, run the following command:
-    ```azurecli    
+
+    ```azurecli
     az stack-hci cluster list \
     --resource-group "${resourceGroup}" \
     --query "[?name=='${clusterName}'].{Name:name, AzureBenefitsHostAttestation:reportedProperties.imdsAttestation}" \
@@ -183,6 +186,7 @@ To turn on Azure Benefits for VMs, select the **VMs** tab, then select the VM(s)
    ```powershell
    Add-AzStackHCIVMAttestation -AddAll
    ```
+
 - Optionally, to check that the VMs can access Azure Benefits on the host, run the following command on the VM:
 
   ```powershell

azure-local/manage/collect-diagnostic-data.md

@@ -4,7 +4,7 @@ description: Understanding Storage Spaces Direct diagnostic data collection tool
 ms.author: sethm
 ms.topic: article
 author: sethmanheim
-ms.date: 02/26/2024
+ms.date: 02/21/2025
 ---
 # Collect diagnostic data for clusters
 
@@ -20,33 +20,33 @@ Because the logs and other information are dense, the information presented in t
 
 You can use Windows Admin Center (version 1812 onwards) to:
 
-- Install SDDC diagnostic tools and keep them up to date
-- Schedule daily diagnostic runs (these have a low impact on your system, usually take less than five minutes to run in the background, and won't take up more than 500MB on your cluster)
-- View previously collected diagnostic information if you need to give it to support or analyze it yourself
+- Install SDDC diagnostic tools and keep them up to date.
+- Schedule daily diagnostic runs (these have a low impact on your system, usually take less than five minutes to run in the background, and won't take up more than 500MB on your cluster).
+- View previously collected diagnostic information if you need to give it to support personnel, or to analyze it yourself.
 
 To install SDDC diagnostic tools and begin collecting data, follow these steps:
 
 1. Launch Windows Admin Center and select **Tools > Diagnostics**. If diagnostics tools are not already installed, click the **Install** button.
-   
+
    :::image type="content" source="media/collect-diagnostic-data/install-diagnostic-tools.png" alt-text="Click Install to install SDDC diagnostic tools." lightbox="media/collect-diagnostic-data/install-diagnostic-tools.png":::
-   
-2. To begin collecting diagnostic data, click **Collect**. You should see a message that says "Collecting diagnostic information. This may take a few minutes." After the initial data collection, if you want to automatically collect data every 24 hours, change the slider to **On**.
-   
+
+1. To begin collecting diagnostic data, click **Collect**. You should see a message that says "Collecting diagnostic information. This may take a few minutes." After the initial data collection, if you want to automatically collect data every 24 hours, change the slider to **On**.
+
    :::image type="content" source="media/collect-diagnostic-data/collect-diagnostic-data.png" alt-text="Click Collect to being collecting diagnostic data." lightbox="media/collect-diagnostic-data/collect-diagnostic-data.png":::
-   
-3. Data collection is not complete until you see the screenshot below. To view collected diagnostic information, choose **Download (.zip)** or **Open in Files tool**.
-   
+
+1. Data collection is not complete until you see the screenshot below. To view collected diagnostic information, choose **Download (.zip)** or **Open in Files tool**.
+
    :::image type="content" source="media/collect-diagnostic-data/view-diagnostic-information.png" alt-text="To view diagnostic information, you can either download a .zip file or open in Files tool." lightbox="media/collect-diagnostic-data/view-diagnostic-information.png":::
-   
-## Installing Get-SDDCDiagnosticInfo with PowerShell
+
+## Install Get-SDDCDiagnosticInfo with PowerShell
 
 You can use the `Get-SDDCDiagnosticInfo` PowerShell cmdlet (also known as `Get-PCStorageDiagnosticInfo`, previously known as `Test-StorageHealth`) to gather logs for and perform health checks for Failover Clustering (cluster, resources, networks, nodes), Storage Spaces (physical disks, enclosures, virtual disks), Cluster Shared Volumes, SMB file shares, and Deduplication.
 
 There are two methods of installing the script: PowerShell Gallery and GitHub. Both are outlined below.
 
 ### PowerShell Gallery
 
-The [PowerShell Gallery](https://www.powershellgallery.com/packages/PrivateCloud.DiagnosticInfo) is a snapshot of the GitHub Repo. Note that installing items from the PowerShell Gallery requires the latest version of the PowerShellGet module, which is available in Windows 10, in Windows Management Framework (WMF) 5.0, or in the MSI-based installer (for PowerShell 3 and 4).
+The [PowerShell Gallery](https://www.powershellgallery.com/packages/PrivateCloud.DiagnosticInfo) is a snapshot of the GitHub repo. Note that installing items from the PowerShell Gallery requires the latest version of the **PowerShellGet** module, which is available in Windows 10, in Windows Management Framework (WMF) 5.0, or in the MSI-based installer (for PowerShell 3 and 4).
 
 We install the latest version of the [Microsoft Networking Diagnostics tools](https://www.powershellgallery.com/packages/MSFT.Network.Diag) during this process as well since `Get-SDDCDiagnosticInfo` relies on this. This manifest module contains network diagnostic and troubleshooting tool, which are maintained by the Microsoft Core Networking Product Group at Microsoft.
 
@@ -67,7 +67,7 @@ Update-Module PrivateCloud.DiagnosticInfo
 
 ### GitHub
 
-The [GitHub Repo](https://github.com/PowerShell/PrivateCloud.DiagnosticInfo/) is the most up-to-date version of the module, since we are continually iterating here. To install the module from GitHub, download the latest module from the [archive](https://github.com/PowerShell/PrivateCloud.DiagnosticInfo/archive/master.zip) and extract the PrivateCloud.DiagnosticInfo directory to the correct PowerShell modules path pointed by ```$env:PSModulePath```
+The [GitHub repo](https://github.com/PowerShell/PrivateCloud.DiagnosticInfo/) is the most up-to-date version of the module, since we are continually iterating here. To install the module from GitHub, download the latest module from the [archive](https://github.com/PowerShell/PrivateCloud.DiagnosticInfo/archive/master.zip) and extract the **PrivateCloud.DiagnosticInfo** directory to the correct PowerShell modules path pointed to by `$env:PSModulePath`:
 
 ``` PowerShell
 # Allowing Tls12 and Tls11 -- e.g. github now requires Tls12
@@ -95,17 +95,17 @@ Import-Module $module -Force
 
 ```
 
-If you need to get this module on an offline cluster, download the zip, move it to your target server node, and install the module.
+If you need to get this module on an offline cluster, download the zip file, move it to your target server node, and install the module.
 
 ## Gathering logs with PowerShell
 
-After you have enabled event channels and completed the installation process, you can use the `Get-SDDCDiagnosticInfo` PowerShell cmdlet in the module to get:
+After you enable event channels and complete the installation process, you can use the `Get-SDDCDiagnosticInfo` PowerShell cmdlet in the module to get:
 
-- Reports on storage health, plus details on unhealthy components
-- Reports of storage capacity by pool, volume, and deduplicated volume
-- Event logs from all cluster nodes and a summary error report
+- Reports on storage health, plus details on unhealthy components.
+- Reports of storage capacity by pool, volume, and deduplicated volume.
+- Event logs from all cluster nodes and a summary error report.
 
-Assume that your storage cluster has the name *"CLUS01".*
+Assume that your storage cluster has the name **CLUS01**.
 
 To execute against a remote storage cluster:
 
@@ -132,19 +132,19 @@ New-Item -Name SDDCDiagTemp -Path d:\ -ItemType Directory -Force
 Get-SddcDiagnosticInfo -ClusterName S2D-Cluster -WriteToPath d:\SDDCDiagTemp
 ```
 
-As you can see, the script will also do validation of current cluster state:
+As you can see, the script also does validation of the current cluster state:
 
 :::image type="content" source="media/collect-diagnostic-data/collect-data.png" alt-text="Data collection PowerShell screenshot." lightbox="media/collect-diagnostic-data/collect-data.png":::
 
-All data is being written to SDDCDiagTemp folder:
+All data is written to the **SDDCDiagTemp** folder:
 
 :::image type="content" source="media/collect-diagnostic-data/collect-data-folder.png" alt-text="Data in File Explorer screenshot." lightbox="media/collect-diagnostic-data/collect-data-folder.png":::
 
-After the script finishes, it will create a ZIP in your user directory:
+After the script finishes, it creates a zip file in your user directory:
 
 :::image type="content" source="media/collect-diagnostic-data/collect-data-result.png" alt-text="Data zip in PowerShell screenshot." lightbox="media/collect-diagnostic-data/collect-data-result.png":::
 
-Let's generate a report into a text file:
+Generate a report into a text file:
 
 ```PowerShell
 #find the latest diagnostic zip in UserProfile
@@ -163,32 +163,32 @@ For reference, here is a link to the [sample report](https://github.com/Microsof
 
 ## Get-SDDCDiagnosticInfo output
 
-The following are the files included in the zipped output of `Get-SDDCDiagnosticInfo`.
+The following files are included in the zipped output of `Get-SDDCDiagnosticInfo`.
 
 ### Health summary Report
 
-The health summary report is saved as:
-- 0_CloudHealthSummary.log
+The health summary report is saved as **0_CloudHealthSummary.log**.
 
 This file is generated after parsing all the data collected and is meant to provide a quick summary of your system. It contains:
 
-- System information
-- Storage health overview (number of nodes up, resources online, cluster shared volumes online, unhealthy components, etc.)
-- Details on unhealthy components (cluster resources that are offline, failed, or online pending)
-- Firmware and driver information
-- Pool, physical disk, and volume details
-- Storage Performance (performance counters are collected)
+- System information.
+- Storage health overview (number of nodes up, resources online, cluster shared volumes online, unhealthy components, etc.).
+- Details on unhealthy components (cluster resources that are offline, failed, or online pending).
+- Firmware and driver information.
+- Pool, physical disk, and volume details.
+- Storage performance (performance counters are collected).
 
-This report is being continually updated to include more useful information. For the latest information, see the [GitHub README](https://github.com/PowerShell/PrivateCloud.DiagnosticInfo/edit/master/README.md).
+This report is continually updated to include more useful information. For the latest information, see the [GitHub readme](https://github.com/PowerShell/PrivateCloud.DiagnosticInfo/edit/master/README.md).
 
 ### Logs and XML files
 
-The script runs various log gathering scripts and saves the output as xml files. We collect cluster and health logs, system information (MSInfo32), unfiltered event logs (failover clustering, dis diagnostics, Hyper-V, storage spaces, and more), and storage diagnostics information (operational logs). For the latest information on what information is collected, see the [GitHub README (what we collect)](https://github.com/PowerShell/PrivateCloud.DiagnosticInfo/blob/master/README.md#what-does-the-cmdlet-output-include).
+The script runs various log gathering scripts and saves the output as xml files. We collect cluster and health logs, system information (MSInfo32), unfiltered event logs (failover clustering, dis diagnostics, Hyper-V, storage spaces, and more), and storage diagnostics information (operational logs). For the latest information about what information is collected, see the [GitHub readme (what we collect)](https://github.com/PowerShell/PrivateCloud.DiagnosticInfo/blob/master/README.md#what-does-the-cmdlet-output-include).
 
 ## How to consume XML files from Get-SDDCDiagnosticInfo
+
 You can consume the data from the XML files provided in data collected by the `Get-SDDCDiagnosticInfo` cmdlet. These files have information about the virtual disks, physical disks, basic cluster information, and other PowerShell related outputs.
 
-To see the results of these outputs, open a PowerShell window and run the following steps.
+To see the results of these outputs, open a PowerShell window and run the following commands:
 
 ```PowerShell
 ipmo storage
@@ -197,4 +197,5 @@ $d
 ```
 
 ## Next steps
-Provide feedback on what you'd like to see by filing issues [here](https://github.com/PowerShell/PrivateCloud.DiagnosticInfo/issues). Also, feel free to contribute helpful changes to the script by submitting a [pull request](https://github.com/PowerShell/PrivateCloud.DiagnosticInfo/pulls).
+
+Provide feedback on what you'd like to see by [filing issues here](https://github.com/PowerShell/PrivateCloud.DiagnosticInfo/issues). Also, feel free to contribute helpful changes to the script by [submitting a pull request](https://github.com/PowerShell/PrivateCloud.DiagnosticInfo/pulls).