<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Azure-Data-Factory on Mark Allison</title>
    <link>https://markallison.co.uk/tags/azure-data-factory/</link>
    <description>Recent content in Azure-Data-Factory on Mark Allison</description>
    <image>
      <title>Mark Allison</title>
      <url>https://markallison.co.uk/%3Clink%20or%20path%20of%20image%20for%20opengraph,%20twitter-cards%3E</url>
      <link>https://markallison.co.uk/%3Clink%20or%20path%20of%20image%20for%20opengraph,%20twitter-cards%3E</link>
    </image>
    <generator>Hugo -- 0.151.2</generator>
    <language>en</language>
    <lastBuildDate>Wed, 29 Mar 2023 10:16:42 +0000</lastBuildDate>
    <atom:link href="https://markallison.co.uk/tags/azure-data-factory/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Which ADF Integration Runtime for my workload?</title>
      <link>https://markallison.co.uk/blog/which-adf-runtime/</link>
      <pubDate>Wed, 29 Mar 2023 08:26:42 +0000</pubDate>
      <guid>https://markallison.co.uk/blog/which-adf-runtime/</guid>
      <description>&lt;h2 id=&#34;self-hosted-or-managed-virtual-network-for-adf&#34;&gt;Self Hosted or Managed Virtual Network for ADF?&lt;/h2&gt;
&lt;p&gt;I was recently asked which runtime would be better to run ADF pipelines in Azure; use Private Managed Endpoints with the Managed Virtual Network, or provision a Self-Hosted Integration Runtime on a Virtual Machine?&lt;/p&gt;
&lt;h3 id=&#34;paas-vs-iaas&#34;&gt;PaaS vs. IaaS&lt;/h3&gt;
&lt;p&gt;My default position on which technology to use is PaaS &lt;em&gt;where possible&lt;/em&gt;. Organisations should focus on providing value to their business, not micro-managing infrastructure. PaaS reduces the operational burden of managing infrastructure in most cases.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Adf Failed To Deactivate Trigger</title>
      <link>https://markallison.co.uk/blog/adf-failed-deactivate-trigger/</link>
      <pubDate>Mon, 09 Jan 2023 13:21:56 +0000</pubDate>
      <guid>https://markallison.co.uk/blog/adf-failed-deactivate-trigger/</guid>
      <description>&lt;p&gt;A colleague had an issue this week with Azure Data Factory (ADF) in that a change to a trigger could not be published. &amp;ldquo;Ah, I know what this is&amp;rdquo;, I thought. Those of you familiar with ADF will know that changes to published triggers cannot be made if the trigger is enabled.&lt;/p&gt;
&lt;h2 id=&#34;troubleshooting-steps&#34;&gt;Troubleshooting Steps&lt;/h2&gt;
&lt;p&gt;I began troubleshooting by first of all disabling the trigger. This also resulted in failure. I then proceeded to detach the trigger from the pipeline, copy out the JSON definition and then save and publish, but also got the same error.&lt;/p&gt;</description>
    </item>
    <item>
      <title>ADF HTTP/3 Issue</title>
      <link>https://markallison.co.uk/blog/adf-https3-issue/</link>
      <pubDate>Tue, 30 Nov 2021 07:44:13 +0000</pubDate>
      <guid>https://markallison.co.uk/blog/adf-https3-issue/</guid>
      <description>&lt;p&gt;One of my ADF pipelines started failing recently where a Generic REST API Linked Service gave the following error:&lt;/p&gt;
&lt;p&gt;&lt;code&gt;525: SSL handshake failed&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;Digging deeper into the logs, I see a message from Cloudflare.&lt;/p&gt;
&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;It appears that the SSL configuration used is not compatible with Cloudflare. This could happen for a several reasons, including no shared cipher suites.
&lt;/code&gt;&lt;/pre&gt;&lt;h2 id=&#34;http3-quic&#34;&gt;HTTP/3 QUIC&lt;/h2&gt;
&lt;p&gt;There had been no code changes in ADF, but something on the source side had changed. After working with the data provider, it turns out that Cloudflare was using HTTP/3 which causes the ADF connection to fail.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
