<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic DLT-Asset bundle : Pipelines do not support a setting a run_as user that is different from the owner in Administration &amp; Architecture</title>
    <link>https://community.databricks.com/t5/administration-architecture/dlt-asset-bundle-pipelines-do-not-support-a-setting-a-run-as/m-p/107856#M2898</link>
    <description>&lt;P&gt;Hello !&lt;/P&gt;&lt;P&gt;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).&lt;/P&gt;&lt;P&gt;This is not an issue for workflows but somehow it is an issue for DLT pipelines as we run into this error :&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Pipelines do not support a setting a run_as user that is different from the owner&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 30 Jan 2025 16:13:44 GMT</pubDate>
    <dc:creator>erigaud</dc:creator>
    <dc:date>2025-01-30T16:13:44Z</dc:date>
    <item>
      <title>DLT-Asset bundle : Pipelines do not support a setting a run_as user that is different from the owner</title>
      <link>https://community.databricks.com/t5/administration-architecture/dlt-asset-bundle-pipelines-do-not-support-a-setting-a-run-as/m-p/107856#M2898</link>
      <description>&lt;P&gt;Hello !&lt;/P&gt;&lt;P&gt;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).&lt;/P&gt;&lt;P&gt;This is not an issue for workflows but somehow it is an issue for DLT pipelines as we run into this error :&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Pipelines do not support a setting a run_as user that is different from the owner&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 30 Jan 2025 16:13:44 GMT</pubDate>
      <guid>https://community.databricks.com/t5/administration-architecture/dlt-asset-bundle-pipelines-do-not-support-a-setting-a-run-as/m-p/107856#M2898</guid>
      <dc:creator>erigaud</dc:creator>
      <dc:date>2025-01-30T16:13:44Z</dc:date>
    </item>
    <item>
      <title>Re: DLT-Asset bundle : Pipelines do not support a setting a run_as user that is different from the o</title>
      <link>https://community.databricks.com/t5/administration-architecture/dlt-asset-bundle-pipelines-do-not-support-a-setting-a-run-as/m-p/108081#M2906</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/84270"&gt;@erigaud&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;yes observed same behaviour either remove run_as and it will automatically take the same information as owner.&lt;/P&gt;&lt;P&gt;OR&lt;/P&gt;&lt;P&gt;if owner can be mapped to run_as&lt;/P&gt;</description>
      <pubDate>Fri, 31 Jan 2025 13:29:14 GMT</pubDate>
      <guid>https://community.databricks.com/t5/administration-architecture/dlt-asset-bundle-pipelines-do-not-support-a-setting-a-run-as/m-p/108081#M2906</guid>
      <dc:creator>saurabh18cs</dc:creator>
      <dc:date>2025-01-31T13:29:14Z</dc:date>
    </item>
    <item>
      <title>Re: DLT-Asset bundle : Pipelines do not support a setting a run_as user that is different from the o</title>
      <link>https://community.databricks.com/t5/administration-architecture/dlt-asset-bundle-pipelines-do-not-support-a-setting-a-run-as/m-p/108151#M2910</link>
      <description>&lt;P&gt;&lt;SPAN&gt;By default who creates pipeline is the owner/run_as.&lt;/SPAN&gt;&lt;/P&gt;
&lt;DIV id="CE2JKAKQC-1738334635.437969-thread-list-Thread_1738335133.891829" class="c-virtual_list__item" tabindex="0" role="listitem" aria-setsize="-1" data-qa="virtual-list-item" data-item-key="1738335133.891829"&gt;
&lt;DIV class="c-message_kit__background c-message_kit__message c-message_kit__thread_message" role="presentation" data-qa="message_container" data-qa-unprocessed="false" data-qa-placeholder="false"&gt;
&lt;DIV class="c-message_kit__hover" role="document" aria-roledescription="message" data-qa-hover="true"&gt;
&lt;DIV class="c-message_kit__actions c-message_kit__actions--above"&gt;
&lt;DIV class="c-message_kit__gutter"&gt;
&lt;DIV class="c-message_kit__gutter__right" role="presentation" data-qa="message_content"&gt;
&lt;DIV class="c-message_kit__blocks c-message_kit__blocks--rich_text"&gt;
&lt;DIV class="c-message__message_blocks c-message__message_blocks--rich_text" data-qa="message-text"&gt;
&lt;DIV class="p-block_kit_renderer" data-qa="block-kit-renderer"&gt;
&lt;DIV class="p-block_kit_renderer__block_wrapper p-block_kit_renderer__block_wrapper--first"&gt;
&lt;DIV class="p-rich_text_block" dir="auto"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;DIV id="CE2JKAKQC-1738334635.437969-thread-list-Thread_1738335149.044059" class="c-virtual_list__item" tabindex="-1" role="listitem" aria-setsize="-1" data-qa="virtual-list-item" data-item-key="1738335149.044059"&gt;
&lt;DIV class="c-message_kit__background c-message_kit__background--hovered c-message_kit__message c-message_kit__thread_message" role="presentation" data-qa="message_container" data-qa-unprocessed="false" data-qa-placeholder="false"&gt;
&lt;DIV class="c-message_kit__hover c-message_kit__hover--hovered" role="document" aria-roledescription="message" data-qa-hover="true"&gt;
&lt;DIV class="c-message_kit__actions c-message_kit__actions--above"&gt;
&lt;DIV class="c-message_kit__gutter"&gt;
&lt;DIV class="c-message_kit__gutter__right" role="presentation" data-qa="message_content"&gt;
&lt;DIV class="c-message_kit__blocks c-message_kit__blocks--rich_text"&gt;
&lt;DIV class="c-message__message_blocks c-message__message_blocks--rich_text" data-qa="message-text"&gt;
&lt;DIV class="p-block_kit_renderer" data-qa="block-kit-renderer"&gt;
&lt;DIV class="p-block_kit_renderer__block_wrapper p-block_kit_renderer__block_wrapper--first"&gt;
&lt;DIV class="p-rich_text_block" dir="auto"&gt;
&lt;DIV class="p-rich_text_section"&gt;However, yes this is a feature in progress.&lt;/DIV&gt;
&lt;DIV class="p-rich_text_section"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class="p-rich_text_section"&gt;I wouls still encorage you to share your request her&amp;nbsp;&lt;SPAN&gt;&lt;A href="https://docs.databricks.com/en/resources/ideas.html#ideas" target="_blank"&gt;https://docs.databricks.com/en/resources/ideas.html#ideas&lt;/A&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;</description>
      <pubDate>Fri, 31 Jan 2025 17:14:11 GMT</pubDate>
      <guid>https://community.databricks.com/t5/administration-architecture/dlt-asset-bundle-pipelines-do-not-support-a-setting-a-run-as/m-p/108151#M2910</guid>
      <dc:creator>NandiniN</dc:creator>
      <dc:date>2025-01-31T17:14:11Z</dc:date>
    </item>
    <item>
      <title>Re: DLT-Asset bundle : Pipelines do not support a setting a run_as user that is different from the o</title>
      <link>https://community.databricks.com/t5/administration-architecture/dlt-asset-bundle-pipelines-do-not-support-a-setting-a-run-as/m-p/108908#M2942</link>
      <description>&lt;P&gt;Hello again,&lt;/P&gt;&lt;P&gt;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&lt;/P&gt;&lt;P&gt;&lt;A href="https://feedback.azure.com/d365community/idea/61e1a9e4-99e3-ef11-b542-00224854717c" target="_blank"&gt;https://feedback.azure.com/d365community/idea/61e1a9e4-99e3-ef11-b542-00224854717c&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 05 Feb 2025 08:20:52 GMT</pubDate>
      <guid>https://community.databricks.com/t5/administration-architecture/dlt-asset-bundle-pipelines-do-not-support-a-setting-a-run-as/m-p/108908#M2942</guid>
      <dc:creator>erigaud</dc:creator>
      <dc:date>2025-02-05T08:20:52Z</dc:date>
    </item>
    <item>
      <title>Re: DLT-Asset bundle : Pipelines do not support a setting a run_as user that is different from the o</title>
      <link>https://community.databricks.com/t5/administration-architecture/dlt-asset-bundle-pipelines-do-not-support-a-setting-a-run-as/m-p/138681#M4458</link>
      <description>&lt;P&gt;I can't believe I have to say this, but this issue should not be marked as "Solved" until the actual problem is... solved.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 12 Nov 2025 03:31:32 GMT</pubDate>
      <guid>https://community.databricks.com/t5/administration-architecture/dlt-asset-bundle-pipelines-do-not-support-a-setting-a-run-as/m-p/138681#M4458</guid>
      <dc:creator>no2</dc:creator>
      <dc:date>2025-11-12T03:31:32Z</dc:date>
    </item>
    <item>
      <title>Re: DLT-Asset bundle : Pipelines do not support a setting a run_as user that is different from the o</title>
      <link>https://community.databricks.com/t5/administration-architecture/dlt-asset-bundle-pipelines-do-not-support-a-setting-a-run-as/m-p/138716#M4461</link>
      <description>&lt;P&gt;Maybe I'm not catching this or missing something else but I've got the following job in one of my demo workspaces:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Coffee77_0-1762937681592.png" style="width: 400px;"&gt;&lt;img src="https://community.databricks.com/t5/image/serverpage/image-id/21596iB179975C98599BA4/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Coffee77_0-1762937681592.png" alt="Coffee77_0-1762937681592.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Creator is my user and the job runs as a service principal account. Those are different identities. I got this by deploying the job with Databricks Asset Bundles and changing in there the "run_as" property while keeping same job identifiers.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Coffee77_1-1762937864425.png" style="width: 400px;"&gt;&lt;img src="https://community.databricks.com/t5/image/serverpage/image-id/21597iD85BDDA49B67B1C0/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Coffee77_1-1762937864425.png" alt="Coffee77_1-1762937864425.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 12 Nov 2025 08:58:11 GMT</pubDate>
      <guid>https://community.databricks.com/t5/administration-architecture/dlt-asset-bundle-pipelines-do-not-support-a-setting-a-run-as/m-p/138716#M4461</guid>
      <dc:creator>Coffee77</dc:creator>
      <dc:date>2025-11-12T08:58:11Z</dc:date>
    </item>
    <item>
      <title>Re: DLT-Asset bundle : Pipelines do not support a setting a run_as user that is different from the o</title>
      <link>https://community.databricks.com/t5/administration-architecture/dlt-asset-bundle-pipelines-do-not-support-a-setting-a-run-as/m-p/142756#M4685</link>
      <description>&lt;P&gt;it's a problem for jobs but for DLT pipeline or dashboards&lt;/P&gt;</description>
      <pubDate>Wed, 31 Dec 2025 13:29:52 GMT</pubDate>
      <guid>https://community.databricks.com/t5/administration-architecture/dlt-asset-bundle-pipelines-do-not-support-a-setting-a-run-as/m-p/142756#M4685</guid>
      <dc:creator>richiesgr_solar</dc:creator>
      <dc:date>2025-12-31T13:29:52Z</dc:date>
    </item>
  </channel>
</rss>

