I can't tell which Power Automate connector will cost me extra before I hit run

I started the morning with a small win in mind: turn our weekly status spreadsheet into a Power Automate flow so the update lands in Teams without another copy-paste job. The first steps were simple. SharePoint, Outlook, and Teams all looked familiar, and the test run gave me enough confidence to keep building.

By lunchtime I added the step that made the flow genuinely useful: a connector to the system where the real customer record lives. That was where the doubt started. The connector showed a premium marker, but the bigger question was not just the label. I needed to know who would need a license when the flow was shared, whether the flow owner mattered, and whether our environment had another billing route switched on.

I did manage to save the draft flow and document the connectors, so the work was not wasted. But the painful part was having to open Microsoft docs, pricing pages, old admin messages, and community threads just to answer one stakeholder question: can we run this without creating a surprise licensing issue?

By the end of the day I had a working automation that I did not fully trust. I asked our admin for a licensing check before sharing it, which was the responsible move, but it meant the flow stayed stuck. What I wish existed is a plain pre-run checklist that tells me what to check, who to ask, and what licensing assumption to write down before I build the clever part.