Merge pull request #267405 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)

Author: Taojunshen

articles/azure-monitor/containers/container-insights-troubleshoot.md

@@ -41,41 +41,41 @@ To diagnose the problem if you can't view status information or no results are r
 
     `kubectl get ds ama-logs --namespace=kube-system`
 
-    The output should resemble the following example, which indicates that it was deployed properly:
+    The number of pods should be equal to the number of Linux nodes on the cluster. The output should resemble the following example, which indicates that it was deployed properly:
 
     ```
     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   2         2         2         2            2           <none>           1d
     ```
 
 1. If you have Windows Server nodes, check the status of the agent by running the following command:
 
-    `kubectl get ds omsagent-win --namespace=kube-system`
+    `kubectl get ds ama-logs-windows --namespace=kube-system`
 
-    The output should resemble the following example, which indicates that it was deployed properly:
+    The number of pods should be equal to the number of Windows nodes on the cluster. The output should resemble the following example, which indicates that it was deployed properly:
 
     ```
     User@aksuser:~$ kubectl get ds ama-logs-windows --namespace=kube-system
-    NAME                   DESIRED   CURRENT   READY     UP-TO-DATE   AVAILABLE   NODE SELECTOR                   AGE
-    ama-logs-windows           2         2         2         2            2           beta.kubernetes.io/os=windows   1d
+    NAME                   DESIRED   CURRENT   READY     UP-TO-DATE   AVAILABLE   NODE SELECTOR    AGE
+    ama-logs-windows           2         2         2         2            2           <none>       1d
     ```
 
-1. Check the deployment status with agent version **06072018** or later by using the following command:
+1. Check the deployment status by using the following command:
 
-    `kubectl get deployment ama-logs-rs -n=kube-system`
+    `kubectl get deployment ama-logs-rs --namespace=kube-system`
 
     The output should resemble the following example, which indicates that it was deployed properly:
 
     ```
-    User@aksuser:~$ kubectl get deployment omsagent-rs -n=kube-system
-    NAME       DESIRED   CURRENT   UP-TO-DATE   AVAILABLE    AGE
-    ama-logs   1         1         1            1            3h
+    User@aksuser:~$ kubectl get deployment ama-logs-rs --namespace=kube-system
+    NAME          READY   UP-TO-DATE   AVAILABLE   AGE
+    ama-logs-rs   1/1     1            1           24d
     ```
 
 1. Check the status of the pod to verify that it's running by using the command `kubectl get pods --namespace=kube-system`.
 
-    The output should resemble the following example with a status of `Running` for the omsagent:
+    The output should resemble the following example with a status of `Running` for ama-logs:
 
     ```
     User@aksuser:~$ kubectl get pods --namespace=kube-system
@@ -85,7 +85,7 @@ To diagnose the problem if you can't view status information or no results are r
     azure-vote-front-3826909965-30n62   1/1       Running   0          22d
     ama-logs-484hw                      1/1       Running   0          1d
     ama-logs-fkq7g                      1/1       Running   0          1d
-    ama-logs-windows-6drwq                  1/1       Running   0          1d
+    ama-logs-windows-6drwq              1/1       Running   0          1d
     ```
 
 1. If the pods are in a running state, but there is no data in Log Analytics or data appears to only send during a certain part of the day, it might be an indication that the daily cap has been met. When this limit is met each day, data stops ingesting into the Log Analytics Workspace and resets at the reset time. For more information, see [Log Analytics Daily Cap](../../azure-monitor/logs/daily-cap.md#determine-your-daily-cap).

articles/azure-monitor/containers/kubernetes-monitoring-enable.md

@@ -693,37 +693,37 @@ The number of pods should be equal to the number of Linux nodes on the cluster.
 
 ```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   2         2         2         2            2           <none>          1d
 ```
 
 **Verify that Windows nodes were deployed properly**
 
 ```
-kubectl get ds ama-metrics-win-node --namespace=kube-system
+kubectl get ds ama-logs-windows --namespace=kube-system
 ```
 
 The number of pods should be equal to the number of Windows nodes on the cluster. The output should resemble the following example:
 
 ```output
 User@aksuser:~$ kubectl get ds ama-logs-windows --namespace=kube-system
-NAME                   DESIRED   CURRENT   READY     UP-TO-DATE   AVAILABLE   NODE SELECTOR                   AGE
-ama-logs-windows           2         2         2         2            2           beta.kubernetes.io/os=windows   1d
+NAME                   DESIRED   CURRENT   READY     UP-TO-DATE   AVAILABLE   NODE SELECTOR     AGE
+ama-logs-windows           2         2         2         2            2       <none>            1d
 ```
 
 
 **Verify deployment of the Container insights solution**
 
 ```
-kubectl get deployment ama-logs-rs -n=kube-system
+kubectl get deployment ama-logs-rs --namespace=kube-system
 ```
 
 The output should resemble the following example:
 
 ```output
-User@aksuser:~$ kubectl get deployment ama-logs-rs -n=kube-system
-NAME       DESIRED   CURRENT   UP-TO-DATE   AVAILABLE    AGE
-ama-logs-rs   1         1         1            1            3h
+User@aksuser:~$ kubectl get deployment ama-logs-rs --namespace=kube-system
+NAME          READY   UP-TO-DATE   AVAILABLE   AGE
+ama-logs-rs   1/1     1            1           24d
 ```
 
 **View configuration with CLI**

articles/azure-vmware/protect-azure-vmware-solution-with-application-gateway.md

@@ -28,7 +28,7 @@ The diagram shows how Application Gateway is used to protect Azure IaaS virtual
 :::image type="content" source="media/application-gateway/app-gateway-protects.png" alt-text="Diagram showing how Application Gateway protects Azure IaaS virtual machines (VMs), Azure Virtual Machine Scale Sets, or on-premises servers."lightbox="media/application-gateway/app-gateway-protects.png" border="false":::
 
 > [!IMPORTANT]
-> Azure Application Gateway is currently the only supported method to expose web apps running on Azure VMware Solution VMs.
+> Azure Application Gateway is the preferred method to expose web apps running on Azure VMware Solution VMs.
 
 The diagram shows the testing scenario used to validate the Application Gateway with Azure VMware Solution web applications.
 

articles/iot-operations/manage-layered-network/howto-deploy-aks-layered-network.md

@@ -54,7 +54,7 @@ These steps deploy Layered Network Management to the AKS cluster. The cluster is
     You should see an output that looks like the following example:
 
     ```Output
-    NAME                                    READY   STATUS        RESTARTS   AGE
+    NAME                                READY   STATUS        RESTARTS   AGE
     aio-lnm-operator-7db49dc9fd-kjf5x   1/1     Running       0          78s
     ```
 
@@ -137,9 +137,9 @@ These steps deploy Layered Network Management to the AKS cluster. The cluster is
     The output should look like:
 
     ```Output
-    NAME                                    READY       STATUS    RESTARTS   AGE
-    aio-lnm-operator-7db49dc9fd-kjf5x   1/1     Running       0          78s
-    lnm-level4-7598574bf-2lgss          1/1     Running       0          4s
+    NAME                                    READY       STATUS    RESTARTS       AGE
+    aio-lnm-operator-7db49dc9fd-kjf5x       1/1         Running       0          78s
+    aio-lnm-level4-7598574bf-2lgss          1/1         Running       0          4s
     ```
 
 1. To view the service, run:
@@ -151,8 +151,8 @@ These steps deploy Layered Network Management to the AKS cluster. The cluster is
     The output should look like the following example:
 
     ```Output
-    NAME          TYPE           CLUSTER-IP     EXTERNAL-IP     PORT(S)                      AGE
-    lnm-level4   LoadBalancer   10.0.141.101   20.81.111.118   80:30960/TCP,443:31214/TCP   29s
+    NAME              TYPE           CLUSTER-IP     EXTERNAL-IP     PORT(S)                      AGE
+    aio-lnm-level4    LoadBalancer   10.0.141.101   20.81.111.118   80:30960/TCP,443:31214/TCP   29s
     ```
 1. To view the config maps, run:
 

articles/postgresql/flexible-server/generative-ai-azure-cognitive.md

@@ -1,9 +1,9 @@
 ---
-title: Integrate with Azure Cognitive Services Preview
-description: Integrate Azure Database for PostgreSQL - Flexible Server with Azure Cognitive Services - Preview.
+title: Integrate Azure AI Language Services with Azure Database for PostgreSQL
+description: Implement scenarios like sentiment analysis with Cognitive Services and Azure Database for PostgreSQL.
 author: mulander
 ms.author: adamwolk
-ms.date: 12/12/2023
+ms.date: 2/26/2024
 ms.service: postgresql
 ms.subservice: flexible-server
 ms.custom: