Merge pull request #16285 from ronmiab/rb-rebrand-updates

JamesJBarnett · web-flow · commit 4fdd106e3868 · 2024-11-08T14:42:10.000-07:00
Updated text per feedback from test review
diff --git a/azure-stack/hci/concepts/telemetry-and-diagnostics-overview.md b/azure-stack/hci/concepts/telemetry-and-diagnostics-overview.md
@@ -61,7 +61,7 @@ To access the options to send telemetry data, follow these steps:
 
 ## Diagnostic data collection
 
-To identify and fix issues with your Azure Local solution, you can collect and send diagnostic logs to Microsoft. To manually collect and send diagnostic logs to Microsoft, use the `Send-DiagnosticData` cmdlet from any Azure Local machines. We recommend that you use this cmdlet to upload diagnostic data before opening a support case.
+To identify and fix issues with your Azure Local solution, you can collect and send diagnostic logs to Microsoft. To manually collect and send diagnostic logs to Microsoft, use the `Send-DiagnosticData` cmdlet from any Azure Local machine. We recommend that you use this cmdlet to upload diagnostic data before opening a support case.
 
 For more information, see [Collect diagnostic logs](../manage/collect-logs.md).
 
diff --git a/azure-stack/hci/hybrid-capabilities-with-azure-services-23h2.md b/azure-stack/hci/hybrid-capabilities-with-azure-services-23h2.md
@@ -18,7 +18,7 @@ Your on-premises Azure Local solution integrates with Azure cloud via several cl
 
 ## Azure Local cloud service
 
-The Azure Local cloud service in Azure is a key part of the Azure Local product offering. It includes standard Azure components, such as a resource provider in Azure Resource Manager and a UI extension in the Azure portal. These components enable access to Azure Local functionality via familiar Azure tools and UX, such as [Azure portal](manage/azure-portal.md), [Azure PowerShell](/powershell/module/az.stackhci/?view=azps-7.2.0&preserve-view=true), and [Azure CLI](/cli/azure/stack-hci?view=azure-cli-latest&preserve-view=true). The Azure Local cloud service also enables contextual navigation from an Azure Local resource to its Arc machines and Arc virtual machines (VMs).
+The Azure Local cloud service in Azure is a key part of the Azure Local product offering. It includes standard Azure components, such as a resource provider in Azure Resource Manager and a UI extension in the Azure portal. These components enable access to Azure Local functionality via familiar Azure tools and UX, such as [Azure portal](manage/azure-portal.md), [Azure PowerShell](/powershell/module/az.stackhci/?view=azps-7.2.0&preserve-view=true), and [Azure CLI](/cli/azure/stack-hci?view=azure-cli-latest&preserve-view=true). The Azure Local cloud service also enables contextual navigation from an Azure Local resource to its Arc servers and Arc virtual machines (VMs).
 
 The Azure Local cloud service extends the hybrid capabilities for Azure Local by enabling the following cloud-based functionalities:
 
diff --git a/azure-stack/hci/includes/end-of-service-22h2.md b/azure-stack/hci/includes/end-of-service-22h2.md
@@ -8,6 +8,6 @@ ms.reviewer: alkohli
 ---
 
 > [!IMPORTANT]
-> Azure Stack HCI, version 22H2 will reach end of service by May 2025. After that, you won't receive monthly security and quality updates that provide protection from the latest security threats. To continue receiving updates, we recommend updating your operating system to [version 23H2](../upgrade/upgrade-22h2-to-23h2-powershell.md).
+> Azure Local, version 22H2 will reach end of service by May 2025. After that, you won't receive monthly security and quality updates that provide protection from the latest security threats. To continue receiving updates, we recommend updating your operating system to [version 23H2](../upgrade/upgrade-22h2-to-23h2-powershell.md).
 >
-> If you're currently running an Azure Stack HCI, version 22H2 stretch cluster or managing Azure Stack HCI via System Center - Virtual Machine Manager, review the [Supported workloads and configurations](../upgrade/about-upgrades-23h2.md#supported-workloads-and-configurations) table for update timelines.
+> If you're currently running an Azure Local, version 22H2 stretch cluster or managing Azure Local via System Center - Virtual Machine Manager, review the [Supported workloads and configurations](../upgrade/about-upgrades-23h2.md#supported-workloads-and-configurations) table for update timelines.
diff --git a/azure-stack/hci/manage/arc-extension-management.md b/azure-stack/hci/manage/arc-extension-management.md
@@ -1,6 +1,6 @@
 ---
 title:  Azure Arc extension management on Azure Local
-description: This article describes how to manage Azure Arc extensions on Azure Local machines.
+description: This article describes how to manage Azure Arc extensions on Azure Local.
 author: ronmiab
 ms.author: robess
 ms.topic: how-to
@@ -13,7 +13,7 @@ ms.date: 10/22/2024
 
 [!INCLUDE [applies-to](../../hci/includes/hci-applies-to-23h2-22h2.md)]
 
-This article describes how to install, upgrade, and manage Azure Arc extensions on Azure Local machines.
+This article describes how to install, upgrade, and manage Azure Arc extensions on Azure Local.
 
 ## Customer-managed Azure Arc extensions on Azure Local
 
@@ -42,7 +42,7 @@ You can install extensions from the **Capabilities** tab for your Azure Local Ar
 
 :::image type="content" source="media/arc-extension-management/arc-extension-overview.png" alt-text="Screenshot of the Capabilities tab and options in the Azure portal." lightbox="media/arc-extension-management/arc-extension-overview.png":::
 
-When you install an extension in the Azure portal, it's a cluster-aware operation. The extension is installed on all machines of the system. If you add more machines to your system, all the extensions installed on your system are automatically added to the new servers.
+When you install an extension in the Azure portal, it's a cluster-aware operation. The extension is installed on all nodes of the system. If you add more nodes to your system, all the extensions installed on your system are automatically added to the new servers.
 
 ### [Azure CLI](#tab/azurecli)
 Azure CLI is available to install in Windows, macOS and Linux environments. It can also be run in Azure Cloud Shell. For more information, refer [Quickstart for Azure Cloud Shell](/azure/cloud-shell/quickstart).
@@ -385,15 +385,15 @@ New-AzStackHciExtension `
 
 ### Manual extension upgrade via the Azure portal
 
-The manual extension upgrade works like the [Automatic extension upgrade](/azure/azure-arc/servers/manage-automatic-vm-extension-upgrade?tabs=azure-portal#how-does-automatic-extension-upgrade-work). On an Azure Local Arc-enabled cluster, when you manually upgrade an extension, Azure saves the version you've selected. Azure then attempts to upgrade the extension on all machines in the system to that version.
+The manual extension upgrade works like the [Automatic extension upgrade](/azure/azure-arc/servers/manage-automatic-vm-extension-upgrade?tabs=azure-portal#how-does-automatic-extension-upgrade-work). On an Azure Local Arc-enabled cluster, when you manually upgrade an extension, Azure saves the version you've selected. Azure then attempts to upgrade the extension on all nodes in the cluster to that version.
 
 On some servers, if the extension upgrade fails the platform attempts to upgrade to the selected version during the next [Azure Local cloud sync](../faq.yml).
 
 Use the manual workflow in these scenarios:
 
 - A new version of the extension is available and you want to upgrade it manually.
 
-- The extension's automatic upgrade option is disabled and there's a version mismatch across different machines of the Azure Local.
+- The extension's automatic upgrade option is disabled and there's a version mismatch across different nodes of Azure Local.
 
 To manually upgrade an extension, follow these steps:
 
@@ -419,7 +419,7 @@ You can disable automatic upgrades for certain extensions in the Azure portal. T
 
 ### Check the extension upgrade history
 
-You can view the Activity Log tab on individual Azure Arc-enabled server resources, resource groups, and subscriptions to check the history of automatic extension upgrades for individual machines. For more information, see [Check automatic extension upgrade history](/azure/azure-arc/servers/manage-automatic-vm-extension-upgrade?tabs=azure-portal#check-automatic-extension-upgrade-history).
+You can view the Activity Log tab on individual Azure Arc-enabled server resources, resource groups, and subscriptions to check the history of automatic extension upgrades for individual nodes. For more information, see [Check automatic extension upgrade history](/azure/azure-arc/servers/manage-automatic-vm-extension-upgrade?tabs=azure-portal#check-automatic-extension-upgrade-history).
 
 ### Availability-first updates
 
@@ -439,7 +439,7 @@ If you continue to have trouble with an extension upgrade, you can [disable auto
 
 ### Upgrades with multiple extensions
 
-If multiple extension upgrades are available for a machine, they might be batched together. However, each extension upgrade is applied individually on the machine. For more information, see [Extension upgrades with multiple extensions](/azure/azure-arc/servers/manage-automatic-vm-extension-upgrade?tabs=azure-portal#extension-upgrades-with-multiple-extensions).
+If multiple extension upgrades are available for a node, they might be batched together. However, each extension upgrade is applied individually on the node. For more information, see [Extension upgrades with multiple extensions](/azure/azure-arc/servers/manage-automatic-vm-extension-upgrade?tabs=azure-portal#extension-upgrades-with-multiple-extensions).
 
 ## Uninstall an extension
 
diff --git a/azure-stack/hci/manage/azure-enhanced-management-managed-identity.md b/azure-stack/hci/manage/azure-enhanced-management-managed-identity.md
@@ -32,7 +32,7 @@ The managed identity serves as an identity for the various components of your ma
 
 - **Protection of VM workloads via Azure Site Recovery** - You can protect your business critical VM workloads running on Azure Local by replicating the VMs using the Azure Site Recovery agent which is deployed as an Arc for Server extension. The Azure Local managed identity is used to download a key credential file from Azure. This file lets the agent know which service to talk to and which Recovery services vault to communicate with. This mechanism allows us to scope the access to the Recovery services vault to only the applicable Azure Local.
 
-    The Arc for Server extension uses the cluster managed identity to download the key credential file to every node of the system. If a new node is added to your system, Azure Local automatically triggers the installation of Arc for Server extension for Azure Site Recovery on the new node. In the absence of managed identity, this was previously a manual step that required you to install the agent to each node that was added to the system.
+    The Arc for Server extension uses the system managed identity to download the key credential file to every machine of the system. If a new machine is added to your system, Azure Local automatically triggers the installation of Arc for Server extension for Azure Site Recovery on the new machine. In the absence of managed identity, this was previously a manual step that required you to install the agent to each machine that was added to the system.
 
     For more information, see [Protect VM workloads with Azure Site Recovery on Azure Local](./azure-site-recovery.md).
 
diff --git a/azure-stack/hci/manage/azure-site-recovery.md b/azure-stack/hci/manage/azure-site-recovery.md
@@ -240,7 +240,7 @@ Here's a list of known issues and the associated workarounds in this release:
 
 | \# | Issue                   | Workaround/Comments    |
 |----|----------------------|---------------------------|
-| 1. | When you register Azure Site Recovery with a system, a node fails to install Azure Site Recovery or register to the Azure Site Recovery service.  | In this instance, your VMs may not be protected. Verify that all machines in the system are registered in the Azure portal by going to the **Recovery Services vault** \> **Jobs** \> **Site Recovery Jobs**. |
+| 1. | When you register Azure Site Recovery with a system, a machine fails to install Azure Site Recovery or register to the Azure Site Recovery service.  | In this instance, your VMs may not be protected. Verify that all machines in the system are registered in the Azure portal by going to the **Recovery Services vault** \> **Jobs** \> **Site Recovery Jobs**. |
 | 2. | Azure Site Recovery agent fails to install. No error details are seen at the system or machine levels in the Azure Local portal. | When the Azure Site Recovery agent installation fails, it is because of the one of the following reasons:  <br><br> - Installation fails as Hyper-V isn't set up on the . </br><br> - The Hyper-V host is already associated to a Hyper-V site and you're trying to install the extension with a different Hyper-V site. </br>  |
 | 3. | Azure Site Recovery agent fails to install. Error message of "Microsoft Azure Site Recovery Provider installation has failed with exit code - 1." appears in the portal with the failed installation. | The installation fails when WDAC is enforced. <br><br> - Setting WDAC to "Audit" mode will allow the installation to complete.  To set the WDAC mode to be Audit, you can follow the instructions in [Manage WDAC settings with PowerShell](/azure-stack/hci/manage/manage-wdac#manage-wdac-settings-with-powershell) |
 
diff --git a/azure-stack/hci/manage/remote-support-arc-extension.md b/azure-stack/hci/manage/remote-support-arc-extension.md
@@ -1,6 +1,6 @@
 ---
 title:  Azure Local Remote Support Arc extension overview
-description: This article describes the remote support arc extension and how to enable it for your Azure Local machines.
+description: This article describes the remote support arc extension and how to enable it for your Azure Local.
 author: ronmiab
 ms.author: robess
 ms.topic: overview
@@ -61,7 +61,7 @@ To enable remote support on your Azure Local, follow these steps:
 
 1. On the client you're using to connect to your system, run PowerShell as an administrator.
 
-2. Open a remote PowerShell session to a node on your Azure Local. Run the following command and provide the credentials of your machine when prompted:
+2. Open a remote PowerShell session to a node on your Azure Local. Run the following command and provide the credentials of your node when prompted:
 
     ```powershell
     $cred = Get-credential
diff --git a/azure-stack/hci/manage/suspend-resume-cluster-maintenance.md b/azure-stack/hci/manage/suspend-resume-cluster-maintenance.md
@@ -42,7 +42,7 @@ To suspend a machine, follow these steps:
     > [!NOTE]
     > Running this command may take some time, depending on the number of VMs that need to be migrated.
 
-1. Confirm that the node is successfully suspended.
+1. Confirm that the machine is successfully suspended.
 
     ```powershell
     Get-Clusternode
@@ -97,7 +97,7 @@ To resume a machine, follow these steps:
     > [!NOTE]
     > Running this command may take some time, depending on the number of VMs that need to be migrated.
 
-1. Confirm that the node is successfully resumed.
+1. Confirm that the machine is successfully resumed.
 
     ```powershell
     Get-Clusternode
@@ -114,7 +114,7 @@ To resume a machine, follow these steps:
     ASRRlS3lRl5Ull      Up           Node
     ```
 
-1. Add the node to the active Arc VM Configuration. **This step can only be done using PowerShell**.
+1. Add the machine to the active Arc VM Configuration. **This step can only be done using PowerShell**.
 
     ```powershell
     New-MocPhysicalNode -nodeName “MachineName”
diff --git a/azure-stack/hci/update/about-updates-23h2.md b/azure-stack/hci/update/about-updates-23h2.md
@@ -111,7 +111,7 @@ Using these interfaces can install out-of-band updates, which aren't supported w
 
 ### Unsupported interfaces for updates
 
-When you install updates for Azure Stack HCI, version 23H2 don't use the following interfaces:
+When you install updates for Azure Local, version 23H2 don't use the following interfaces:
 
 - SConfig
 - Windows Admin Center
diff --git a/azure-stack/hci/update/solution-builder-extension.md b/azure-stack/hci/update/solution-builder-extension.md
@@ -63,7 +63,7 @@ The following table provides the hardware update method for different hardware v
 | DataON   | Models starting with S2D6, S2D7, AZS6, AZS7   | Solution Builder Extension | [Must Stay Up to Date - DataON](https://www.dataonstorage.com/dataon-must/must-stay-up-to-date/) |
 | DataON  | Other Integrated Systems and Validated Nodes (not previously listed)    | [Windows Admin Center Extension](https://dev.azure.com/WindowsAdminCenter/Windows%20Admin%20Center%20Feed/_artifacts/feed/WAC/NuGet/DataON.MUSTPro/overview/3.2.6) | [Enhancing the Windows Admin Center Experience with DataON MUST](https://www.dataonstorage.com/must/windows-admin-center/)                   |
 | Dell Technologies  | Premier Solutions: </br><br> MC-660, MC-760 | APEX Cloud Platform Hardware Updates (Solution Builder Extension) | [Support Matrix of Dell APEX Cloud Platform for Microsoft Azure](https://dl.dell.com/content/manual34666301-dell-apex-cloud-platform-for-microsoft-azure-support-matrix.pdf) |
-| Dell Technologies | **15G and 16G Integrated Systems - Clusters running Azure Stack OS, version 23H2**:</br><br> AX-650, AX-750, AX-6515, AX-7525, AX-4510c, AX-4520c, AX-760 | Solution Builder Extension (once available)  | [Dell Solution Builder Extensions for Azure Stack HCI Integrated System AX Server Release Notes](https://www.dell.com/support/kbdoc/en-us/000224407) |
+| Dell Technologies | **15G and 16G Integrated Systems - Clusters running Azure Stack OS, version 23H2**:</br><br> AX-650, AX-750, AX-6515, AX-7525, AX-4510c, AX-4520c, AX-760 | Solution Builder Extension (once available)  | [Dell Solution Builder Extensions for Azure Local Integrated System AX Server Release Notes](https://www.dell.com/support/kbdoc/en-us/000224407) |
 | Dell Technologies | **15G Integrated Systems - Clusters running Azure Stack OS, version 22H2**:</br><br> AX-650, AX-750, AX-6515, AX-7525, AX-4150c, AX-4520c | [Windows Admin Center Extension](https://dev.azure.com/WindowsAdminCenter/Windows%20Admin%20Center%20Feed/_artifacts/feed/WAC/NuGet/dell-emc.openmanage-integration/overview/3.2.0)  | [E2E Deployment and Operations Guide - Cluster Creation Using Windows Admin Center (WAC) \| Dell Technologies Info Hub](https://infohub.delltechnologies.com/en-us/t/e2e-deployment-and-operations-guide-cluster-creation-using-windows-admin-center-wac-1/) |
 | Dell Technologies | 14G Integrated Systems - Clusters running Azure Stack OS, version 22H2:</br><br> AX-740xd, AX-640 | [Windows Admin Center Extension](https://dev.azure.com/WindowsAdminCenter/Windows%20Admin%20Center%20Feed/_artifacts/feed/WAC/NuGet/dell-emc.openmanage-integration/overview/3.2.0) | [E2E Deployment and Operations Guide - Cluster Creation Using Windows Admin Center (WAC) \| Dell Technologies Info Hub](https://infohub.delltechnologies.com/en-us/t/e2e-deployment-and-operations-guide-cluster-creation-using-windows-admin-center-wac-1/) |
 | Hewlett Packard Enterprise | All | Solution Builder Extension and [Windows Admin Center Extension](https://dev.azure.com/WindowsAdminCenter/Windows%20Admin%20Center%20Feed/_artifacts/feed/WAC/NuGet/hpe.hci.snap-in/overview/1.3.0) | 1. Install [Solution Builder Extension](https://www.hpe.com/info/ASHCI-SBE) </br><br> 2. Install hardware updates via [Windows Admin Center](https://www.hpe.com/us/en/alliance/microsoft/ws-admin-center.html) |
diff --git a/azure-stack/hci/update/update-via-powershell-23h2.md b/azure-stack/hci/update/update-via-powershell-23h2.md
@@ -29,7 +29,7 @@ When you apply a solution update, here are the high-level steps that you take:
 
 1. Make sure that all the prerequisites are completed.
 1. Identify the software version running on your cluster.
-1. Connect to your Azure Stack HCI cluster via remote PowerShell.
+1. Connect to your Azure Local instance via remote PowerShell.
 1. Discover the updates that are available and filter the ones that you can apply to your cluster.
 1. Download the updates, assess the update readiness of your cluster and once ready, install the updates on your cluster. Track the progress of the updates. If needed, you can also monitor the detailed progress.
 1. Verify the version of the updates installed.

Original file line number	Diff line number	Diff line change
`@@ -8,6 +8,6 @@ ms.reviewer: alkohli`
`8`	`8`	`---`
`9`	`9`
`10`	`10`	`> [!IMPORTANT]`
`11`		`-> Azure Stack HCI, version 22H2 will reach end of service by May 2025. After that, you won't receive monthly security and quality updates that provide protection from the latest security threats. To continue receiving updates, we recommend updating your operating system to [version 23H2](../upgrade/upgrade-22h2-to-23h2-powershell.md).`
	`11`	`+> Azure Local, version 22H2 will reach end of service by May 2025. After that, you won't receive monthly security and quality updates that provide protection from the latest security threats. To continue receiving updates, we recommend updating your operating system to [version 23H2](../upgrade/upgrade-22h2-to-23h2-powershell.md).`
`12`	`12`	`>`
`13`		`-> If you're currently running an Azure Stack HCI, version 22H2 stretch cluster or managing Azure Stack HCI via System Center - Virtual Machine Manager, review the [Supported workloads and configurations](../upgrade/about-upgrades-23h2.md#supported-workloads-and-configurations) table for update timelines.`
	`13`	`+> If you're currently running an Azure Local, version 22H2 stretch cluster or managing Azure Local via System Center - Virtual Machine Manager, review the [Supported workloads and configurations](../upgrade/about-upgrades-23h2.md#supported-workloads-and-configurations) table for update timelines.`