Merge pull request #271644 from kgremban/apr9-cosmosga

cosmos db endpoint ga

Author: prmerger-automator[bot]

articles/iot-hub/how-to-routing-portal.md

@@ -68,7 +68,7 @@ Routes send messages or event logs to an Azure service for storage or processing
 
    | Parameter | Value |
    | --------- | ----- |
-   | **Endpoint type** | Select **Cosmos DB (preview)**. |
+   | **Endpoint type** | Select **Cosmos DB**. |
    | **Endpoint name** | Provide a unique name for a new endpoint, or select **Select existing** to choose an existing Storage endpoint. |
    | **Cosmos DB account** | Use the drop-down menu to select an existing Cosmos DB account in your subscription. |
    | **Database** | Use the drop-down menu to select an existing database in your Cosmos DB account. |

articles/iot-hub/iot-hub-devguide-endpoints.md

@@ -76,7 +76,7 @@ IoT Hub currently supports the following Azure services as custom endpoints:
 * Event Hubs
 * Service Bus Queues
 * Service Bus Topics
-* Cosmos DB (preview)
+* Cosmos DB
 
 For the limits on endpoints per hub, see [Quotas and throttling](iot-hub-devguide-quotas-throttling.md).
 
@@ -126,7 +126,7 @@ Service Bus queues and topics used as IoT Hub endpoints must not have **Sessions
 
 Apart from the built-in-Event Hubs compatible endpoint, you can also route data to custom endpoints of type Event Hubs.
 
-### Azure Cosmos DB as a routing endpoint (preview)
+### Azure Cosmos DB as a routing endpoint
 
 You can send data directly to Azure Cosmos DB from IoT Hub. IoT Hub supports writing to Cosmos DB in JSON (if specified in the message content-type) or as base 64 encoded binary.
 

articles/iot-hub/iot-hub-devguide-messages-d2c.md

@@ -34,7 +34,7 @@ IoT Hub currently supports the following endpoints for message routing:
 * Service Bus queues
 * Service Bus topics
 * Event Hubs
-* Cosmos DB (preview)
+* Cosmos DB
 
 For more information about each of these endpoints, see [IoT Hub endpoints](./iot-hub-devguide-endpoints.md#custom-endpoints-for-message-routing).
 

articles/iot-hub/iot-hub-event-grid-routing-comparison.md

@@ -30,7 +30,7 @@ While both message routing and Event Grid enable alert configuration, there are
 | **Device messages and events** | Yes, message routing supports telemetry data, device twin changes, device lifecycle events, digital twin change events, and device connection state events. | Yes, Event Grid supports telemetry data and device events like device created/deleted/connected/disconnected. But Event Grid doesn't support device twin change events and digital twin change events. |
 | **Ordering** | Yes, message routing maintains the order of events.  | No, Event Grid doesn't guarantee the order of events. |
 | **Filtering** | Rich filtering on message application properties, message system properties, message body, device twin tags, and device twin properties. Filtering isn't applied to digital twin change events. For examples, see [Message Routing Query Syntax](iot-hub-devguide-routing-query-syntax.md). | Filtering based on event type, subject type and attributes in each event. For examples, see [Understand filtering events in Event Grid Subscriptions](../event-grid/event-filtering.md). When subscribing to telemetry events, you can apply filters on the data to filter on message properties, message body and device twin in your IoT Hub, before publishing to Event Grid. See [how to filter events](../iot-hub/iot-hub-event-grid.md#filter-events). |
-| **Endpoints** | <ul><li>Event Hubs</li> <li>Azure Blob Storage</li> <li>Service Bus queue</li> <li>Service Bus topics</li><li>Cosmos DB (preview)</li></ul><br>Paid IoT Hub SKUs (S1, S2, and S3) can have 10 custom endpoints and 100 routes per IoT Hub. | <ul><li>Azure Functions</li> <li>Azure Automation</li> <li>Event Hubs</li> <li>Logic Apps</li> <li>Storage Blob</li> <li>Custom Topics</li> <li>Queue Storage</li> <li>Power Automate</li> <li>Third-party services through WebHooks</li></ul><br>Event Grid supports 500 endpoints per IoT Hub. For the most up-to-date list of endpoints, see [Event Grid event handlers](../event-grid/overview.md#event-handlers). |
+| **Endpoints** | <ul><li>Event Hubs</li> <li>Azure Blob Storage</li> <li>Service Bus queue</li> <li>Service Bus topics</li><li>Cosmos DB</li></ul><br>Paid IoT Hub SKUs (S1, S2, and S3) can have 10 custom endpoints and 100 routes per IoT Hub. | <ul><li>Azure Functions</li> <li>Azure Automation</li> <li>Event Hubs</li> <li>Logic Apps</li> <li>Storage Blob</li> <li>Custom Topics</li> <li>Queue Storage</li> <li>Power Automate</li> <li>Third-party services through WebHooks</li></ul><br>Event Grid supports 500 endpoints per IoT Hub. For the most up-to-date list of endpoints, see [Event Grid event handlers](../event-grid/overview.md#event-handlers). |
 | **Cost** | There is no separate charge for message routing. Only ingress of telemetry into IoT Hub is charged. For example, if you have a message routed to three different endpoints, you're billed for only one message. | There is no charge from IoT Hub. Event Grid offers the first 100,000 operations per month for free, and then $0.60 per million operations afterwards. |
 
 ## Similarities