<?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 Re: Linked Service in ADF to One Lake in Pipelines</title>
    <link>https://community.fabric.microsoft.com/t5/Pipelines/Linked-Service-in-ADF-to-One-Lake/m-p/3262383#M154</link>
    <description>&lt;P&gt;I fully intend to once it supports what I need! Currently Fabric copy data activity in pipeline only has very basic API support; I need to be able to pass a bearer key in the auth header (which I've ideally retrieved from key vault or new fabric equivalent), or for internal Microsoft stuff use a managed identity/service principal.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I was just thinking until that was available (I understand it's coming) I could use ADF in azure to land the data while I experiment with fabric.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;That said having now played with it more I think the way to go is simply create a shortcut to my exisiting ADLS storage and get the data in that way.&lt;/P&gt;</description>
    <pubDate>Wed, 31 May 2023 16:58:20 GMT</pubDate>
    <dc:creator>bcdobbs</dc:creator>
    <dc:date>2023-05-31T16:58:20Z</dc:date>
    <item>
      <title>Linked Service in ADF to One Lake</title>
      <link>https://community.fabric.microsoft.com/t5/Pipelines/Linked-Service-in-ADF-to-One-Lake/m-p/3257578#M152</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I was wondering if anyone knew of a work around to let existing resources in ADF or Azure Synapse write to One Lake.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I was hoping I could configure a service principal and then setup a linked service in ADF. However it enforces a name convention of the URL:&lt;/P&gt;
&lt;P&gt;&lt;img /&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;For reference I took the URL from:&amp;nbsp;&lt;A href="https://learn.microsoft.com/en-us/fabric/onelake/onelake-access-api" target="_blank" rel="noopener"&gt;OneLake access and APIs - Microsoft Fabric | Microsoft Learn&lt;/A&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks&lt;/P&gt;
&lt;P&gt;Ben&lt;BR /&gt;Ben&lt;/P&gt;</description>
      <pubDate>Fri, 09 Jun 2023 03:13:14 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Pipelines/Linked-Service-in-ADF-to-One-Lake/m-p/3257578#M152</guid>
      <dc:creator>bcdobbs</dc:creator>
      <dc:date>2023-06-09T03:13:14Z</dc:date>
    </item>
    <item>
      <title>Re: Linked Service in ADF to One Lake</title>
      <link>https://community.fabric.microsoft.com/t5/Pipelines/Linked-Service-in-ADF-to-One-Lake/m-p/3262214#M153</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="javascript:void(0)" data-lia-user-mentions="" data-lia-user-uid="168297" data-lia-user-login="bcdobbs" class="lia-mention lia-mention-user"&gt;bcdobbs&lt;/a&gt;&amp;nbsp;&amp;nbsp;&lt;SPAN&gt;&lt;SPAN class=""&gt;Any reasons to not use Fabric Pipelines to load into OneLake?&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 31 May 2023 15:01:26 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Pipelines/Linked-Service-in-ADF-to-One-Lake/m-p/3262214#M153</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2023-05-31T15:01:26Z</dc:date>
    </item>
    <item>
      <title>Re: Linked Service in ADF to One Lake</title>
      <link>https://community.fabric.microsoft.com/t5/Pipelines/Linked-Service-in-ADF-to-One-Lake/m-p/3262383#M154</link>
      <description>&lt;P&gt;I fully intend to once it supports what I need! Currently Fabric copy data activity in pipeline only has very basic API support; I need to be able to pass a bearer key in the auth header (which I've ideally retrieved from key vault or new fabric equivalent), or for internal Microsoft stuff use a managed identity/service principal.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I was just thinking until that was available (I understand it's coming) I could use ADF in azure to land the data while I experiment with fabric.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;That said having now played with it more I think the way to go is simply create a shortcut to my exisiting ADLS storage and get the data in that way.&lt;/P&gt;</description>
      <pubDate>Wed, 31 May 2023 16:58:20 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Pipelines/Linked-Service-in-ADF-to-One-Lake/m-p/3262383#M154</guid>
      <dc:creator>bcdobbs</dc:creator>
      <dc:date>2023-05-31T16:58:20Z</dc:date>
    </item>
    <item>
      <title>Re: Linked Service in ADF to One Lake</title>
      <link>https://community.fabric.microsoft.com/t5/Pipelines/Linked-Service-in-ADF-to-One-Lake/m-p/3262830#M155</link>
      <description>&lt;P&gt;&lt;SPAN&gt;&lt;SPAN class=""&gt;&lt;a href="javascript:void(0)" data-lia-user-mentions="" data-lia-user-uid="168297" data-lia-user-login="bcdobbs" class="lia-mention lia-mention-user"&gt;bcdobbs&lt;/a&gt; It depends on what you want to do with the data, if your source data is already structured/curated then you don't generally need to copy it again in the lakehouse/warehouse, shortcuts will work.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 01 Jun 2023 01:34:08 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Pipelines/Linked-Service-in-ADF-to-One-Lake/m-p/3262830#M155</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2023-06-01T01:34:08Z</dc:date>
    </item>
    <item>
      <title>Re: Linked Service in ADF to One Lake</title>
      <link>https://community.fabric.microsoft.com/t5/Pipelines/Linked-Service-in-ADF-to-One-Lake/m-p/3268880#M156</link>
      <description>&lt;P&gt;Anonymous&lt;/a&gt;&amp;nbsp; &amp;nbsp;Will the connectors for the Fabric copy data activity be expanded to match what is available in Azure Data Factory?&amp;nbsp; For instance, I have on premises Oracle data that I would like to land in OneLake.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you.&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jun 2023 15:38:33 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Pipelines/Linked-Service-in-ADF-to-One-Lake/m-p/3268880#M156</guid>
      <dc:creator>kdoherty</dc:creator>
      <dc:date>2023-06-05T15:38:33Z</dc:date>
    </item>
    <item>
      <title>Re: Linked Service in ADF to One Lake</title>
      <link>https://community.fabric.microsoft.com/t5/Pipelines/Linked-Service-in-ADF-to-One-Lake/m-p/3269047#M157</link>
      <description>&lt;P&gt;&lt;SPAN&gt;&lt;SPAN class=""&gt;&lt;a href="javascript:void(0)" data-lia-user-mentions="" data-lia-user-uid="190741" data-lia-user-login="kdoherty" class="lia-mention lia-mention-user"&gt;kdoherty&lt;/a&gt;&amp;nbsp;Yes, on-prem connectivity is tracked for GA,&amp;nbsp;Until then a workaround is to use on-prem gateways in pbi to stage the data in a cloud location and then use copy activity.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jun 2023 17:12:36 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Pipelines/Linked-Service-in-ADF-to-One-Lake/m-p/3269047#M157</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2023-06-05T17:12:36Z</dc:date>
    </item>
    <item>
      <title>Re: Linked Service in ADF to One Lake</title>
      <link>https://community.fabric.microsoft.com/t5/Pipelines/Linked-Service-in-ADF-to-One-Lake/m-p/3269063#M158</link>
      <description>&lt;P&gt;That's good news.&amp;nbsp; Thank you for replying.&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jun 2023 17:21:44 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Pipelines/Linked-Service-in-ADF-to-One-Lake/m-p/3269063#M158</guid>
      <dc:creator>kdoherty</dc:creator>
      <dc:date>2023-06-05T17:21:44Z</dc:date>
    </item>
  </channel>
</rss>

