Merge pull request #214909 from shayoniseth/patch-105

Update azure-monitor-agent-windows-client.md

Author: prmerger-automator[bot]

articles/azure-monitor/agents/azure-monitor-agent-windows-client.md

@@ -4,7 +4,7 @@ description: This article describes the instructions to install the agent on Win
 ms.topic: conceptual
 author: shseth
 ms.author: shseth
-ms.date: 10/10/2022
+ms.date: 10/18/2022
 ms.custom: references_region
 ms.reviewer: shseth
 
@@ -95,12 +95,14 @@ The image below demonstrates how this works:
 
 Then, proceed with the instructions below to create and associate them to a Monitored Object, using REST APIs or PowerShell commands.
 
+### Permissions required
+Since MO is a tenant level resource, the scope of the permission would be higher than a subscription scope. Therefore, an Azure tenant admin may be needed to perform this step. [Follow these steps to elevate Azure AD Tenant Admin as Azure Tenant Admin](../../role-based-access-control/elevate-access-global-admin.md). It will give the Azure AD admin 'owner' permissions at the root scope. This is needed for all methods described below in this section.
+
 ### Using REST APIs
 
 #### 1. Assign ‘Monitored Object Contributor’ role to the operator
 
 This step grants the ability to create and link a monitored object to a user.
-**Permissions required:** Since MO is a tenant level resource, the scope of the permission would be higher than a subscription scope. Therefore, an Azure tenant admin may be needed to perform this step. [Follow these steps to elevate Azure AD Tenant Admin as Azure Tenant Admin](../../role-based-access-control/elevate-access-global-admin.md). It will give the Azure AD admin 'owner' permissions at the root scope.
 
 **Request URI**
 ```HTTP