Hi Badr,

Thanks for the detailed follow-up -- this is a genuinely confusing area of the docs, so you are not alone in being tripped up by it.

The short answer: serverless budget policies (Settings > Compute > Serverless budget policies > Manage > Create) are tagging mechanisms for cost attribution, not spending caps. They do not have a "budget amount" field -- you just give them a name and tags. That is expected behavior in the UI you saw.

The account-level budgets (Account Console > Usage > Budgets > Add Budget) are separate -- those do have a dollar amount field and are used for monitoring spend. But they are also alert-only and do not block access.

The docs requirement that says "Access to a serverless budget policy with a nonzero budget" is unfortunately worded in a way that conflates these two concepts. In practice, the requirement is satisfied by simply having a serverless budget policy created and having your user assigned to it (with the "User" or "Manager" role on the policy's Permissions tab). There is no numeric budget value you need to set within the policy itself.

So to confirm your setup:

1. Preview enablement -- sounds good.
2. Serverless budget policy -- create one at the workspace level (Settings > Compute > Serverless budget policies), then go to its Permissions tab and make sure your user (or a group you belong to) is assigned the "User" role.
3. Also verify: serverless compute is enabled for the workspace, Unity Catalog is enabled, and the workspace is in us-east-1 or us-west-2.

If all of that checks out and you still cannot access Agents, the support ticket referencing workspace adb-7405613569341731 is the right move -- it may be a backend provisioning issue that the product team needs to investigate.

Sources:

• Attribute usage with serverless budget policies
• Create and monitor budgets
• Agent Bricks requirements