Merge pull request #113773 from SnehaGunda/partners

denrea · web-flow · commit 343cf4f7454a · 2020-05-04T15:02:57.000-07:00
Updating autoscale and partners doc
diff --git a/articles/cosmos-db/TOC.yml b/articles/cosmos-db/TOC.yml
@@ -139,7 +139,7 @@
       - name: Provision throughput on containers and databases
         displayName: request units, RUs, RU, limits, database throughput, shared throughput, container throughput
         href: set-throughput.md
-      - name: Provision throughput - autoscale mode
+      - name: Provision throughput - autoscale
         href: provision-throughput-autoscale.md
       - name: Autoscale FAQ
         href: autoscale-faq.md
@@ -1062,7 +1062,7 @@
           href: monitor-server-side-latency.md
         - name: Monitor request unit usage
           href: monitor-request-unit-usage.md
-      - name : Use diagnostic logs
+      - name : Use Azure monitor logs
         items:
         - name: Monitor with diagnostic logs
           href: cosmosdb-monitor-resource-logs.md
diff --git a/articles/cosmos-db/autoscale-faq.md b/articles/cosmos-db/autoscale-faq.md
@@ -1,5 +1,5 @@
 ---
-title: Frequently asked questions on autoscale mode in Azure Cosmos DB 
+title: Frequently asked questions on autoscale provisioned throughput in Azure Cosmos DB 
 description: Frequently asked questions about autoscale provisioned throughput for Azure Cosmos DB databases and containers
 author: deborahc
 ms.author: dech
@@ -10,36 +10,36 @@ ms.date: 04/28/2020
 
 # Frequently asked questions about autoscale provisioned throughput in Azure Cosmos DB
 
-With provisioned throughput in autoscale mode, Azure Cosmos DB will automatically manage and scale the RU/s of your container or database based on usage. This article answers commonly asked questions about autoscale.
+With autoscale provisioned throughput, Azure Cosmos DB will automatically manage and scale the RU/s of your container or database based on usage. This article answers commonly asked questions about autoscale.
 
 ## Frequently asked questions
 
-### Is autoscale mode supported for all APIs?
-Yes, autoscale mode is supported for all APIs: Core (SQL), Gremlin, Table, Cassandra, and API for MongoDB.
+### Is autoscale supported for all APIs?
+Yes, autoscale is supported for all APIs: Core (SQL), Gremlin, Table, Cassandra, and API for MongoDB.
 
-### Is autoscale mode supported for multi-master accounts?
-Yes, autoscale mode is supported for multi-master accounts. The max RU/s are available in each region that is added to the Cosmos account. 
+### Is autoscale supported for multi-master accounts?
+Yes, autoscale is supported for multi-master accounts. The max RU/s are available in each region that is added to the Cosmos account. 
 
-### What is the pricing for autoscale?
+### What is the pricing for autoscale ?
 Refer to the Azure Cosmos DB [pricing page](https://azure.microsoft.com/pricing/details/cosmos-db/) for details. 
 
 ### How do I enable autoscale for my containers or databases?
-Autoscale mode can be enabled on new containers and databases created using the Azure portal. 
+Autoscale can be enabled on new containers and databases created using the Azure portal.
 
-### Is there CLI or SDK support to create containers or databases with autoscale mode?
-Currently, you can only create resources with autoscale mode from the Azure portal. Support for CLI and SDK is not yet available.
+### Is there CLI or SDK support to create containers or databases with autoscale provisioned throughput?
+Currently, you can only create resources with autoscale provisioned throughput from the Azure portal. Support for CLI and SDK is not yet available.
 
 ### Can I enable autoscale on an existing container or a database?
-Currently, you can enable autoscale on new containers and databases when creating them. Support to enable autoscale mode on existing containers and databases is not yet available. You can migrate existing containers to a new container using [Azure Data Factory](../data-factory/connector-azure-cosmos-db.md) or [change feed](change-feed.md). 
+Currently, you can enable autoscale on new containers and databases when creating them. Support to enable autoscale on existing containers and databases is not yet available. You can migrate existing containers to a new container using [Azure Data Factory](../data-factory/connector-azure-cosmos-db.md) or [change feed](change-feed.md). 
 
-### Can I turn off autoscale mode on a container or database?
-Yes, you can turn off autoscale by switching to the 'Manual' option for the provisioned throughput. In the current release, after switching from autoscale mode to manual mode, you cannot enable autoscale again for the same resource. 
+### Can I turn off autoscale on a container or database?
+Yes, you can turn off autoscale by switching to the 'standard (Manual)' option for the provisioned throughput. In the current release, after switching from autoscale to standard provisioned throughput, you cannot enable autoscale again for the same resource. 
 
-### Is autoscale mode supported for shared throughput databases?
-Yes, autoscale mode is supported for shared throughput databases. To enable this feature, select autoscale mode and the **Provision throughput** option when creating the database. 
+### Is autoscale supported for shared throughput databases?
+Yes, autoscale is supported for shared throughput databases. To enable this feature, select autoscale and the **Provision throughput** option when creating the database. 
 
 ### What is the number of allowed collections per shared throughput database when autoscale is enabled?
-For shared throughput databases with autoscale mode enabled, the number of allowed collections is: MIN(25, Max RU/s of database / 1000). For example, if the max throughput of the database is 20,000 RU/s, the database can have MIN(25, 20,000 RU/s / 1000) = 20 collections. 
+For shared throughput databases with autoscale enabled, the number of allowed collections is: MIN(25, Max RU/s of database / 1000). For example, if the max throughput of the database is 20,000 RU/s, the database can have MIN(25, 20,000 RU/s / 1000) = 20 collections. 
 
 
 ### What is the storage limit associated with each max RU/s option?  
@@ -50,13 +50,13 @@ See the [autoscale limits](provision-throughput-autoscale.md#autoscale-limits) a
 If the storage limit associated with the max throughput of the database or container is exceeded, Azure Cosmos DB will automatically increase the max throughput to the next highest tier that can support that level of storage. For example, suppose a database or container is provisioned with the 4000 RU/s max throughput option, which has a storage limit of 50 GB. If the storage of the resource increases to 100 GB, the max RU/s of the database or container will be automatically increased to 20,000 RU/s, which can support up to 200 GB. 
 
 ### How quickly will autoscale up and down based on spikes in traffic?
-In autoscale mode, you can instantaneously scale up or scale down the RU/s within the minimum and maximum RU/s range, based on incoming traffic. Billing is done at a 1-hour granularity, where you are charged for the highest RU/s in a particular hour.
+With autoscale, you can instantaneously scale up or scale down the RU/s within the minimum and maximum RU/s range, based on incoming traffic. Billing is done at a 1-hour granularity, where you are charged for the highest RU/s in a particular hour.
 
-### Can I specify a custom max throughput (RU/s) value for autoscale mode?
+### Can I specify a custom max throughput (RU/s) value for autoscale?
 Currently, you can select between [four options](provision-throughput-autoscale.md#autoscale-limits) for max throughput (RU/s).
 
 ### Can I increase the max RU/s (move to a higher tier) on the database or container? 
-Yes. From the **Scale & Settings** option for your container, or **Scale** option for your database, you can select a higher max RU/s for autoscale mode. This is an asynchronous scale-up operation that may take sometime to complete (typically 4-6 hours, depending on the RU/s selected) as the service provisions more resources to support the higher scale. 
+Yes. From the **Scale & Settings** option for your container, or **Scale** option for your database, you can select a higher max RU/s for autoscale. This is an asynchronous scale-up operation that may take sometime to complete (typically 4-6 hours, depending on the RU/s selected) as the service provisions more resources to support the higher scale. 
 
 ### Can I reduce the max RU/s (move to a lower tier) on the database or container?
 Yes. As long as the current storage of the database or container is below the [storage limit](#what-is-the-storage-limit-associated-with-each-max-rus-option) associated with the max RU/s tier you want to scale down to, you can reduce the max RU/s to that tier. For example, if you have selected 20,000 RU/s as the max RU/s, you can scale down the max RU/s to 4000 RU/s if you have less than 50 GB of storage (the storage limit associated with 4000 RU/s).
@@ -82,5 +82,5 @@ For example, if you select the 20,000 RU/s max throughput option and have 200 GB
 ## Next steps
 
 * Learn how to [enable autoscale on an Azure Cosmos container or database](provision-throughput-autoscale.md#create-db-container-autoscale).
-* Learn about the [benefits of provisioned throughput in autoscale mode](provision-throughput-autoscale.md#autoscale-benefits).
+* Learn about the [benefits of provisioned throughput with autoscale ](provision-throughput-autoscale.md#autoscale-benefits).
 * Learn more about [logical and physical partitions](partition-data.md).
diff --git a/articles/cosmos-db/concepts-limits.md b/articles/cosmos-db/concepts-limits.md
@@ -133,9 +133,9 @@ Cosmos DB uses HMAC for authorization. You can use either a master key, or a [re
 
 Cosmos DB supports execution of triggers during writes. The service supports a maximum of one pre-trigger and one post-trigger per write operation. 
 
-## Autoscale mode limits
+## Limits for autoscale provisioned throughput
 
-See the [Autoscale](provision-throughput-autoscale.md#autoscale-limits) article for the throughput and storage limits in autoscale mode.
+See the [Autoscale](provision-throughput-autoscale.md#autoscale-limits) article for the throughput and storage limits with autoscale.
 
 ## SQL query limits
 
diff --git a/articles/cosmos-db/manage-cassandra-with-resource-manager.md b/articles/cosmos-db/manage-cassandra-with-resource-manager.md
@@ -24,7 +24,7 @@ To create any of the Azure Cosmos DB resources below, copy the following example
 
 <a id="create-autoscale"></a>
 
-## Azure Cosmos account for Cassandra with autoscale throughput
+## Azure Cosmos account for Cassandra with autoscale provisioned throughput
 
 This template creates an Azure Cosmos account in two regions with options for consistency and failover, with a keyspace and table configured for autoscale throughput. This template is also available for one-click deploy from Azure Quickstart Templates Gallery.
 
@@ -34,9 +34,9 @@ This template creates an Azure Cosmos account in two regions with options for co
 
 <a id="create-manual"></a>
 
-## Azure Cosmos account for Cassandra with manual throughput
+## Azure Cosmos account for Cassandra with standard (manual) provisioned throughput
 
-This template creates an Azure Cosmos account in two regions with options for consistency and failover, with a keyspace and table configured for manual throughput. This template is also available for one-click deploy from Azure Quickstart Templates Gallery.
+This template creates an Azure Cosmos account in two regions with options for consistency and failover, with a keyspace and table configured for standard throughput. This template is also available for one-click deploy from Azure Quickstart Templates Gallery.
 
 [![Deploy to Azure](https://aka.ms/deploytoazurebutton)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FAzure%2Fazure-quickstart-templates%2Fmaster%2F101-cosmosdb-cassandra%2Fazuredeploy.json)
 
diff --git a/articles/cosmos-db/manage-gremlin-with-resource-manager.md b/articles/cosmos-db/manage-gremlin-with-resource-manager.md
@@ -24,7 +24,7 @@ To create any of the Azure Cosmos DB resources below, copy the following example
 
 <a id="create-autoscale"></a>
 
-## Azure Cosmos DB account for Gremlin with autoscale throughput
+## Azure Cosmos DB account for Gremlin with autoscale provisioned throughput
 
 This template will create an Azure Cosmos account for Gremlin API with a database and graph with autoscale throughput.
 
@@ -36,9 +36,9 @@ This template is also available for one-click deploy from Azure Quickstart Templ
 
 <a id="create-manual"></a>
 
-## Azure Cosmos DB account for Gremlin with manual throughput
+## Azure Cosmos DB account for Gremlin with standard provisioned throughput
 
-This template will create an Azure Cosmos account for Gremlin API with a database and graph with manual throughput.
+This template will create an Azure Cosmos account for Gremlin API with a database and graph with standard (manual) throughput.
 
 This template is also available for one-click deploy from Azure Quickstart Templates Gallery.
 
diff --git a/articles/cosmos-db/manage-mongodb-with-resource-manager.md b/articles/cosmos-db/manage-mongodb-with-resource-manager.md
@@ -24,7 +24,7 @@ To create any of the Azure Cosmos DB resources below, copy the following example
 
 <a id="create-autoscale"></a>
 
-## Azure Cosmos account for MongoDB with autoscale throughput
+## Azure Cosmos account for MongoDB with autoscale provisioned throughput
 
 This template will create an Azure Cosmos account for MongoDB API (3.2 or 3.6) with two collections that share autoscale throughput at the database level. This template is also available for one-click deploy from Azure Quickstart Templates Gallery.
 
@@ -34,9 +34,9 @@ This template will create an Azure Cosmos account for MongoDB API (3.2 or 3.6) w
 
 <a id="create-manual"></a>
 
-## Azure Cosmos account for MongoDB with manual throughput
+## Azure Cosmos account for MongoDB with standard provisioned throughput
 
-This template will create an Azure Cosmos account for MongoDB API (3.2 or 3.6) with two collections that share 400 RU/s manual throughput at the database level. This template is also available for one-click deploy from Azure Quickstart Templates Gallery.
+This template will create an Azure Cosmos account for MongoDB API (3.2 or 3.6) with two collections that share 400 RU/s standard (manual) throughput at the database level. This template is also available for one-click deploy from Azure Quickstart Templates Gallery.
 
 [![Deploy to Azure](https://aka.ms/deploytoazurebutton)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FAzure%2Fazure-quickstart-templates%2Fmaster%2F101-cosmosdb-mongodb%2Fazuredeploy.json)
 
diff --git a/articles/cosmos-db/manage-scale-cassandra.md b/articles/cosmos-db/manage-scale-cassandra.md
@@ -53,9 +53,9 @@ You can scale the system dynamically with code by executing the [CQL ALTER comma
 
 The advantage of this approach is that it allows you to respond to scale needs dynamically and in a custom way that suits your application. With this approach, you can still leverage the standard RU/s charges and rates. If your system's scale needs are mostly predictable (around 70% or more), using SDK with CQL may be a more cost-effective method of auto-scaling than using autoscale. The disadvantage of this approach is that it can be quite complex to implement retries while rate limiting may increase latency.
 
-## <a id="use-autoscale"></a>Use autoscale
+## <a id="use-autoscale"></a>Use autoscale provisioned throughput
 
-In addition to manual or programmatic way of provisioning throughput, you can also configure Azure cosmos containers in autoscale mode. Autoscale mode will automatically and instantly scale to your consumption needs within specified RU ranges without compromising SLAs. To learn more, see the [Create Azure Cosmos containers and databases in autoscale mode](provision-throughput-autoscale.md) article.
+In addition to standard (manual) or programmatic way of provisioning throughput, you can also configure Azure cosmos containers in autoscale provisioned throughput. Autoscale will automatically and instantly scale to your consumption needs within specified RU ranges without compromising SLAs. To learn more, see the [Create Azure Cosmos containers and databases in autoscale](provision-throughput-autoscale.md) article.
 
 The advantage of this approach is that it is the easiest way to manage the scaling needs in your system. It guarantees not to apply rate-limiting **within the configured RU ranges**. The disadvantage is that, if the scaling needs in your system are predictable, autoscale may be a less cost-effective way of handling your scaling needs than using the bespoke control plane or SDK level approaches mentioned above.
 
diff --git a/articles/cosmos-db/manage-sql-with-resource-manager.md b/articles/cosmos-db/manage-sql-with-resource-manager.md
@@ -35,9 +35,9 @@ This template creates an Azure Cosmos account in two regions with options for co
 
 <a id="create-manual"></a>
 
-## Azure Cosmos account with manual throughput
+## Azure Cosmos account with standard (manual) throughput
 
-This template creates an Azure Cosmos account in two regions with options for consistency and failover, with database and container configured for manual throughput that has most policy options enabled. This template is also available for one-click deploy from Azure Quickstart Templates Gallery.
+This template creates an Azure Cosmos account in two regions with options for consistency and failover, with database and container configured for standard throughput that has most policy options enabled. This template is also available for one-click deploy from Azure Quickstart Templates Gallery.
 
 [![Deploy to Azure](https://aka.ms/deploytoazurebutton)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FAzure%2Fazure-quickstart-templates%2Fmaster%2F101-cosmosdb-sql%2Fazuredeploy.json)
 
diff --git a/articles/cosmos-db/manage-table-with-resource-manager.md b/articles/cosmos-db/manage-table-with-resource-manager.md
@@ -37,9 +37,9 @@ This template will create an Azure Cosmos account for Table API with one table w
 
 <a id="create-manual"></a>
 
-## Azure Cosmos account for Table with manual throughput
+## Azure Cosmos account for Table with standard (manual) throughput
 
-This template will create an Azure Cosmos account for Table API with one table with manual throughput. This template is also available for one-click deploy from Azure Quickstart Templates Gallery.
+This template will create an Azure Cosmos account for Table API with one table with standard throughput. This template is also available for one-click deploy from Azure Quickstart Templates Gallery.
 
 [![Deploy to Azure](https://aka.ms/deploytoazurebutton)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FAzure%2Fazure-quickstart-templates%2Fmaster%2F101-cosmosdb-table%2Fazuredeploy.json)
 
diff --git a/articles/cosmos-db/mongodb-pre-migration.md b/articles/cosmos-db/mongodb-pre-migration.md
@@ -25,7 +25,7 @@ If you have already completed the above pre-requisites for migration, you can [M
 
 The following are specific characteristics about Azure Cosmos DB's API for MongoDB:
 
-- **Capacity model**: Database capacity on Azure Cosmos DB is based on a throughput-based model. This model is based on [Request Units per second](request-units.md), which is a unit that represents the number of database operations that can be executed against a collection on a per-second basis. This capacity can be allocated at [a database or collection level](set-throughput.md), and it can be provisioned on an allocation model, or using the [Autoscale model](provision-throughput-autoscale.md).
+- **Capacity model**: Database capacity on Azure Cosmos DB is based on a throughput-based model. This model is based on [Request Units per second](request-units.md), which is a unit that represents the number of database operations that can be executed against a collection on a per-second basis. This capacity can be allocated at [a database or collection level](set-throughput.md), and it can be provisioned on an allocation model, or using the [autoscale provisioned throughput](provision-throughput-autoscale.md).
 
 - **Request Units**: Every database operation has an associated Request Units (RUs) cost in Azure Cosmos DB. When executed, this is subtracted from the available request units level on a given second. If a request requires more RUs than the currently allocated RU/s there are two options to solve the issue - increase the amount of RUs, or wait until the next second starts and then retry the operation.
 
diff --git a/articles/cosmos-db/partners-migration-cosmosdb.md b/articles/cosmos-db/partners-migration-cosmosdb.md
diff --git a/articles/cosmos-db/provision-throughput-autoscale.md b/articles/cosmos-db/provision-throughput-autoscale.md
diff --git a/articles/cosmos-db/resource-manager-samples.md b/articles/cosmos-db/resource-manager-samples.md
