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.

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)

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.

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.

add suupport for 'timescaldb'-extension for 'PostgeSQL flexible server' , that is already availble for PostgreSQL Single Server.

Can we have SQL Query Editor for PostgreSQL in Azure Portal where we can query PostgreSQL database?

Similar feature is available for Azure SQL.
https://feedback.azure.com/forums/217321-sql-database/suggestions/19283488-sql-editor-in-azure-portal

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.

It would be a nice feature to allow setting server parameters like pgaudit.log for current active session using query:
set pgaudit.log to NONE;
which can only affect the current session's parameters and leaving the instance level setting as it is so that for new connection/session it uses the default/global server parameters. Aws Rds for Postgresql supports this.

Please add read replicas for Azure database for PostgreSQL Flexible server so we can deploy Disaster Recovery enabled applications.

When will postgres 12 be supported on azure database for postgresql Single Server?

When are timescaledb community edition features are expected with Azure single server for postgresql db, as open source edition in azure managed service db for postgresql does not provide continuous aggregation as well as time compression, which are strong timescaledb extension features.
Time bucketing is also a strong feature of community edition.

Thanks

Include neo4j_fdw foreign data wrapper for Neo4j Graph Database

It'd be great if we was able to turn on ATP for PostgreSQL server via policy. For CosmosDB there is a policy definition 'Deploy Advanced Threat Protection for Cosmos DB Accounts'

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

It will be helpful if we have pgrepack feature in azure database for postgresql to handle bloat.vacuum full will place an exclusive lock on the table and until the vacuum full is completed the transactions related to that table will be held if the vacuum full is performed at table level.So pgrepack is the alternate option where the reorg of table can be performed with out impacting any ongoing transactions.Performing repack during the time when there are less number of transactions to that table will decrease the overhead and can be able to handle bloat in efficient way.