Merge pull request #17549 from LouisBerner/v-loberner-mar-local-freshness-1

Freshness updates for Alpa.

Author: ttorble

azure-local/concepts/single-server-clusters.md

@@ -6,7 +6,7 @@ ms.author: robess
 ms.topic: overview
 ms.reviewer: kimlam
 ms.lastreviewed: 04/01/2024
-ms.date: 04/01/2024
+ms.date: 04/03/2025
 ---
 
 # Using Azure Stack HCI on a single server
@@ -22,10 +22,10 @@ This article provides an overview of running Azure Stack HCI on a single server,
 Along with the benefits mentioned, there are some initial limitations to recognize.
 
 - You must use PowerShell to create the single-node cluster and enable Storage Spaces Direct.
-- Single servers must use only a single drive type: Non-volatile Memory Express (NVMe) or Solid-State (SSD) drives.
+- Single servers must use only a single drive type: Nonvolatile Memory Express (NVMe) or Solid-State (SSD) drives.
 - Stretched (dual-site) clusters aren't supported with individual servers (stretched clusters require a minimum of two servers in each site).
 - To install updates for single-node clusters, see [Updating single-node clusters](../deploy/single-server.md#updating-single-node-clusters). For solution updates (such as driver and firmware updates), see your solution vendor.
-- Operating system or other updates requiring a restart cause downtime to running virtual machines (VMs) because there isn't another running cluster node to move the VMs to. We recommend manually shutting down the VMs before restarting to ensure that the VMs have enough time to shut down prior to the restart.
+- Operating system or other updates requiring a restart cause downtime to running virtual machines (VMs) because there isn't another running cluster node to move the VMs to. We recommend manually shutting down the VMs before restarting to ensure that the VMs have enough time to shut down before the restart.
 
 ## Prerequisites
 
@@ -72,11 +72,11 @@ The following table describes currently known issues for single-node clusters. T
 
 |Issue | Notes|
 |-----------|---------------|
-|SBL cache isn't supported in single-node clusters. | All-flash, flat configuration with Non-volatile Memory Express (NVMe) or Solid-State Drives (SSD) must be used. |
+|SBL cache isn't supported in single-node clusters. | All-flash, flat configuration with Nonvolatile Memory Express (NVMe) or Solid-State Drives (SSD) must be used. |
 |Windows Admin Center doesn't support creating single-node clusters. | [Deploy single server with PowerShell](../deploy/create-cluster-powershell.md). |
-|Windows Admin Center cosmetic user interface (UI) changes needed. | Doesn't limit Live Migration within the same cluster; allows affinity rules to be created, etc. Actions will fail without any harm. |
+|Windows Admin Center cosmetic user interface (UI) changes needed. | Doesn't limit Live Migration within the same cluster; allows affinity rules to be created, etc. Actions fail without any harm. |
 |Windows Admin Center pause server fails since it tries to drain the server. | Utilize PowerShell to pause (suspend the server). |
-|Cluster Aware Updating (CAU) doesn't support single-node clusters in 21H2. You'll need to update to 22H2. | Update using Windows Admin Center (through server manager), PowerShell, or the Server Configuration tool (SConfig). [Learn more](../deploy/single-server.md#updating-single-node-clusters) |
+|Cluster Aware Updating (CAU) doesn't support single-node clusters in 21H2. You need to update to 22H2. | Update using Windows Admin Center (through server manager), PowerShell, or the Server Configuration tool (SConfig). [Learn more](../deploy/single-server.md#updating-single-node-clusters) |
 
 ## Next steps
 

azure-local/deploy/deployment-arc-register-server-permissions.md

@@ -3,7 +3,7 @@ title: Register your Azure Local machines with Azure Arc and assign permissions
 description: Learn how to Register your Azure Local machines with Azure Arc and assign permissions for deployment. 
 author: alkohli
 ms.topic: how-to
-ms.date: 03/20/2025
+ms.date: 04/03/2025
 ms.author: alkohli
 ms.service: azure-local
 ms.custom: devx-track-azurepowershell
@@ -17,7 +17,7 @@ This article describes how to register your Azure Local machines and then set up
 
 ## Prerequisites
 
-Before you begin, make sure you've completed the following prerequisites:
+Before you begin, make sure you complete the following prerequisites:
 
 ### Azure Local machine prerequisites
 
@@ -79,7 +79,7 @@ Before you begin, make sure you've completed the following prerequisites:
     ```
 
     ---
-2. Connect to your Azure account and set the subscription. You'll need to open browser on the client that you're using to connect to the machine and open this page: `https://microsoft.com/devicelogin` and enter the provided code in the Azure CLI output to authenticate. Get the access token and account ID for the registration.  
+2. Connect to your Azure account and set the subscription. Open a browser on the client that you're using to connect to the machine and open this page: `https://microsoft.com/devicelogin` and enter the provided code in the Azure CLI output to authenticate. Get the access token and account ID for the registration.  
 
     # [PowerShell](#tab/powershell)
 
@@ -192,7 +192,7 @@ This section describes how to assign Azure permissions for deployment from the A
 
 1. In the right pane, go to **Role assignments**. Verify that the deployment user has all the configured roles.
 
-1. In the Azure portal go to **Microsoft Entra Roles and Administrators** and assign the **Cloud Application Administrator** role permission at the Microsoft Entra tenant level.
+1. In the Azure portal, go to **Microsoft Entra Roles and Administrators** and assign the **Cloud Application Administrator** role permission at the Microsoft Entra tenant level.
 
     :::image type="content" source="media/deployment-arc-register-server-permissions/cloud-application-administrator-role-at-tenant.png" alt-text="Screenshot of the Cloud Application Administrator permission at the tenant level." lightbox="./media/deployment-arc-register-server-permissions/cloud-application-administrator-role-at-tenant.png":::
 

azure-local/deploy/deployment-azure-resource-manager-template.md

@@ -3,7 +3,7 @@ title: Azure Resource Manager template deployment for Azure Local, version 23H2
 description: Learn how to prepare and then deploy Azure Local instance, version 23H2 using the Azure Resource Manager template.
 author: alkohli
 ms.topic: how-to
-ms.date: 02/20/2024
+ms.date: 04/03/2025
 ms.author: alkohli
 ms.reviewer: alkohli
 ms.service: azure-local

azure-local/manage/remote-support-arc-extension.md

@@ -6,7 +6,7 @@ ms.author: robess
 ms.topic: overview
 ms.reviewer: shisab
 ms.lastreviewed: 01/19/2024
-ms.date: 10/22/2024
+ms.date: 04/03/2025
 ---
 
 # Azure Local Remote Support ARC extension overview
@@ -17,7 +17,7 @@ This article provides a brief overview of the Remote Support Arc extension, its
 
 ## About the Remote Support Arc extension
 
-The Remote Support Arc extension, shown as AzureEdgeRemoteSupport in the Azure portal, can expedite setup time and enhance support issue resolution. This capability happens by pre-installing the remote support agent on all nodes of the system. Additionally, it supports the configuration of scheduled tasks for [Just Enough Administration (JEA)](../manage/get-remote-support.md#install-jea-configurations-before-azure-registration).
+The Remote Support Arc extension, shown as AzureEdgeRemoteSupport in the Azure portal, can expedite setup time and enhance support issue resolution. This capability happens by preinstalling the remote support agent on all nodes of the system. Additionally, it supports the configuration of scheduled tasks for [Just Enough Administration (JEA)](../manage/get-remote-support.md#install-jea-configurations-before-azure-registration).
 
 The scheduled tasks to configure JEA are set up through either:
 
@@ -176,7 +176,7 @@ Get-RemoteSupportSessionHistory -IncludeSessionTranscript -SessionId <SessionId>
 ```
 
 > [!NOTE]
-> Session transcript details are retained for ninety days. You can retrieve details for a remote session within ninety days after the session.
+> Session transcript details are retained for 90 days. You can retrieve details for a remote session within 90 days after the session.
 
 ## Error handling
 

azure-stack/operator/azure-site-recovery-known-issues.md

@@ -5,7 +5,7 @@ author: ronmiab
 ms.author: robess
 ms.topic: troubleshooting
 ms.custom: linux-related-content
-ms.date: 06/03/2024
+ms.date: 04/03/2025
 ms.reviewer: rtiberiu
 ms.lastreviewed: 04/25/2024
 ---
@@ -14,22 +14,22 @@ ms.lastreviewed: 04/25/2024
 
 This article describes known issues for Azure Site Recovery on Azure Stack Hub. Use the following sections for details about the current known issues and limitations in Azure Site Recovery on Azure Stack Hub.
 
-## Maximum disk size supported is 1022 GB
+## Maximum disk size supported is 1,022 GB
 
-When you protect a VM, Azure Site Recovery needs to add an additional 1 GB of data to an existing disk. Since Azure Stack Hub has a hard limitation for the maximum size of a disk at 1023 GB, the maximum size of a disk protected by Site Recovery must be equal to or less than 1022.
+When you protect a virtual machine (VM), Azure Site Recovery needs to add an additional 1 GB of data to an existing disk. Since Azure Stack Hub has a hard limitation for the maximum size of a disk at 1,023 GB, the maximum size of a disk protected by Site Recovery must be equal to or less than 1022.
 
 When you try to protect a VM with a disk of 1023Gb, the following behavior occurs:
 
-- Enable protection succeeds as a seed disk of only 1 GB is created and ready for use. There is no error at this step.
-- Replication is blocked at **xx% Synchronized** and after a while, the replication health becomes **Critical** with the error **AzStackToAzStackSourceAgentDiskSourceAgentSlowResyncProgressOnPremToAzure**. The error occurs because during replication, Site Recovery tries to resize the seed disk to 1024 GB and write to it. This operation fails, as Azure Stack Hub does not support 1024 GB disks.
+- Enable protection succeeds as a seed disk of only 1 GB is created and ready for use. There's no error at this step.
+- Replication is blocked at **xx% Synchronized** and after a while, the replication health becomes **Critical** with the error **AzStackToAzStackSourceAgentDiskSourceAgentSlowResyncProgressOnPremToAzure**. The error occurs because during replication, Site Recovery tries to resize the seed disk to 1,024 GB and write to it. This operation fails, as Azure Stack Hub doesn't support 1,024 GB disks.
 
   :::image type="content" source="media/azure-site-recovery-known-issues/max-disk-number-1.png" alt-text="Screenshot of Azure portal showing maximum disk error." lightbox="media/azure-site-recovery-known-issues/max-disk-number-1.png":::
 
 - The seed disk created for this disk (in the target subscription) is still at 1 GB in size, and the **Activity log** shows a few **Write Disk** failures with the error message **The value '1024' of parameter 'disk.diskSizeGb' is out of range. Value '1024' must be between '1' and '1023' inclusive.**
 
   :::image type="content" source="media/azure-site-recovery-known-issues/max-disk-number-2.png" alt-text="Screenshot of Azure portal showing write disk errors." lightbox="media/azure-site-recovery-known-issues/max-disk-number-2.png":::
 
-The current workaround for this issue is to create a new disk (of 1022 GB or less), attach it to your source VM, copy the data from the 1023 GB disk to the new one, and then remove the 1023 GB disk from the source VM. Once this procedure is done, and the VM has all disks smaller or equal to 1022 GB, you can enable the protection using Azure Site Recovery.
+The current workaround for this issue is to create a new disk (of 1,022 GB or less), attach it to your source VM, copy the data from the 1,023 GB disk to the new one, and then remove the 1,023 GB disk from the source VM. Once this procedure is done, and the VM has all disks smaller or equal to 1,022 GB, you can enable the protection using Azure Site Recovery.
 
 ## Re-protection: available data disk slots on appliance
 
@@ -42,7 +42,7 @@ The current workaround for this issue is to create a new disk (of 1022 GB or les
     - Increase the size of the Azure Site Recovery appliance VM.
 
     >[!NOTE]
-    > We do not test and validate large VM SKUs for the appliance VM.
+    > We don't test and validate large VM SKUs for the appliance VM.
 
 4. If you're trying to re-protect a VM, but there aren't enough slots on the appliance to hold the replication disks, the error message **An internal error occurred** displays. You can check the number of the data disks currently on the appliance, or sign in to the appliance, go to **Event Viewer**, and open logs for **Azure Site Recovery** under **Applications and Services Logs**:
 
@@ -134,10 +134,10 @@ When replicating multiple VMs, you might see the **Protected item health changed
 
 :::image type="content" source="../operator/media/azure-site-recovery/known-issues/mobility-service-agent-warning.png" alt-text="Sample screenshot of the Protected item health change warning."lightbox="media/azure-site-recovery/known-issues/mobility-service-agent-warning.png":::
 
-This error message should only be a warning and is not a blocking issue for the actual replication or failover processes.
+This error message should only be a warning and isn't a blocking issue for the actual replication or failover processes.
 
 >[!TIP]
->You can check the the state of the respective VM to ensure it's healthy.
+>You can check the state of the respective VM to ensure it's healthy.
 
 ## Deleting the appliance VM (source) blocks the deletion of the vault (target)
 

azure-stack/user/overview-patterns-solution-examples.md

@@ -6,7 +6,7 @@ ms.topic: overview
 ms.date: 05/24/2021
 ms.author: robess
 ms.reviewer: anajod
-ms.lastreviewed: 05/24/2021
+ms.lastreviewed: 04/03/2025
 
 # Intent: As an Azure Stack user, I want an overview of hybrid patterns and solution examples so I can learn about building hybrid solutions on Azure and Azure Stack.
 # Keyword: azure stack hybrid patterns solution examples
@@ -41,7 +41,7 @@ There are two types of pattern articles:
 
 ## Solution deployment guides
 
-Step-by-step deployment guides assist in deploying a solution example. The guide may also refer to a companion code sample, stored in the GitHub [solutions sample repo](https://github.com/Azure-Samples/azure-intelligent-edge-patterns).
+Step-by-step deployment guides help you deploy a solution example. The guide may also refer to a companion code sample, stored in the GitHub [solutions sample repo](https://github.com/Azure-Samples/azure-intelligent-edge-patterns).
 
 ## Next steps
 

azure-stack/user/pattern-cicd-pipeline.md

@@ -3,7 +3,7 @@ title: The DevOps pattern in Azure Stack Hub
 description: Learn about the DevOps pattern so you can ensure consistency across deployments in Azure and Azure Stack Hub.
 author: ronmiab 
 ms.topic: article
-ms.date: 11/05/2019
+ms.date: 04/03/2025
 ms.author: robess
 ms.reviewer: anajod
 ms.lastreviewed: 11/05/2019
@@ -21,7 +21,7 @@ Code from a single location and deploy to multiple targets in development, test,
 
 Application deployment continuity, security, and reliability are essential to organizations and critical to development teams.
 
-Apps often require refactored code to run in each target environment. This means that an app isn't completely portable. It must be updated, tested, and validated as it moves through each environment. For example, code written in a development environment must then be rewritten to work in a test environment and rewritten when it finally lands in a production environment. Furthermore, this code is specifically tied to the host. This increases the cost and complexity of maintaining your app. Each version of the app is tied to each environment. The increased complexity and duplication increase the risk of security and code quality. In addition, the code can't be readily redeployed when you remove restore failed hosts or deploy additional hosts to handle increases in demand.
+Apps often require refactored code to run in each target environment. This means that an app isn't completely portable. It must be updated, tested, and validated as it moves through each environment. For example, code written in a development environment must then be rewritten to work in a test environment and rewritten when it finally lands in a production environment. Furthermore, this code is tied to the host. This increases the cost and complexity of maintaining your app. Each version of the app is tied to each environment. The increased complexity and duplication increase the risk of security and code quality. In addition, the code can't be readily redeployed when you remove restore failed hosts or deploy additional hosts to handle increases in demand.
 
 ## Solution
 

azure-stack/user/pattern-cross-cloud-scale-on-premises-data.md

@@ -3,7 +3,7 @@ title: Cross-cloud scaling (on-premises data) pattern in Azure Stack Hub
 description: Learn how to build a scalable cross-cloud app that uses on-premises data in Azure and Azure Stack Hub.
 author: ronmiab 
 ms.topic: article
-ms.date: 11/05/2019
+ms.date: 04/03/2025
 ms.author: robess
 ms.reviewer: anajod
 ms.lastreviewed: 11/05/2019
@@ -40,7 +40,7 @@ This solution uses the following components:
 | | Azure Traffic Manager | [Azure Traffic Manager](/azure/traffic-manager/traffic-manager-overview) is a DNS-based traffic load balancer. It allows you to control the distribution of user traffic for service endpoints in different datacenters. |
 | | Azure Application Insights | [Application Insights](/azure/azure-monitor/app/app-insights-overview) is an extensible Application Performance Management service for web developers building and managing apps on multiple platforms.|
 | | Azure Functions | [Azure Functions](/azure/azure-functions/) allows you to execute your code in a serverless environment without having to first create a VM or publish a web app. |
-| | Azure Autoscale | [Autoscale](/azure/azure-monitor/platform/autoscale-overview) is a built-in feature of Cloud Services, VMs, and web apps. The feature allows apps to perform their best when demand changes. Apps will adjust for traffic spikes, notifying you when metrics change and scaling as needed. |
+| | Azure Autoscale | [Autoscale](/azure/azure-monitor/platform/autoscale-overview) is a built-in feature of Cloud Services, VMs, and web apps. The feature allows apps to perform their best when demand changes. Apps adjust for traffic spikes, notifying you when metrics change and scaling as needed. |
 | Azure Stack Hub | IaaS Compute | Azure Stack Hub allows you to use the same app model, self-service portal, and APIs enabled by Azure. Azure Stack Hub IaaS allows a broad range of open-source technologies for consistent hybrid cloud deployments. The solution example uses a Windows Server VM to SQL Server, for example.|
 | | Azure App Service | Just like the Azure web app, the solution uses [Azure App Service on Azure Stack Hub](/azure-stack/operator/azure-stack-app-service-overview) to host the web app. |
 | | Networking | The Azure Stack Hub Virtual Network works exactly like the Azure Virtual Network. It uses many of the same networking components, including custom hostnames.
@@ -58,7 +58,7 @@ Azure and Azure Stack Hub are uniquely suited to support the needs of today's gl
 
 #### Hybrid cloud without the hassle
 
-Microsoft offers an unrivaled integration of on-premises assets with Azure Stack Hub and Azure in one unified solution. This integration eliminates the hassle of managing multiple point solutions and a mix of cloud providers. With cross-cloud scaling, the power of Azure is just a few clicks away. Just connect your Azure Stack Hub to Azure with cloud bursting and your data and apps will be available in Azure when needed.
+Microsoft offers an unrivaled integration of on-premises assets with Azure Stack Hub and Azure in one unified solution. This integration eliminates the hassle of managing multiple point solutions and a mix of cloud providers. With cross-cloud scaling, the power of Azure is just a few clicks away. Just connect your Azure Stack Hub to Azure with cloud bursting and your data and apps are available in Azure when needed.
 
 - Eliminate the need to build and maintain a secondary DR site.
 - Save time and money by eliminating tape backup and house up to 99 years of backup data in Azure.

azure-stack/user/pattern-cross-cloud-scale.md

@@ -3,7 +3,7 @@ title: Cross-cloud scaling pattern in Azure Stack Hub
 description: Learn how to build a scalable cross-cloud app on Azure and Azure Stack Hub.
 author: ronmiab 
 ms.topic: article
-ms.date: 11/05/2019
+ms.date: 04/03/2025
 ms.author: robess
 ms.reviewer: anajod
 ms.lastreviewed: 11/05/2019