Name your flows by what they do, not when you built them

Open a tenant's flow list cold and you'll usually find some version of "Flow 3", "Copy of HR automation", or "New flow (2)" sitting next to something genuinely load-bearing. None of that tells you what happens if you turn it off, and that's exactly the question you need answered fast during an incident.

Name every flow by trigger and outcome, not by when you built it or what number it happened to be. "Leaver form submitted -> disable AD account + notify IT" tells you everything a generic name doesn't: what starts it, and what it actually does. Add the owning team if more than one team's flows share a tenant.

This isn't tidiness for its own sake. The moment something breaks at 2am, or you're handing the tenant over to someone else, or you're trying to work out whether it's safe to delete an old flow nobody remembers building, a descriptive name is the difference between understanding the blast radius in five seconds and opening every flow one by one to find out. Ask an AI tool to help you draft names for an existing tangle of "Flow 1" through "Flow 12" from their trigger and action list - it's a five-minute pass that pays for itself the first time someone else has to touch your tenant.