1. Explicitly define spot_bid_max_price in the instance pool

If your pool uses Spot instances, check that the pool configuration includes a valid value.

How to check:

Go to Compute → Instance Pools

Edit the pool

Confirm that spot_bid_max_price is visible and set

If it’s not set, add:

spot_bid_max_price = 100

or whatever value your organization prefers.

2. Override spot_bid_max_price in the cluster policy

If the pool does not enforce the value, the policy must.

Example (fixed value):

"azure_attributes.spot_bid_max_price": {

"type": "fixed",

"value": 100

}

Example (allow a range):

"azure_attributes.spot_bid_max_price": {

"type": "range",

"minValue": 0,

"maxValue": 100

}

This ensures the cluster always satisfies the required attribute.

3. Remove spot configuration from the pool and let the policy control it

If the pool has conflicting spot settings, you can simplify:

Edit the instance pool

Remove any explicit spot_bid_max_price

Set the correct value only in the cluster policy

This avoids double-definition.

4. Check Databricks Runtime version and policy behavior

Older DBR versions sometimes behave differently with inherited policy fields.

If possible:

Use DBR 11.x or newer

Test with a simplified policy first (no hidden attributes)

Then re-apply constraints gradually