# Missing Auto-Pause on Synapse Spark Pools | Cloud Efficiency Hub Canonical: https://www.pointfive.co/efficiency-hub/inefficiencies/missing-auto-pause-on-synapse-spark-pools A serverless Apache Spark pool in Azure Synapse Analytics is only a definition until a job or notebook session starts it. By: PointFive Updated: 2026-09-28 [Cloud Efficiency Hub](https://www.pointfive.co/efficiency-hub) The short version A serverless Apache Spark pool in Azure Synapse Analytics is only a definition until a job or notebook session starts it. PointFive Research Cloud cost research at PointFive Azure service [Azure Synapse Analytics](https://www.pointfive.co/efficiency-hub/cloud-services/azure-synapse-analytics) Category [Compute](https://www.pointfive.co/efficiency-hub/service-category/compute) Reference CER-0449 Type Inefficient Configuration ## Explanation Why the waste happens and who it affects. From that moment, every node in the instance is billed per vCore-hour, prorated by the minute, until the pool pauses. Microsoft states that billing runs from pool start until the idle timeout, whether or not the nodes are doing work. When automatic pause is disabled, or set to a long idle timeout, nodes keep running after notebooks and pipeline jobs finish. Interactive development makes this worse: Synapse Studio sends keep-alive messages to hold sessions open, so a forgotten notebook can keep a pool alive for hours. Fixed-size pools without autoscale add further idle capacity during light stages of a job. Azure Advisor flags both conditions with 'Consider enabling automatic pause feature on spark compute' and 'Consider enabling autoscale feature on spark compute'. ## Billing model The pricing dimensions that drive this cost. Spark pool charges depend only on how long instances run and how many nodes they use. Pool definition Creating a Spark pool is free; charges start only when a Spark instance is instantiated for a job or session vCore-hours Running instances are charged per vCore-hour for every node, prorated by the minute Idle timeout Billing continues after the last activity until the automatic pause delay expires Autoscale No extra charge; scaling up or down changes node count and increases pool runtime while scaling ## How to detect 5 checks to find it in your estate. - Review Azure Advisor Cost recommendations for 'Consider enabling automatic pause feature on spark compute' and 'Consider enabling autoscale feature on spark compute' on Synapse workspaces - List Spark pools with az synapse spark pool list and flag pools where autoPause.enabled is false or autoPause.delayInMinutes is long relative to how the pool is used - Flag pools where autoScale.enabled is false and nodeCount is well above the minimum of three nodes - Compare the bigDataPools metrics vCores allocated (BigDataPoolAllocatedCores) and Active Apache Spark applications (BigDataPoolApplicationsActive) to find periods where cores stay allocated with no active applications - Review Apache Spark pool vCore-hour cost in Cost Management by pool to find pools whose runtime far exceeds scheduled job durations ## How to fix 5 ways to remove the waste. - Enable automatic pause on every Spark pool with a short idle delay (az synapse spark pool update --enable-auto-pause true --delay \, or the pool's Additional settings in the portal); active sessions must be restarted for the change to apply - Enable autoscale with a minimum and maximum node count so light workloads run on fewer nodes; the minimum cannot be below three nodes - Ask developers to stop notebook sessions when they finish and to shorten the Synapse Studio session timeout, since keep-alive messages hold sessions open - Create separate small pool definitions for development and validation and reserve larger node sizes for performance testing and production, since pool definitions cost nothing - When updating an existing pool, note that forcing new settings terminates all running Spark sessions; schedule the change outside active job windows ## Documentation Vendor references for pricing and configuration. - [Plan to manage costs for Azure Synapse Analytics learn.microsoft.com](https://learn.microsoft.com/en-us/azure/synapse-analytics/plan-manage-costs) - [Apache Spark pool concepts learn.microsoft.com](https://learn.microsoft.com/en-us/azure/synapse-analytics/spark/apache-spark-pool-configurations) - [Automatically scale Apache Spark instances learn.microsoft.com](https://learn.microsoft.com/en-us/azure/synapse-analytics/spark/apache-spark-autoscale) - [Cost recommendations - Azure Advisor learn.microsoft.com](https://learn.microsoft.com/en-us/azure/advisor/advisor-reference-cost-recommendations) - [az synapse spark pool learn.microsoft.com](https://learn.microsoft.com/en-us/cli/azure/synapse/spark/pool) - [Pricing - Azure Synapse Analytics azure.microsoft.com](https://azure.microsoft.com/en-us/pricing/details/synapse-analytics/) ## Related inefficiencies [Browse the library](https://www.pointfive.co/efficiency-hub) - Azure Synapse Analytics CER-0448 ### [Synapse Dedicated SQL Pools Running During Idle Periods](https://www.pointfive.co/efficiency-hub/inefficiencies/synapse-dedicated-sql-pools-running-during-idle-periods) An Azure Synapse Analytics dedicated SQL pool is billed for its data warehouse unit (DWU) level for every hour it is online, regardless of whether any queries run. Compute and storage are billed separately, and pausing the pool releases... Databases - Azure Virtual Machine Scale Sets CER-0314 ### [Fixed Instance Count on Virtual Machine Scale Set Without Autoscaling](https://www.pointfive.co/efficiency-hub/inefficiencies/fixed-instance-count-on-virtual-machine-scale-set-without-autoscaling) Azure Virtual Machine Scale Sets can operate in two modes: manual scaling with a fixed instance count, or autoscaling with dynamic instance counts that respond to demand. When a scale set is configured with manual scaling, it maintains the... Compute - Azure App Service CER-0306 ### [Non-Production App Service Plans Running Higher Tiers During Off-Hours](https://www.pointfive.co/efficiency-hub/inefficiencies/non-production-app-service-plans-running-higher-tiers-during-off-hours) Azure App Service Plans define the compute resources allocated to web applications and are billed continuously based on their pricing tier - regardless of whether the hosted apps are actively serving traffic. In non-production environments... Compute --- Source: the public page above. Product screenshots and illustrative interfaces are examples, not live customer data.