Budget Policy - Service Principals don't seem to be allowed to use budget policies

enr0c — Wed, 20 Nov 2024 08:33:09 GMT

Objective

Transfer existing DLT pipeline to new owner (service principal). Budget policies enabled.

Steps to reproduce

Created a service principal
Assigned it group membership of a group that is allowed to use a budget policy
Ensured it has access to the budget policy
Moved the ownership of DLT pipeline to service principal

Issue:

Pipeline is not running and the error says: Pipeline "Run As" identity does not have access to selected budget policy. Can you please advise?

Thanks

Re: Budget Policy - Service Principals don't seem to be allowed to use budget policies

Abishek — Tue, 10 Dec 2024 16:39:47 GMT

“Thanks for your question! I’m looking into this and will get back to you.”

Re: Budget Policy - Service Principals don't seem to be allowed to use budget policies

mark_ott — Tue, 04 Nov 2025 17:56:38 GMT

The error message "Pipeline 'Run As' identity does not have access to selected budget policy" typically indicates that, while your service principal is properly configured for general pipeline ownership, it’s missing explicit permission on the budget policy itself. Assigning group membership or workspace access alone is not sufficient for budget policy usage with service principals in Databricks DLT pipelines.

Required Steps to Resolve

You must explicitly assign the service principal as a user (can use) or manager (can edit/manage) on the budget policy in question. This must be done directly on the policy's permissions page or via API:
- Go to the budget policy’s page in the Databricks console.
- Click the Permissions tab.
- Add your service principal as an identity (not just via group membership).
- Assign it the appropriate role, ideally user for running pipelines.
- Save changes.
If programmatically managing access for large numbers of users/principals, Databricks offers an API endpoint for access-control rule sets where you may need to add the service principal to roles such as budgetPolicy.user or budgetPolicy.manager.

Additional Notes

Merely moving pipeline ownership or assigning group access does not grant budget policy usage rights; these permissions are independent and must be set at the policy level for the service principal’s identity.
For troubleshooting, ensure the service principal appears under the budget policy’s permission list and is marked with Can use or Manager rights.
Access issues frequently occur when organizational role assignment and policy-level permission assignment are confused – always confirm direct budget policy access.

If you follow the above steps to explicitly add and grant access to your service principal for the budget policy, your DLT pipeline should run without the access error. If issues persist, double check the principal’s assignment in the policy UI or the result of the API call for permissions.

topic Re: Budget Policy - Service Principals don't seem to be allowed to use budget policies in Administration & Architecture

Budget Policy - Service Principals don't seem to be allowed to use budget policies

Objective

Steps to reproduce

Issue:

Re: Budget Policy - Service Principals don't seem to be allowed to use budget policies

Re: Budget Policy - Service Principals don't seem to be allowed to use budget policies

Required Steps to Resolve

Additional Notes