It is - fabric only requires only azure identity from plethora of different
dependcies that azure contains.


Thanks & Regards,
Amogh Desai

On Thu, 19 Nov 2026 at 10:27 AM, Vikram Koka via dev <[email protected]>
wrote:

> Fascinating, thanks for following up on this, Amogh!
>
> Is the Azure identity part not required for this?
>
> Thanks,
> Vikram
>
>
> On Wed, Nov 18, 2026 at 4:22 AM Amogh Desai via dev <
> [email protected]>
> wrote:
>
> > Reviving an old thread :)
> >
> > Thanks, Niko, for adding that context.
> >
> > Re Vikram's question on interest, I checked PyPI, which has a decent
> signal
> > for this -
> > apache-airflow-providers-microsoft-fabric gets about 1.5M downloads a
> > month, which is
> > roughly over 2 times our Azure provider (~650K). Some of that may be
> likely
> > Fabric's  managed Airflow
> > image or something, but irrespective of that, it's still a lot of Fabric
> +
> > Airflow usage,  on a package pinned
> > to Airflow 2. And, to add further, it appears to be a direct fit for
> > durable execution too because Fabric runs
> > are long-running submit + poll jobs.
> >
> > On where to place it - I lean towards a separate microsoft fabric
> provider.
> > Fabric needs little more than
> > azure-identity only, so users should not have to pull in the whole Azure
> > provider, and it can be retired on its
> > own if it goes stale
> >
> >
> > Thanks & Regards,
> > Amogh Desai
> >
> >
> > On Sat, Sep 12, 2026 at 3:10 AM Vikram Koka via dev <
> > [email protected]>
> > wrote:
> >
> > > Thanks Niko, I was trying to find that thread too, since I had a
> similar
> > > recollection.
> > >
> > > David,
> > >
> > > A couple of comments and questions:
> > > 1. I think resolving whether this should be integrated into one of the
> > > existing 4 Microsoft providers is important.
> > >     Similar to other provider conversations (for example Oracle), I
> don't
> > > think it should automatically default to the Azure provider.
> > >     I am not immediately opposed, but it logically seems different.
> > >
> > > 2. From a quick glance, at least 2 of the 4 Microsoft providers are
> > > candidates for deprecation.
> > >     Given that, why do you believe there is sufficient interest in
> adding
> > > and maintaining the Microsoft Fabric provider?
> > >
> > > Best regards,
> > > Vikram
> > >
> > >
> > >
> > > On Fri, Sep 11, 2026 at 2:14 PM Niko Oliveira <[email protected]>
> > wrote:
> > >
> > > > +1 from me, this is worth having!
> > > >
> > > > I remember the discussion a couple years ago (went and found it on
> the
> > > dev
> > > > lsit [1]), someone from the Fabric team proposed the same thing.
> Nobody
> > > > entirely objected to the integration itself, but the thread kind of
> > > stalled
> > > > after explaining the minimum requirements. It looks like, based on
> what
> > > you
> > > > linked, they went and built it outside of Airflow.
> > > >
> > > > Do you plan to add the integration to the Azure provider, or a new
> > > > microsoft.fabric one? Anyone from Microsoft helping this time around
> > and
> > > > available to steward the Azure provider these days?
> > > >
> > > > Cheers,
> > > > Niko
> > > >
> > > > [1] https://lists.apache.org/thread/2yrwzgzbo44fqo2rgcyqxw1sjd2sob30
> > > >
> > > >
> > > >
> > > > On Thu, Sep 10, 2026 at 1:49 AM Aaron Chen <[email protected]>
> wrote:
> > > >
> > > > > +1, I think it would be great to have it in the Azure provider.
> > > > >
> > > > > On Thu, Sep 10, 2026 at 4:41 PM Jarek Potiuk <[email protected]>
> > wrote:
> > > > >
> > > > > > Go ahead!
> > > > > >
> > > > > > On Thu, Sep 10, 2026 at 9:03 AM Blain David <
> > [email protected]
> > > >
> > > > > > wrote:
> > > > > >
> > > > > > > Hello,
> > > > > > >
> > > > > > > I'm wondering if there would be interest of having Fabric
> > > integration
> > > > > in
> > > > > > > Airflow via the Azure provider?
> > > > > > >
> > > > > > > There is already an existing provider from Microsoft here:
> > > > > > >
> https://github.com/microsoft/airflow-providers-microsoft-fabric
> > > > > > >
> > > > > > > But it's not maintained, and only compatible with Airflow 2 and
> > > thus
> > > > > > > doesn't work in Airflow 3.
> > > > > > >
> > > > > > > If yes, then I would be planning to add it into the Airflow
> > > Microsoft
> > > > > > > Azure Provider.
> > > > > > >
> > > > > > > Kind regards,
> > > > > > > David
> > > > > > >
> > > > > > > General (Internal Property)
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>

Reply via email to