Merge pull request #10096 from MicrosoftDocs/main638451940905780410sync_temp

For protected branch, push strategy should use PR and merge to target branch method to work around git push error

Author: learn-build-service-prod[bot]

.docutune/config/docutune-visualstudio-docs-pr.json

@@ -39,7 +39,7 @@
     "*right-click*",
     "*for-more-information-see*",
     "*had-had*",
-
+    "formatting-accessibility-advanced",
     "formatting-learn-more",
     "*and-then-click*",
     "casing-product-windows-windows",

docs/azure/azure-app-insights-add-connected-service.md

@@ -8,12 +8,13 @@ ms.topic: conceptual
 ms.date: 05/03/2023
 ms.author: angelpe
 ---
+
 # Add Azure Application Insights by using Visual Studio Connected Services
 
 With Visual Studio, you can connect any of the following to Azure Application Insights by using the **Connected Services** feature:
 
 - .NET Framework console app
-- ASP.NET MVC (.NET Framework) 
+- ASP.NET Model-View-Controller (MVC) (.NET Framework)
 - ASP.NET Core
 - .NET Core (including console app, WPF, Windows Forms, class library)
 - .NET Core Worker Role
@@ -49,7 +50,7 @@ The connected service functionality adds all the needed references and connectio
 
     ![Screenshot showing "Add Azure Application Insights" screen.](./media/azure-app-insights-add-connected-service/azure-app-insights.png)
 
-    If you aren't signed in already, sign into your Azure account. If you don't have an Azure account, you can sign up for a [free trial](https://azure.microsoft.com/free/).
+    If you aren't signed in already, sign in to your Azure account. If you don't have an Azure account, you can sign up for a [free trial](https://azure.microsoft.com/free/).
 
 1. In the **Configure Azure Application Insights** screen, select an existing Azure Application Insights component, and select **Next**.
 
@@ -97,9 +98,9 @@ The connected service functionality adds all the needed references and connectio
 
    ![Screenshot showing Application Insights choices.](./media/azure-app-insights-add-connected-service/vs-2022/application-insights-choices-2.png)
 
-   If you choose to use the Application Insights Sdk locally, click **Next** to see the **Summary of changes** screen, which shows how your project is being modified. A NuGet package reference is added to your project and the connection code for the local emulator is added to your project.
+   If you choose to use the Application Insights SDK locally, click **Next** to see the **Summary of changes** screen, which shows how your project is being modified. A NuGet package reference is added to your project and the connection code for the local emulator is added to your project.
 
-   If you want to connect to the Azure service, continue to the next step, or if you aren't signed in already, sign into your Azure account before continuing. If you don't have an Azure account, you can sign up for a [free trial](https://azure.microsoft.com/free/).
+   If you want to connect to the Azure service, continue to the next step, or if you aren't signed in already, sign in to your Azure account before continuing. If you don't have an Azure account, you can sign up for a [free trial](https://azure.microsoft.com/free/).
 
 1. In the **Configure Azure Application Insights** screen, select an existing Azure Application Insights component, and select **Next**.
 

docs/azure/azure-cache-for-redis-add-connected-service.md

@@ -1,6 +1,6 @@
 ---
 title: Add Azure Cache for Redis by using Connected Services
-description: Learn how to add Azure cache for Redis support to your app with the Visual Studio process for adding a connected service.
+description: Learn how to add Azure Cache for Redis support to your app with the Visual Studio process for adding a connected service.
 author: AngelosP
 manager: jmartens
 ms.subservice: azure-development
@@ -9,12 +9,13 @@ ms.date: 05/15/2023
 ms.author: angelpe
 monikerRange: ">= vs-2019"
 ---
+
 # Add Azure Cache for Redis by using Visual Studio Connected Services
 
 With Visual Studio, you can connect any of the following to Azure Cache for Redis by using the **Connected Services** feature:
 
 - .NET Framework console app
-- ASP.NET MVC (.NET Framework) 
+- ASP.NET Model-View-Controller (MVC) (.NET Framework)
 - ASP.NET Core
 - .NET Core (including console app, WPF, Windows Forms, class library)
 - .NET Core Worker Role
@@ -27,6 +28,7 @@ The connected service functionality adds all the needed references and connectio
 
 > [!NOTE]
 > This topic applies to Visual Studio on Windows. For Visual Studio for Mac, see [Connected services in Visual Studio for Mac](/visualstudio/mac/connected-services).
+
 ## Prerequisites
 
 - Visual Studio with the Azure workload installed.
@@ -48,15 +50,15 @@ The connected service functionality adds all the needed references and connectio
 
     ![Screenshot of the Add Dependency page. Azure Cache for Redis is selected.](./media/azure-redis-cache-add-connected-service/azure-redis-cache.png)
 
-    If you aren't signed in already, sign into your Azure account. If you don't have an Azure account, you can sign up for a [free trial](https://azure.microsoft.com/free/).
+    If you aren't signed in already, sign in to your Azure account. If you don't have an Azure account, you can sign up for a [free trial](https://azure.microsoft.com/free/).
 
 1. In the **Configure Azure Cache for Redis** screen, select an existing Azure Cache for Redis, and select **Next**.
 
     If you need to create a new component, go to the next step. Otherwise, skip to step 7.
 
     ![Screenshot of the Configure Azure Cache for Redis screen. Next is highlighted.](./media/azure-redis-cache-add-connected-service/created-azure-redis-cache.png)
 
-1. To create an Azure Redis Cache:
+1. To create an Azure Cache for Redis:
 
    1. Select **Create a new Azure Redis Cache** at the bottom of the screen.
 
@@ -92,29 +94,29 @@ The connected service functionality adds all the needed references and connectio
 
 1. Choose **Azure Cache for Redis**. The **Connect to dependency** page appears. You should see two options, one for a local emulator, **Redis Cache on container (Local)**, and one for connecting to the live Azure Cache for Redis service. You can reduce cost and simplify early development by starting with the local emulator. You can migrate to the live service later by repeating these steps and choosing the other option.
 
-   ![Screenshot showing Redis cache choices](./media/azure-redis-cache-add-connected-service/vs-2022/azure-cache-for-redis-add-dependency-2.png)
+   ![Screenshot showing Azure Cache for Redis choices](./media/azure-redis-cache-add-connected-service/vs-2022/azure-cache-for-redis-add-dependency-2.png)
 
-   If you choose the Redis cache locally, click **Next** to the **Connect to Redis cache on container** screen.
+   If you choose the Azure Cache for Redis locally, click **Next** to the **Connect to Redis cache on container** screen.
 
-   ![Screenshot showing connection options for Redis cache in a local container.](./media/azure-redis-cache-add-connected-service/vs-2022/connect-to-redis-cache-on-container.png)
+   ![Screenshot showing connection options for Azure Cache for Redis in a local container.](./media/azure-redis-cache-add-connected-service/vs-2022/connect-to-redis-cache-on-container.png)
 
    Specify **Container name**, **Container image**, and port mappings or accept the defaults, and click **Next** to see the **Summary of changes** screen, which shows what changes would be made to your project. A NuGet package reference is added to your project and the connection code for the local emulator is added to your project.
 
-   If you want to connect to the Azure service, continue to the next step, or if you aren't signed in already, sign into your Azure account before continuing. If you don't have an Azure account, you can sign up for a [free trial](https://azure.microsoft.com/free/).
+   If you want to connect to the Azure service, continue to the next step, or if you aren't signed in already, sign in to your Azure account before continuing. If you don't have an Azure account, you can sign up for a [free trial](https://azure.microsoft.com/free/).
 
 1. To go with the live service, select **Azure Cache for Redis**.
 
     ![Screenshot of the Add Dependency page. Azure Cache for Redis is selected.](./media/azure-redis-cache-add-connected-service/azure-redis-cache.png)
 
-    If you aren't signed in already, sign into your Azure account. If you don't have an Azure account, you can sign up for a [free trial](https://azure.microsoft.com/free/).
+    If you aren't signed in already, sign in to your Azure account. If you don't have an Azure account, you can sign up for a [free trial](https://azure.microsoft.com/free/).
 
 1. In the **Configure Azure Cache for Redis** screen, select an existing Azure Cache for Redis, and select **Next**.
 
     If you need to create a new component, go to the next step. Otherwise, skip to step 7.
 
     ![Screenshot of the Configure Azure Cache for Redis screen. Next is highlighted.](./media/azure-redis-cache-add-connected-service/created-azure-redis-cache.png)
 
-1. To create an Azure Redis Cache:
+1. To create an Azure Cache for Redis:
 
    1. Select **Create a new Azure Redis Cache** at the bottom of the screen.
 
@@ -142,7 +144,7 @@ The connected service functionality adds all the needed references and connectio
 
 ## Next steps
 
-For ASP.NET apps, common use cases for Azure cache for Redis are to cache session state or page output (HTTP responses). ASP.NET Core provides built-in services for these use cases, which should be used instead when you're using ASP.NET Core.
+For ASP.NET apps, common use cases for Azure Cache for Redis are to cache session state or page output (HTTP responses). ASP.NET Core provides built-in services for these use cases, which should be used instead when you're using ASP.NET Core.
 
 To cache session state in an ASP.NET app, see [ASP.NET Session State Provider](/azure/azure-cache-for-redis/cache-aspnet-session-state-provider).
 

docs/azure/azure-cosmosdb-add-connected-service.md

@@ -9,12 +9,13 @@ ms.date: 02/15/2024
 ms.author: ghogen
 monikerRange: ">= vs-2019"
 ---
+
 # Add Azure Cosmos DB to your app by using Visual Studio Connected Services
 
 With Visual Studio, you can connect any of the following to Azure Cosmos DB by using the **Connected Services** feature:
 
 - .NET Framework console app
-- ASP.NET MVC (.NET Framework) 
+- ASP.NET Model-View-Controller (MVC) (.NET Framework)
 - ASP.NET Core
 - .NET Core (including console app, WPF, Windows Forms, class library)
 - .NET Core Worker Role
@@ -27,13 +28,15 @@ The connected service functionality adds all the needed references and connectio
 
 > [!NOTE]
 > This topic applies to Visual Studio on Windows. For Visual Studio for Mac, see [Connected services in Visual Studio for Mac](/visualstudio/mac/connected-services).
+
 ## Prerequisites
 
 - Visual Studio with the Azure workload installed.
 - A project of one of the supported types
 - [!INCLUDE [prerequisites-azure-subscription](includes/prerequisites-azure-subscription.md)]
 
 ## Connect to Azure Cosmos DB using Connected Services
+
 :::moniker range="vs-2019"
 1. Open your project in Visual Studio.
 
@@ -47,7 +50,7 @@ The connected service functionality adds all the needed references and connectio
 
     ![Screenshot showing "Add Dependency" screen, selecting the "Add Azure Cosmos DB" option.](./media/azure-cosmosdb-add-connected-service/azure-cosmos-db.png)
 
-    If you aren't signed in already, sign into your Azure account. If you don't have an Azure account, you can sign up for a [free trial](https://azure.microsoft.com/free/).
+    If you aren't signed in already, sign in to your Azure account. If you don't have an Azure account, you can sign up for a [free trial](https://azure.microsoft.com/free/).
 
 1. In the **Azure Cosmos DB** screen, select an existing Azure Cosmos DB, and select **Next**.
 
@@ -95,7 +98,7 @@ The connected service functionality adds all the needed references and connectio
 
    If you choose to use the Azure Cosmos DB Emulator, click **Next** to see the **Summary of changes** screen, which shows how your project is being modified. A NuGet package reference is added to your project and the connection code for the local emulator is added to your project. Once you click **Finish** on the last screen, the container for the emulator is created; you'll see the image download status in the output window.
 
-   If you want to connect to the Azure service, continue to the next step, or if you aren't signed in already, sign into your Azure account before continuing. If you don't have an Azure account, you can sign up for a [free trial](https://azure.microsoft.com/free/).
+   If you want to connect to the Azure service, continue to the next step, or if you aren't signed in already, sign in to your Azure account before continuing. If you don't have an Azure account, you can sign up for a [free trial](https://azure.microsoft.com/free/).
 
 1. In the **Azure Cosmos DB** screen, select an existing Azure Cosmos DB, and select **Next**.
 
@@ -129,7 +132,7 @@ The connected service functionality adds all the needed references and connectio
 
    If you click on the three dots next to the dependency you added, you can see various options such as **Connect** to reopen the wizard and change the connection. You can also click the three dots at the top right of the window to see options to start local dependencies, change settings, and more.
 
-1. By default, the memory limit in the container is set to 2G, but normally, more memory is required to run CosmosDB. To fix this, navigate to the `.vs/sd/<GUID>/local` folder under your solution folder. In Windows Explorer, you might have to enable hidden files to see the `.vs` folder. Find and open the file *cosmosdb1.docker-compose.yml*. Set a 4G or higher memory limit.
+1. By default, the memory limit in the container is set to 2G, but normally, more memory is required to run Azure Cosmos DB. To fix this, navigate to the `.vs/sd/<GUID>/local` folder under your solution folder. In Windows Explorer, you might have to enable hidden files to see the `.vs` folder. Find and open the file *cosmosdb1.docker-compose.yml*. Set a 4G or higher memory limit.
 
    ```yml
    mem_limit = 4G
@@ -140,7 +143,7 @@ The connected service functionality adds all the needed references and connectio
 :::moniker-end
 
 > [!NOTE]
-> The local emulator for CosmosDB might reference a base image that uses a temporary license for Azure CosmosDB. If the container doesn't start, check the **Logs** tab in the **Containers*** window for the Cosmos DB container. If it mentions a PAL expiration issue, you need to get the latest base image for the local container. Run the following command from the console prompt: `docker pull mcr.microsoft.com/cosmosdb/linux/azure-cosmos-emulator:latest`. The license is periodically updated, and when it expires, refreshing to the newest container should solve the issue. You can view and report issues for the Azure CosmosDB emulator at the [Azure CosmosDB emulator GitHub repo](https://github.com/Azure/azure-cosmos-db-emulator-docker/issues).
+> The local emulator for Azure Cosmos DB might reference a base image that uses a temporary license for Azure Cosmos DB. If the container doesn't start, check the **Logs** tab in the **Containers*** window for the Azure Cosmos DB container. If it mentions a PAL expiration issue, you need to get the latest base image for the local container. Run the following command from the console prompt: `docker pull mcr.microsoft.com/cosmosdb/linux/azure-cosmos-emulator:latest`. The license is periodically updated, and when it expires, refreshing to the newest container should solve the issue. You can view and report issues for the Azure Cosmos DB emulator at the [Azure Cosmos DB emulator GitHub repo](https://github.com/Azure/azure-cosmos-db-emulator-docker/issues).
 
 ## Next steps
 
@@ -153,7 +156,7 @@ using CosmosClient client = new(
 );
 ```
 
-The `CosmosClient` provides access to Cosmos DB functionality through its various methods. Once you have an instance of `CosmosClient`, you can create a NoSQL database by following this guide: [Create a database in Azure Cosmos DB for NoSQL using .NET](/azure/cosmos-db/nosql/how-to-dotnet-create-database).
+The `CosmosClient` provides access to Azure Cosmos DB functionality through its various methods. Once you have an instance of `CosmosClient`, you can create a NoSQL database by following this guide: [Create a database in Azure Cosmos DB for NoSQL using .NET](/azure/cosmos-db/nosql/how-to-dotnet-create-database).
 
 ## Related content