# Overprovisioned Azure Database for PostgreSQL flexible server Canonical: https://www.pointfive.co/efficiency-hub/inefficiencies/overprovisioned-azure-database-for-postgresql-flexible-server Azure Database for PostgreSQL - Flexible Server often defaults to general-purpose D-series VMs, which may be oversized for many production or... By: Balazs Engedi Updated: 2026-09-28 [Cloud Efficiency Hub](https://www.pointfive.co/efficiency-hub) # Overprovisioned Azure Database for PostgreSQL Flexible Server The short version Azure Database for PostgreSQL - Flexible Server often defaults to general-purpose D-series VMs, which may be oversized for many production or development workloads. [Balazs Engedi](https://www.linkedin.com/in/engedib/) FinOps Specialist @ KPN Azure service [Azure Database for PostgreSQL - Flexible Server](https://www.pointfive.co/efficiency-hub/cloud-services/azure-database-for-postgresql---flexible-server) Category [Databases](https://www.pointfive.co/efficiency-hub/service-category/databases) Reference CER-0148 Type Overprovisioned Resource ## Explanation Why the waste happens and who it affects. Many PostgreSQL workloads do not need high sustained CPU and can run on fewer vCores. Memory-optimized (E-series) instances reduce cost only when fewer vCores with more memory per vCore replace a larger general-purpose server, and burstable (B-series) instances suit development, test, or low-concurrency workloads. When actual usage consistently falls below the provisioned capacity - particularly CPU - the deployment may be overprovisioned, resulting in unnecessary compute charges. Choosing the wrong VM family or size leads to silent overspend, especially in long-lived database environments. ## Billing model The pricing dimensions that drive this cost. - Charged based on: - Provisioned compute (vCores and instance family) - Provisioned storage (per GB/month) - Pricing varies significantly by VM series (e.g., D-series vs. B-series vs. E-series) - Charges accrue continuously, regardless of actual CPU or memory usage ## How to detect 4 checks to find it in your estate. - Analyze average CPU and memory utilization of PostgreSQL Flexible Server instances - Determine whether current performance requirements justify the provisioned instance size - Identify servers running on D-series or other general-purpose SKUs that could be supported by B-series or E-series - Validate compatibility and performance before considering a shift in instance family ## How to fix 4 ways to remove the waste. - Resize the PostgreSQL Flexible Server to a smaller or more suitable VM family based on actual workload behavior - For low-CPU workloads, first reduce vCores within the same family. Consider E-series (memory-optimized) only if you can cut vCores while preserving memory, since E-series costs more per vCore than D-series, and keep B-series (burstable) for dev/test or low-concurrency workloads, as Microsoft does not recommend Burstable for production - Review usage patterns quarterly to ensure the selected SKU remains aligned with performance needs - Avoid unnecessary performance buffer unless justified by workload spikes or growth ## Documentation Vendor references for pricing and configuration. - [Azure Database for PostgreSQL - Flexible Server Pricing azure.microsoft.com](https://azure.microsoft.com/en-us/pricing/details/postgresql/flexible-server/) - [Compute options - Azure Database for PostgreSQL learn.microsoft.com](https://learn.microsoft.com/en-us/azure/postgresql/compute-storage/concepts-compute) ## Related inefficiencies [Browse the library](https://www.pointfive.co/efficiency-hub) - Azure Database for PostgreSQL - Flexible Server CER-0443 ### [High Availability Enabled on Non-Production PostgreSQL Flexible Servers](https://www.pointfive.co/efficiency-hub/inefficiencies/high-availability-enabled-on-non-production-postgresql-flexible-servers) High availability on Azure Database for PostgreSQL flexible server provisions a standby replica, in another availability zone (zone-redundant) or the same zone (same-zone), with the same vCores, storage and network configuration as the... Databases - Azure Database for PostgreSQL - Flexible Server CER-0444 ### [Non-Production PostgreSQL Flexible Servers Running Outside Working Hours](https://www.pointfive.co/efficiency-hub/inefficiencies/non-production-postgresql-flexible-servers-running-outside-working-hours) Development, test, QA and demo servers on Azure Database for PostgreSQL flexible server are usually needed only during working hours, yet many run 24x7 with no stop schedule. Compute is billed for every hour the server exists in a running... Databases - Azure Database for PostgreSQL - Flexible Server CER-0445 ### [Missing Reserved Capacity for Steady-State PostgreSQL Flexible Servers](https://www.pointfive.co/efficiency-hub/inefficiencies/missing-reserved-capacity-for-steady-state-postgresql-flexible-servers) Production Azure Database for PostgreSQL flexible servers typically run around the clock for years, yet many estates pay the pay-as-you-go vCore rate for all of them. Reservations and savings plans are often bought for virtual machines... Databases --- Source: the public page above. Product screenshots and illustrative interfaces are examples, not live customer data.