Merge pull request #14948 from v-stsavell/515387

[SCOPED] Quality check: Replace "Cosmos DB for Mongo DB" with "Azure DocumentDB"

Author: JamesJBarnett

docs/ai-ml/idea/unlock-insights-from-conversational-data-content.md

@@ -106,7 +106,7 @@ Consider the alternative approach if your workload has the following characteris
 
 - **Current approach:** This solution uses AI Search with vector embeddings to enable semantic search across conversation transcripts. It supports natural language queries and RAG-based interactions.
 
-- **Alternative approach:** Implement a pure vector database solution by using Azure Cosmos DB for MongoDB with vector search capabilities. Alternatively, use Azure Database for PostgreSQL with the pgvector extension.
+- **Alternative approach:** Implement a pure vector database solution by using Azure DocumentDB with vector search capabilities. Alternatively, use Azure Database for PostgreSQL with the pgvector extension.
 
 Consider the alternative approach if your workload has the following characteristics:
 

docs/browse/thumbs/aks-microservices-advanced-production-deployment.png

@@ -91,15 +91,15 @@ Use document data stores to store semi-structured documents, often in JSON forma
 
 - [Azure Cosmos DB for NoSQL](/azure/cosmos-db/nosql/) is a schema-less, multi-region NoSQL database that has low-latency reads and writes.
 
-- [Azure Cosmos DB for MongoDB](/azure/cosmos-db/mongodb/overview) is a globally distributed database that has MongoDB wire protocol compatibility and autoscaling.
+- [Azure DocumentDB](/azure/documentdb/overview) is a globally distributed database that has MongoDB wire protocol compatibility and autoscaling.
 - [Azure Cosmos DB in Fabric](/fabric/database/cosmos-db/overview) is a schema-less, NoSQL database that has low-latency reads and writes, simplified management, and built-in Fabric analytics.
 
 Use the following table to help determine which Azure service meets your use case requirements.
 
 | Service | Best for | Key features | Example use case |
 |--------|----------|--------------|------------------|
 | [Azure Cosmos DB for NoSQL](/azure/cosmos-db/nosql/) | Custom JSON document models that support SQL-like querying | Rich query language, multi-region writes, time to live (TTL), change feed | Building a multitenant SaaS platform that supports flexible schemas |
-| [Azure Cosmos DB for MongoDB](/azure/cosmos-db/mongodb/overview) | Apps that use MongoDB drivers or JSON-centric APIs | Global distribution, autoscale, native MongoDB wire protocol | Migrating a Node.js app from MongoDB to Azure |
+| [Azure DocumentDB](/azure/documentdb/overview) | Apps that use MongoDB drivers or JSON-centric APIs | Global distribution, autoscale, MongoDB-native wire protocol | Migrating a Node.js app from MongoDB to Azure |
 | [Azure Cosmos DB in Fabric](/fabric/database/cosmos-db/overview) | Real-time analytics over NoSQL data | Automatic extract, transform, and load (ETL) to OneLake through Fabric integration | Transactional apps that include real-time analytical dashboards |
 
 ### Column-family data stores <a id="columnar-data-stores"></a>

docs/browse/thumbs/microservices-architecture.png

@@ -12,12 +12,10 @@ The example workload is a containerized microservices application. It reuses the
 
 ## Architecture
 
-:::image type="complex" border="false" source="./media/microservices-with-container-apps.png" alt-text="Diagram that shows the runtime architecture for the solution." lightbox="./media/microservices-with-container-apps.png":::
-   The diagram shows a Container Apps environment as a large rectangle that contains five container apps. An HTTP traffic source arrow points into the Ingestion service. An upward arrow from Ingestion goes to Azure Service Bus. A downward arrow goes from Service Bus and returns to the Workflow service. From Workflow, three black connectors descend and bend toward each lower service: the Package, the Drone Scheduler, and the Delivery services. Each lower service has a vertical arrow to its own external state store: Package service goes to Azure Cosmos DB for MongoDB API. Drone Scheduler service goes to Azure Cosmos DB for NoSQL. Delivery service goes to Azure Managed Redis. Two arrows exit the middle of the environment: the upper arrow goes to Azure Application Insights. The lower arrow goes to Azure Log Analytics workspace. Under the workspace is Azure Key Vault and below that Azure Container Registry, shown without connecting arrows.
+:::image type="complex" border="false" source="./media/microservices-with-container-apps.svg" alt-text="Diagram that shows the runtime architecture for the solution." lightbox="./media/microservices-with-container-apps.svg":::
+   The diagram shows a Container Apps environment as a large rectangle that contains five container apps. An HTTP traffic source arrow points into the Ingestion service. An upward arrow from Ingestion goes to Azure Service Bus. A downward arrow goes from Service Bus and returns to the Workflow service. From Workflow, three black connectors descend and bend toward each lower service: the Package, the Drone Scheduler, and the Delivery services. Each lower service has a vertical arrow to its own external state store: Package service goes to Azure DocumentDB. Drone Scheduler service goes to Azure Cosmos DB for NoSQL. Delivery service goes to Azure Managed Redis. Two arrows exit the middle of the environment: the upper arrow goes to Azure Application Insights. The lower arrow goes to Azure Log Analytics workspace. Under the workspace is Azure Key Vault and below that Azure Container Registry, shown without connecting arrows.
 :::image-end:::
 
-The following diagram illustrates the runtime architecture for the solution.
-
 *Download a [Visio file](https://arch-center.azureedge.net/microservices-with-container-apps.vsdx) of this architecture.*
 
 Services that share the same environment benefit in the following ways:
@@ -55,7 +53,9 @@ The workload uses the following Azure services in coordination with each other:
 
 - [Container Registry](/azure/container-registry/container-registry-intro) is a managed registry service for storing and managing private container images. In this architecture, it's the source of all container images that are deployed to the Container Apps environment. The registry is the same one used in the AKS implementation.
 
-- [Azure Cosmos DB](/azure/well-architected/service-guides/cosmos-db) is a globally distributed, multiple-model database service. It supports open-source APIs for [MongoDB](/azure/cosmos-db/mongodb-introduction) and SQL. Microservices should write their state to dedicated external data stores. In this architecture, the microservices write their state and application data to their own Azure Cosmos DB databases.
+- [Azure Cosmos DB](/azure/well-architected/service-guides/cosmos-db) is a globally distributed, multiple-model database service.  In this architecture, the drone scheduler service uses Azure Cosmos DB as its data store.
+
+- [Azure DocumentDB](/azure/documentdb/overview) is a fully managed MongoDB-compatible database service for building modern applications. In this architecture, the package service uses Azure DocumentDB as its data store.
 
 - [Service Bus](/azure/well-architected/service-guides/service-bus/reliability) is a cloud messaging service that provides asynchronous communication capabilities and hybrid integration. In this architecture, it handles asynchronous messaging between the ingestion service and the task-based, workflow microservice. The rest of the services in the existing application are designed so other services can invoke them with HTTP requests.
 
@@ -166,7 +166,7 @@ Container Apps helps you deploy, manage, maintain, and monitor the applications
 
 - Use the dynamic load balancing and scaling features of Container Apps to improve availability. Over-provision your environment's subnet so that it always has enough [available IP addresses for future replicas or jobs](/azure/container-apps/custom-virtual-networks#subnet).
 
-- Avoid storing state directly within the Container Apps environment, because all state is lost when the replica shuts down. Externalize state to a dedicated state store for each microservice. This architecture distributes state across three distinct stores: Azure Managed Redis, Azure Cosmos DB for NoSQL, and Azure Cosmos DB for MongoDB.
+- Avoid storing state directly within the Container Apps environment, because all state is lost when the replica shuts down. Externalize state to a dedicated state store for each microservice. This architecture distributes state across three distinct stores: Azure Managed Redis, Azure Cosmos DB for NoSQL, and Azure DocumentDB.
 
 - Deploy all resources, including Container Apps, by using a multi-zone topology. For more information, see [Availability zone support in Container Apps](/azure/reliability/reliability-azure-container-apps#availability-zone-support).
 

docs/browse/thumbs/microservices-with-container-apps.png

@@ -34,7 +34,7 @@ Your application might have specific requirements that make IaaS a more suitable
 | Elasticsearch | [Azure AI Search](/azure/search/search-what-is-azure-search) |
 | Hadoop | [Azure HDInsight](/azure/hdinsight/hdinsight-overview) |
 | IIS | [Azure App Service](/azure/app-service/overview) |
-| MongoDB | [Azure Cosmos DB for MongoDB](/azure/cosmos-db/mongodb/introduction) |
+| MongoDB | [Azure DocumentDB](/azure/documentdb/overview) |
 | Redis | [Azure Managed Redis](/azure/redis/overview) |
 | SQL Server | [Azure SQL Database](/azure/azure-sql/database/sql-database-paas-overview) |
 | File share | [Azure Files](/azure/storage/files/storage-files-introduction) |

docs/data-guide/technology-choices/understand-data-store-models.md

@@ -115,7 +115,7 @@ The following table lists common use scenario requirements and the recommended d
 
 The following table lists features available in Azure database services.
 
-|  Feature         | SQL Database | SQL Managed Instance | Azure Database for PostgreSQL | Azure Database for MySQL | Azure Managed Instance for Apache Cassandra | Azure Cosmos DB | Azure Managed Redis | Azure Cosmos DB for MongoDB
+| Feature | SQL Database | SQL Managed Instance | Azure Database for PostgreSQL | Azure Database for MySQL | Azure Managed Instance for Apache Cassandra | Azure Cosmos DB | Azure Managed Redis | Azure DocumentDB
 |------------------|---------|--------|--------|--------|--------|--------|--------|--------|--------|
 |Database type|Relational |Relational |Relational |Relational |NoSQL |NoSQL |In-memory |NoSQL
 |Data model|Relational |Relational |Relational |Relational |Wide-column |Multimodel: Document, wide-column, key-value, graph |Key-value |Document |