Hi Ícaro Sousa
Thankyou for reaching Microsoft Q&A!
We understand the urgency of upgrading compute for your Azure Database for PostgreSQL Flexible Server and appreciate the details you have shared.
Based on the information provided, this behavior is expected for your current configuration.
Your server is running on the Standard_B1MS SKU, which belongs to the Burstable (B-series) compute tier. PostgreSQL Flexible Server does not support in-place vertical scaling from Burstable SKUs to other compute tiers. Because of this platform-level limitation, the Azure Portal does not present any scaling options, and the operation cannot be initiated via the portal, CLI, ARM, or any backend process.
At this time, there is no backend or internal method available to force or manually apply a compute tier change for B-series servers. This restriction is enforced by the service architecture.
Supported resolution:
To upgrade performance, the supported approach is to move to a new server created with the required compute tier (for example, General Purpose or Memory Optimized):
- Create a new Azure Database for PostgreSQL Flexible Server in East US using the desired SKU.
- Migrate your data using one of the supported methods:
- Azure Database Migration Service
- pg_dump and pg_restore
- Logical replication for minimal downtime scenarios
- Update your application connection strings to point to the new server.
- Validate functionality and performance before decommissioning the existing B1MS server.
If future vertical scaling is expected, we recommend using General Purpose SKUs, which support seamless compute scaling without requiring server recreation.
Please let us know if you would like assistance selecting an appropriate target SKU or guidance on the fastest migration path for your workload. We are happy to help you move forward as quickly as possible.