Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into tsk544791-sfi-ssh

Author: asudbring

articles/sap/center-sap-solutions/install-software.md

@@ -4,7 +4,7 @@ description: Learn how to install SAP software on an SAP system that you created
 ms.service: sap-on-azure
 ms.subservice: center-sap-solutions
 ms.topic: how-to
-ms.date: 02/03/2023
+ms.date: 02/02/2026
 author: sagarkeswani
 ms.author: sagarkeswani
 ms.custom: sfi-ropc-nochange
@@ -15,12 +15,7 @@ ms.custom: sfi-ropc-nochange
 # Install SAP software
 
 
-
-
-
-After you've created infrastructure for your new SAP system using *Azure Center for SAP solutions*, you need to install the SAP software.
-
-In this how-to guide, you'll learn two ways to install the SAP software for your system. Choose whichever method is appropriate for your use case. You can either:
+After you've created infrastructure for your new SAP system using *Azure Center for SAP solutions*, you need to install the SAP software. In this how-to guide, you'll learn two ways to install the SAP software for your system. Choose whichever method is appropriate for your use case. You can either:
 
 - [Install the SAP software through Azure Center for SAP solutions directly using the installation wizard](#install-sap-with-azure-center-for-sap-solutions).
 - [Install the SAP software outside of Azure Center for SAP solutions, then detect the installed system from the service](#install-sap-through-outside-method).

articles/sap/center-sap-solutions/overview.md

@@ -4,7 +4,7 @@ description: Azure Center for SAP solutions is an Azure offering that makes SAP
 ms.service: sap-on-azure
 ms.subservice: center-sap-solutions
 ms.topic: overview
-ms.date: 10/19/2022
+ms.date: 02/02/2026
 ms.author: sagarkeswani
 author: sagarkeswani
 #Customer intent: As a developer, I want to learn about Azure Center for SAP solutions so that I can decide to use the service with a new or existing SAP system.
@@ -13,8 +13,6 @@ author: sagarkeswani
 
 # What is Azure Center for SAP solutions?
 
-
-
 *Azure Center for SAP solutions* is an Azure offering that makes SAP a top-level workload on Azure. Azure Center for SAP solutions is an end-to-end solution that enables you to create and run SAP systems as a unified workload on Azure and provides a more seamless foundation for innovation. You can take advantage of the management capabilities for both new and existing Azure-based SAP systems.
 
 The guided deployment experience takes care of creating the necessary compute, storage and networking components needed to run your SAP system. Azure Center for SAP solutions then helps automate the installation of the SAP software according to Microsoft best practices.

articles/sap/monitor/about-azure-monitor-sap-solutions.md

@@ -6,8 +6,10 @@ ms.service: sap-on-azure
 ms.subservice: sap-monitor
 ms.topic: overview
 ms.custom: subject-monitoring
-ms.date: 08/21/2024
-ms.author: jacobjaygbay
+
+ms.date: 02/02/2026
+ms.author: jushiman
+
 #Customer intent: As a developer, I want to learn how to monitor my SAP resources on Azure so that I can better understand their availability, performance, and operation.
 # Customer intent: As an IT administrator, I want to monitor my SAP resources on Azure for availability and performance, so that I can ensure the reliability and smooth operation of critical business processes.
 ---

articles/sap/sap-on-azure-overview.md

@@ -5,12 +5,14 @@ author: ju-shim
 ms.author: bentrin
 ms.service: sap-on-azure
 ms.topic: overview
+
 ms.date: 02/03/2026
+
 ms.custom: template-overview
 # Customer intent: As an IT manager overseeing SAP systems, I want to explore available offerings for running and managing SAP on Azure, so that I can choose the best solutions for deploying, integrating, and monitoring our SAP workloads effectively.
 ---
 
-# What SAP on Azure offerings are available?
+# SAP on Azure offerings
 
 ## Overview
 
@@ -116,7 +118,7 @@ Microsoft Azure provides multiple offerings for running and managing SAP systems
 
 ## Microsoft Services Integration
 
-### SAP Integration with Microsoft Services
+### SAP integration with Microsoft services
 
 **Integration Scope**: SAP workloads (IaaS and SaaS) with Microsoft product ecosystem  
 **Service Coverage**: Microsoft Entra ID, Exchange Online, Power Platform, Power BI, Azure Integration Services
@@ -210,10 +212,13 @@ Microsoft Azure provides multiple offerings for running and managing SAP systems
 
 #### Azure Key Vault
 
+For more information, see the [SAP integration with Microsoft services](workloads/integration-get-started.md) documentation.
+
 **Service Overview**: Secure storage and management for cryptographic keys, certificates, and secrets  
 **SAP Integration**: Centralized secret management for SAP applications and infrastructure  
 **Security Benefits**: Hardware security module protection and access control
 
+
 **Key Capabilities**:
 - Centralized cryptographic key management
 - Certificate lifecycle management

articles/sap/workloads/certifications.md

@@ -8,11 +8,11 @@ ms.service: sap-on-azure
 ms.subservice: sap-vm-workloads
 ms.topic: article
 ms.tgt_pltfrm: vm-linux
-ms.date: 01/25/2022
+ms.date: 02/02/2026
 ms.author: juergent
 # Customer intent: As an SAP administrator, I want to access a comprehensive list of supported SAP certifications and configurations on Azure, so that I can ensure compliance and optimize my SAP workloads on the cloud platform.
 ---
-# SAP certifications and configurations running on Microsoft Azure
+# SAP certifications and configurations on Microsoft Azure
 
 SAP and Microsoft have a long history of working together in a strong partnership that has mutual benefits for their customers. Microsoft is constantly updating its platform and submitting new certification details to SAP in order to ensure Microsoft Azure is the best platform on which to run your SAP workloads. The following tables outline Azure supported configurations and list of growing SAP certifications. This list is an overview list that might deviate here and there from the official SAP lists. How to get to the detailed data is documented in the article [What SAP software is supported for Azure deployments](./supported-product-on-azure.md)
 
@@ -44,7 +44,7 @@ References:
 | SAP BusinessObjects BI | Windows |N/A | [1928533 - SAP Applications on Azure: Supported Products and Azure VM types](https://launchpad.support.sap.com/#/notes/1928533) |
 | SAP NetWeaver | Windows, SUSE Linux Enterprise, Red Hat Enterprise Linux, Oracle Linux |SQL Server, Oracle (Windows and Oracle Linux only), DB2, SAP ASE | [1928533 - SAP Applications on Azure: Supported Products and Azure VM types](https://launchpad.support.sap.com/#/notes/1928533) |
 
-## Other SAP Workload supported on Azure
+## Other SAP Workloads supported on Azure
 
 | SAP Product | Guest OS | RDBMS | Virtual Machine Types |
 | --- | --- | --- | --- |

articles/sap/workloads/deployment-checklist.md

@@ -6,12 +6,12 @@ manager: bburns
 ms.service: sap-on-azure
 ms.subservice: sap-vm-workloads
 ms.topic: article
-ms.date: 11/19/2024
+ms.date: 02/02/2026
 ms.author: juergent
 # Customer intent: "As an SAP solutions architect, I want to utilize a detailed checklist for deploying SAP workloads to Azure, so that I can ensure a smooth migration and optimize system performance throughout each project phase."
 ---
 
-# SAP workloads on Azure: planning and deployment checklist
+# SAP workload planning and deployment checklist
 
 This checklist is designed for customers moving SAP applications to Azure infrastructure as a service. SAP applications in this document represent SAP products running the SAP kernel, including SAP NetWeaver, S/4HANA, BW and BW/4 and others. Throughout the duration of the project, a customer and/or SAP partner should review the checklist. It's important to note that many of the checks are completed at the beginning of the project and during the planning phase. After the deployment is done, straightforward changes on deployed Azure infrastructure or SAP software releases can become complex.
 
@@ -116,7 +116,7 @@ We recommend that you set up and validate a full HADR solution and security desi
    [Migrate very large databases (VLDB) to Azure for SAP](/training/modules/migrate-very-large-databases-to-azure/)  
 
 ### Technical validation
-
+In the pilot phase, validate the following technical aspects of your planned deployment:
 - **Compute / VM types**
   - Review the resources in SAP support notes, in the SAP HANA hardware directory, and in the SAP PAM again. Make sure to match supported VMs for Azure, supported OS releases for those VM types, and supported SAP and DBMS releases.
   - Validate again the sizing of your application and the infrastructure you deploy on Azure. If you're moving existing applications, you can often derive the necessary SAPS from the infrastructure you use and the [SAP benchmark webpage](https://www.sap.com/dmc/exp/2018-benchmark-directory/#/sd) and compare it to the SAPS numbers listed in [SAP note 1928533](https://launchpad.support.sap.com/#/notes/1928533). Also keep [this article on SAPS ratings](https://techcommunity.microsoft.com/t5/Running-SAP-Applications-on-the/SAPS-ratings-on-Azure-VMs-8211-where-to-look-and-where-you-can/ba-p/368208) in mind.

articles/sap/workloads/exchange-online-integration-sap-email-outbound.md

@@ -6,7 +6,7 @@ author: MartinPankraz
 ms.service: sap-on-azure
 ms.subservice: sap-vm-workloads
 ms.topic: how-to
-ms.date: 03/11/2022
+ms.date: 02/02/2026
 ms.author: mapankra
 ms.custom: sfi-image-nochange
 # Customer intent: "As an SAP system administrator, I want to configure outbound email communication from SAP ABAP Platform to Exchange Online, so that I can efficiently manage notifications and workflows while ensuring compliance with modern authentication standards."

articles/sap/workloads/hana-vm-operations-storage.md

@@ -7,7 +7,9 @@ keywords: 'SAP, Azure HANA, Storage Ultra disk, Premium storage'
 ms.service: sap-on-azure
 ms.subservice: sap-vm-workloads
 ms.topic: article
-ms.date: 01/05/2026
+
+ms.date: 02/2/2026
+
 ms.author: juergent
 ms.custom: H1Hack27Feb2017, linux-related-content
 # Customer intent: As an SAP HANA administrator, I want to configure optimal Azure storage solutions for my virtual machines, so that I can ensure high performance and reliability for my database workloads.
@@ -38,7 +40,7 @@ In the on-premises world, you rarely had to care about the I/O subsystems and it
 
 Given that low storage latency is critical for DBMS systems, even as DBMS, like SAP HANA, keep data in-memory. The critical path in storage is usually around the transaction log writes of the DBMS systems. But also operations like writing savepoints or loading data in-memory after crash recovery can be critical. Therefore, it's **mandatory** to use Azure premium SSD v1/v2, Ultra disk, or Azure NetApp Files NFS for **/hana/data** and **/hana/log** volumes. 
 
-Some guiding principles in selecting your storage configuration for HANA can be listed like:
+The following are some guiding principles in selecting your storage configuration for HANA:
 
 - Decide on the type of storage based on [Azure Storage types for SAP workload](./planning-guide-storage.md) and [Select a disk type](/azure/virtual-machines/disks-types)
 - The overall VM I/O throughput and IOPS limits in mind when sizing or deciding for a VM. Overall VM storage throughput is documented in the article [Memory optimized virtual machine sizes](/azure/virtual-machines/sizes-memory)   
@@ -78,7 +80,7 @@ If you're using LVM or mdadm to build stripe sets across several Azure premium d
 - 64 KB for **/hana/log**
 
 > [!NOTE]
-> The stripe size for **/hana/data** got changed from earlier recommendations calling for 64 KB or 128 KB to 256 KB based on customer experiences with more recent Linux versions. The size of 256 KB is providing slightly better performance. We also changed the recommendation for stripe sizes of **/hana/log** from 32 KB to 64 KB in order to get enough throughput with larger I/O sizes.
+> The stripe size for **/hana/data** got changed from earlier recommendations calling for 64 KB or 128 KB to 256 KB based on customer experiences with more recent Linux versions. The size of 256 KB provides a slightly better performance. We also changed the recommendation for stripe sizes of **/hana/log** from 32 KB to 64 KB to get enough throughput with larger I/O sizes.
 
 > [!NOTE]
 > You don't need to configure any redundancy level using RAID volumes since Azure block storage keeps three images of a VHD. The usage of a stripe set with Azure premium disks is purely to configure volumes that provide sufficient IOPS and/or I/O throughput.

articles/sap/workloads/high-availability-guide-suse-nfs.md

@@ -1,13 +1,13 @@
 ---
-title: High availability for NFS on Azure VMs on SLES | Microsoft Docs
+title: High availability for NFS on Azure VMs on SUSE Linux Enterprise Server | Microsoft Docs
 description: High availability for NFS on Azure VMs on SUSE Linux Enterprise Server
 services: virtual-machines-windows,virtual-network,storage
 author: rdeltcheva
 manager: juergent
 ms.service: sap-on-azure
 ms.subservice: sap-vm-workloads
 ms.topic: article
-ms.date: 06/19/2024
+ms.date: 02/02/2026
 ms.author: radeltch
 ms.custom:
   - linux-related-content
@@ -36,7 +36,7 @@ ms.custom:
 [sap-hana-ha]:sap-hana-high-availability.md
 
 > [!NOTE]
-> We recommend deploying one of the Azure first-party NFS services: [NFS on Azure Files](../../storage/files/storage-files-quick-create-use-linux.md) or [NFS ANF volumes](../../azure-netapp-files/azure-netapp-files-create-volumes.md) for storing shared data in a highly available SAP system. Be aware, that we are de-emphasizing SAP reference architectures, utilizing NFS clusters.  
+> We recommend deploying one of the Azure first-party NFS services: [NFS on Azure Files](../../storage/files/storage-files-quick-create-use-linux.md) or [NFS ANF volumes](../../azure-netapp-files/azure-netapp-files-create-volumes.md) for storing shared data in a highly available SAP system. Be aware, that we're de-emphasizing SAP reference architectures, utilizing NFS clusters.  
 
 This article describes how to deploy the virtual machines, configure the virtual machines, install the cluster framework, and install a highly available NFS server that can be used to store the shared data of a highly available SAP system.
 This guide describes how to set up a highly available NFS server that is used by two SAP systems, NW1 and NW2. The names of the resources (for example virtual machines, virtual networks) in the example assume that you have used the [SAP file server template][template-file-server] with resource prefix **prod**.
@@ -83,7 +83,7 @@ The NFS server uses a dedicated virtual hostname and virtual IP addresses for ev
 * Probe port 61001 for NW2
 
 ## Set up a highly available NFS server
-
+In the following sections, you'll learn how to set up a highly available NFS server on SUSE Linux Enterprise Server.
 ### Deploy Linux manually via Azure portal
 
 This document assumes that you've already deployed a resource group, [Azure Virtual Network](../../virtual-network/virtual-networks-overview.md), and subnet.
@@ -110,7 +110,7 @@ Follow [create load balancer](../../load-balancer/quickstart-load-balancer-stand
      * Check "Enable Floating IP"
 
 > [!NOTE]
-> Health probe configuration property numberOfProbes, otherwise known as "Unhealthy threshold" in Portal, isn't respected. So to control the number of successful or failed consecutive probes, set the property "probeThreshold" to 2. It is currently not possible to set this property using Azure portal, so use either the [Azure CLI](/cli/azure/network/lb/probe) or [PowerShell](/powershell/module/az.network/new-azloadbalancerprobeconfig) command.
+> Health probe configuration property numberOfProbes, otherwise known as "Unhealthy threshold" in Portal, isn't respected. So to control the number of successful or failed consecutive probes, set the property "probeThreshold" to 2. It's currently not possible to set this property using Azure portal, so use either the [Azure CLI](/cli/azure/network/lb/probe) or [PowerShell](/powershell/module/az.network/new-azloadbalancerprobeconfig) command.
 
 > [!NOTE]
 > When VMs without public IP addresses are placed in the backend pool of internal (no public IP address) Standard Azure load balancer, there will be no outbound internet connectivity, unless additional configuration is performed to allow routing to public end points. For details on how to achieve outbound connectivity see [Public endpoint connectivity for Virtual Machines using Azure Standard Load Balancer in SAP high-availability scenarios](./high-availability-guide-standard-load-balancer-outbound-connections.md).  
@@ -386,11 +386,11 @@ The following items are prefixed with either **[A]** - applicable to all nodes,
 
 1. **[A]** Setup drbd split-brain detection
 
-    When using drbd to synchronize data from one host to another, a so called split brain can occur. A split brain is a scenario where both cluster nodes promoted the drbd device to be the primary and went out of sync. It might be a rare situation but you still want to handle and resolve a split brain as fast as possible. It is therefore important to be notified when a split brain happened.
+    When using drbd to synchronize data from one host to another, a so called split brain can occur. A split brain is a scenario where both cluster nodes promoted the drbd device to be the primary and went out of sync. It might be a rare situation but you still want to handle and resolve a split brain as fast as possible. It's therefore important to be notified when a split brain happened.
 
     Read [the official drbd documentation](https://www.linbit.com/drbd-user-guide/users-guide-drbd-8-4/#s-split-brain-notification) on how to set up a split brain notification.
 
-    It is also possible to automatically recover from a split brain scenario. For more information, read [Automatic split brain recovery policies](https://www.linbit.com/drbd-user-guide/users-guide-drbd-8-4/#s-automatic-split-brain-recovery-configuration)
+    It's also possible to automatically recover from a split brain scenario. For more information, read [Automatic split brain recovery policies](https://www.linbit.com/drbd-user-guide/users-guide-drbd-8-4/#s-automatic-split-brain-recovery-configuration)
 
 ### Configure Cluster Framework
 
@@ -404,7 +404,7 @@ The following items are prefixed with either **[A]** - applicable to all nodes,
    > * For SLES 15/15 SP1, the version must be at least resource-agents-4.3.0184.6ee15eb2-4.13.1.  
    >
    > Note that the change will require brief downtime.  
-   > For existing Pacemaker clusters, if the configuration was already changed to use socat as described in [Azure Load-Balancer Detection Hardening](https://www.suse.com/support/kb/doc/?id=7024128), there is no requirement to switch immediately to azure-lb resource agent.
+   > For existing Pacemaker clusters, if the configuration was already changed to use socat as described in [Azure Load-Balancer Detection Hardening](https://www.suse.com/support/kb/doc/?id=7024128), there's no requirement to switch immediately to azure-lb resource agent.
 
    ```bash
    sudo crm configure rsc_defaults resource-stickiness="200"

articles/sap/workloads/high-availability-guide-suse-pacemaker.md

@@ -8,7 +8,7 @@ ms.service: sap-on-azure
 ms.subservice: sap-vm-workloads
 ms.topic: article
 ms.custom: devx-track-azurepowershell, linux-related-content
-ms.date: 01/07/2026
+ms.date: 02/02/2026
 ms.author: radeltch
 # Customer intent: "As a system administrator, I want to set up Pacemaker with fencing on SUSE Linux Enterprise Server in Azure, so that I can ensure high availability and reliability for my applications running in the cloud."
 ---