Merge pull request #184251 from timsander1/master

add section on provisioning dedicated gateway

Author: PRMerger10

articles/cosmos-db/dedicated-gateway.md

@@ -80,6 +80,14 @@ The dedicated gateway is available in the following sizes:
 > [!NOTE]
 > Once created, you can't modify the size of the dedicated gateway nodes. However, you can add or remove nodes.
 
+There are many different ways to provision a dedicated gateway:
+
+- [Provision a dedicated gateway using the Azure Portal](how-to-configure-integrated-cache.md#provision-a-dedicated-gateway-cluster)
+- [Use Azure Cosmos DB's REAT API](https://docs.microsoft.com/rest/api/cosmos-db-resource-provider/2021-04-01-preview/service/create)
+- [Azure CLI](https://docs.microsoft.com/cli/azure/cosmosdb/service?view=azure-cli-latest#az_cosmosdb_service_create)
+- [ARM template](https://docs.microsoft.com/azure/templates/microsoft.documentdb/databaseaccounts/services?tabs=bicep)
+    - Note: You cannot deprovision a dedicated gateway using ARM templates
+
 ## Dedicated gateway in multi-region accounts
 
 When you provision a dedicated gateway cluster in multi-region accounts, identical dedicated gateway clusters are provisioned in each region. For example, consider an Azure Cosmos DB account in East US and North Europe. If you provision a dedicated gateway cluster with two D8 nodes in this account, you'd have four D8 nodes in total - two in East US and two in North Europe. You don't need to explicitly configure dedicated gateways in each region and your connection string remains the same. There are also no changes to best practices for performing failovers.