Merge pull request #278394 from sreekzz/Freshness-MS-Date-Change

MS Freshness Date Change

Author: PMEds28

articles/hdinsight/apache-ambari-email.md

@@ -3,7 +3,7 @@ title: 'Tutorial: Configure Apache Ambari email notifications in Azure HDInsight
 description: This article describes how to use SendGrid with Apache Ambari for email notifications.
 ms.service: hdinsight
 ms.topic: tutorial
-ms.date: 05/25/2023
+ms.date: 06/15/2024
 
 #Customer intent: As a HDInsight user, I want to configure Apache Ambari to send email notifications.
 ---
@@ -36,7 +36,7 @@ In this tutorial, you learn how to:
 
 1. From the Overview page, click **Open SaaS Account on publisher’s site**, to go the SendGrid webpage for your account.
 
-    :::image type="content" source="./media/apache-ambari-email/azure-portal-sendgrid-manage.png" alt-text="SendGrid overview in azure portal.":::
+    :::image type="content" source="./media/apache-ambari-email/azure-portal-sendgrid-manage.png" alt-text="SendGrid overview in Azure portal.":::
 
 1. From the left menu, navigate to your **Settings** and then **API Keys**.
 

articles/hdinsight/apache-ambari-usage.md

@@ -3,12 +3,12 @@ title: Apache Ambari usage in Azure HDInsight
 description: Discussion of how Apache Ambari is used in Azure HDInsight.
 ms.service: hdinsight
 ms.topic: conceptual
-ms.date: 05/10/2023
+ms.date: 06/15/2024
 ---
 
 # Apache Ambari usage in Azure HDInsight
 
-HDInsight uses Apache Ambari for cluster deployment and management. Ambari agents run on every node (headnode, worker node, zookeeper, and edgenode if exists). Ambari server runs only on headnode. Only one instance of Ambari server shall run at one time. This is controlled by HDInsight failover controller. When one of the headnodes is down for reboot or maintenance, the other headnode will become active and Ambari server on the second headnode will be started.
+HDInsight uses Apache Ambari for cluster deployment and management. Ambari agents run on every node provided if headnode, worker node, zookeeper, and edgenode are present. Ambari server runs only on headnode. Only one instance of Ambari server shall run at one time. This is controlled by HDInsight failover controller. When one of the headnodes is down for reboot or maintenance, the other headnode will become active and Ambari server on the second headnode will be started.
 
 All cluster configuration should be done through the [Ambari UI](./hdinsight-hadoop-manage-ambari.md), any local change will be overwritten when the node is restarted.
 

articles/hdinsight/cluster-availability-monitor-logs.md

@@ -3,7 +3,7 @@ title: How to monitor cluster availability with Azure Monitor logs in HDInsight
 description: Learn how to use Azure Monitor logs to monitor cluster health and availability.
 ms.service: hdinsight
 ms.topic: how-to
-ms.date: 05/23/2023
+ms.date: 06/15/2024
 ---
 
 # How to monitor cluster availability with Azure Monitor logs in HDInsight
@@ -100,7 +100,7 @@ After these blades close, you should see your action group listed under the **Ac
 :::image type="content" source="media/cluster-availability-monitor-logs/portal-create-alert-rule-finish.png" alt-text="Portal creates alert rule finish.":::
 
 > [!TIP]
-> The ability to specify **Severity** is a powerful tool that can be used when creating multiple alerts. For example, you could create one alert to raise a Warning (Sev 1) if a single head node goes down and another alert that raises Critical (Sev 0) in the unlikely event that both head nodes go down.
+> The ability to specify **Severity** is a powerful tool that can be used when creating multiple alerts. For example, you could create one alert to raise a Warning (severity 1) if a single head node goes down and another alert that raises Critical (severity 1) in the unlikely event that both head nodes go down.
 
 When the condition for this alert is met, the alert will fire and you'll receive an email with the alert details like this:
 
@@ -110,9 +110,9 @@ You can also view all alerts that have fired, grouped by severity, by going to *
 
 :::image type="content" source="media/cluster-availability-monitor-logs/hdi-portal-oms-alerts.png" alt-text="Log Analytics workspace alerts.":::
 
-Selecting on a severity grouping (i.e. **Sev 1,** as highlighted above) will show records for all alerts of that severity that have fired like below:
+When you select on a severity group (i.e. **severity 1,** as highlighted above) it will show records for all alerts of that severity that have fired like below:
 
-:::image type="content" source="media/cluster-availability-monitor-logs/portal-oms-alerts-sev1.png" alt-text="Log Analytics workspace sev one alert.":::
+:::image type="content" source="media/cluster-availability-monitor-logs/portal-oms-alerts-sev1.png" alt-text="Screenshot showing Log Analytics workspace severity  one alert.":::
 
 ## Next steps
 

articles/hdinsight/cluster-reboot-vm.md

@@ -4,7 +4,7 @@ description: Learn how to reboot unresponsive VMs for Azure HDInsight clusters.
 ms.custom: hdinsightactive
 ms.service: hdinsight
 ms.topic: how-to
-ms.date: 05/25/2023
+ms.date: 06/15/2024
 ---
 
 # Reboot VMs for HDInsight clusters

articles/hdinsight/connect-on-premises-network.md

@@ -4,7 +4,7 @@ description: Learn how to create an HDInsight cluster in an Azure Virtual Networ
 ms.service: hdinsight
 ms.topic: how-to
 ms.custom: hdinsightactive
-ms.date: 05/23/2023
+ms.date: 06/15/2024
 ---
 
 # Connect HDInsight to your on-premises network

articles/hdinsight/control-network-traffic.md

@@ -3,7 +3,7 @@ title: Control network traffic in Azure HDInsight
 description: Learn techniques for controlling inbound and outbound traffic to Azure HDInsight clusters.
 ms.service: hdinsight
 ms.topic: conceptual
-ms.date: 05/23/2023
+ms.date: 06/15/2024
 ---
 
 # Control network traffic in Azure HDInsight
@@ -26,7 +26,7 @@ If you plan on using **network security groups** to control network traffic, per
 
 2. Identify the service tags required by HDInsight for your region. There are multiple ways to obtain these service tags:
     1. Consult the list of published service tags in [Network security group (NSG) service tags for Azure HDInsight](hdinsight-service-tags.md).
-    2. If your region is not present in the list, use the [Service Tag Discovery API](../virtual-network/service-tags-overview.md#use-the-service-tag-discovery-api) to find a service tag for your region.
+    2. If your region isn't present in the list, use the [Service Tag Discovery API](../virtual-network/service-tags-overview.md#use-the-service-tag-discovery-api) to find a service tag for your region.
     3. If you are unable to use the API, download the [service tag JSON file](../virtual-network/service-tags-overview.md#discover-service-tags-by-using-downloadable-json-files) and search for your desired region.
 
 
@@ -44,9 +44,9 @@ For more information on controlling outbound traffic from HDInsight clusters, se
 
 Forced tunneling is a user-defined routing configuration where all traffic from a subnet is forced to a specific network or location, such as your on-premises network or Firewall. Forced tunneling of all data transfer back to on-premises is _not_ recommended due to large volumes of data transfer and potential performance impact.
 
-Customers who are interested to setup forced tunneling, should use [custom metastores](./hdinsight-use-external-metadata-stores.md) and setup the appropriate connectivity from the cluster subnet or on-premises network to these custom metastores.
+Customers who are interested to set up forced tunneling, should use [custom metastores](./hdinsight-use-external-metadata-stores.md) and set up the appropriate connectivity from the cluster subnet or on-premises network to these custom metastores.
 
-To see an example of the UDR setup with Azure Firewall, see [Configure outbound network traffic restriction for Azure HDInsight clusters](hdinsight-restrict-outbound-traffic.md).
+To see an example of the UDR set up with Azure Firewall, see [Configure outbound network traffic restriction for Azure HDInsight clusters](hdinsight-restrict-outbound-traffic.md).
 
 ## Required ports
 

articles/hdinsight/create-cluster-error-dictionary.md

@@ -4,7 +4,7 @@ description: Learn how to troubleshoot errors that occur when creating Azure HDI
 ms.service: hdinsight
 ms.topic: troubleshooting
 ms.custom: hdinsightactive
-ms.date: 05/18/2023
+ms.date: 06/15/2024
 ---
 
 

articles/hdinsight/disk-encryption.md

@@ -4,7 +4,7 @@ titleSuffix: Azure HDInsight
 description: This article describes the two layers of encryption available for data at rest on Azure HDInsight clusters.
 ms.service: hdinsight
 ms.topic: conceptual
-ms.date: 05/23/2023
+ms.date: 06/15/2024
 ms.custom: devx-track-azurepowershell, devx-track-azurecli 
 ms.devlang: azurecli
 ---
@@ -28,8 +28,8 @@ These types are summarized in the following table.
 
 |Cluster type |OS Disk (Managed disk) |Data disk (Managed disk) |Temp data disk (Local SSD) |
 |---|---|---|---|
-|Kafka, HBase with Accelerated writes|Layer1: [SSE Encryption](../virtual-machines/managed-disks-overview.md#encryption) by default|Layer1: [SSE Encryption](../virtual-machines/managed-disks-overview.md#encryption) by default, Layer2: Optional encryption at rest using CMK|Layer1: Optional Encryption at host using PMK, Layer2: Optional encryption at rest using CMK|
-|All other clusters (Spark, Interactive, Hadoop, HBase without Accelerated writes)|Layer1: [SSE Encryption](../virtual-machines/managed-disks-overview.md#encryption) by default|N/A|Layer1: Optional Encryption at host using PMK, Layer2: Optional encryption at rest using CMK|
+|Kafka, HBase with Accelerated writes|Layer 1: [SSE Encryption](../virtual-machines/managed-disks-overview.md#encryption) by default|Layer 1: [SSE Encryption](../virtual-machines/managed-disks-overview.md#encryption) by default, Layer 2: Optional encryption at rest using CMK|Layer 1: Optional Encryption at host using PMK, Layer 2: Optional encryption at rest using CMK|
+|All other clusters (Spark, Interactive, Hadoop, HBase without Accelerated writes)|Layer 1: [SSE Encryption](../virtual-machines/managed-disks-overview.md#encryption) by default|N/A|Layer 1: Optional Encryption at host using PMK, Layer 2: Optional encryption at rest using CMK|
 
 ## Encryption at rest using Customer-managed keys
 

articles/hdinsight/domain-joined/apache-domain-joined-architecture.md

@@ -4,7 +4,7 @@ description: Learn how to plan Azure HDInsight security with Enterprise Security
 ms.service: hdinsight
 ms.topic: conceptual
 ms.custom: hdinsightactive, has-azure-ad-ps-ref
-ms.date: 05/11/2023
+ms.date: 06/15/2024
 ---
 
 # Use Enterprise Security Package in HDInsight
@@ -55,11 +55,11 @@ Because Kerberos relies on password hashes, you must [enable password hash sync
 
 If you're using federation with Active Directory Federation Services (AD FS), you must enable password hash sync. (For a recommended setup, see [this video](https://youtu.be/qQruArbu2Ew).) Password hash sync helps with disaster recovery in case your AD FS infrastructure fails, and it also helps provide leaked-credential protection. For more information, see [Enable password hash sync with Microsoft Entra Connect Sync](../../active-directory/hybrid/how-to-connect-password-hash-synchronization.md).
 
-Using on-premises Active Directory or Active Directory on IaaS VMs alone, without Microsoft Entra ID and Microsoft Entra Domain Services, isn't a supported configuration for HDInsight clusters with ESP.
+When you use on-premises Active Directory or Active Directory on IaaS VMs alone, without Microsoft Entra ID and Microsoft Entra Domain Services, isn't a supported configuration for HDInsight clusters with ESP.
 
 [!INCLUDE [Azure AD PowerShell deprecation note](~/reusable-content/msgraph-powershell/includes/aad-powershell-deprecation-note.md)]
 
-If federation is being used and password hashes are synced correctly, but you're getting authentication failures, check if cloud password authentication is enabled for the PowerShell service principal. If not, you must set a [Home Realm Discovery (HRD) policy](../../active-directory/manage-apps/configure-authentication-for-federated-users-portal.md) for your Microsoft Entra tenant. To check and set the HRD policy:
+If you use federation and password hashes are synced correctly, but you're getting authentication failures, check if cloud password authentication is enabled for the PowerShell service principal. If not, you must set a [Home Realm Discovery (HRD) policy](../../active-directory/manage-apps/configure-authentication-for-federated-users-portal.md) for your Microsoft Entra tenant. To check and set the HRD policy:
 
 1. Install the preview [Azure AD PowerShell module](/powershell/azure/active-directory/install-adv2).
 

articles/hdinsight/domain-joined/apache-domain-joined-manage.md

@@ -3,14 +3,14 @@ title: Manage Enterprise Security Package clusters - Azure HDInsight
 description: Learn how to manage Azure HDInsight clusters with Enterprise Security Package.
 ms.service: hdinsight
 ms.topic: how-to
-ms.date: 05/24/2023
+ms.date: 06/15/2024
 ---
 
 # Manage HDInsight clusters with Enterprise Security Package
 
 Learn the users and the roles in HDInsight Enterprise Security Package (ESP), and how to manage ESP clusters.
 
-## Use VSCode to link to domain joined cluster
+## Use VS Code to link to domain joined cluster
 
 You can link a normal cluster by using Apache Ambari managed username, also link a security Apache Hadoop cluster by using domain username (such as: `[email protected]`).
 
@@ -72,7 +72,7 @@ If you have Beeline installed locally, and connect over an Azure Virtual Network
 Connection string: -u 'jdbc:hive2://<headnode-FQDN>:10001/;transportMode=http'
 ```
 
-To find the fully qualified domain name of a headnode, use the information in the Manage HDInsight using the Ambari REST API document.
+To find the fully qualified domain name of a headnode, use the information in the Managed HDInsight using the Ambari REST API document.
 
 ## Users of HDInsight clusters with ESP
 
@@ -91,9 +91,9 @@ A HDInsight cluster with ESP has three new users in addition to Ambari Admin.
 
     Note the other AD users also have these privileges.
 
-    There are some end points within the cluster (for example, Templeton) which are not managed by Ranger, and hence aren't secure. These end points are locked down for all users except the cluster admin domain user.
+    There are some end points within the cluster (for example, Templeton) which aren't managed by Ranger, and hence  secure. These end points are locked down for all users except the cluster admin domain user.
 
-- **Regular**: During cluster creation, you can provide multiple active directory groups. The users in these groups are synced to Ranger and Ambari. These users are domain users and have access to only Ranger-managed endpoints (for example, Hiveserver2). All the RBAC policies and auditing will be applicable to these users.
+- **Regular**: During cluster creation, you can provide multiple active directory groups. The users in these groups are synced to Ranger and Ambari. These users are domain users and have access to only Ranger-managed endpoints (for example, `Hiveserver2`). All the RBAC policies and auditing will be applicable to these users.
 
 ## Roles of HDInsight clusters with ESP