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

Author: asudbring

articles/ai-services/language-service/personally-identifiable-information/concepts/conversations-entity-categories.md

@@ -16,8 +16,6 @@ ms.custom: language-service-pii, build-2024
 
 Use this article to find the entity categories that can be returned by the [conversational PII detection feature](../how-to-call-for-conversations.md). This feature runs a predictive model to identify, categorize, and redact sensitive information from an input conversation.
 
-The PII preview feature includes the ability to detect personal (`PII`) information from conversations.
-
 ## Entity categories
 
 The following entity categories are returned when you're sending API requests PII feature.

articles/ai-services/language-service/personally-identifiable-information/how-to-call-for-conversations.md

@@ -26,11 +26,11 @@ By default, this feature will use the latest available AI model on your input. Y
 
 ### Language support
 
-Currently the conversational PII preview API only supports English language.
+See the [PII Language Support page](language-support.md) for more details. Currently the conversational PII GA model only supports the English language. The preview model and API support the [same list languages](../concepts/language-support.md) as the other Language services.
 
 ### Region support
 
-Currently the conversational PII preview API supports all Azure regions supported by the Language service.
+The conversational PII API supports all Azure regions supported by the Language service.
 
 ## Submitting data
 
@@ -82,7 +82,7 @@ When you get results from PII detection, you can stream the results to an applic
 Use the following example if you have conversations transcribed using the Speech service's [speech to text](../../Speech-Service/speech-to-text.md) feature:
 
 ```bash
-curl -i -X POST https://your-language-endpoint-here/language/analyze-conversations/jobs?api-version=2022-05-15-preview \
+curl -i -X POST https://your-language-endpoint-here/language/analyze-conversations/jobs?api-version=2024-05-01 \
 -H "Content-Type: application/json" \
 -H "Ocp-Apim-Subscription-Key: your-key-here" \
 -d \
@@ -195,7 +195,7 @@ curl -i -X POST https://your-language-endpoint-here/language/analyze-conversatio
             "taskName": "analyze 1",
             "kind": "ConversationalPIITask",
             "parameters": {
-                "modelVersion": "2022-05-15-preview",
+                "modelVersion": "2023-04-15-preview",
                 "redactionSource": "text",
                 "includeAudioRedaction": true,
                 "piiCategories": [
@@ -213,7 +213,7 @@ curl -i -X POST https://your-language-endpoint-here/language/analyze-conversatio
 Use the following example if you have conversations that originated in text. For example, conversations through a text-based chat client.
 
 ```bash
-curl -i -X POST https://your-language-endpoint-here/language/analyze-conversations/jobs?api-version=2022-05-15-preview \
+curl -i -X POST https://your-language-endpoint-here/language/analyze-conversations/jobs?api-version=2024-05-01 \
 -H "Content-Type: application/json" \
 -H "Ocp-Apim-Subscription-Key: your-key-here" \
 -d \
@@ -251,7 +251,7 @@ curl -i -X POST https://your-language-endpoint-here/language/analyze-conversatio
             "taskName": "analyze 1",
             "kind": "ConversationalPIITask",
             "parameters": {
-                "modelVersion": "2022-05-15-preview"
+                "modelVersion": "2023-04-15-preview"
             }
         }
     ]

articles/ai-services/language-service/personally-identifiable-information/language-support.md

@@ -102,7 +102,7 @@ Use this article to learn which natural languages are supported by the PII and c
 |Chinese-Simplified   |`zh-hans`    |`zh` also accepted|
 |Chinese-Traditional  |`zh-hant`    |                  |
 
-# [PII for conversations (preview)](#tab/conversations)
+# [PII for conversations](#tab/conversations)
 
 ## PII language support
 

articles/azure-arc/resource-bridge/overview.md

@@ -131,8 +131,6 @@ The following private cloud environments and their versions are officially suppo
 
 ### Supported versions
 
-The minimum supported version of Arc resource bridge is 1.0.15.
-
 Generally, the latest released version and the previous three versions (n-3) of Arc resource bridge are supported. For example, if the current version is 1.0.18, then the typical n-3 supported versions are:
 
 * Current version: 1.0.18

articles/azure-linux/concepts-core.md

@@ -1,17 +1,17 @@
 ---
 title: Azure Linux Container Host for AKS basic core concepts
 description: Learn the basic core concepts that make up the Azure Linux Container Host for AKS. 
-author: htaubenfeld
-ms.author: htaubenfeld
+author: suhuruli
+ms.author: suhuruli
 ms.service: microsoft-linux
 ms.topic: conceptual 
-ms.date: 09/29/2023
+ms.date: 08/18/2024
 ms.custom: template-concept, linux-related-content
 ---
 
 # Core concepts for the Azure Linux Container Host for AKS
 
-Microsoft Azure Linux is an open-sourced project maintained by Microsoft, which means that Microsoft is responsible for the entire Azure Linux Container Host stack, from the Linux kernel to the [Common Vulnerabilities and Exposures (CVEs)](https://cve.mitre.org/) infrastructure, support, and end-to-end validation. Microsoft makes it easy for you to create an AKS cluster with Azure Linux, without worrying about details such as verification and critical security vulnerability patches from a third party distribution.
+Microsoft Azure Linux is an open-sourced project maintained by Microsoft, which means that Microsoft is responsible for the entire Azure Linux Container Host stack, from the Linux kernel to the Common Vulnerabilities and Exposures (CVEs) infrastructure, support, and end-to-end validation. Microsoft makes it easy for you to create an AKS cluster with Azure Linux, without worrying about details such as verification and critical security vulnerability patches from a third party distribution.
 
 ## CVE infrastructure
 

articles/azure-linux/concepts-packages.md

@@ -1,11 +1,11 @@
 ---
 title: Azure Linux Container Host for AKS packages
 description: Learn about the packages supported by the Azure Linux Container Host for AKS.
-author: htaubenfeld
-ms.author: htaubenfeld
+author: suhuruli
+ms.author: suhuruli
 ms.service: microsoft-linux
 ms.topic: conceptual
-ms.date: 05/10/2023
+ms.date: 08/18/2024
 ms.custom: template-concept, linux-related-content
 ---
 
@@ -17,7 +17,7 @@ The Azure Linux Container Host for AKS is based on the Microsoft Azure Linux dis
 
 The Azure Linux Container Host package list includes all the needed dependencies to run an Azure Linux VM and also pulls in any necessary Azure Kubernetes Service dependencies. A list of all the packages in the Azure Linux Container Host can be viewed [here](https://github.com/Azure/AgentBaker/blob/master/vhdbuilder/release-notes/AKSCBLMariner/gen2/latest.txt).
 
-Whenever a new image is released by AKS, the [AKSCBLMariner release notes folder](https://github.com/Azure/AgentBaker/tree/master/vhdbuilder/release-notes/AKSCBLMariner/gen2) is updated with a new `latest.txt` file, which details the most up-to-date package list. You can also view previous image package lists and the historical versions of each package in the most recent image release in the GitHub repository. For each prior image release, you can find a corresponding `.txt` file with the naming convention `YYYY.MM.DD.txt`, where `YYYY.MM.DD` is the date of each previous image release. 
+Whenever a new image is released by AKS, the [AKS Azure Linux release notes folder](https://github.com/Azure/AgentBaker/blob/master/vhdbuilder/release-notes/AKSAzureLinux/gen2/latest.txt) is updated with a new `latest.txt` file, which details the most up-to-date package list. You can also view previous image package lists and the historical versions of each package in the most recent image release in the GitHub repository. For each prior image release, you can find a corresponding `.txt` file with the naming convention `YYYY.MM.DD.txt`, where `YYYY.MM.DD` is the date of each previous image release. 
 
 
 > [!NOTE]
@@ -49,7 +49,7 @@ To determine the `nodeImageVersion`, run the following command:
 az aks show -g <groupname> -n <clustername> | grep nodeImageVersion
 ```
 
-Then, as described above, check the [AKSCBLMariner release notes folder](https://github.com/Azure/AgentBaker/tree/master/vhdbuilder/release-notes/AKSCBLMariner/gen2) for the file that corresponds with the previously determined node image version date. In the file, the *Installed Packages Begin* section lists all the package versions in your cluster.
+Then, as described above, check the [AKS Azure Linux release notes folder](https://github.com/Azure/AgentBaker/blob/master/vhdbuilder/release-notes/AKSAzureLinux/gen2) for the file that corresponds with the previously determined node image version date. In the file, the *Installed Packages Begin* section lists all the package versions in your cluster.
 
 
 ## Next steps

articles/azure-linux/how-to-install-certs.md

@@ -1,18 +1,18 @@
 ---
 title: Installing certificates on the Azure Linux Container Host for AKS
 description: How to install certificates on the Azure Linux Container Host for AKS.
-author: htaubenfeld
-ms.author: htaubenfeld
+author: suhuruli
+ms.author: suhuruli
 ms.editor: schaffererin
 ms.service: microsoft-linux
 ms.topic: how-to
-ms.date: 06/30/2023
+ms.date: 08/18/2023
 ms.custom: template-how-to-pattern, linux-related-content
 ---
 
 # Installing certificates on the Azure Linux Container host for AKS
 
-By default, the Azure Linux Container Host for AKS image has a minimal set of root certs to trust certain Microsoft resources, such as packages.microsoft.com. All Microsoft certificates aren't automatically included in our image, which is consistent with the least-privilege principle and gives you the flexibility to opt in to just the root certificates you need and to customize your image.
+By default, the Azure Linux Container Host for AKS image has a minimal set of root certs to trust certain Microsoft resources, such as `packages.microsoft.com`. All Microsoft certificates aren't automatically included in our image, which is consistent with the least-privilege principle and gives you the flexibility to opt in to just the root certificates you need and to customize your image.
 
 The `ca-certificates-base` is preinstalled in the container host image and contains certificates from a small set of Microsoft-owned CAs. It consists of certificates from Microsoft's root and intermediate CAs. This package allows your container host to trust a minimal set of servers, all of which were verified and had their certificates issued by Microsoft.
 

articles/azure-linux/troubleshoot-packages.md

@@ -1,12 +1,12 @@
 ---
 title: Troubleshooting Azure Linux Container Host for AKS package upgrade issues
 description: How to troubleshoot Azure Linux Container Host for AKS package upgrade issues.
-author: htaubenfeld
-ms.author: htaubenfeld
+author: suhuruli
+ms.author: suhuruli
 ms.service: microsoft-linux
 ms.custom: linux-related-content
 ms.topic: troubleshooting
-ms.date: 05/10/2023
+ms.date: 08/18/2024
 ---
 
 # Troubleshoot issues with package upgrades on the Azure Linux Container Host
@@ -22,11 +22,11 @@ However, sometimes the packages in the Azure Linux Container Host fail to receiv
 
 ## Cause
 
-Some packages, such as the Linux Kernel, require a reboot for the updates to take effect. To facilitate automatic reboots, the Azure Linux VM runs the check-restart service, which creates the /var/run/reboot-required file when a package update requires a reboot.
+Some packages, such as the Linux Kernel, require a reboot for the updates to take effect. To facilitate automatic reboots, the Azure Linux VM runs the check-restart service, which creates the `/var/run/reboot-required` file when a package update requires a reboot.
 
 ## Solution
 
-To ensure that Kubernetes acts on the request for a reboot, we recommend setting up the [kured daemonset](/azure/aks/node-updates-kured). [Kured](https://github.com/kubereboot/kured) monitors your nodes for the /var/run/reboot-required file and, when it's found, drains the work off the node and reboots it.
+To ensure that Kubernetes acts on the request for a reboot, we recommend setting up the [kured daemonset](/azure/aks/node-updates-kured). [Kured](https://github.com/kubereboot/kured) monitors your nodes for the `/var/run/reboot-required` file and, when it's found, drains the work off the node and reboots it.
 
 ## Next steps
 

articles/azure-linux/tutorial-azure-linux-telemetry-monitor.md

@@ -1,12 +1,12 @@
 ---
 title: Azure Linux Container Host for AKS tutorial - Enable telemetry and monitoring for the Azure Linux Container Host
 description: In this Azure Linux Container Host for AKS tutorial, you'll learn how to enable telemetry and monitoring for the Azure Linux Container Host.
-author: htaubenfeld
-ms.author: htaubenfeld
+author: suhuruli
+ms.author: suhuruli
 ms.service: microsoft-linux
 ms.custom: linux-related-content
 ms.topic: tutorial
-ms.date: 04/18/2023
+ms.date: 08/18/2024
 ---
 
 # Tutorial: Enable telemetry and monitoring for your Azure Linux Container Host cluster
@@ -28,21 +28,33 @@ In the next and last tutorial, you'll learn how to upgrade your Azure Linux node
 
 ## 1 - Enable monitoring
 
-### Use a default Log Analytics workspace
+### Option 1: Use a default Log Analytics workspace
 
 The following step enables monitoring for your Azure Linux Container Host cluster using Azure CLI. In this example, you aren't required to precreate or specify an existing workspace. This command simplifies the process for you by creating a default workspace in the default resource group of the AKS cluster subscription. If one doesn't already exist in the region, the default workspace created will resemble the format *DefaultWorkspace-< GUID >-< Region >*. 
 
 ```azurecli
 az aks enable-addons -a monitoring -n testAzureLinuxCluster -g testAzureLinuxResourceGroup
 ```
 
-The output will resemble the following example:
+The first few lines of the output should contain the following in the `addonProfiles` configuration :
 
 ```output
-provisioningState       : Succeeded
+{
+  "aadProfile": null,
+  "addonProfiles": {
+    "omsagent": {
+      "config": {
+        "logAnalyticsWorkspaceResourceID": "/subscriptions/<WorkspaceSubscription>/resourceGroups/DefaultResourceGroup-EUS2/providers/Microsoft.OperationalInsights/workspaces/DefaultWorkspace-<WorkspaceSubscription>-EUS2",
+        "useAADAuth": "true"
+      },
+      "enabled": true,
+      "identity": null
+    }
+  },
+}
 ```
 
-### Specify a Log Analytics workspace
+### Option 2: Specify a Log Analytics workspace
 
 In this example, you can specify a Log Analytics workspace to enable monitoring of your Azure Linux Container Host cluster. The resource ID of the workspace will be in the form `"/subscriptions/<SubscriptionId>/resourceGroups/<ResourceGroupName>/providers/Microsoft.OperationalInsights/workspaces/<WorkspaceName>"`.
 
@@ -68,8 +80,8 @@ The output should resemble the following example, which indicates that it was de
 
 ```output
 User@aksuser:~$ kubectl get ds ama-logs --namespace=kube-system
-NAME       DESIRED   CURRENT   READY     UP-TO-DATE   AVAILABLE   NODE SELECTOR                 AGE
-ama-logs   2         2         2         2            2           beta.kubernetes.io/os=linux   1d
+NAME       DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR   AGE
+ama-logs   3         3         3       3            3           <none>          3m22s
 ```
 
 To verify deployment of the solution, run the following command:

articles/azure-linux/tutorial-azure-linux-upgrade.md

@@ -1,12 +1,12 @@
 ---
 title: Azure Linux Container Host for AKS tutorial - Upgrade Azure Linux Container Host nodes
 description: In this Azure Linux Container Host for AKS tutorial, you learn how to upgrade Azure Linux Container Host nodes.
-author: htaubenfeld
-ms.author: htaubenfeld
+author: suhuruli
+ms.author: suhuruli
 ms.service: microsoft-linux
 ms.custom: linux-related-content
 ms.topic: tutorial
-ms.date: 05/10/2023
+ms.date: 08/18/2024
 ---
 
 # Tutorial: Upgrade Azure Linux Container Host nodes
@@ -59,9 +59,9 @@ For more information on upgrade channels, see [Using cluster auto-upgrade](/azur
 
 ## Enable automatic package upgrades
 
-Similar to setting your clusters to auto-upgrade, you can use the same set once and forget mechanism for package upgrades by enabling the node-os upgrade channel. If automatic package upgrades are enabled, the dnf-automatic systemd service runs daily and installs any updated packages that have been published.
+Similar to setting your clusters to auto-upgrade, you can use the same set once and forget mechanism for package upgrades by enabling the node-os upgrade channel. If automatic package upgrades are enabled, the `dnf-automatic` systemd service runs daily and installs any updated packages that have been published.
 
-To set the node-os upgrade channel on existing cluster, update the `--node-os-upgrade-channel` parameter, similar to the following example, which automatically enables package upgrades. Note that for some settings of [Node OS Upgrade Channel](/azure/aks/auto-upgrade-node-image), `dnf-automatic` is disabled by default.
+To set the node-os upgrade channel on existing cluster, update the `--node-os-upgrade-channel` parameter, similar to the following example, which automatically enables package upgrades.
 
 ```azurecli-interactive
 az aks update --resource-group testAzureLinuxResourceGroup --name testAzureLinuxCluster --node-os-upgrade-channel Unmanaged