copy edit

Author: tfitzmac

articles/azure-resource-manager/management/authenticate-multi-tenant.md

@@ -3,12 +3,12 @@ title: Authenticate across tenants
 description: Describes how Azure Resource Manager handles authentication requests across tenants.
 ms.topic: conceptual
 ms.custom: devx-track-arm-template
-ms.date: 09/26/2024
+ms.date: 01/22/2025
 ---
 
 # Authenticate requests across tenants
 
-When creating a multi-tenant application, you may need to handle authentication requests for resources that are in different tenants. A common scenario is when a virtual machine in one tenant must join a virtual network in another tenant. Azure Resource Manager provides a header value for storing auxiliary tokens to authenticate the requests to different tenants.
+When creating a multitenant application, you might need to handle authentication requests for resources in different tenants. A common scenario is when a virtual machine in one tenant must join a virtual network in another tenant. Azure Resource Manager provides a header value for storing auxiliary tokens to authenticate the requests to different tenants.
 
 ## Header values for authentication
 
@@ -21,15 +21,15 @@ The request has the following authentication header values:
 
 The auxiliary header can hold up to three auxiliary tokens.
 
-In the code of your multi-tenant app, get the authentication token for other tenants and store them in the auxiliary headers. The user or application must have been invited as a guest to the other tenants.
+In the code of your multitenant app, get the authentication token for other tenants and store them in the auxiliary headers. The user or application must be invited as a guest to the other tenants.
 
 ## Processing the request
 
-When your app sends a request to Resource Manager, the request is run under the identity from the primary token. The primary token must be valid and unexpired. This token must be from a tenant that can manage the subscription.
+When your app sends a request to Resource Manager, the request runs under the identity from the primary token. The primary token must be valid and unexpired. This token must be from a tenant that can manage the subscription.
 
-When the request references a resource from different tenant, Resource Manager checks the auxiliary tokens to determine if the request can be processed. All auxiliary tokens in the header must be valid and unexpired. If any token is expired, Resource Manager returns a 401 response code. The response includes the client ID and tenant ID from the token that isn't valid. If the auxiliary header contains a valid token for the tenant, the cross tenant request is processed.
+When the request references a resource from different tenant, Resource Manager checks the auxiliary tokens to determine if it can process the request. All auxiliary tokens in the header must be valid and unexpired. If any token is expired, Resource Manager returns a 401 response code. The response includes the client ID and tenant ID from the token that isn't valid. If the auxiliary header contains a valid token for the tenant, the cross-tenant request is processed.
 
 ## Next steps
 
 * To learn about authentication requests, see [Authentication flows and application scenarios](../../active-directory/develop/authentication-flows-app-scenarios.md).
-* For more information about tokens, see [Microsoft Entra access tokens](../../active-directory/develop/access-tokens.md).
+* For more information about tokens, see [Microsoft Entra access tokens](../../active-directory/develop/access-tokens.md).

articles/azure-resource-manager/management/create-private-link-access-commands.md

@@ -2,12 +2,12 @@
 title: Manage resources through private link
 description: Restrict management access for resource to private link
 ms.topic: conceptual
-ms.date: 09/26/2024
+ms.date: 01/22/2025
 ---
 
 # Use APIs to create a private link for managing Azure resources
 
-This article explains how you can use [Azure Private Link](../../private-link/index.yml) to restrict access for managing resources in your subscriptions.
+This article explains how to use [Azure Private Link](../../private-link/index.yml) to restrict access for managing resources in your subscriptions.
 
 [!INCLUDE [Create content](../../../includes/resource-manager-create-rmpl.md)]
 
@@ -67,17 +67,17 @@ To create resource management private link, send the following request:
 
 ---
 
-Note the ID that is returned for the new resource management private link. You'll use it for creating the private link association.
+Note the ID that is returned for the new resource management private link. You use it for creating the private link association.
 
 ## Create private link association
 
-The resource name of a private link association resource must be a GUID, and it isn't yet supported to disable the publicNetworkAccess field. 
+The resource name of a private link association resource must be a GUID, and you can't disable the `publicNetworkAccess` field.
 
 To create the private link association, use:
 
 # [Azure CLI](#tab/azure-cli)
 
-  ### Example
+### Example
 
   ```azurecli
   # Login first with az login if not using Cloud Shell
@@ -133,7 +133,7 @@ To create the private link association, use:
 
 ## Add private endpoint
 
-This article assumes you already have a virtual network. In the subnet that will be used for the private endpoint, you must turn off private endpoint network policies. If you haven't turned off private endpoint network policies, see [Disable network policies for private endpoints](../../private-link/disable-private-endpoint-network-policy.md).
+This article assumes you already have a virtual network. In the subnet that you plan to use for the private endpoint, you must turn off private endpoint network policies. To turn off private endpoint network policies, see [Disable network policies for private endpoints](../../private-link/disable-private-endpoint-network-policy.md).
 
 To create a private endpoint, see Private Endpoint documentation for creating via [Portal](../../private-link/create-private-endpoint-portal.md), [PowerShell](../../private-link/create-private-endpoint-powershell.md), [CLI](../../private-link/create-private-endpoint-cli.md), [Bicep](../../private-link/create-private-endpoint-bicep.md), or [template](../../private-link/create-private-endpoint-template.md).
 
@@ -177,4 +177,4 @@ If your request is automatically approved, you can continue to the next section.
 
 ## Next steps
 
-To learn more about private links, see [Azure Private Link](../../private-link/index.yml).
+To learn more about private links, see [Azure Private Link](../../private-link/index.yml).