Merge pull request #94615 from SnehaGunda/master

Removing pricing details from analytical storage page

Author: ktoliver

articles/cosmos-db/globally-distributed-transactional-analytical-storage.md

@@ -31,8 +31,8 @@ The transactional storage engine is backed by local SSDs, whereas the analytical
 |Durability  |    99.99999 (7-9 s)     |  99.99999 (7-9 s)       |
 |APIs that access the data  |   SQL, MongoDB, Cassandra, Gremlin, Tables, and Etcd.       | Apache Spark         |
 |Retention (Time-to-live or TTL)   |  Policy driven, configured on the Azure Cosmos container by using the `DefaultTimeToLive` property.       |   Policy driven, configured on the Azure Cosmos container by using the `ColumnStoreTimeToLive` property.      |
-|Price per GB    |   $0.25/GB      |  $0.02/GB       |
-|Price for storage transactions    | Provisioned throughput is charged at $0.008 per 100 RU/s with hourly billing.        |  Consumption-based throughput is charged at $0.05 for 10,000 write transactions and $0.004 for 10,000 read transactions.       |
+|Price per GB    |   See the [pricing page](https://azure.microsoft.com/pricing/details/cosmos-db/)     |   See the [pricing page](https://azure.microsoft.com/pricing/details/cosmos-db/)        |
+|Price for storage transactions    |  See the [pricing page](https://azure.microsoft.com/pricing/details/cosmos-db/)         |   See the [pricing page](https://azure.microsoft.com/pricing/details/cosmos-db/)        |
 
 ## Benefits of transactional and analytical storage
 
@@ -62,16 +62,6 @@ In a given region, the transactional workloads operate against your container’
 
 The transactional workloads consume the provisioned throughput (RUs). Unlike the transactional workloads, the analytical workloads throughput is based on the actual consumption. The analytical workloads consume resources on-demand.
 
-### On-demand snapshots and time-travel analytics
-
-You can take snapshots of your data stored in the analytical storage of your Azure Cosmos containers, at any time, by calling the `CreateSnapshot (name, timestamp)` command on the container. Snapshots are named “bookmarks” in the history of the updates that were ever done on your container.
-
-![On-demand snapshots and time-travel analytics](./media/globally-distributed-transactional-analytical-storage/ondemand-analytical-data-snapshots.png)
-
-At the time of creating the snapshot, in addition to the name, you can specify the timestamp that defines the state of your container in the history of updates. You can then load the snapshot data into Spark and perform the queries.
-
-Currently, you can only take snapshots on-demand at any time on the container, the ability to automatically take snapshots based on a schedule or custom policy isn’t yet supported.
-
 ### Configure and tier data between transactional and analytical storage independently
 
 Depending on your scenario, you can independently enable or disable each of the two storage engines. The following are the configurations for each scenario:

articles/cosmos-db/mongodb-mongochef.md

@@ -1,35 +1,36 @@
 ---
 title: Connect to Azure Cosmos DB's API for MongoDB using Studio 3T
-titleSuffix: Azure Cosmos DB
-description: Learn how to connect to Cosmos DB using Studio 3T and Azure Cosmos DB's API for MongoDB.
+description: Learn how to connect to an Azure Cosmos DB's API for MongoDB using Studio 3T.
 ms.service: cosmos-db
 ms.subservice: cosmosdb-mongo
 ms.topic: conceptual
-ms.date: 12/26/2018
+ms.date: 11/01/2019
 author: sivethe
 ms.author: sivethe
 ms.custom: seodec18
 ---
-# Connect to Cosmos account using Studio 3T
+# Connect to an Azure Cosmos account using Studio 3T
 
-To connect to a Cosmos account using Azure Cosmos DB's API for MongoDB, you must:
+To connect to an Azure Cosmos DB's API for MongoDB using Studio 3T, you must:
 
-* Download and install [Studio 3T](https://studio3t.com/)
-* Have your Cosmos DB [connection string](connect-mongodb-account.md) information
+* Download and install [Studio 3T](https://studio3t.com/).
+* Have your Azure Cosmos account's [connection string](connect-mongodb-account.md) information.
 
 > [!NOTE]
-> Currently, Robo 3T v1.2 and lower are supported with Cosmos DB's API for MongoDB. 
+> Currently, Robo 3T v1.2 and lower versions are supported with Cosmos DB's API for MongoDB.
 
 ## Create the connection in Studio 3T
-To add your Cosmos account to the Studio 3T connection manager, perform the following steps:
 
-1. Retrieve the connection information for your Cosmos account configured with Azure Cosmos DB's API for MongoDB using the instructions in the [Connect a MongoDB application to Azure Cosmos DB](connect-mongodb-account.md) article.
+To add your Azure Cosmos account to the Studio 3T connection manager, use the following steps:
+
+1. Retrieve the connection information for your Azure Cosmos DB's API for MongoDB account using the instructions in the [Connect a MongoDB application to Azure Cosmos DB](connect-mongodb-account.md) article.
 
     ![Screenshot of the connection string page](./media/mongodb-mongochef/ConnectionStringBlade.png)
+
 2. Click **Connect** to open the Connection Manager, then click **New Connection**
 
     ![Screenshot of the Studio 3T connection manager](./media/mongodb-mongochef/ConnectionManager.png)
-3. In the **New Connection** window, on the **Server** tab, enter the HOST (FQDN) of the Azure Cosmos DB account and the PORT.
+3. In the **New Connection** window, on the **Server** tab, enter the HOST (FQDN) of the Azure Cosmos account and the PORT.
 
     ![Screenshot of the Studio 3T connection manager server tab](./media/mongodb-mongochef/ConnectionManagerServerTab.png)
 4. In the **New Connection** window, on the **Authentication** tab, choose Authentication Mode **Basic (MONGODB-CR or SCARM-SHA-1)** and enter the USERNAME and PASSWORD.  Accept the default authentication db (admin) or provide your own value.

articles/private-link/private-link-overview.md

@@ -42,7 +42,7 @@ Azure Private Link provides the following benefits:
 |  | Azure Data Lake Storage Gen2        |  East US, West US, West Central US       | Preview         |
 |  |  Azure SQL Database         | West Central US; WestUS; South Central US; East US; North Central US      |   Preview      |
 ||Azure SQL Data Warehouse| West Central US; WestUS; South Central US; East US; North Central US |Preview|
-||Azure Cosmos DB| West Central US; WestUS; EastUS; North Central US; EastUS 2; WestUS 2 |Preview|
+||Azure Cosmos DB| West Central US; WestUS; North Central US |Preview|
 
 For the most up-to-date notifications, check the [Azure Virtual Network updates page](https://azure.microsoft.com/updates/?product=virtual-network).