Merge branch 'main' of https://github.com/microsoftdocs/azure-docs-pr into akv-md2

msmbaldwin · msmbaldwin · commit bf829ac5edb3 · 2024-02-20T14:57:48.000-08:00
diff --git a/articles/azure-vmware/remove-arc-enabled-azure-vmware-solution-vsphere-resources-from-azure.md b/articles/azure-vmware/remove-arc-enabled-azure-vmware-solution-vsphere-resources-from-azure.md
@@ -108,6 +108,6 @@ During onboarding, to create a connection between your VMware vCenter and Azure,
 
 As a last step, run the following command: 
 
-[`az rest --method delete --url`](https://management.azure.com/subscriptions/%3csubscrption-id%3e/resourcegroups/%3cresource-group-name%3e/providers/Microsoft.AVS/privateClouds/%3cprivate-cloud-name%3e/addons/arc?api-version=2022-05-01%22)
+`az rest --method delete --url` [URL](https://management.azure.com/subscriptions/%3csubscrption-id%3e/resourcegroups/%3cresource-group-name%3e/providers/Microsoft.AVS/privateClouds/%3cprivate-cloud-name%3e/addons/arc?api-version=2022-05-01%22)
 
 Once that step is done, Arc no longer works on the Azure VMware Solution private cloud. When you delete Arc resources from vCenter Server, it doesn't affect the Azure VMware Solution private cloud for the customer. 
diff --git a/articles/cosmos-db/cassandra/index.yml b/articles/cosmos-db/cassandra/index.yml
@@ -12,7 +12,7 @@ metadata:
   ms.service: cosmos-db
   ms.subservice: apache-cassandra
   ms.topic: landing-page
-  ms.date: 02/28/2023
+  ms.date: 02/21/2024
 landingContent:
   - title: About API for Cassandra
     linkLists:
@@ -82,5 +82,5 @@ landingContent:
         links:
           - text: Migrate from PostgreSQL using Apache Kafka
             url: postgres-migrate-cosmos-db-kafka.md
-          - text: Migrate from Oracle DB to API for Striim
+          - text: Migrate from Oracle Database to API for Striim
             url: migrate-data-striim.md
diff --git a/articles/cosmos-db/gremlin/index.yml b/articles/cosmos-db/gremlin/index.yml
@@ -12,16 +12,15 @@ metadata:
   ms.service: cosmos-db
   ms.subservice: apache-gremlin
   ms.topic: landing-page
-
-  ms.date: 02/28/2023
+  ms.date: 02/21/2024
 landingContent:
   - title: About API for Gremlin
     linkLists:
       - linkListType: overview
         links:
           - text: What is Azure Cosmos DB for Gremlin?
             url: introduction.md
-          - text: Wire protocol compatibility with Tinkerpop
+          - text: Wire protocol compatibility with TinkerPop
             url: support.md
           - text: FAQ
             url: gremlin-api-faq.yml
@@ -35,7 +34,7 @@ landingContent:
     linkLists:
       - linkListType: quickstart
         links:
-          - text: Manage your data using using Gremlin Console
+          - text: Manage your data using Gremlin Console
             url: quickstart-console.md
           - text: Manage your data using a .NET app
             url: quickstart-dotnet.md
@@ -63,9 +62,9 @@ landingContent:
     linkLists:
       - linkListType: how-to-guide
         links:
-          - text: Third-party data visualization tools
+          - text: Non-Microsoft data visualization tools
             url: visualization-partners.md
-          - text: Third-party data modeling tools
+          - text: Non-Microsoft data modeling tools
             url: modeling-tools.md
       - linkListType: sample
         links:
diff --git a/articles/cosmos-db/index.yml b/articles/cosmos-db/index.yml
@@ -12,8 +12,7 @@ metadata:
   ms.reviewer: mjbrown
   ms.service: cosmos-db
   ms.topic: landing-page
-
-  ms.date: 02/28/2023
+  ms.date: 02/21/2024
 highlightedContent:
   items:
     - title: Introduction to Azure Cosmos DB
@@ -25,7 +24,7 @@ highlightedContent:
     - title: Distributed NoSQL databases
       itemType: concept
       url: distributed-nosql.md
-    - title: Q&A
+    - title: Microsoft Questions and Answers
       itemType: reference
       url: /answers/tags/187/azure-cosmos-db
     - title: Vector Search with Azure Cosmos DB
@@ -49,8 +48,6 @@ additionalContent:
           links:
             - text: SQL queries
               url: nosql/query/getting-started.md
-            - text: Stored procedures, triggers, UDFs
-              url: nosql/how-to-write-stored-procedures-triggers-udfs.md
             - text: Model document data
               url: nosql/modeling-data.md
             - text: See more >
@@ -125,11 +122,11 @@ additionalContent:
               url: concepts-limits.md
         - title: Analytics with Azure Synapse Link
           links:
-            - text: Synapse Link for Azure Cosmos DB
+            - text: Azure Synapse Link for Azure Cosmos DB
               url: synapse-link.md
             - text: Azure Cosmos DB Analytical Store
               url: analytical-store-introduction.md
-            - text: Synapse Link use cases
+            - text: Azure Synapse Link use cases
               url: synapse-link-use-cases.md
             - text: Configure Azure Synapse Link
               url: configure-synapse-link.md
@@ -165,19 +162,19 @@ additionalContent:
       items:
         - title: Migration options
           links:
-            - text: CQL shell, Spark – API for Cassandra
+            - text: Cassandra Query Language (CQL) shell, Spark – API for Cassandra
               url: cassandra/migrate-data.md
             - text: Azure Database Migration Service – API for MongoDB
               url: ../dms/tutorial-mongodb-cosmos-db.md
         - title: Migration guides
           links:
-            - text: Oracle DB to Azure Cosmos DB API for NoSQL using Striim
+            - text: Oracle Database to Azure Cosmos DB API for NoSQL using Striim
               url: cosmosdb-sql-api-migrate-data-striim.md
-            - text: Oracle DB to Azure Cosmos DB API for Cassandra using Striim
+            - text: Oracle Database to Azure Cosmos DB API for Cassandra using Striim
               url: cassandra/migrate-data-striim.md
-            - text: Oracle DB to Azure Cosmos DB API for Cassandra using Arcion
+            - text: Oracle Database to Azure Cosmos DB API for Cassandra using Arcion
               url: cassandra/oracle-migrate-cosmos-db-arcion.md
             - text: Apache Cassandra to Azure Cosmos DB using Arcion
               url: cassandra/migrate-data-arcion.md
-            - text: Migrate 100's TBs of data
+            - text: Migrate hundreds of terabytes of data
               url: migrate.md
diff --git a/articles/cosmos-db/mongodb/index.yml b/articles/cosmos-db/mongodb/index.yml
@@ -12,8 +12,7 @@ metadata:
   ms.service: cosmos-db
   ms.subservice: mongodb
   ms.topic: landing-page
-
-  ms.date: 02/28/2023
+  ms.date: 02/21/2024
 landingContent:
   - title: About API for MongoDB
     linkLists:
@@ -69,7 +68,7 @@ landingContent:
     linkLists:
       - linkListType: architecture
         links:
-          - text: Pre-migration guide
+          - text: Premigration guide
             url: pre-migration-steps.md
       - linkListType: how-to-guide
         links:
diff --git a/articles/cosmos-db/mongodb/vcore/index.yml b/articles/cosmos-db/mongodb/vcore/index.yml
@@ -6,15 +6,13 @@ summary: Azure Cosmos DB for MongoDB vCore makes it easy to create a database wi
 metadata:
   title: Azure Cosmos DB for MongoDB vCore documentation
   description: Azure Cosmos DB for MongoDB vCore makes it easy to create a database with full native MongoDB support.
+  author: seesharprun
+  ms.author: sidandrews
+  ms.reviewer: gahllevy
   ms.service: cosmos-db
   ms.subservice: mongodb-vcore
-  ms.custom:
-    - ignite-2023
   ms.topic: landing-page
-  author: gahl-levy
-  ms.author: gahllevy
-  ms.reviewer: sidandrews
-  ms.date: 08/28/2023
+  ms.date: 02/21/2024
 landingContent:  
   - title: Get started with Azure Cosmos DB for MongoDB vCore
     linkLists:
diff --git a/articles/cosmos-db/nosql/index.yml b/articles/cosmos-db/nosql/index.yml
@@ -12,7 +12,7 @@ metadata:
   ms.service: cosmos-db
   ms.subservice: nosql
   ms.topic: landing-page
-  ms.date: 02/28/2023
+  ms.date: 02/21/2024
 landingContent:
   - title: About API for NoSQL 
     linkLists:
@@ -104,5 +104,5 @@ landingContent:
             url: /training/modules/build-cosmos-db-java-app/
       - linkListType: video
         links:
-          - text: Azure Friday - Extension for Azure Functions update with AAD support
+          - text: Azure Friday - Extension for Azure Functions update with Microsoft Entra support
             url: /shows/azure-friday/azure-cosmos-db-extension-for-azure-functions-update-with-aad-support
diff --git a/articles/cosmos-db/table/index.yml b/articles/cosmos-db/table/index.yml
@@ -12,8 +12,7 @@ metadata:
   ms.service: cosmos-db
   ms.subservice: table
   ms.topic: landing-page
-
-  ms.date: 02/28/2023
+  ms.date: 02/21/2024
 landingContent:
   - title: About API for Table
     linkLists:
diff --git a/articles/load-balancer/load-balancer-test-frontend-reachability.md b/articles/load-balancer/load-balancer-test-frontend-reachability.md
@@ -1,6 +1,6 @@
 ---
-title: Test reachability of Azure Public Load Balancer front-ends with ping and traceroute
-description: Learn how to test Azure Public Load Balancer front-end IPv4 and IPv6 addresses for reachability from an Azure VM or an external device. Supports ping and traceroute.
+title: Test reachability of Azure Public Load Balancer frontends with ping and traceroute
+description: Learn how to test Azure Public Load Balancer frontend IPv4 and IPv6 addresses for reachability from an Azure VM or an external device. Supports ping and traceroute.
 services: load-balancer
 author: mbender-ms
 ms.service: load-balancer
@@ -10,39 +10,39 @@ ms.author: mbender
 ms.custom: template-how-to
 ---
 
-# Test reachability of Azure Public Load Balancer front-ends with ping and traceroute
+# Test reachability of Azure Public Load Balancer frontends with ping and traceroute
 
-Standard Public Azure Load Balancer front-end IPv4 and IPv6 addresses support testing reachability using ping and traceroute. Testing reachability of a load balancer front-end is useful for troubleshooting inbound connectivity issues to Azure resources. In this article, you learn how to use ping and traceroute for testing a front-end of an existing Standard public load balancer. It can be completed from an Azure Virtual Machine or from a device outside of Azure.
+Standard Public Azure Load Balancer frontend IPv4 and IPv6 addresses support testing reachability using ping and traceroute. Testing reachability of a load balancer frontend is useful for troubleshooting inbound connectivity issues to Azure resources. In this article, you learn how to use ping and traceroute for testing a frontend of an existing Standard public load balancer. It can be completed from an Azure Virtual Machine or from a device outside of Azure.
 
 ## Prerequisites
 
 - An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F) and access to the Azure portal.
 
-- A standard public load balancer with an IPv4 and IPv6 front-end in your subscription. For more information on creating an Azure Load Balancer, see [Quickstart: Create a public load balancer](/azure/load-balancer/quickstart-load-balancer-standard-public-portal) to load balance VMs using the Azure portal.
+- A standard public load balancer with an IPv4 and IPv6 frontend in your subscription. For more information on creating an Azure Load Balancer, see [Quickstart: Create a public load balancer](/azure/load-balancer/quickstart-load-balancer-standard-public-portal) to load balance VMs using the Azure portal.
 
 - An Azure Virtual Machine with a public IP address assigned to its network interface. For more information on creating a virtual machine with a public IP, see [Quickstart: Create a Windows virtual machine in the Azure portal](/azure/virtual-machines/windows/quick-create-portal).
 
 > [!NOTE]
-> Testing inbound connectivity to Azure Load Balancer front-ends is only supported for public load balancers. Testing inbound connectivity to internal load balancer front-ends is not supported.
+> Testing inbound connectivity to Azure Load Balancer frontends is only supported for public load balancers. Testing inbound connectivity to internal load balancer frontends is not supported.
 
 ## Testing from a device outside of Azure
 ### [Windows](#tab/windows-outside)
 
-This section describes testing reachability of a standard load balancer front-end from a Windows device outside of Azure.
+This section describes testing reachability of a standard load balancer frontend from a Windows device outside of Azure.
 
 ### [Linux](#tab/linux-outside)
 
-This section describes testing reachability of a standard load balancer front-end from a Linux device outside of Azure.
+This section describes testing reachability of a standard load balancer frontend from a Linux device outside of Azure.
 
 ---
 
-### Test the load balancer's front-end
+### Test the load balancer's frontend
 
-Choose either ping or traceroute to test reachability of a standard load balancer front-end from a device outside of Azure.
+Choose either ping or traceroute to test reachability of a standard load balancer frontend from a device outside of Azure.
 
 ### [Ping](#tab/ping/windows-outside)
 
-Follow these steps to test reachability of a standard public load balancer front-end using `ping` from a Windows device outside of Azure:
+Follow these steps to test reachability of a standard public load balancer frontend using `ping` from a Windows device outside of Azure:
 
 1. From your Windows device, open the **Search taskbar** and enter `cmd`. Select **Command Prompt**.
 2. In the command prompt, type the following command: 
@@ -55,7 +55,7 @@ Follow these steps to test reachability of a standard public load balancer front
 
 ### [Ping](#tab/ping/linux-outside)
 
-Follow these steps to test reachability of a standard public load balancer front-end using `ping` from a Linux device outside of Azure:
+Follow these steps to test reachability of a standard public load balancer frontend using `ping` from a Linux device outside of Azure:
 
 1. Open Terminal.
 2. Type the following command:
@@ -68,7 +68,7 @@ Follow these steps to test reachability of a standard public load balancer front
 
 ### [Traceroute](#tab/traceroute/windows-outside)
 
-Follow these steps to test reachability of a standard public load balancer front-end using `tracert` from a Windows device outside of Azure:
+Follow these steps to test reachability of a standard public load balancer frontend using `tracert` from a Windows device outside of Azure:
 
 1. From your Windows device, open the **Search taskbar** and enter `cmd`. Select **Command Prompt**.
 2. In the command prompt, type the following command:
@@ -81,7 +81,7 @@ Follow these steps to test reachability of a standard public load balancer front
 
 ### [Traceroute](#tab/traceroute/linux-outside)
 
-Follow these steps to test reachability of a standard public load balancer front-end using `traceroute` from a Linux device outside of Azure:
+Follow these steps to test reachability of a standard public load balancer frontend using `traceroute` from a Linux device outside of Azure:
 
 1. Open Terminal.
 2. Type the following command:
@@ -96,7 +96,7 @@ Follow these steps to test reachability of a standard public load balancer front
 
 ## Testing from an Azure Virtual Machine
 
-This section describes how to test reachability of a standard public load balancer front-end from an Azure Virtual Machine. First, you create an inbound Network Security Group (NSG) rule on the virtual machine to allow ICMP traffic. Then, you test reachability of the front-end of the load balancer from the virtual machine with ping or traceroute.
+This section describes how to test reachability of a standard public load balancer frontend from an Azure Virtual Machine. First, you create an inbound Network Security Group (NSG) rule on the virtual machine to allow ICMP traffic. Then, you test reachability of the frontend of the load balancer from the virtual machine with ping or traceroute.
 
 ### Configure inbound NSG rule
 
@@ -130,26 +130,26 @@ This section describes how to test reachability of a standard public load balanc
 
 ### [Windows](#tab/windowsvm)
 
-This section describes testing reachability of a standard load balancer front-end from a Windows Virtual Machine on Azure.
+This section describes testing reachability of a standard load balancer frontend from a Windows Virtual Machine on Azure.
 
 1. Return to **Overview** in the virtual machine’s menu and select **Connect**.
 1. Sign in to your virtual machine using RDP, SSH, or Bastion.
 
 ### [Linux](#tab/linuxvm/)
 
-This section describes testing reachability of a standard load balancer front-end from a Linux Virtual Machine on Azure.
+This section describes testing reachability of a standard load balancer frontend from a Linux Virtual Machine on Azure.
 
 1. Return to **Overview** in the virtual machine’s menu and select **Connect**.
 1. Sign in to your virtual machine using SSH or Bastion.
 ---
 
-### Test the load balancer's front-end
+### Test the load balancer's frontend
 
-Choose either ping or traceroute to test reachability of a standard public load balancer front-end from an Azure Virtual Machine.
+Choose either ping or traceroute to test reachability of a standard public load balancer frontend from an Azure Virtual Machine.
 
 ### [Ping](#tab/ping/windowsvm)
 
-Follow these steps to test reachability of a standard public load balancer front-end using `ping` from a Windows virtual machine:
+Follow these steps to test reachability of a standard public load balancer frontend using `ping` from a Windows virtual machine:
 
 1. From your Windows device, open the **Search taskbar** and enter `cmd`. Select **Command Prompt**.
 2. In the command prompt, type the following command:
@@ -162,7 +162,7 @@ Follow these steps to test reachability of a standard public load balancer front
 
 ### [Ping](#tab/ping/linuxvm)
 
-Follow these steps to test reachability of a standard public load balancer front-end using `ping` from a Linux virtual machine:
+Follow these steps to test reachability of a standard public load balancer frontend using `ping` from a Linux virtual machine:
 
 1. Open Terminal.
 2. Type the following command:
@@ -175,7 +175,7 @@ Follow these steps to test reachability of a standard public load balancer front
 
 ### [Traceroute](#tab/traceroute/windowsvm)
 
-Follow these steps to test reachability of a standard public load balancer front-end using `tracert` from a Windows virtual machine:
+Follow these steps to test reachability of a standard public load balancer frontend using `tracert` from a Windows virtual machine:
 
 1. From your Windows device, open the **Search taskbar** and enter `cmd`. Select **Command Prompt**.
 2. In the command prompt, type the following command:
@@ -188,7 +188,7 @@ Follow these steps to test reachability of a standard public load balancer front
 
 ### [Traceroute](#tab/traceroute/linuxvm)
 
-Follow these steps to test reachability of a standard public load balancer front-end using `traceroute` from a Linux virtual machine:
+Follow these steps to test reachability of a standard public load balancer frontend using `traceroute` from a Linux virtual machine:
 
 1. Open Terminal.
 2. Type the following command:
@@ -203,7 +203,7 @@ Follow these steps to test reachability of a standard public load balancer front
 
 ## Expected replies with ping
 
-Based on the current health probe state of your backend instances, you receive different replies when testing the Load Balancer’s front-end with ping. Review the following scenarios for the expected reply:
+Based on the current health probe state of your backend instances, you receive different replies when testing the Load Balancer’s frontend with ping. Review the following scenarios for the expected reply:
 
 | **Scenario** | **Expected reply** |
 | --- | --- |
diff --git a/articles/virtual-machines/capacity-reservation-associate-virtual-machine-scale-set-flex.md b/articles/virtual-machines/capacity-reservation-associate-virtual-machine-scale-set-flex.md
@@ -27,6 +27,7 @@ This content applies to the flexible orchestration mode. For uniform orchestrati
 > [!IMPORTANT]
 > Capacity Reservations with virtual machine set using flexible orchestration is currently in general availability for Fault Domain equlas to 1.
 
+> [!IMPORTANT]
 > Capacity Reservations with virtual machine set using flexible orchestration is currently in Public Preview for Fault Domain greater than 1. This preview version is provided without a service-level agreement, and we don't recommend it for production workloads. Certain features might not be supported or might have constrained capabilities. For more information, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
 > During the preview, always attach reserved capacity during creation of new scale sets using flexible orchestration mode. There are known issues attaching capacity reservations to existing scale sets using flexible orchestration. Microsoft will update this page as more options become enabled during preview. 
 
