u/MonkeyDDataHQ

It came to me in an epiphany today.
Fabric is upside down to my mental model.
In general, when I deploy or create something, I want THAT code first.
If I want to check or monitor something, I want that GUI first.
My expectations of a mature platform:

Authoring? Code.
Configuration? Code. Deployment? Git.
Policy? Declarative. Automation? API.
Monitoring? GUI.
Lineage? GUI

#Is my platform on fire?#

#👆 I want to click that#

And Fabric does almost everything upside down to the way most engineers I know develop:

Dataflows? GUI. Configuration? GUI. Deployment? GUI plus Workaround. Policy? N/A.
Automation? Not sure actually
Lineage? API

Is my platform on fire?
API

Monitoring?
Install a Workaround and it's code first.

No wonder I'm tired. 😂

-Your perpetually exhausted Data Engineer

--MonkeyDData

PS this is half in jest and half I finally put my finger on it

Over the past week Fabric has proved itself to be everything I thought it was.

This song (ya it's AI mostly) is based on real reddit threads and real problems.

There are days when I merely dislike Azure.

Then there are days when I have to write sentences like this:

>

That is not a sentence.

That is what happens when a cloud provider puts a thesaurus in a blender and names infrastructure from the slurry.

For context, my architectural requirement is:

THING A SENDS MESSAGE TO THING B.

That’s it.

I am not coordinating a distributed fleet of autonomous yellow submarines ferrying the Village People and the Beatles around on tour.

I would simply like one Azure service to receive a message and another Azure service to get that message.

Apparently this requires me to understand the subtle theological distinctions between Event Grid, Event Grid Namespace, Event Hubs, Event Hubs Namespace, topics, subscriptions, managed identities, service principals, RBAC roles, and whatever new noun Microsoft has released into production this week.

And God help you if you assume two things with nearly identical names are related.

Azure Service Bus and Azure Service Fabric? Different.

Event Grid Namespace and Event Hubs Namespace? Also Different.

Naturally, I need BOTH namespaces in order to send one fucking message.

At some point Azure stops being a cloud platform and becomes a vocabulary certification program with billing regret attached.

Then I hit the permissions problem.

So I opened a support ticket.

To describe it, I had to write:

>

The form then asked me which Azure resource I was having the problem with.

I DON’T KNOW, MICROSOFT. YOU INVENTED ALL THESE NOUNS.

And here is the best part:

I am an administrator.

I activated my privileged role through PIM.

I still cannot perform the assignment.

Because somewhere, somehow, somebody has put an RBAC restriction in place that overrides the access I appear to have, and I cannot find the bastard.

So now the architecture is:

MQTT message → Event Grid Namespace → topic → subscription → Event Hubs Namespace → Event Hub

And the troubleshooting architecture is:

Me → Entra → PIM → Azure RBAC → role assignments → deny assignments → inheritance → increasingly obscure blade → support ticket → despair

I have not successfully sent the message.

I have, however, obtained an advanced degree in Why Am I Not Allowed To Do The Thing The Portal Says I Am Allowed To Do?

Cloud abstraction was supposed to reduce infrastructure complexity.

Microsoft instead invented Infrastructure as Vocabulary, followed immediately by Permissions as Archaeology.

Somewhere in this tenant is one checkbox, policy, deny assignment, management-group inheritance rule, or ancient curse preventing this from working.

And apparently my job is to find it.

The MQTT message remains UNDELIVERED.

/rant over

Why exactly is Airflow in Fabric still on version 2?

Version 3 has been out for over a year!

I went to help a colleague because he was stuck with a particularly difficult meta data driven pipeline and found out that we couldn't use best practices that have become the defacto standard for a year.

u/itsnotaboutthecell please fix this this 😭

Every single time I try to like Fabric it does something ridiculous.

My dudes on the PowerAutomate team.

Can someone please mail an envelope of glitter to the dev and PM who decided that every webhook that hits PowerAutomate gets a 202?

Thanks.

Edit: The 202 is generated by the trigger endpoint, not by my flow. My complaint is that the endpoint acknowledges receipt even when the trigger never instantiates a flow run. If the trigger dies before a run exists, I have no way to detect or debug it.

I finally used the Microsoft Foundry multi agents.

This is genuinely the first feature that is genuinely implemented well, in my opinion.

​

I wanted to let you all know because every comment from me so far has been negative.

And I wanted to show that if something is done well, I will praise it.

​

#MakeGitNotSuckTooPlease

I just wanted to say I hate the person who decided that sending a 202 when power automate doesn't do anything with the http request trigger and that I hope they end up in hell.

I thought I was going insane.

Nope I just had to add an empty header to the post for it to trigger.

With my compliments.

Seriously that engineer is a doofus.

I spent hours with the documentation and copilot until I was like wait, what if I just sent an empty f'ing header?

For a task that should have taken two minutes.