Azure Database for PostgreSQL Reviews

My main use cases for Azure Database for PostgreSQL came from a personal project to scratch an itch, and it was the easiest one to go grab.

I appreciate how easy PostgreSQL is to get running locally. You can grab a container and run it, as opposed to the old days when having a local database was very challenging and required special scripts that would take hours to run. Now I can grab a container and be good to go in seconds, which makes life a lot simpler and has influenced my application development process.

My experience with the monitoring and management tools provided by Azure Database for PostgreSQL has been minimal, but the ability to see what's there and tweak it is a good feature to have.

Azure Database for PostgreSQL security features such as encryption and advanced threat protection are very helpful, especially when you have medical data and personally identifiable information that you need to protect. The fact that these security features are embedded certainly makes my job easier. The ability to encrypt personally identifiable information and health data at rest is what my company finds most valuable.

Azure Database for PostgreSQL integration with other Azure services has impacted my overall cloud strategy. Depending on the customer, having it there and having it be easy to utilize, with the ability to switch to it, is valuable. I have conversations where customers are using one data store, but maybe that's not the right data store and perhaps another should be used instead. The fact that you can do this with such a low barrier of entry makes it simpler to have those conversations. It isn't a situation where you have to hire somebody who knows how to stand this up; you just click and now you have that data store.

Azure Database for PostgreSQL integrations have been most beneficial to my operations with Azure Kubernetes Service and Container Apps. The different eventing systems provide another valuable conversation point about which of the three different eventing systems should be used. The different tiers available allow you to think in terms of crawl, walk, run. You don't have to go straight to the heaviest duty enterprise level until you need it. When you're just getting started and trying to find market fit, you can use something simpler that gets you up and running with some training wheels and fewer knobs you need to worry about. When demand requires it, you can graduate to the next tier up.

Azure Database for PostgreSQL has helped reduce infrastructure costs depending on the client.

Azure Database for PostgreSQL can be improved in ways I'm very curious to explore with Horizon. I'm interested in seeing how the fully enterprise-hardened features change things and where that blurs the lines with other data stores available on Azure, as that will probably make it harder to choose between solutions.

I've been working in my area of expertise for almost thirty years.

Compared to my previous expenses for maintaining an on-premise PostgreSQL database, Azure Database for PostgreSQL is far easier, far simpler, and far cheaper in my opinion. Having to maintain staff whose job is the care and feeding of the database and the time it takes to get a local version spun up for somebody was a burden. Being able to do that with some clicks is a huge win. Additionally, you don't have to worry about whether it's up to date, because it always is.

I have previously used an on-premise database.

Azure Database for PostgreSQL has influenced the adoption of artificial intelligence technologies in my company. Artificial intelligence is definitely in almost every conversation that happens these days. The clients I've worked with haven't used it yet, but it's at least in the air. That's another thing that will eventually have to tie in, depending on the customer.

Azure Database for PostgreSQL has had a significant impact on my company's data protection strategy compared to previous solutions. Not having to manage it yourself is a huge win. You can shift that responsibility to someone else who does it at scale and can hire the best people in the world to do it. It's one less thing that you need to spend cycles on, so it's just an overall win.

My experience with the migration process to Azure Database for PostgreSQL, particularly in terms of the technical expertise required and support received from Microsoft, is generally straightforward as I've seen it. It helps to have people who've done it before and know the pitfalls and can help you speed things up, but by and large, it's a fairly straightforward proposition. How much data you have does matter for the timeline.

I would rate Azure Database for PostgreSQL overall a nine out of ten, and we will see how the Horizon offering works.

My advice to other companies considering Azure Database for PostgreSQL is to choose the data store that makes sense for your use case. I've noticed a tendency to just grab whatever database was used last time, but maybe that's the right choice and maybe it's not. I've seen instances where people choose a data store because they think it's cool or they want to play with it and put it on their resume. Resume-driven design is a real thing. Make sure the data store you choose is the right one for your use case. If you're doing microservices, you don't have to have one-size-fits-all. If a service needs a time series database, then use that. If a service would benefit from graphs, then use graphs. Use the data store that fits your needs.

Public Cloud

Microsoft Azure

My main use cases for Azure Database for PostgreSQL are to use it as data storage for a lot of apps, involving different app services, functions, and other platforms, where we bring in and process a lot of data for integrating different cloud platforms. We have document management systems where we're pulling back-end data from on-premises systems or other cloud systems, using many Azure functions and different app services to pull data through Azure Database for PostgreSQL to track and sync with other systems.

Azure Database for PostgreSQL has influenced my application development process by enabling me to take some of what we used to do on-premises, with PostgreSQL hosted in virtual machines, and transition that process into a SaaS solution. This transition means we don't have to spin up a virtual machine for installation and configuration, streamlining the process and making it faster and allowing us to script much of it out, so whenever our developers need a new environment, it's just a couple of clicks and an automation, resulting in a consistent build every time.

The impact of moving to Azure has been significant; we can take what was already built on-premises and split it into services without needing to build a whole server, making the deployment much lighter, faster, and scalable.

My favorite feature about Azure Database for PostgreSQL is that it's quick and easy to set up and deploy, without a lot of overhead or configurations, making it fast and easy to include in any of our builds. When we automate for scaling up or scaling out, it's easy to do that automation side of it, and since it's PostgreSQL, it's lightweight and simple for the basic things we need to do from a data perspective, so it works well.

A benefit that Azure Database for PostgreSQL has for my company is that it serves as a native back-end solution for several utilities and tools that we use, making it a quick and easy solution that we deploy as part of larger problems or solutions. This capability helps us scale economically because we're often reselling these solutions, keeping our costs down and making deployment and rollout easier.

My impression of the security features in Azure Database for PostgreSQL, such as encryption and Advanced Threat Protection, is that it has met all of our security requirements; anytime our apps go through a security review, we've never had any issues while using identities and registering the app. It has been great, trusted, and it works without needing extra security reviews for implementation.

Regarding improvement in Azure Database for PostgreSQL, I would have to discuss that specifically with our lead developers.

I have been using Azure Database for PostgreSQL for approximately seven or eight years.

I can assess the stability and reliability of Azure Database for PostgreSQL as excellent; we have no issues or problems with it. Occasionally, we experience throughput issues due to bandwidth limitations of client setups with Azure, which have limited connections, but as far as the service itself goes, it has been rock solid.

In some ways, Azure Database for PostgreSQL has facilitated adopting AI technologies in my organization, mainly because we can take output from AI processes, particularly document and contract summarization, and dump that data into a database for later retrieval. We are only beginning to experiment with this and hope for more native solutions within the AI tools, which are now coming, and PostgreSQL has allowed us to lay the groundwork for this. I rate this product a 10.

Public Cloud

Microsoft Azure

We are an insurance company with many applications that handle policy processing, so we use Azure Database for PostgreSQL for those applications. We have different usage for every database, and for all of our in-house applications, we use Azure Database for PostgreSQL.

We have monitoring for Azure Database for PostgreSQL. Our on-premises monitoring is connected to LogicMonitor, which we use as a centralized monitoring tool. If a database has any task that has been interrupted or any connection issue, it will alert LogicMonitor, and we have a centralized panel for all the alerts.

Regarding Azure Database for PostgreSQL security, I have not received any report or incident indicating a breach to our database. However, I cannot definitively say this is because of Azure Database for PostgreSQL or our overall security ecosystem.

I am not certain if Azure Database for PostgreSQL helped reduce infrastructure costs because we are in the process of migrating to the cloud. Our on-premises cost and on-premises infrastructure cost is fixed, and we pay an annual fee to the data center. Once we migrate to Azure, I could check the cost bill, but I have not yet. This is not my main responsibility. The management definitely did an estimate, and I think it will probably save some money for them, which is why they chose to migrate. That is my assumption.

I am not a DBA, so for my experience with Azure Database for PostgreSQL on the database side, I do not know if it has certain capabilities. The most significant thing I do and communicate with our DBA about is performance tweaking. I think we still have to do it regardless because you still build on a server with the OS level on it. I do not know if in the future the database will have its native OS layer instead of using Microsoft and dynamically assign the CPUs and memories based on the transaction or task it is running. This could save us some time so it does not have to use sysadmin's time to constantly tweak and assign the CPU. Currently, most databases will try to use all the CPUs available and use all the memories available. We try to give all the databases one hundred percent of the hardware capacity, but sometimes because the OS layer itself will need some resources. If the database used everything, when we try to remote to it, sometimes you will just see a black screen. If we can make this better, why not?

On the deployment side of Azure Database for PostgreSQL, it is easy to deploy. The deployment of Azure Database for PostgreSQL is pretty straightforward, and there is not much to specify. It is very basic. Usually I will work with the DB team, they will give us all the instance, all the SSA, and all the accounts. We basically deploy, install it, and deploy it.

The deployment of Azure Database for PostgreSQL usually takes one hour for us to deploy it. I do not know if the deployment time for Azure Database for PostgreSQL is similar to other solutions. For MS SQL, I think it is also the same amount of time. For AWS, I cannot say because it is a cloud team thing, and I deploy on-premises.

I am the admin part, so I basically deploy Azure Database for PostgreSQL. I do not actually directly use the product, but I do the deployment.

I cannot say much about the features of Azure Database for PostgreSQL because I am not the actual user and just do the deployment.

Azure Database for PostgreSQL has influenced our application development process, which is the reason why we stick with Azure Database for PostgreSQL. Otherwise, we would not use it as heavily. Our company's strategy is always to not put all eggs in one basket. We have Azure Database for PostgreSQL, MS SQL as well, and some AWS databases. We have all kinds of DB and also MongoDB.

For our solution using Azure Database for PostgreSQL, I have never gotten any complaints from any incidents, security incidents, or any technical troubles. It is very rare, but incidents are code-based and not database-related. We have some code-based incidents because the application has some bugs, so we have to fix them. Based on the database itself, the most tweaking we did was the performance. We have to monitor the performance of all the transactions and all the journals, and we have to do tweaking such as determining how many CPUs and memory we have to reassign to those servers and applications. That is the only thing that we actually deal with. The patches happen on the Windows server side because we use Microsoft servers. Most of the patches happen on the Windows server side, though we have Linux servers too. When Microsoft releases some patches, it will sometimes interrupt some connections, but it is not a PostgreSQL issue and is just a server issue.

We are a hybrid environment including our on-premises AD. We are in the process to migrate and try to get rid of our on-premises AD and completely use Entra as our main identity management solutions. Currently, we are hybrid and everything is Microsoft. We also use Okta as well. We have Okta and Entra. The hybrid arrangement has its advantage because it really connects our old legacy technology. Everything has to be on-premises because we have not had time to completely convert it to cloud apps yet. The hybrid approach creates a bridge to both worlds. A native cloud approach actually has more advantage because it is easy to deploy, faster to deploy, and easy to recover and roll back. It is more agile and more convenient for us. It really shortens the time for us to deploy on-premises. When you try to deploy something on-premises, especially when a new product comes in, you have to get the hardware, set up all the firewall rules on-premises, and then deploy all the applications on those servers. Because we moved to AWS and moved to Azure, everything is basically just policies, and you can define everything in the cloud. It is way faster and more convenient for us. I gave Azure Database for PostgreSQL a rating of nine.

Hybrid Cloud

Microsoft Azure

We have a few custom-built applications where we use Azure Database for PostgreSQL as the database layer. It is not used for Azure Database for PostgreSQL because it's for an online service.

Horizontal scaling has helped manage our workloads, making it easier for us to stay cost-efficient while also scaling when we get more traffic on our application. Our applications often don't get as much traffic, so we can scale down in terms of cost efficiency by utilizing Azure Database for PostgreSQL. If there is a reason why the traffic goes up, it scales up without our hands on the service.

Azure Database for PostgreSQL is fully managed, so I don't have to manage it on my own. That's the main thing from my point of view.

When it comes to network integration, we always try to have everything in a private network. There were different options on how you can deploy it, and it was a bit difficult to understand what the right option was for us.

It's not so easy to replicate it to another region or something of that nature. At least, the last time I had my hands on it was one or two years ago, so perhaps things have changed.

I have been using Azure Database for PostgreSQL for three or four years.

We have not had any outages that I'm aware of with Azure Database for PostgreSQL, so it's working well.

Azure Database for PostgreSQL is not our main database, so it's working well for the purpose of scaling with the growing needs of our company.

Microsoft support for Azure Database for PostgreSQL rates about four out of ten based on my experience. You always get the same questions with Microsoft support, and it's not really straightforward. We already pay for better support. It was worse before, but now it's still worse, not as bad as before. It really depends on which team or which person takes over the case. We have a few good experiences, but the majority is not so good.

Neutral

For the service I had in mind, I did not use another database prior to adopting Azure Database for PostgreSQL. This custom-developed application was developed by an external company for us, and the technology and database were already chosen.

The experience with pricing, setup costs, and licensing of Azure Database for PostgreSQL was straightforward from my point of view. There is some marketplace licensing involved.

I have been involved in deploying and implementing Azure Database for PostgreSQL. We deployed the whole project through Terraform, and it worked for Azure Database for PostgreSQL with no issues.

To be honest, I don't know how much money we're saving by horizontally scaling up and down in terms of return on investment in Azure Database for PostgreSQL. I think it's mainly operational cost that we save.

I personally did not consider any other database for this project.

That's something I would need to ask our developers regarding how Azure's integration with other services has impacted our application development. I have not realized other benefits from using Azure Database for PostgreSQL. This review received a rating of 8 out of 10.

Private Cloud

Microsoft Azure

We are building enterprise solutions mainly across healthcare but also in other industries like retail and financial services.

PostgresSQL is acknowledged as an incredibly powerful industry leader. We've built critical pieces of national infrastructure in the UK that rely on Postgres. A version of Postgres on Azure that's easy to adopt enables us to innovate. The addition of AI extensions is even more exciting. It's a significant opportunity for us.

While we haven't implemented any AI features yet, we believe that will help our development because of the platform's simplicity. The ability to write code and deploy applications using standard Azure principles will be a game changer, simplifying integration and deployment. 

Azure Database is simple and easy to use. We followed the prescribed training and upskilled 10 engineers. They think it's straightforward. They've already got PostgreSQL skills to optimize the solution, so they know what to do. It was easy to get started quickly and become effective.

My team speaks highly of the platform's observability and monitoring features. It's as efficient as an enterprise needs it to be and. has all of the tooling and telemetry necessary to run an enterprise database.

We take security seriously. The team has looked at the security features, and nothing has been flagged to us. My takeaway as a CTO is that they're comfortable with the security posture, the features, the observability, alerts, and now it integrates into the rest of the Azure landscape.

The OpenAI integration and extensions have massively simplified integrating AI into a database. PostgreSQL's native vector capabilities are also incredibly powerful. 

The critical service is the Azure OpenAI service. It would help to make it simpler and easier to integrate with that or cognitive services.

I have been using Azure Database for PostgreSQL for probably three months.

We don't have a solution in production, but there have been no complaints about latency or performance. However, we haven't got any stats to back that up or anything hard. It's all anecdotal based on the opinions of 10 hardcore developers, including experienced database engineers. 

So far, we have encountered no scalability concerns. However, we can see how well it scales after we deploy it for some large enterprise customers or big government organizations. No one is suggesting that we can't scale to, you know, this to run big critical national infrastructure projects.

The experience with support has been fantastic. The documentation and training we've received through Microsoft Learn on how to migrate, deploy, and manage the solution is exceptional. 

Positive

We have used PostgreSQL extensively on-premise and have migrated it to the cloud, expecting enhanced security and control in Azure compared to on-premise solutions.

The initial setup was seamless, and the quality of the training was commendable. 

We have used products like Redis Cache, which is powerful but expensive. Now, we use embedded PostgreSQL vectors, which will undoubtedly reduce the TCO by using a much more cost-effective solution.

The pay-as-you-go pricing model plays a critical role in managing database-related costs and resource allocation. We build using Infrastructure as Code (IAC) and maintain a focus on FinOps to control Azure service costs. Some clients are pushy on price. It's critical to automate it, so we're just using it when appropriate and switching it off in certain scenarios.

Previously, we used products like Redis Cache, which is powerful but costly. Now, Azure Database for PostgreSQL's vector embeddings mean we prefer it over Redis Cache.

I rate Azure Database for PostgreSQL 10 out of 10. 

Public Cloud

Microsoft Azure

We're a managed service provider using Azure Database for PostgreSQL to deliver services to 300 customers, so there are potentially 300 different use cases. We use it as a normal database instead of MySQL or Azure SQL because PostgreSQL performs well, especially with the flexible server. 

We do many things in the cloud with Kubernetes containers, and our customers can use a containerized version of Postgres. We abstract it so that it runs in Azure itself instead of being part of the Kubernetes cluster. It makes sense to go from Postgres to Postgres.

Our organization's database uptime has improved after implementing Azure Database for PostgreSQL, particularly with the flexible server's redundant configuration capabilities, which allow for failovers and read-only configurations. This results in greater resilience and uptime for end customers.

The most valuable features of Azure Database for PostgreSQL are its networking capabilities, which allow for integration with other Azure services. It's easy to configure with the flexible server we used. The newest iterations of Postgres are easier and easier to upgrade.

Azure Database for PostgreSQL can be improved by allowing quicker scaling without blips. It would help if it were more dynamic and required less planning. You can't just scale back performance and storage as needed. Adding flexible scaling capabilities would enhance performance, making it greener and more efficient.  Additionally, addressing the reliability issue where the database might crash during sudden performance peaks would be beneficial.

Azure PostgreSQL's monitoring and management tools are constantly improving, but costs can be challenging. Azure Monitor provides the default metrics, but if you want all the metrics, you need to enable all logging, which will have more cloud costs than the database itself. 

I have been using Azure Database for PostgreSQL for a couple of years.

There is a stability issue where, if the database usage peaks quickly, it may crash and require intervention to restore functionality. It does not auto-heal or self-heal in such situations.

Previously, we used PostgreSQL running in a container on a different platform, not on-premises.

Sometimes, we use Azure technologies for migration, and other times, we use customer technologies. The migration process did not require support from Microsoft.

Azure Database for PostgreSQL has reduced our total ownership cost, but I can't provide the exact figure because it varies among customers. Overall, PostgreSQL is cheaper and more efficient. It offers at least 25 percent cost savings compared to maintaining on-premises databases.

The pricing experience is positive. Azure Database for PostgreSQL reduces the need for hardware investments, and the pay-as-you-go pricing model positively affects database-related costs by allowing us to start small and scale as needed.

I would rate Azure Database for PostgreSQL an eight out of 10. Its scaling capabilities could be improved, and ensuring reliability during sudden usage spikes is needed.

Public Cloud

Microsoft Azure

We have turned on pgvector, which is an extension for the vector search. We use PostgreSQL as the RAG database for the Gen AI application.

We use it as a RAG database. It coordinates our chunks and connects them with the embedded model to organize them into high-dimensional space. The performance of our RAG application is very good. We have 96% satisfaction.

It facilitates AI technology adoption by coordinating chunks and connecting them with the embedded model.

We are a bank. Our information is mainly stored in a SQL database. Azure Database for PostgreSQL offers a way for our colleagues to quickly understand vector search by using the combination of RDB and the vector search extension. This means we do not have to learn vector databases at the beginning. We can just turn on the extension, and it has the vector search right away.

It helps us to retrieve the context. I use it a lot. It is easy to execute an SQL query.

It offers an easy vector search, which is helpful, but does not offer knowledge graph functionalities.

It is easy to use and optimize. It is very easy for us to understand how a chopped chunk can be translated into embedding. We can put some additional value into the chunk itself.

They can offer more RAG extensions. Currently, it only has the vector search. 

It does not presently support knowledge graph functionalities as Neo4j does. It also does not offer some tools to improve indexing the way other vector databases offer.

We have been using it for a year.

The stability seems fine. We have not noticed any issues. We have generative AI applications, and we have not noticed any latency.

It scales well with the workload.

We handle most implementations in-house, without extensive reliance on Microsoft's technical support.

Neutral

We previously used an on-premise PostgreSQL database. Azure Database for PostgreSQL provides a console to monitor PostgreSQL.

We are now considering using Neo4j in parallel for its knowledge graph capabilities.

We do not pay for a full-year subscription because our usage is still at the beginning phase and not much. The pay-as-you-go model works well for us.

I would rate Azure Database for PostgreSQL an eight out of ten.

We started using Azure Database for PostgreSQL about five to six years ago. Initially, we were doing an on-premises Kubernetes setup, but since Azure was accepted at the bank, we moved to Azure. We currently run fairly large clusters with around five clusters spanning three environments, along with disaster recovery aspects and smaller clusters for specific products.

Having a relational database like PostgreSQL, which is cheaper than competitors, is beneficial. We have extensive experience with SQL Server and Sybase SQL Server, but the applications mainly care about the backend database's total cost. As long as it meets the needs, it serves its purpose well.

While the flexibility of the server for financial reasons is understandable, better switching between primary and backup would make transitions smoother. I noticed an issue where the primary refuses to launch if the backup isn't running. Another improvement could be the ability to scale storage back down after scaling up, as we can do with compute resources. It's likely a financial restriction from Microsoft.

We started using Azure Database for PostgreSQL about five to six years ago.

When not abused and sized correctly, performance has been very good. We are holding large volumes of data, and it has been doing well for us.

We can scale up compute and scale it down, but once storage is allocated, there is no way to scale it back down.

Given the amount of money we spend with Microsoft, we receive excellent support. As a big bank, we get prompt responses, especially for high-severity issues. Once we open a support case, we have people engaged within about 20 minutes, especially for a Sev 1 issue.

Neutral

I have a lot of experience with SQL Server from a previous position and even more with Sybase SQL Server from a previous role.

We abstracted the normal Azure creation mechanisms using a PowerShell-based system. I create a JSON config with the server details, and it quickly creates them. Initially, running the templates required frequent updates as configurations drifted in a young system. Now, it's managed behind the scenes, and I don't experience the pain.

It doesn't take much to maintain. We have a couple of individuals managing it alongside their other responsibilities. It operates like an internal open source project, where anyone can contribute. If an issue arises, I communicate it to them, and they address it.

Overall, Azure Database for PostgreSQL has been good for us. When sized properly, performance has been great, and we handle substantial data volumes. I would rate it an eight or nine.

Hybrid Cloud

Microsoft Azure

Our primary use cases of PostgreSQL are migrations for our customers. We specialize in Oracle to Postgres migrations. We offer customers the potential advantages and cost savings of migrating to Postgres.

Postgres has helped us innovate and stay competitive. It has dramatically reduced our application development time, improving our efficiency by about 40 percent. It has cut costs by about 60 percent compared to on-premises applications. 

The effective integration of Postgres with Microsoft products, especially with the inclusion of AI features in Azure AI, is significant for our applications. Postgres is not just a database but includes robust AI features that aid in innovation and competitiveness. PostgreSQL's seamless integration with other Azure services and ability to handle numerous integrations seamlessly has been very beneficial. 

Performance is one area that has constraints for our customers. I believe there could be improvements in the mirroring part and Change Data Capture (CDC).

I have used Azure Database for PostgreSQL for two years.

We are monitoring database uptime following the implementation.

Additionally, the scaling options with FlexServer provide us with the flexibility we need based on application complexity.

We do provide feedback to the Microsoft community, and regular communication with their engineering team allows us to gain insights and evaluate our tools.

Positive

We previously used on-premises Oracle and SQL databases. We moved from Oracle to Postgres due to the latter's feature set and open-source advantages.

We have a dedicated development team focused on enhancing our in-house migration product by gathering feedback and insights from Microsoft.

There is a 40 percent increase in efficiency, resulting in enhanced ROI.

The pay-as-you-go pricing model has significantly lowered our database-related costs. We've reduced costs by 60 percent compared to maintaining on-premises solutions.

I would rate Azure Database for PostgreSQL eight on a scale of 10.

Hybrid Cloud

Microsoft Azure

At a prior agency, we used the solution primarily for reporting, incident situation awareness, and providing public information regarding different safety programs. It's used for general information sharing within the public domain, and it is nothing too complicated or in-depth.

We don't need to worry about maintenance or updating servers. My use case is querying the data, so it doesn't affect me much. It's a lot easier to leverage other Microsoft technologies outside of our network.

Azure Database has become easier to use over time. Initially, there were many limitations, especially concerning permissions, but now it is straightforward to create a database by clicking a few buttons and ensuring security and user authentication. 

In terms of integration, we already have SharePoint online, and we're starting to explore PowerApps and PowerFlow. It's all seamless. The ease of integrating PostgresSQL and licensing purposes plays a significant role, making it a comfortable choice for the organization.

Perhaps a minor improvement could be made in simplifying user additions, allowing for an easier process rather than scripting it out. However, scripting is not a significant issue.

I have been using SQL on Azure for about 10 years.

Overall, I have not encountered any real latency issues or stability concerns since we do not push SQL on Azure to its limits; our internal database handles more complex applications.

From the limited use cases I've encountered, SQL on Azure is pretty scalable, and I have not faced any issues.

Microsoft's expertise or customer service is really a non-factor, because connecting to another type of database system is possible if needed. However, the organization's comfort with Microsoft's practical solutions keeps us with them.

Positive

Previously, I used databases like MySQL, but the organization's decision to go with Microsoft products was based on the ease of integration and their comfort in working with the company.

There were some initial challenges with authentication during migration, but it's much easier now to integrate with our existing systems.

The solution has helped us reduce our organization's total cost of ownership a little bit, but I can see it decreasing more in the future, given how everything is moving into the cloud.

I'm not familiar with the licensing aspect, as I do not handle it. However, pricing, licensing, and setup costs are not major issues.

I rate Azure Database for PostgreSQL nine out of 10. 

Microsoft Azure