The India regions are available to customers with a business presence in India.
The India Regions are available to customers with a business presence in India. The West India data center is currently only available to select volume licensing customers and partners. For more information, contact your Microsoft India partner manager or account manager.
Azure Government is available to US government entities to purchase physically and network isolated instance of Azure Government from a Licensed Azure Government Service Provider or Partner with no upfront financial commitment or fee. Or, you can sign up for a free Azure Government trial.
Important: The price in R$ is merely a reference; this is an int'l transaction and the final price is subject to exchange rates and the inclusion of IOF taxes and an eNF will not be issued.
Azure Germany is available to customers and partners in the European Union (EU) and European Free Trade Association (EFTA) and provides data residency in Germany with additional levels of control and data protection with a modest price uplift over global cloud offerings (% varies per service).
At any scale, you can store data and provision throughput capacity. Each collection is billed hourly based on the amount of data stored (in GBs) and throughput reserved in units of 100 RUs/second, with a minimum of 400 RUs/second.
|SSD Storage (per GB)||$- GB / Month|
|Reserved RUs /second (per 100 RUs, 400 RUs minimum)||$-|
For high-throughput and high-storage workloads you can create partitioned collections by defining a partition key at collection creation. A partitioned collection will seamlessly scale out as the quantity of stored data grows and reserved throughput increases.
DocumentDB Emulator (Free)
Download the free DocumentDB Emulator to develop and test applications using DocumentDB from your local machine. Once you’re satisfied with how your application works, you can deploy it by just changing your configuration to point to an Azure DocumentDB instance.
Planet scale with geo-replication
DocumentDB collections can be globally distributed to help you easily build apps with planet scale which means all of your data is automatically replicated to the regions you specify. Your app continues to work with one logical endpoint, while your data is automatically served from the region closest to your users with an intuitive programming model for data consistency and 99.99 availability. Globally distributed collections are billed based on the storage consumed in each region and throughput reserved for each DocumentDB collection x the number of regions associated with a DocumentDB database account. Standard data transfer rates apply for replication data transfer between regions. As an example, say you have a database account spanning three Azure regions and two collections provisioned with 1M RUs and 2M RUs respectively. The total RUs provisioned for the first collection will be 3M RUs (1M RUs x 3 regions) and the second one will be 6M RUs (2M RUs x 3 regions).
High throughput and low latency queries
With DocumentDB you can write a sustained volume of data and it will be synchronously indexed to serve consistent SQL queries using a write-optimized, latch-free database engine designed for solid-state drives (SSDs) and low latency access. Read and write requests are always served from your local region while data is distributed globally. You can further optimize performance by customizing automatic index behavior.
Collections with pre-defined performance and size
Until August 1st, 2017, current customers on S1-, S2-, or S3-sized collections can continue using them with a pre-defined 10GB of storage and throughput quantities that vary with the instance size: an S1 instance provides 250 RU/second and is billed at $-/hr; an S2 instance provides 1000 RU/second and is billed at $-/hr; an S3 instance provides 2500 RU/second and is billed at $-/hr. If you want to reconfigure throughput for these collections, see Changing performance levels using the Azure Portal. If you want to take advantage of partitioned collections, you need to convert your previously created S1, S2, or S3 collections to use the limitless throughput and storage scale described above, as described in Partitioning and scaling in Azure DocumentDB.
Support & SLA
- We provide technical support for all Azure services released to General Availability, including Document DB, through Azure Support, starting at $29.0/month. Billing and subscription management support is provided at no cost.
- SLA: We guarantee at least 99.99% of the time we will successfully process requests to perform operations against DocumentDB Resources. To learn more about our SLA, please visit the SLA page.
- What is a Request Unit?
A Request Unit (RU) is the measure of throughput in DocumentDB. 1 RU corresponds to the throughput of the GET of a 1KB document. Every operation in DocumentDB, including reads, writes, SQL queries, and stored procedure executions has a deterministic Request Unit value based on the throughput required to complete the operation. Instead of thinking about CPU, IO and memory and how they each impact your application throughput, you can think in terms of a single Request Unit measure.
For more information about Request Units and for help determining your collection needs, please go here
- How does Request Unit usage show up on my bill?
You are billed with a flat, predictable hourly rate based on the overall capacity (RU/sec) that has been provisioned under your DocumentDB account during that period.
If you create an account in East US 2 using two single partitions with 500 RU/sec and 700 RU/sec, respectively, you would have a total provisioned capacity of 1,200 RU/sec. You would thus be charged 12 x $- = $-/hr.
If your throughput needs changed and you increased each partition’s capacity by 500 RU/sec while also creating a new partitioned collection using 20,000 RU/sec, your overall provisioned capacity would be 22,200 RU/sec (1,000 RU/sec + 1,200 RU/sec + 20,000RU/sec). Your bill would then change to: $- x 222 = $-/hr.
In a month of 720 hours, if 500 hours are provisioned at 1,200 RU/sec and 220 hours are provisioned at 22,200 RU/sec, your monthly bill will show: 500 x $-/hr + 220 x $-/hr = $-/hr
- If I specify my own performance for a collection how is storage billed?
Storage capacity is billed in units of the maximum hourly amount of data stored, in GB, over a monthly period. For example, if you utilized 100 GB of storage for half of the month and 50GB for the second half of the month, you would be billed for an equivalent of 75 GB of storage during that month.
- What if my collection is active for less than an hour?
You are billed the flat rate for each hour the collection exists, regardless of usage or if the collection is active for less than an hour. For example, if you create a collection and delete it 5 minutes later, your bill will reflect a charge for 1 unit hour.
- When does the billing rate change after I upgrade a collection?
If you define your own performance for a collection and you upgrade at 9:30AM from 400 RUs to 1,000 RUs and downgrade at 10:45AM back to 400 RUs, you will be charged for two hours of 1,000 RUs.
If you select a pre-defined collection performance level and you upgrade at 9:30AM from an S1 collection to an S3 collections and downgrade at 10:45AM back to S1, you will be charged for two hours of S3.
- How do I scale up or scale down throughput per collection?
You can scale up or scale down the number of Request Units for each collection within your DocumentDB account by using the Azure Portal, one of the supported SDKs or the REST API.
- Can I purchase a mix of collections with pre-defined and user-defined performance with a single database account?
Yes, you can have a mix of collections. However, for new applications, it is encouraged to create collections with user-defined performance as they can support large storage sizes and provisioned throughput, as well as a flexible and granular billing model.
- How can I move from a S1/S2/S3 collection to a single partition?
To move a collection of S1, S2, or S3 performance tier to a single partition with the same storage size, see Changing performance levels using the Azure Portal.
To move an existing single collection to a partitioned collection, see Partitioning and Scaling in Azure DocumentDB.
- What do I get when leveraging single partition versus S1/S2/S3 collection?
At an entry point, single partition has more throughput than S1 (400 RU/sec versus 250 RU/sec) at a lower price. You can also scale up to 10,000 RU/sec versus 2,500 RU/sec with S3. The great thing with the new provisioning model is that you can scale by increment of 100 RU/sec so you don’t need to pay for S3 at 2,500 RU/sec when you only need 1,200 RU/sec.