- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hello !
We're using Databricks asset bundles to deploy to several environments using a devops pipeline. The service principal running the CICD pipeline and creating the job (owner) is not the same as the SPN that will be running the jobs (run_as).
This is not an issue for workflows but somehow it is an issue for DLT pipelines as we run into this error :
Pipelines do not support a setting a run_as user that is different from the owner
Is there a way to solve this issue or is it going to be supported by the DLT pipelines ? It seems like a very big constraint.
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
Hello again,
I've created an idea for that issue if someone wants to give it an upvote. It can be a very blocking issue for architectures where you cannot allow to use the same SPN for deployment and runs
https://feedback.azure.com/d365community/idea/61e1a9e4-99e3-ef11-b542-00224854717c
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @erigaud
yes observed same behaviour either remove run_as and it will automatically take the same information as owner.
OR
if owner can be mapped to run_as
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
By default who creates pipeline is the owner/run_as.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
Hello again,
I've created an idea for that issue if someone wants to give it an upvote. It can be a very blocking issue for architectures where you cannot allow to use the same SPN for deployment and runs
https://feedback.azure.com/d365community/idea/61e1a9e4-99e3-ef11-b542-00224854717c

