Merge pull request #278423 from MicrosoftDocs/main

Publish to live, Monday 4 AM PST, 6/17

Author: ttorble

articles/aks/azure-app-configuration.md

@@ -63,6 +63,8 @@ Create the Azure App Configuration extension, which installs Azure App Configura
 
 For example, install the latest version of Azure App Configuration Kubernetes Provider via the Azure App Configuration extension on your AKS cluster:
 
+### [Azure CLI](#tab/cli)
+
 ```azurecli
 az k8s-extension create --cluster-type managedClusters \
     --cluster-name myAKSCluster \
@@ -72,20 +74,71 @@ az k8s-extension create --cluster-type managedClusters \
     --release-train preview
 ```
 
+### [Bicep](#tab/bicep)
+
+Create a Bicep template using the following example. 
+
+```bicep
+@description('The name of the Managed Cluster resource.')
+param clusterName string
+
+resource existingManagedCluster 'Microsoft.ContainerService/managedClusters@2024-02-01' existing = {
+  name: clusterName
+}
+
+resource appConfigExtension 'Microsoft.KubernetesConfiguration/extensions@2022-11-01' = {
+  name: 'appconfigurationkubernetesprovider'
+  scope: existingManagedCluster
+  properties: {
+    autoUpgradeMinorVersion: true
+    configurationSettings: {
+      'global.clusterType': 'managedclusters'
+    }
+    extensionType: 'microsoft.appconfiguration'
+    releaseTrain: 'preview'
+  }
+}
+```
+
+Deploy the Bicep template using the `az deployment group` command.
+
+```azurecli
+az deployment group create \
+  --resource-group myResourceGroup \
+  --template-file ./my-bicep-file-path.bicep \
+  --parameters clusterName=myAKSCluster
+```
+
+---
+
 ### Configure automatic updates
 
 If you create Azure App Configuration extension without specifying a version, `--auto-upgrade-minor-version` *is automatically enabled*, configuring the Azure App Configuration extension to automatically update its minor version on new releases.
 
 You can disable auto update by specifying the `--auto-upgrade-minor-version` parameter and setting the value to `false`. 
 
+#### [Azure CLI](#tab/cli)
+
 ```azurecli
 --auto-upgrade-minor-version false
 ```
 
+#### [Bicep](#tab/bicep)
+
+```bicep
+properties {
+  autoUpgradeMinorVersion: false
+}
+```
+
+---
+
 ### Targeting a specific version
 
 The same command-line argument is used for installing a specific version of Azure App Configuration Kubernetes Provider or rolling back to a previous version. Set `--auto-upgrade-minor-version` to `false` and `--version` to the version of Azure App Configuration Kubernetes Provider you wish to install. If the `version` parameter is omitted, the extension installs the latest version.
 
+#### [Azure CLI](#tab/cli)
+
 ```azurecli
 az k8s-extension create --cluster-type managedClusters \
     --cluster-name myAKSCluster \
@@ -97,6 +150,44 @@ az k8s-extension create --cluster-type managedClusters \
     --version 2.0.0-preview
 ```
 
+#### [Bicep](#tab/bicep)
+
+Create a Bicep template using the following example. 
+
+```bicep
+@description('The name of the Managed Cluster resource.')
+param clusterName string
+
+resource existingManagedCluster 'Microsoft.ContainerService/managedClusters@2024-02-01' existing = {
+  name: clusterName
+}
+
+resource appConfigExtension 'Microsoft.KubernetesConfiguration/extensions@2022-11-01' = {
+  name: 'appconfigurationkubernetesprovider'
+  scope: existingManagedCluster
+  properties: {
+    autoUpgradeMinorVersion: false
+    configurationSettings: {
+      'global.clusterType': 'managedclusters'
+    }
+    extensionType: 'microsoft.appconfiguration'
+    releaseTrain: 'preview'
+    version: '2.0.0-preview'
+  }
+}
+```
+
+Deploy the Bicep template using the `az deployment group` command.
+
+```azurecli
+az deployment group create \
+  --resource-group myResourceGroup \
+  --template-file ./my-bicep-file-path.bicep \
+  --parameters clusterName=myAKSCluster
+```
+
+---
+
 ## Extension versions
 
 The Azure App Configuration extension supports the following version of Azure App Configuration Kubernetes Provider:

articles/azure-monitor/alerts/log-alert-rule-health.md

@@ -15,7 +15,7 @@ ms.date: 02/08/2024
 [Azure Service Health](../../service-health/overview.md) monitors the health of your cloud resources, including log search alert rules. When a log search alert rule is healthy, the rule runs and the query executes successfully. This article explains how to view the health status of your log search alert rule, and tells you what to do if there are issues affecting your log search alert rules.
 
 Azure Service Health monitors:
-- [Resource health](../../service-health/resource-health-overview.md): information about the health of your individual cloud resources, such as a specific log search alert rule. 
+- [Resource health](../../service-health/resource-health-overview.md): information about the health of your individual cloud resources, such as a specific log search alert rule. See [here](../../service-health/resource-health-checks-resource-types.md) for the resource health checks performed on log search alert rules.
 - [Service health](../../service-health/service-health-overview.md): information about the health of the Azure services and regions you're using, which might affect your log search alert rule, including communications about outages, planned maintenance activities, and other health advisories.
 
  > [!NOTE]

articles/communication-services/quickstarts/voice-video-calling/includes/teams-interop/teams-interop-ios.md

@@ -14,6 +14,7 @@ In this quickstart, you'll learn how to join a Teams meeting using the Azure Com
 
 - A working [Communication Services calling iOS app](../../getting-started-with-calling.md).
 - A [Teams deployment](/deployoffice/teams-install).
+- The Minimum Version supported for Teams meeting ID and passcode join API : 2.11.0
 - An [access token](../../../identity/access-tokens.md).
 
 We will use beta.12 of AzureCommunicationCalling SDK for this quickstart so we need to update the podfile and install the Pods again. 

articles/communication-services/quickstarts/voice-video-calling/includes/teams-interop/teams-interop-javascript.md

@@ -17,7 +17,7 @@ Find the finalized code for this quickstart on [GitHub](https://github.com/Azure
 
 - A working [Communication Services calling web app](../../getting-started-with-calling.md).
 - A [Teams deployment](/deployoffice/teams-install).
-- The Minimum Version supported for Teams meetingId and passcode join API : 1.17.1
+- The Minimum Version supported for Teams meeting ID and passcode join API : 1.17.1
 - An [access token](../../../identity/access-tokens.md).
 
 ## Add the Teams UI controls

articles/governance/policy/samples/built-in-initiatives.md

@@ -1,7 +1,7 @@
 ---
 title: List of built-in policy initiatives
 description: List built-in policy initiatives for Azure Policy. Categories include Regulatory Compliance, Guest Configuration, and more.
-ms.date: 06/07/2024
+ms.date: 06/17/2024
 ms.topic: sample
 ms.custom: generated
 ---

articles/governance/policy/samples/built-in-policies.md

@@ -1,7 +1,7 @@
 ---
 title: List of built-in policy definitions
 description: List built-in policy definitions for Azure Policy. Categories include Tags, Regulatory Compliance, Key Vault, Kubernetes, Guest Configuration, and more.
-ms.date: 06/07/2024
+ms.date: 06/17/2024
 ms.topic: sample
 ms.custom: generated
 ---
@@ -166,6 +166,10 @@ The name of each built-in links to the policy definition in the Azure portal. Us
 
 [!INCLUDE [azure-policy-reference-policies-devcenter](../../../../includes/policy/reference/bycat/policies-devcenter.md)]
 
+## DevOpsInfrastructure
+
+[!INCLUDE [azure-policy-reference-policies-devopsinfrastructure](../../../../includes/policy/reference/bycat/policies-devopsinfrastructure.md)]
+
 ## ElasticSan
 
 [!INCLUDE [azure-policy-reference-policies-elasticsan](../../../../includes/policy/reference/bycat/policies-elasticsan.md)]

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