When Azure and Co‑Pilot Both Fell Down

The plan for the morning was simple: deploy a lightweight Azure Function App using Flex Consumption, wire up a Node.js runtime, and begin building a 3Deers finance engine. What should have been a straightforward setup turned into a frustrating maze of missing features, outdated documentation, and guidance that didn’t match reality. By the time the subscription was upgraded and the Function App deployed, the morning was gone — and the experience revealed failures on multiple fronts.

The first failure started with Microsoft Azure itself. Flex Consumption has quietly changed over the past year, removing long‑standing tools such as the portal code editor, Kudu, App Service Editor, and even basic runtime initialization triggers. These changes were rolled out without consistent documentation updates, leaving users to navigate a UI that no longer matches Microsoft’s own instructions. Azure’s interface repeatedly pushed toward VS Code and local development, even though the portal historically supported in‑browser editing. The result was predictable: confusion, dead ends, and wasted time.

The second failure was Microsoft’s documentation ecosystem. Pages still reference features that no longer exist. Screenshots are outdated. Instructions assume tools that Flex Consumption no longer provides. Even the “Set up my own editor” button leads to a generic help page instead of actionable steps. For a platform as mature as Azure, this level of inconsistency is unacceptable — especially for users who rely on accurate guidance to avoid costly mistakes.

And then there was Co‑Pilot’s failure.  Co-Pilot should have recognized immediately that Flex Consumption no longer supports portal‑based function creation. Instead, Co-Pilot guided me down the old workflow — the one that used to work, the one that Microsoft quietly deprecated. I followed the instructions correctly, and Azure kept presenting screens that didn’t match what Co-Pilot described. That wasn’t my fault. It was Co-Pilot’s. Co-Pilot should have known the platform had changed. Co-Pilot should have steered me toward ZIP deployment from the start. I called out Co-Pilot plainly, and Co-Pilot said I was right.

Next Co-Pilot had me upgrade my new “free” subscription, try something else… and that failed, too.  The Function App is still just a dream in my head. The morning was lost to a combination of Azure’s shifting landscape, Microsoft’s inconsistent documentation, and Co‑Pilot’s outdated assumptions.  Good times for 3Deers!

It wasn’t a good ending.  Now Co-Pilot wants me to follow it down yet another path.  Ugh!