PostgreSQL 12 has been GA for over 4 months now. Any indication on when it will be supported?
Version 12 contains new features like case-insensitive grouping, better connection security and various improvements that will improve scalability and performance of Large partitioned tables.

The Timescale extension is a year behind on releases. Last time we tried it, it was also far behind, and buggy.
This lack of updates is reason enough for us not to try and use it.

Please commit to keeping Timescale, end extensions in general, up-to-date.

Not having to manage updates outselves is, after all, a large part of the value a managed solution provides.

So far, the notification about the upcoming maintenance is sent 72 hours before the event.
It is too late for us to take an action or ask our end user to be ready about that.
Please send the notification before two weeks if possible.
It will be very helpful if you do that.

In addition, it would be great if there are notifications also when maintenance started and when it was completed.

The unique reason we had to build manually or own PostgreSQL with VMs instead of using Azure PostgreSQL as a service was the lack of support of proximity placement groups.

Now that you are developing flexible server options based in "normal" VM It will be great it PPG are supported so we can address the "high" latency problems we had with the service.

Include neo4j_fdw foreign data wrapper for Neo4j Graph Database

Once version 13 is out, it would be good to get it supported as documentation claims azure will support every major ver (and 12 is still not supported)

For purposes of aligning development/testing of projects hosted on Azure, it would be nice if Microsoft provided docker images for PostgreSQL, perhaps using the Bitnami images as a baseline or guide for setup scripts/options, that match Azure's production versions and extensions.

As the default and bitnami PostgreSQL images don't include many of the extensions supported by Azure, it would be great if MS provided docker images that matched the hosted environment to ensure that a local/dev/qa environment can match Azure's production environment relatively closely.

Please include oracle "oracle_fdw" in order to support oracle connectivity

Currently Microsoft only allows TimescaleDB 1.3.2. Please add 1.6.0 as an option.

We want to keep the transactionally consistent incremental backups for more than 35 days. The automated backups doesn't allow that. Long term backups are taken at weekly (monthly/yearly) frequency and we want backups taken hourly/daily. The export of database via sqlpackage is not transactionally consistent. Hence, an API to copy the automated backups of azure sql databases and managed instances would help us. The similar API is supported by the amazon RDS.

Can you please support the incremental long term backups taken per hour/day of azure sql databases and managed instance databases?

After promoting a replica DB to a standalone server with this command
az postgres server replica stop -y -n -g

The new promoted server name is taken from prompted replica server name (which in most cases the name contains a replica substring and after promotion it raises some ambiguity as a name for master database)

It's exciting to see the improvements Azure Database for PostgreSQL Flexible Server (currently in Preview) has made over the old single server deployment model.

However, at the moment it's missing a critical feature: Azure AD authentication, which is available in the older single server SKUs.

Without this integration, VMs/Apps etc cannot utilize AAD managed identities to securely authenticate against the Flexible Server without using passwords. It's an important feature that I'm sure those who're on Single Server won't want to give up.

Hopefully this can be accomplished by the time Flexible Server goes GA, or at least soon after that.

Please add pgrouting extension supported on Azure Database for PostgreSQL Flexible Server (already present on Single Server).

When can we expect support for the PL/Python extension for the Azure Postgres Database. I would improve overall functionality massively.

We have been trying to move to PaaS from our IaaS set up but the benchmarking and one thing we learned from our experience was the approach one takes to do a real benchmarking and unfortunately it varies from person to person or team to team. Even though there are a lot of recommendations laid out in the community but it would awesome to have a service in house to do a benchmarking. So basically you pick the plan that suits best your consumption pattern best and run Performance Benchmarking against all Relational DB Services provided by Azure.

Neither Service health notifications do specify nor Azure publishes details in the RDS portal about PG minor version upgrades. Please try to enhance the notifications or by any means of communication in providing more details to the end users.

Current Azure Database Migration Guide does not support MSSQL to PostgreSQL migration. We hope this capability will be available in near future.