Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into tamram22-0509

Author: tamram

articles/azure-monitor/agents/azure-monitor-agent-troubleshoot-windows-arc.md

@@ -20,10 +20,11 @@ Follow the steps below to troubleshoot the latest version of the Azure Monitor a
 
 2. **Verify that the extension was successfully installed and provisioned, which installs the agent binaries on your machine**:  
 	1. Open Azure portal > select your Arc-enabled server > Open **Settings** : **Extensions** blade from left menu > 'AzureMonitorWindowsAgent'should show up with Status: 'Succeeded'  
-	2. If not, check if machine can reach Azure and find the extension to install using the command below:  
+	2. If not, check if the Arc agent (Connected Machine Agent) is able to connect to Azure and the extension service is running. 
 		```azurecli
-		az vm extension image list-versions --location <machine-region> --name AzureMonitorWindowsAgent --publisher Microsoft.Azure.Monitor
-		```  
+		azcmagent show
+		```   
+		If you see `Agent Status: Disconnected`, [file a ticket](#file-a-ticket) with **Summary** as 'Arc agent or extensions service not working' and **Problem type** as 'I need help with Azure Monitor Windows Agent'.
 	3. Wait for 10-15 minutes as extension maybe in transitioning status. If it still doesn't show up, [uninstall and install the extension](./azure-monitor-agent-manage.md) again and repeat the verification to see the extension show up. 
 	4. If not, check if you see any errors in extension logs located at `C:\ProgramData\GuestConfig\extension_logs\Microsoft.Azure.Monitor.AzureMonitorWindowsAgent` on your machine  
 	5. If none of the above works, [file a ticket](#file-a-ticket) with **Summary** as 'AMA extension fails to install or provision' and **Problem type** as 'I need help with Azure Monitor Windows Agent'.  

articles/azure-monitor/agents/azure-monitor-agent-troubleshoot-windows-vm.md

@@ -4,7 +4,7 @@ description: Guidance for troubleshooting issues on Windows virtual machines, sc
 ms.topic: conceptual
 author: shseth
 ms.author: shseth
-ms.date: 5/3/2022
+ms.date: 5/10/2022
 ms.custom: references_region
 
 ---
@@ -13,7 +13,7 @@ ms.custom: references_region
 
 [!INCLUDE [azure-monitor-agent-architecture](../../../includes/azure-monitor-agent/azure-monitor-agent-architecture-include.md)]
 
-## Basic troubleshooting steps
+## Basic troubleshooting steps (installation, agent not running, configuration issues)
 Follow the steps below to troubleshoot the latest version of the Azure Monitor agent running on your Windows virtual machine:
 
 1. **Carefully review the [prerequisites here](./azure-monitor-agent-manage.md#prerequisites).**  

articles/virtual-machines/workloads/sap/sap-ascs-ha-multi-sid-wsfc-azure-shared-disk.md

@@ -13,7 +13,7 @@ ms.service: virtual-machines-sap
 ms.topic: article
 ms.tgt_pltfrm: vm-windows
 ms.workload: infrastructure-services
-ms.date: 04/14/2022
+ms.date: 05/10/2022
 ms.author: radeltch
 ms.custom: H1Hack27Feb2017
 
@@ -34,7 +34,9 @@ Currently you can use Azure Premium SSD disks as an Azure shared disk for the SA
    - Locally redundant storage (LRS) for premium shared disk (skuName - Premium_LRS) is supported with deployment in availability set.
    - Zone-redundant storage (ZRS) for premium shared disk (skuName - Premium_ZRS) is supported with deployment in availability zones.
 -  Azure shared disk value [maxShares](../../disks-shared-enable.md?tabs=azure-cli#disk-sizes) determines how many cluster nodes can use the shared disk. Typically for SAP ASCS/SCS instance you will configure two nodes in Windows Failover Cluster, therefore the value for `maxShares` must be set to two.
--  [Azure proximity placement group](../../windows/proximity-placement-groups.md) is not required for Azure shared disk. But if you are using PPG for SAP system, all virtual machines sharing a disk must be part of the same PPG.
+-  [Azure proximity placement group](../../windows/proximity-placement-groups.md) is not required for Azure shared disk. But for SAP deployment with PPG, follow below guidelines:
+   -  If you are using PPG for SAP system deployed in a region then all virtual machines sharing a disk must be part of the same PPG.
+   -  If you are using PPG for SAP system deployed across zones like described in the document [Proximity placement groups with zonal deployments](sap-proximity-placement-scenarios.md#proximity-placement-groups-with-zonal-deployments), you can attach Premium_ZRS storage to virtual machines sharing a disk.
 
 For further details on limitations for Azure shared disk, please review carefully the [limitations](../../disks-shared.md#limitations) section of Azure Shared Disk documentation.
 

articles/virtual-machines/workloads/sap/sap-high-availability-guide-wsfc-shared-disk.md

@@ -13,7 +13,7 @@ ms.service: virtual-machines-sap
 ms.topic: article
 ms.tgt_pltfrm: vm-windows
 ms.workload: infrastructure-services
-ms.date: 04/14/2022
+ms.date: 05/10/2022
 ms.author: radeltch
 ms.custom: H1Hack27Feb2017
 
@@ -151,7 +151,9 @@ Currently you can use Azure Premium SSD disks as an Azure shared disk for the SA
    - Locally redundant storage (LRS) for premium shared disk (skuName - Premium_LRS) is supported with deployment in Azure availability set.
    - Zone-redundant storage (ZRS) for premium shared disk (skuName - Premium_ZRS) is supported with deployment in Azure availability zones.
 -  Azure shared disk value [maxShares](../../disks-shared-enable.md?tabs=azure-cli#disk-sizes) determines how many cluster nodes can use the shared disk. Typically for SAP ASCS/SCS instance you will configure two nodes in Windows Failover Cluster, therefore the value for `maxShares` must be set to two.
--  [Azure proximity placement group](../../windows/proximity-placement-groups.md) is not required for Azure shared disk. But if you are using PPG for SAP system, all virtual machines sharing a disk must be part of the same PPG.
+-  [Azure proximity placement group](../../windows/proximity-placement-groups.md) is not required for Azure shared disk. But for SAP deployment with PPG, follow below guidelines:
+   -  If you are using PPG for SAP system deployed in a region then all virtual machines sharing a disk must be part of the same PPG.
+   -  If you are using PPG for SAP system deployed across zones like described in the document [Proximity placement groups with zonal deployments](sap-proximity-placement-scenarios.md#proximity-placement-groups-with-zonal-deployments), you can attach Premium_ZRS storage to virtual machines sharing a disk.
 
 For further details on limitations for Azure shared disk, please review carefully the [limitations](../../disks-shared.md#limitations) section of Azure Shared Disk documentation.
 

articles/virtual-machines/workloads/sap/sap-high-availability-infrastructure-wsfc-shared-disk.md

@@ -13,7 +13,7 @@ ms.service: virtual-machines-sap
 ms.topic: article
 ms.tgt_pltfrm: vm-windows
 ms.workload: infrastructure-services
-ms.date: 04/14/2022
+ms.date: 05/10/2022
 ms.author: radeltch
 ms.custom: H1Hack27Feb2017
 
@@ -172,7 +172,7 @@ Before you begin the installation, review this article:
 
 ## Create the ASCS VMs
 
-For SAP ASCS / SCS cluster deploy two VMs in Azure availability set or Azure availability zones based on the type of your deployment. If you are using [Azure proximity placement groups (PPG)](./sap-proximity-placement-scenarios.md), make sure all virtual machines sharing a disk must be part of the same PPG. Once the VMs are deployed:
+For SAP ASCS / SCS cluster deploy two VMs in Azure availability set or Azure availability zones based on the type of your deployment. Once the VMs are deployed:
 
 - Create Azure Internal Load Balancer for SAP ASCS /SCS instance.
 - Add Windows VMs to the AD domain.
@@ -202,7 +202,9 @@ Based on your deployment type, the host names and the IP addresses of the scenar
 The steps mentioned in the document remain same for both deployment type. But if your cluster is running in availability set, you need to deploy LRS for Azure  premium shared disk (Premium_LRS) and if the cluster is running in availability zone deploy ZRS for Azure premium shared disk (Premium_ZRS).
 
 > [!Note]
-> [Azure proximity placement group](../../windows/proximity-placement-groups.md) is not required for Azure shared disk. But if you are using PPG for SAP system, all virtual machines sharing a disk must be part of the same PPG.
+> [Azure proximity placement group](../../windows/proximity-placement-groups.md) is not required for Azure shared disk. But for SAP deployment with PPG, follow below guidelines:
+> - If you are using PPG for SAP system deployed in a region then all virtual machines sharing a disk must be part of the same PPG.
+> -  If you are using PPG for SAP system deployed across zones like described in the document [Proximity placement groups with zonal deployments](sap-proximity-placement-scenarios.md#proximity-placement-groups-with-zonal-deployments), you can attach Premium_ZRS storage to virtual machines sharing a disk.
 
 ## <a name="fe0bd8b5-2b43-45e3-8295-80bee5415716"></a> Create Azure internal load balancer