Update stream-analytics-documentdb-output.md

Removed recommendation to add blanket access to cosmos DB. If customers have their resources behind a firewall. Our recommendation would be for them to use private endpoint and ASA clusters

Author: enkrumah

articles/stream-analytics/stream-analytics-documentdb-output.md

@@ -5,7 +5,7 @@ author: enkrumah
 ms.author: ebnkruma
 ms.service: stream-analytics
 ms.topic: conceptual
-ms.date: 02/2/2020
+ms.date: 09/15/2022
 ms.custom: seodec18
 ---
 # Azure Stream Analytics output to Azure Cosmos DB  
@@ -22,8 +22,6 @@ The Azure Cosmos DB output in Stream Analytics enables writing your stream proce
 
 Stream Analytics doesn't create containers in your database. Instead, it requires you to create them up front. You can then control the billing costs of Azure Cosmos DB containers. You can also tune the performance, consistency, and capacity of your containers directly by using the [Azure Cosmos DB APIs](/rest/api/cosmos-db/).
 
-> [!Note]
-> You must add 0.0.0.0 to the list of allowed IPs from your Azure Cosmos DB firewall.
 
 The following sections detail some of the container options for Azure Cosmos DB.
 
@@ -143,4 +141,4 @@ If a transient failure, service unavailability, or throttling happens while Stre
 
 * [Understand outputs from Azure Stream Analytics](stream-analytics-define-outputs.md) 
 * [Azure Stream Analytics output to Azure SQL Database](stream-analytics-sql-output-perf.md)
-* [Azure Stream Analytics custom blob output partitioning](stream-analytics-custom-path-patterns-blob-storage-output.md)
+* [Azure Stream Analytics custom blob output partitioning](stream-analytics-custom-path-patterns-blob-storage-output.md)