Merge pull request #115572 from LuisBosquez/vnet-notebook-note

VNET notebook note

Author: PMEds28

articles/cosmos-db/create-mongodb-java.md

@@ -38,7 +38,7 @@ In this quickstart, you create and manage an Azure Cosmos DB for MongoDB API acc
 
 Name your new database **db**, and your new collection **coll**.
 
-[!INCLUDE [cosmos-db-create-collection](../../includes/cosmos-db-create-collection.md)] 
+[!INCLUDE [cosmos-db-create-collection](../../includes/cosmos-db-mongodb-create-collection.md)] 
 
 ## Clone the sample application
 

articles/cosmos-db/vnet-service-endpoint.md

@@ -20,6 +20,10 @@ By default, an Azure Cosmos account is accessible from any source if the request
 
 Here are some frequently asked questions about configuring access from virtual networks:
 
+### Are Notebooks and Mongo Shell currently compatible with Virtual Network enabled accounts?
+
+At the moment the [Mongo shell integration in the Cosmos DB Data Explorer](https://devblogs.microsoft.com/cosmosdb/preview-native-mongo-shell/) and the [Jupyter Notebooks service](https://docs.microsoft.com/azure/cosmos-db/cosmosdb-jupyter-notebooks) are not supported with VNET access. This is currently in active development.
+
 ### Can I specify both virtual network service endpoint and IP access control policy on an Azure Cosmos account? 
 
 You can enable both the virtual network service endpoint and an IP access control policy (aka firewall) on your Azure Cosmos account. These two features are complementary and collectively ensure isolation and security of your Azure Cosmos account. Using IP firewall ensures that static IPs can access your account. 

includes/cosmos-db-mongodb-create-collection.md

@@ -0,0 +1,31 @@
+---
+ title: include file
+ description: include file
+ services: cosmos-db
+ author: LuisBosquez
+ ms.service: cosmos-db
+ ms.topic: include
+ ms.date: 04/08/2020
+ ms.author: lbosq
+ ms.custom: include file
+---
+
+You can now use the Data Explorer tool in the Azure portal to create an Azure Cosmos DB's API for MongoDB database and container. 
+
+1. Select **Data Explorer** > **New Container**. 
+    
+    The **Add Container** area is displayed on the far right, you may need to scroll right to see it.
+
+    ![The Azure portal Data Explorer, Add Container pane](./media/cosmos-db-create-collection/azure-cosmosdb-mongodb-data-explorer.png)
+
+2. In the **Add container** page, enter the settings for the new container.
+
+    |Setting|Suggested value|Description
+    |---|---|---|
+    |**Database ID**|db|Enter *db* as the name for the new database. Database names must contain from 1 through 255 characters, and they cannot contain `/, \\, #, ?`, or a trailing space. Check the **Provision database throughput** option, it allows you to share the throughput provisioned to the database across all the containers within the database. This option also helps with cost savings. |
+    |**Throughput**|400|Leave the throughput at 400 request units per second (RU/s). If you want to reduce latency, you can scale up the throughput later. You can also choose [Autopilot mode](https://docs.microsoft.com/azure/cosmos-db/provision-throughput-autopilot), which will give you a range of RU/s that will dynamically increase and decrease as needed.| 
+    |**Collection ID**|coll|Enter *coll* as the name for your new container. Container IDs have the same character requirements as database names.|
+    |**Storage capacity**|Fixed (10GB)|Enter *Fixed (10GB)* for this application. If you select *Unlimited*, you will have to create a `Shard Key`, which all items inserted will require.|
+    |**Shard key**| /_id| The sample described in this article does not use a Shard Key, so setting it to  */_id* will use the automatically generated ID field as the shard key. Learn more about sharding, also known as partitioning, in [Partitioning in Azure Cosmos DB](https://docs.microsoft.com/azure/cosmos-db/partitioning-overview)|
+        
+    Select **OK**. The Data Explorer displays the new database and container.