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

Author: Karthigasree

articles/active-directory/develop/scenario-web-app-call-api-acquire-token.md

@@ -61,7 +61,7 @@ public async Task<IActionResult> Profile()
 
  // Use the access token to call a protected web API.
  HttpClient client = new HttpClient();
- client.DefaultRequestHeaders.Add("Authorization", authorizationHeader);
+ client.DefaultRequestHeaders.Add("Authorization", accessToken);
  string json = await client.GetStringAsync(url);
 }
 ```

articles/ai-services/document-intelligence/index.yml

@@ -65,6 +65,8 @@ landingContent:
                url: concept-custom.md
              - text: Tax document models
                url: concept-tax-document.md
+             - text: Contract model
+               url: concept-contract.md
              - text: Invoice model
                url: concept-invoice.md
              - text: Receipt model

articles/azure-monitor/essentials/migrate-to-azure-storage-lifecycle-policy.md

@@ -120,7 +120,7 @@ The sample policy definition file below sets the retention for all blobs in the
   ]
 }
 
-``````
+```
 
 ## [Templates](#tab/templates)
 
@@ -130,7 +130,7 @@ Apply the following template to create a lifecycle management policy. You must s
 
 az deployment group create  --resource-group <resource group name> --template-file <template file>
 
-``````
+```
 
 The following template sets the retention for storage account *azmonstorageaccount001* for all blobs in the container *insights-activity-logs* for all resources for the subscription ID *ABCD1234-5849-ABCD-1234-9876543210AB*.
 
@@ -180,7 +180,7 @@ The following template sets the retention for storage account *azmonstorageaccou
         }
     ]
 }
-``````
+```
 
 ---
 

articles/hdinsight/domain-joined/apache-domain-joined-configure-using-azure-adds.md

@@ -5,7 +5,7 @@ description: Learn how to set up and configure an HDInsight cluster integrated w
 ms.service: hdinsight
 ms.topic: how-to
 ms.custom: seodec18,seoapr2020, contperf-fy21q2
-ms.date: 04/25/2023
+ms.date: 09/21/2023
 ---
 
 # Configure HDInsight clusters for Azure Active Directory integration with Enterprise Security Package
@@ -19,7 +19,7 @@ For a detailed, step-by-step tutorial on setting up and configuring a domain in
 Enterprise Security Package (ESP) provides Active Directory integration for Azure HDInsight. This integration allows domain users to use their domain credentials to authenticate with HDInsight clusters and run big data jobs.
 
 > [!NOTE]  
-> ESP is generally available in HDInsight 3.6 and 4.0 for these cluster types: Apache Spark, Interactive, Hadoop, and HBase. ESP for the Apache Kafka cluster type is in preview with best-effort support only. ESP clusters created before the ESP GA date (October 1, 2018) are not supported.
+> ESP is generally available in HDInsight 4.0 and 5.0 for these cluster types: Apache Spark, Interactive, Hadoop, Apache Kafka and HBase. ESP clusters created before the ESP GA date (October 1, 2018) are not supported.
 
 ## Prerequisites
 
@@ -31,7 +31,7 @@ There are a few prerequisites to complete before you can create an ESP-enabled H
 - Create and authorize a managed identity.
 - Complete Networking setup for DNS and related issues.
 
-Each of these items will be discussed in detail below. For a walkthrough of completing all of these steps, see [Create and configure Enterprise Security Package clusters in Azure HDInsight](apache-domain-joined-create-configure-enterprise-security-cluster.md).
+Each of these items are discussed in details. For a walkthrough of completing all of these steps, see [Create and configure Enterprise Security Package clusters in Azure HDInsight](apache-domain-joined-create-configure-enterprise-security-cluster.md).
 
 ### Enable Azure AD DS
 
@@ -102,7 +102,7 @@ Change the configuration of the DNS servers in the Azure AD DS virtual network.
 
 It's easier to place both the Azure AD DS instance and the HDInsight cluster in the same Azure virtual network. If you plan to use different virtual networks, you must peer those virtual networks so that the domain controller is visible to HDInsight VMs. For more information, see [Virtual network peering](../../virtual-network/virtual-network-peering-overview.md).
 
-After the virtual networks are peered, configure the HDInsight virtual network to use a custom DNS server. And enter the Azure AD DS private IPs as the DNS server addresses. When both virtual networks use the same DNS servers, your custom domain name will resolve to the right IP and will be reachable from HDInsight. For example, if your domain name is `contoso.com`, then after this step, `ping contoso.com` should resolve to the right Azure AD DS IP.
+After the virtual networks are peered, configure the HDInsight virtual network to use a custom DNS server. And enter the Azure AD DS private IPs as the DNS server addresses. When both virtual networks use the same DNS servers, your custom domain name resolves to the right IP and it is reachable from HDInsight. For example, if your domain name is `contoso.com`, then after this step, `ping contoso.com` should resolve to the right Azure AD DS IP.
 
 :::image type="content" source="./media/apache-domain-joined-configure-using-azure-adds/hdinsight-aadds-peered-vnet-configuration.png" alt-text="Configuring custom DNS servers for a peered virtual network" border="true":::