I would rather they use those mature processes, build on them, make them better and replace as needed. But lately, it seems we release a new product with almost no features and build from scratch for years.

I am not saying "Don't innovate" but lately, especially with things like Fabric, it is like they have no idea that any other tools exist or existed. They take forever to "add new and exciting features" that should have been there from the start, we have always had everywhere else, and were mature.

They are releasing a Terraform provider which is a little limited for now and they stated that bicep would be coming at a later date. But that is not on this year's projected roadmap...

Now that they are moving all of the data platform to fabric, they made a special new rest APi and cli tool and started development on a python library for ci/cd and fabric deployment pipelines instead of sticking with bicep and ado pipelines. So much for unification...

Entra and m365 are both graph only and I don't believe they are available using Bicep. Unless you are saying that entra id is now available via bicep (preview). That would at least be helpful if not late.

Microsoft Fabric provider for bicep · Issue #12905 · Azure/bicep "Microsoft Fabric" is a seperate SaaS offering which will require automated lifecycle mgmt / CD / IaC. Altough the current state of the corresponding APIs / tooling / etc. is at an early stage now ...

Bicep provider for Microsoft Fabric resources

I would love for anyone who sees this with interest to review and upvote the addition of a Bicep provider for Fabric resources. I am personally passionate about this as I have have a large investment in Bicep already.
Here: github.com/Azure/bicep/...

AC/DC in Minneapolis!

Excited to attend the Microsoft Fabric Community Conference!