Microsoft Azure Cosmos DB has helped improve the search result quality of our customers' organization. The customer gave us the feedback that they are able to easily find the data they are looking for. It is very quick. That is the best feedback. They have a large amount of data, and they can find it quickly.
Company at a tech vendor with 1,001-5,000 employees
Helped improve the search result quality of our customers' organization
Pros and Cons
- "The customer gave us the feedback that they are able to easily find the data they are looking for. It is very quick."
- "Our customer is very satisfied with it."
- "There are no particular factors that need improvement. There is a little bit of a learning curve with scaling workloads, but it works smoothly."
How has it helped my organization?
What is most valuable?
Our customer is very satisfied with it. Our branch does not use it yet. We used it for a customer, and the customer is very satisfied so far.
What needs improvement?
There are no particular factors that need improvement. There is a little bit of a learning curve with scaling workloads, but it works smoothly.
For how long have I used the solution?
I am still learning it and have only used it for one application so far.
Buyer's Guide
Microsoft Azure Cosmos DB
April 2025

Learn what your peers think about Microsoft Azure Cosmos DB. Get advice and tips from experienced pros sharing their opinions. Updated: April 2025.
849,190 professionals have used our research since 2012.
What do I think about the stability of the solution?
No issues have been reported regarding the stability. It is very fast.
What do I think about the scalability of the solution?
There was a little bit of a learning curve with scaling workloads, but overall, it went smoothly.
How was the initial setup?
I have not had any challenges. However, the configuration done in a session at Microsoft Ignite looked complicated. It would be a bit challenging to do the same configuration.
There is a little bit of a learning curve. The onboarding process for the team took about two weeks.
What was our ROI?
The only feedback the customer gave us was that it was way cheaper than they expected.
What's my experience with pricing, setup cost, and licensing?
The customer had a high budget, but it turned out to be a little bit cheaper than what they expected. I am not sure how much they have spent so far, but they are satisfied with the pricing.
What other advice do I have?
I would recommend this product. I would like my organization to develop and explore it further. I would rate Microsoft Azure Cosmos DB an eight out of ten.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Microsoft Azure
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Last updated: Nov 24, 2024
Flag as inappropriate
IT Service Delivery Manager at DXC
Makes data ingestion, using data in different applications, and connecting with other tools easier
Pros and Cons
- "What I like about Microsoft Azure Cosmos DB is that it's easy to do data ingestion and use the data in different applications. If you talk about business intelligence such as the Power BI tool, it's easy to connect because both are Microsoft products. With Microsoft Azure Cosmos DB, it's easy to connect and do data ingestion."
- "It would be nice to have more options to ingest the data, for example, more file options or more search options. Currently, you can use JSON, but if there were other file types you can use for data ingestion, that would be nice."
What is our primary use case?
The company is using Microsoft Azure Cosmos DB for business intelligence information, specifically for demand management.
What is most valuable?
What I like about Microsoft Azure Cosmos DB is that it's easy to do data ingestion and use the data in different applications. If you talk about business intelligence such as the Power BI tool, it's easy to connect because both are Microsoft products. With Microsoft Azure Cosmos DB, it's easy to connect and do data ingestion.
What needs improvement?
At the moment, because I'm still new in terms of using Microsoft Azure Cosmos DB, I don't have any feedback regarding areas for improvement in the product. So far, it has met all the expectations and needs of my company.
It would be nice to have more options to ingest the data, for example, more file options or more search options. Currently, you can use JSON, but if there were other file types you can use for data ingestion, that would be nice. This is the additional feature I'd like to see in the next release of Microsoft Azure Cosmos DB.
For how long have I used the solution?
I've been using Microsoft Azure Cosmos DB for the past six months.
What do I think about the stability of the solution?
Microsoft Azure Cosmos DB is a stable product.
What do I think about the scalability of the solution?
Microsoft Azure Cosmos DB is a scalable product.
How are customer service and support?
We have a partnership with Microsoft, so the response time of the technical support team for Microsoft Azure Cosmos DB is really good at the moment.
How was the initial setup?
Microsoft Azure Cosmos DB was easy to set up.
What other advice do I have?
I've been using Microsoft Azure Cosmos DB, a cloud DB solution. It's deployed in a cloud environment, on a public cloud with security for ourselves.
My company is a partner of Microsoft and also a reseller.
My advice to people looking into implementing Microsoft Azure Cosmos DB is that it would be good for them to use, specifically if they are looking for a NoSQL database to ingest the data and do data discovery using the data in a BI tool. It's easy to ingest the data and work with the data in Microsoft Azure Cosmos DB and understand that, because it is not a SQL database, which means it's not as structured. You can add data, and then do a data discovery, and use it the best way for you. I would recommend Microsoft Azure Cosmos DB.
My rating for Microsoft Azure Cosmos DB is eight out of ten.
Which deployment model are you using for this solution?
Public Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
Buyer's Guide
Microsoft Azure Cosmos DB
April 2025

Learn what your peers think about Microsoft Azure Cosmos DB. Get advice and tips from experienced pros sharing their opinions. Updated: April 2025.
849,190 professionals have used our research since 2012.
Senior Consultant at ProArch
Is scalable with multiple master file and provides good performance
Pros and Cons
- "The most valuable feature of the solution is that it is scalable with multiple master files."
- "Microsoft Azure Cosmos DB's pricing model is complicated, which people don't understand."
What is our primary use case?
We use Microsoft Azure Cosmos DB for faster databases.
What is most valuable?
The most valuable feature of the solution is that it is scalable with multiple master files. The performance of the solution is also good.
What needs improvement?
Microsoft Azure Cosmos DB's pricing model is complicated, which people don't understand. So, the pricing model should be improved.
For how long have I used the solution?
I have been using Microsoft Azure Cosmos DB for five years.
What do I think about the stability of the solution?
Microsoft Azure Cosmos DB is a stable solution.
What do I think about the scalability of the solution?
Microsoft Azure Cosmos DB is a highly scalable solution, and 15 to 20 people use the solution in my organization.
How are customer service and support?
I rate Microsoft Azure Cosmos DB’s technical support an eight out of ten. They do take some time to get to the root of a problem.
How would you rate customer service and support?
Positive
How was the initial setup?
The initial setup is straightforward and needs a few tools to upload.
What was our ROI?
We have had an ROI with the solution.
What's my experience with pricing, setup cost, and licensing?
The pricing model of Microsoft Azure Cosmos DB is a bit complex.
What other advice do I have?
We are using Microsoft Azure Cosmos DB as a cloud-based solution. Two admins and one manager are required for the deployment and maintenance of the solution.
New users must keep an eye on its pricing models and configure them properly.
Overall, I rate Microsoft Azure Cosmos DB an eight out of ten.
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
Technical advisor and software architect at Technical advisor and software architect
Provides auto-scalability and is a multimodal NoSQL database
Pros and Cons
- "One of the nice features is the ability to auto-scale"
- "I hope they improve the service. Before last year, improvements on Cosmos DB were very slow."
What is our primary use case?
We use different Azure services in the development of our solutions. Some of the services we use are Azure Cognitive Services, ADB2C, and SignalR.
For most of the solutions, we use a mixture of Azure SQL Database and Cosmos DB. We use Cosmos DB when the data size is huge, and we need to scale.
Currently, only two people in my organization are working on this solution: one developer and myself. In the future, I think once the system gets deployed, we will have thousands of users.
What is most valuable?
Cosmos DB solves certain problems that relational databases cannot handle. It's a multimodal NoSQL database, and it's very scalable. One of the nice features is the ability to auto-scale, plus Cosmos DB's API is easy to use.
What needs improvement?
I hope they improve the service. Before last year, improvements on Cosmos DB were very slow. I didn't see many changes in the functionality.
For how long have I used the solution?
I have been using this solution for four years.
What do I think about the stability of the solution?
I would rate the stability as nine out of ten.
What do I think about the scalability of the solution?
It's very scalable and fast.
How are customer service and support?
I had developer support with Microsoft Azure. I faced a problem a few years ago, and they helped me solve it.
How would you rate customer service and support?
Positive
How was the initial setup?
It's very easy to set up Cosmos DB. First, you decide what type of API to use, like SQL, Graph, etc., or if you want support for MongoDB or Cassandra APIs. I usually use SQL API. Once you choose the type of API, you create an account and a database. Then you create containers, and you can easily write queries.
What was our ROI?
I believe there will be a return on investment because using cloud solutions will remove all capital expenses. Cosmos DB's auto-scaling options minimize the cost. Choosing "pay as you go" services cuts costs especially when users are not using the system.
What's my experience with pricing, setup cost, and licensing?
I hope Microsoft lowers the cost further.
Which other solutions did I evaluate?
We evaluated MongoDB and Cassandra,
What other advice do I have?
I would rate this solution as eight out of ten.
The APIs are improving and are easy to use. It is easy to set up a new database, and the auto scalability and support for different models are good features.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Microsoft Azure
Disclosure: I am a real user, and this review is based on my own experience and opinions.
CTO at Kultua
An application with great velocity to make queries
Pros and Cons
- "The best feature is the velocity to make a query."
- "A further simple application is required for Brazil."
What is our primary use case?
I use Cosmos DB for geolocation identification.
If you pass by a market on the street, it sends me your location. My application will then send you a personalized notification about relevant products you can buy at the market.
What is most valuable?
The best feature is the velocity of making queries.
What needs improvement?
I would like to see better documentation for this solution.
The pricing of the solution should be reduced.
For how long have I used the solution?
I have been using Cosmos DB for one year.
What do I think about the stability of the solution?
I would rate stability an eight out of ten.
What do I think about the scalability of the solution?
I would rate scalability a five out of ten.
How are customer service and support?
I would rate technical support a ten out of ten.
How was the initial setup?
The initial setup is straightforward. It's very easy to start a function or application with Azure.
What's my experience with pricing, setup cost, and licensing?
The solution is very expensive.
What other advice do I have?
I would overall rate the solution an eight out of ten.
Which deployment model are you using for this solution?
Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Associate Director at a financial services firm with 10,001+ employees
Provides single-digit millisecond response times but struggles with large amounts of data
Pros and Cons
- "I would recommend Cosmos. It made our lives a lot easier. There's not a big learning curve in order to understand the structure and how to use it."
- "We should have more freedom to tweak it and make our own queries for non-traditional use-cases."
What is our primary use case?
We have a database stored on Microsoft Azure where we fetch records and validate them against the application data that is displayed. We use it as a backend in an application to store data.
Within our organization, there are around 500 people using this solution.
What is most valuable?
There's no specific feature of Cosmos. Basically, we try to query the database. Since it's unstructured data, all the related fields are stored as a single JSON. You don't have to go ahead and hit multiple tables, or multiple containers. Instead, you get all of those things, relationally, stored in a nested JSON — in one single container itself. This way, you don't have to go back and forth to different tables. There are pros and cons with this feature, but often it makes things easier for us.
I am impressed with the TTL (time to live feature) of Cosmos. If we need to perform a manual addition to a container, we just need to configure the time to live. And then based on that, it can be deleted.
What needs improvement?
We should have more freedom to tweak it and make our own queries for non-traditional use-cases.
For how long have I used the solution?
I have been using Microsoft Azure Cosmos DB for roughly one year.
What do I think about the stability of the solution?
Cosmos should be more stable. Sometimes we fetch more than 60,000 records at a time. When we try to fetch large amounts of data, sometimes it breaks-down, requiring us to rescale it. Overall, performance-wise, it needs to be a little more stable.
How are customer service and technical support?
I personally haven't had contact with the technical support. Our solution architects deal with support.
How was the initial setup?
I wasn't involved in the initial setup. We have a DevOps team that was responsible for handling the installation. We are just leveraging it for developmental purposes.
What's my experience with pricing, setup cost, and licensing?
Cosmos should be cheaper. We actually intend to stop using it in the near future because the price is too high — and because of the stability issues.
What other advice do I have?
Overall, on a scale from one to ten, I would give this solution a rating of seven. Aside from the scalability issues, we haven't experienced any other issues.
I would recommend Cosmos. It made our lives a lot easier. There's not a big learning curve in order to understand the structure and how to use it. We were good to go with only one container. Anybody who is new can learn quickly.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Microsoft Azure
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Sr System Support Engineer at Premier Systems
Easy-to-use solution and highly scalable
Pros and Cons
- "It is a scalable product."
- "The initial setup was difficult."
What is our primary use case?
Primarily, people do not have a clear understanding of the cloud and cloud services. Customers are a little bit scared about taking their data onto the cloud, and they think and they assume that it is not safe. So we just make them understand that databases or services on the cloud are more secure than on-premises infrastructure.
What needs improvement?
The performance point can be improved because when we run a search query on our on-premises machine and develop connectivity, a response comes in. But sometimes, the response gets delayed, and it can be due to network latency or something else we are yet to figure out.
Performance and high availability are two features I want to be added in the next release because that is the basic requirement of customers. Mostly, we have customers with the bank and banking institutions, and they want their databases perfectly integrated with the high availability feature.
For how long have I used the solution?
I have been using Microsoft Azure Cosmos DB for less than a year.
What do I think about the stability of the solution?
It is a stable product. I would give it an eight out of ten.
What do I think about the scalability of the solution?
It is a quite scalable product. I give it a nine out of ten. There are more than ten users using this product.
How was the initial setup?
The initial setup was difficult. I would give it a six or seven out of ten.
What's my experience with pricing, setup cost, and licensing?
The pricing depends on the budget allocated to the client; for some, it can be high, and for some not high. But mostly, when the prices are moderate, they are not very high. I would rate it a seven out of ten.
What other advice do I have?
It's a highly scalable, highly robust, and very user-friendly solution. It is easy to set up; the most important point is that it is on a cloud. The solution is also very easy to deploy. Only some connectivity features need to be developed.
I give it an eight out of ten.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Microsoft Azure
Disclosure: My company has a business relationship with this vendor other than being a customer: partner
Azure IoT Developer & Solutions Architecture trainee (AZ-220) at Afrika Tikkun Services
Helps to input data but pricing is expensive
Pros and Cons
- "Microsoft Azure Cosmos DB's most valuable feature is latency."
- "The tool's pricing is expensive."
What is our primary use case?
We use the product to input data that doesn't require structuring.
What is most valuable?
Microsoft Azure Cosmos DB's most valuable feature is latency.
What needs improvement?
The tool's pricing is expensive.
For how long have I used the solution?
I have been using the product since November 2021.
What do I think about the stability of the solution?
Microsoft Azure Cosmos DB is stable.
What do I think about the scalability of the solution?
The product is scalable. My company has eight users.
How are customer service and support?
Microsoft Azure Cosmos DB's tech support is okay.
How was the initial setup?
Microsoft Azure Cosmos DB's deployment is straightforward.
What's my experience with pricing, setup cost, and licensing?
Microsoft Azure Cosmos DB's licensing costs are monthly.
What other advice do I have?
I rate the tool a nine out of ten.
Disclosure: I am a real user, and this review is based on my own experience and opinions.

Buyer's Guide
Download our free Microsoft Azure Cosmos DB Report and get advice and tips from experienced pros
sharing their opinions.
Updated: April 2025
Product Categories
Managed NoSQL Databases Database as a Service (DBaaS) NoSQL Databases Vector DatabasesPopular Comparisons
MongoDB Atlas
Amazon DynamoDB
Amazon Neptune
Amazon DocumentDB
Amazon Timestream
Google Cloud Bigtable
Neo4j AuraDB
Oracle NoSQL Database Cloud
Buyer's Guide
Download our free Microsoft Azure Cosmos DB Report and get advice and tips from experienced pros
sharing their opinions.