Skip to main content

πŸ›‘οΈ Azure Synapse Spark pool auto-pause is disabled🟒

  • Contextual name: πŸ›‘οΈ Spark pool auto-pause is disabled🟒
  • ID: /ce/ca/azure/synapse/spark-pool-auto-pause-disabled
  • Tags:
  • Policy Type: BEST_PRACTICE
  • Policy Categories: COST

Stats​

not available

Logic​

Description​

Open File

Description​

Ensure that auto-pause is enabled for Azure Synapse Spark pools. Auto-pause pauses a pool after its configured period of inactivity, reducing the cost of idle compute.

Rationale​

Spark pools can continue consuming compute resources when no Spark jobs are running. Enabling auto-pause reduces unnecessary spend while preserving the pool configuration for future workloads.

Impact​

Without auto-pause, idle Spark pools can incur avoidable compute charges. Enabling it can add resume latency to scheduled and interactive workloads, so the delay must suit the workload's startup tolerance.

Audit​

This policy evaluates an Azure Synapse Spark pool only when its Provisioning State is Succeeded.

A pool is marked as INCOMPLIANT when Auto Pause: State is Disabled.

A pool is marked as INAPPLICABLE when its Provisioning State is not Succeeded.

A pool is marked as UNDETERMINED when the provisioning state is unavailable, the auto-pause state is missing or unrecognized, or an enabled pool has no configured delay.

Remediation​

Open File

Remediation​

Before you begin​

Review scheduled and interactive workloads, dependencies, and acceptable resume latency. Choose a delay that avoids pausing the pool between expected jobs.

Azure portal​

  1. Open the Synapse workspace in the Azure portal.
  2. Select Manage and then Apache Spark pools.
  3. Select the affected pool, enable Auto-pause, and set an appropriate idle delay.
  4. Save the change.

Azure CLI​

az synapse spark pool update \
--name <spark-pool-name> \
--workspace-name <workspace-name> \
--resource-group <resource-group-name> \
--enable-auto-pause true \
--delay <idle-delay-in-minutes>

Run representative scheduled and interactive workloads after the change. Confirm that the pool resumes within the accepted startup window and that the next Cloudaware collection reports auto-pause as enabled.

policy.yaml​

Open File

Linked Framework Sections​

SectionSub SectionsInternal RulesPoliciesFlagsCompliance
πŸ’Ό Cloudaware Framework β†’ πŸ’Ό Resource Optimization37no data