Merge branch 'MicrosoftDocs:main' into 240611-update-output-arc-data

Author: MikeRayMSFT

articles/aks/azure-nfs-volume.md

@@ -1,13 +1,13 @@
 ---
 title: Manually create a Linux NFS Server persistent volume for Azure Kubernetes Service
 titleSuffix: Azure Kubernetes Service
-description: Learn how to manually create an Ubuntu Linux NFS Server persistent volume for use with pods in Azure Kubernetes Service (AKS)
-author: ozboms
+description: Learn how to manually create an Ubuntu Linux NFS Server persistent volume for use with pods in Azure Kubernetes Service (AKS).
+author: tamram
 ms.topic: article
 ms.date: 01/24/2024
 ms.subservice: aks-storage
 ms.custom: linux-related-content
-ms.author: obboms
+ms.author: tamram
 ---
 
 # Manually create and use a Linux NFS (Network File System) Server with Azure Kubernetes Service (AKS)

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

@@ -13,6 +13,9 @@ Container Insights defaults to managed identity authentication, which has a moni
 
 This article describes how to migrate to managed identity authentication if you enabled Container insights using legacy authentication method and also how to enable legacy authentication if you have that requirement.
 
+> [!IMPORTANT]
+> If you have a cluster with legacy authentication and Log Analytics workspace keys are rotated, then monitoring data will stop flowing to the Log Analytics workspace. You must disable and then reenable the Container insights addon to get monitoring data to start flowing again with the new rotated workspace keys.  You should migrate to Container insights managed identity authentication which doesn't use Log Analytics workspace keys.
+
 ## Migrate to managed identity authentication
 
 If you enabled Container insights before managed identity authentication was available, you can use the following methods to migrate your clusters.

articles/cosmos-db/mongodb/vcore/how-to-connect-mongo-shell.md

@@ -1,75 +1,75 @@
 ---
-title: Use Mongo Shell to connect
-titleSuffix: Azure Cosmos DB for MongoDB vCore
-description: Connect to an Azure Cosmos DB for MongoDB vCore account using Mongo Shell community tool to query data.
+title: Use MongoDB Shell to connect
+titleSuffix: Azure Cosmos DB for MongoDB in vCore architecture
+description: Connect to an Azure Cosmos DB for MongoDB (vCore architecture) account by using the MongoDB Shell community tool to query data.
 author: kruti-m
 ms.author: krmeht
 ms.reviewer: yongl
 ms.service: cosmos-db
 ms.subservice: mongodb-vcore
 ms.topic: how-to
 ms.date: 02/05/2024
-# CustomerIntent: As a database owner, I want to use Mongo Shell to connect and query my database & collections.
+# customer intent: As a database owner, I want to use Mongo Shell to connect to and query my database and collections.
 ---
 
-# Use MongoDB Shell (Mongosh) to connect to Azure Cosmos DB for MongoDB vCore
+# Use MongoDB Shell to connect to Azure Cosmos DB for MongoDB (vCore)
 
 [!INCLUDE[MongoDB vCore](~/reusable-content/ce-skilling/azure/includes/cosmos-db/includes/appliesto-mongodb-vcore.md)]
 
-MongoDB Shell (Mongosh), is a JavaScript and Node.js environment for interacting with MongoDB deployments. It's a popular community tool to test queries and interact with the data in your Azure Cosmos DB for MongoDB database.
+MongoDB Shell (`mongosh`) is a JavaScript and Node.js environment for interacting with MongoDB deployments. It's a popular community tool to test queries and interact with the data in your Azure Cosmos DB for MongoDB database.
 
 ## Prerequisites
-Here are some prerequisites. 
-- An existing Azure Cosmos DB for MongoDB vCore cluster.
-- An installed version of the MongoShell from the community site.
-- Ensure you're setting up the necessary environment variables post installation for your operating system
-- Ensure the firewall settings to allow the machine to connect. Follow the guidelines for [configuring the firewall for Azure Cosmos DB](../../../cosmos-db/how-to-configure-firewall.md)
-    - You can choose to allow requests from your current IP, requests from cloud services or requests from virtual machines - specific IP Ranges
-    
-![Illustration that shows Firewall Settings update for MongoDB Vcore.](media/how-to-connect-mongo-shell/firewall-settings.gif)
 
-If you accidentally open all the ports, you're warned before saving the changes.
+- An existing Azure Cosmos DB for MongoDB (vCore architecture) cluster.
+- An installed version of MongoDB Shell from the community site.
+- Setup of the necessary post-installation environment variables for your operating system.
+- Firewall settings that allow the machine to connect. Follow the guidelines for [configuring the firewall for Azure Cosmos DB](../../../cosmos-db/how-to-configure-firewall.md).
+  
+  You can choose to allow requests from your current IP address, requests from cloud services, or requests from virtual machines (specific IP ranges).
 
-## Connect using Mongo Shell (Mongosh)
+  ![Animation that shows an update of firewall settings for Azure Cosmos DB for MongoDB in the vCore architecture.](media/how-to-connect-mongo-shell/firewall-settings.gif)
 
-To add your Azure Cosmos DB cluster to Mongo shell, perform the following steps:
-1. Retrieve the connection information for your Azure Cosmos DB for MongoDB vCore using the instructions [here](quickstart-portal.md#get-cluster-credentials).
+  If you accidentally open all the ports, you're warned before you save the changes.
 
-![Illustration that shows getting connection string.](./media/how-to-connect-mongo-shell/get-connection-string-portal.gif)
-Once you have the connection string, you can either 
-- Have the shell prompt you to enter the password or
-- Provide the password as a part of the connection string 
+## Connect by using MongoDB Shell
 
-2. Connect using Mongo Shell
+To add your Azure Cosmos DB cluster to MongoDB Shell, perform the following steps:
 
-**A. By entering the password in the MongoShell Prompt**
+1. Retrieve the connection information for your Azure Cosmos DB for MongoDB (vCore) instance by using [these instructions](quickstart-portal.md#get-cluster-credentials).
 
+   ![Animation that shows selections for getting a connection string.](./media/how-to-connect-mongo-shell/get-connection-string-portal.gif)
 
-Your connection string would look like this:
-    ```
-    "mongodb+srv://<username>@<servername>.mongocluster.cosmos.azure.com/?tls=true&authMechanism=SCRAM-SHA-256&retrywrites=false&maxIdleTimeMS=120000"
-    ```
-Here's an example of how the command looks like: 
-    ```
-    mongosh "mongodb+srv://[email protected]/?tls=true&authMechanism=SCRAM-SHA-256&retrywrites=false&maxIdleTimeMS=120000
-    ```
-![Illustration that shows how to connect by entering a password.](./media/how-to-connect-mongo-shell/mongo-shell-connect.gif)
+2. Connect by using either of these methods:
 
-Once you provide the password and are successfully authenticated, you notice some warning. It states *"This server or service appears to be an emulation of MongoDB"*. 
-The warning can be ignored. It's the shell's way of notifying that you aren't connection to an emulation of MongoDB. When, it's an Azure as a platform as a service offering it's expected. 
+   - Enter the password in the Mongo Shell prompt. Your connection string looks like this example:
 
-**B. By providing the password as a part of the connection string**
+     ```
+     "mongodb+srv://<username>@<servername>.mongocluster.cosmos.azure.com/?tls=true&authMechanism=SCRAM-SHA-256&retrywrites=false&maxIdleTimeMS=120000"
+     ```
 
-Alternately you can also use a connection string with the password in which case the format looks something like this.
-```
-mongosh "mongodb+srv://<SERVERNAME>.mongocluster.cosmos.azure.com/?tls=true&authMechanism=SCRAM-SHA-256&retrywrites=false&maxIdleTimeMS=120000" --username "<USER>" -password "<PASSWORD>"
-```
+     The command looks like this example:
 
-Here's an example of how the command looks like: 
-```
- mongosh "mongodb+srv://mongodbvcoretesting.mongocluster.cosmos.azure.com/?tls=true&authMechanism=SCRAM-SHA-256&retrywrites=false&maxIdleTimeMS=120000" --username "testuser" -password "******"
-```
-![Screenshot that shows a password as a part of a connection string.](./media/how-to-connect-mongo-shell/connection-string-with-password.png)
+     ```
+     mongosh "mongodb+srv://[email protected]/?tls=true&authMechanism=SCRAM-SHA-256&retrywrites=false&maxIdleTimeMS=120000
+     ```
+
+     ![Animation that shows how to connect by entering a password.](./media/how-to-connect-mongo-shell/mongo-shell-connect.gif)
+
+     After you provide the password and are successfully authenticated, this warning appears: "This server or service appears to be an emulation of MongoDB." You can ignore it. This warning is generated because the connection string contains `cosmos.azure`. Azure Cosmos DB is a native Azure platform as a service (PaaS) offering.
+
+   - Provide the password as a part of the connection string. The format looks something like this example:
+
+     ```
+     mongosh "mongodb+srv://<SERVERNAME>.mongocluster.cosmos.azure.com/?tls=true&authMechanism=SCRAM-SHA-256&retrywrites=false&maxIdleTimeMS=120000" --username "<USER>" -password "<PASSWORD>"
+     ```
+
+     The command looks like this example:
+
+     ```
+     mongosh "mongodb+srv://mongodbvcoretesting.mongocluster.cosmos.azure.com/?tls=true&authMechanism=SCRAM-SHA-256&retrywrites=false&maxIdleTimeMS=120000" --username "testuser" -password "******"
+     ```
+
+     ![Screenshot that shows a password as a part of a connection string.](./media/how-to-connect-mongo-shell/connection-string-with-password.png)
 
 ## Next step
 

articles/cosmos-db/mongodb/vcore/how-to-connect-studio-3t.md

@@ -1,55 +1,55 @@
 ---
 title: Use Studio 3T to connect
-titleSuffix: Azure Cosmos DB for MongoDB vCore
-description: Connect to an Azure Cosmos DB for MongoDB vCore account using the Studio 3T community tool to query data.
+titleSuffix: Azure Cosmos DB for MongoDB in vCore architecture
+description: Connect to an Azure Cosmos DB for MongoDB (vCore architecture) account by using the Studio 3T community tool to query data.
 author: gahl-levy
 ms.author: gahllevy
 ms.reviewer: sidandrews
 ms.service: cosmos-db
 ms.subservice: mongodb-vcore
 ms.topic: how-to
 ms.date: 08/28/2023
-# CustomerIntent: As a database owner, I want to use Studio 3T so that I can connect to and query my collections.
+# customer intent: As a database owner, I want to use Studio 3T so that I can connect to and query my collections.
 ---
 
-# Use Studio 3T to connect to Azure Cosmos DB for MongoDB vCore
+# Use Studio 3T to connect to Azure Cosmos DB for MongoDB (vCore)
 
 [!INCLUDE[MongoDB vCore](~/reusable-content/ce-skilling/azure/includes/cosmos-db/includes/appliesto-mongodb-vcore.md)]
 
-Studio 3T (also known as Robomongo or Robo 3T) is a professional GUI that offers IDE & client tools for MongoDB. It's a popular community tool to speed up MongoDB development with a straightforward user interface.
+Studio 3T is a professional GUI that offers IDE and client tools for MongoDB. It's a popular community tool to speed up MongoDB development with a straightforward user interface.
 
 ## Prerequisites
 
-- An existing Azure Cosmos DB for MongoDB vCore cluster.
+- An existing Azure Cosmos DB for MongoDB (vCore architecture) cluster.
   - If you don't have an Azure subscription, [create an account for free](https://azure.microsoft.com/free).
-  - If you have an existing Azure subscription, [create a new Azure Cosmos DB for MongoDB vCore cluster](quickstart-portal.md).
-- [Studio 3T](https://robomongo.org/) community tool
+  - If you have an existing Azure subscription, [create a new Azure Cosmos DB for MongoDB (vCore) cluster](quickstart-portal.md).
+- The [Studio 3T](https://robomongo.org/) community tool.
 
-## Connect using Studio 3T
+## Connect by using Studio 3T
 
-To add your Azure Cosmos DB cluster to the Studio 3T connection manager, perform the following steps:
+To add your Azure Cosmos DB cluster to the Studio 3T Connection Manager, perform the following steps:
 
-1. Retrieve the connection information for your Azure Cosmos DB for MongoDB vCore using the instructions [here](quickstart-portal.md#get-cluster-credentials).
+1. Retrieve the connection information for your Azure Cosmos DB for MongoDB (vCore) instance by using [these instructions](quickstart-portal.md#get-cluster-credentials).
 
-    :::image type="content" source="./media/connect-using-robomongo/connection-string.png" alt-text="Screenshot of the connection string page.":::
+    :::image type="content" source="./media/connect-using-robomongo/connection-string.png" alt-text="Screenshot of the pane for connection strings.":::
 
 1. Run the **Studio 3T** application.
 
-1. Select the connection button under **File** to manage your connections. Then, select **New Connection** in the **Connection Manager** window, which opens another window where you can paste the connection credentials.
+1. Under **File**, select the **Connect** button to manage your connections. Then, in the **Connection Manager** dialog, select **New Connection**.
 
-1. In the connection credentials window, choose the first option and paste your connection string. Select **Next** to move forward.
+1. In the **New Connection** dialog, select the first option and paste your connection string. Then select **Next**.
 
-    :::image type="content" source="./media/connect-using-robomongo/new-connection.png" alt-text="Screenshot of the Studio 3T connection credentials window.":::
+    :::image type="content" source="./media/connect-using-robomongo/new-connection.png" alt-text="Screenshot of the dialog for entering  connection credentials in Studio 3T.":::
 
-1. Choose a **Connection name** and double check your connection credentials.
+1. On the **Server** tab, enter a name for **Connection name** and double-check your connection credentials.
 
-    :::image type="content" source="./media/connect-using-robomongo/connection-configuration.png" alt-text="Screenshot of the Studio 3T connection details window.":::
+    :::image type="content" source="./media/connect-using-robomongo/connection-configuration.png" alt-text="Screenshot of server connection information in Studio 3T for a new connection.":::
 
-1. On the **SSL** tab, check **Use SSL protocol to connect**.
+1. On the **SSL** tab, select **Use SSL protocol to connect**.
 
-    :::image type="content" source="./media/connect-using-robomongo/connection-ssl.png" alt-text="Screenshot of the Studio 3T new connection TLS/SSL Tab.":::
+    :::image type="content" source="./media/connect-using-robomongo/connection-ssl.png" alt-text="Screenshot of SSL details in Studio 3T for a new connection.":::
 
-1. Finally, select **Test Connection** in the bottom left to verify that you're able to connect, then select **Save**.
+1. Select **Test Connection** to verify that you can connect, and then select **Save**.
 
 ## Next step