Someone on the team asked me this week whether we should swap our Service Bus trigger for an HTTP one, so a single request could tell us where a file is. The file leaves Azure, lands on-premises, and gets forwarded from there to a customer's site. Compliance says the report has to come from the on-prem machine, not from us in the cloud. Fair. But the question hid something more interesting than a trigger choice.

Ask which Well-Architected pillar gets cut first under deadline pressure and the honest answer is operational excellence. Nobody schedules it. Nobody demos it. Cost gets a dashboard, security gets a review gate, reliability gets a diagram with two regions on it. "Can I see where this file is?" gets a shrug and a promise for phase two.

Then phase two arrives as a single question in a chat thread.

Why the HTTP idea is tempting

I understand the pull. One request in, one answer out.…