Any Power Automate flow or Power Apps app that uses a premium connector needs a paid licence for every person who runs it: NZ$24.30 a user a month for Power Automate Premium, or NZ$32.40 for Power Apps Premium. A flow that ran fine in testing can hit a licensing wall the moment it goes live. The connectors most likely to trip it are the unremarkable-looking ones: SQL Server, the HTTP connector, Microsoft's own Dataverse. Premium licensing is charged per user who touches the flow rather than per flow, so the bill grows with your headcount.
At a glance: A premium connector, SQL Server, HTTP, Dataverse, Salesforce, DocuSign and hundreds more, needs a paid plan for every person who runs the flow or app, the builder included. As at 1 October 2026, that is NZ$24.30 a user a month for Power Automate Premium, or NZ$32.40 a user a month for Power Apps Premium if the connector sits inside an app (Microsoft list prices, paid yearly). The cheaper USD 5-a-user Power Apps per-app plan is still worth asking about: Microsoft ended new direct sales on 2 January 2026, but it came back on CSP price lists in early April, and Enterprise Agreement customers can keep renewing it. If you buy through a partner, which most NZ businesses do, it is probably still on the table. Check current list prices before you budget, Microsoft moves them.
For the NZD cost at 5, 10 and 20 users and how to check your own tenant, see the Power Apps premium licence trap. Two follow-ups since this was written: the full NZD licence maths for flows is in what Power Automate actually costs a small NZ business, and if the premium connector you need is SQL Server because the job database lives on your own server, moving a SQL Server database into Microsoft 365 walks through whether to keep it there or move it.
Where the SQL Server connector shows up in a migration, and the alternatives, are on the Power Platform migration hub.
What makes a connector premium
Microsoft splits every connector into tiers. Standard connectors come free with the Power Automate and Power Apps access you already get through a normal Microsoft 365 licence: SharePoint, Outlook, Teams, OneDrive, Excel Online, Forms, Approvals, Planner. Premium connectors need a separate paid plan on top. Custom connectors, ones you or a developer build yourself against an API with no native connector, are premium by default too.
The part that catches people out is that the split isn't intuitive. Outlook is standard. Dataverse, the database Microsoft's own documentation recommends as the preferred data store for Power Apps, is premium. SharePoint lists are standard. SQL Server is premium. The HTTP connector, arguably the single most useful action in the whole product because it can call almost any web API, has been premium since February 2019. You cannot tell any of that from the connector's icon or its name in the flow designer. The only reliable way to know is to check the tier before you build around it, not after.
The trap: it's licensed per user, not per flow
This is the rule that does the damage. Any flow or app that uses even one premium connector requires every person who runs it, builder included, to hold a plan that includes premium access: Power Automate Premium at NZ$24.30 a user a month, or Power Apps Premium at NZ$32.40 a user a month if the connector lives inside an app rather than a flow. It's a per-seat cost that multiplies by headcount, and it's separate from whatever you paid to have the thing built.
The usual way this bites: someone builds a flow using their own account, which often has premium access through a trial, an admin's plan, or a licence they already hold for other reasons. It works perfectly in testing. It gets rolled out to a five-person team, and either the flow quietly fails for everyone without the licence, or someone in finance finds five new premium seats on next month's Microsoft invoice that nobody scoped in. The build worked exactly as designed. The licence just never made it into the decision to use that connector. From February 2027, Microsoft will stop applying these rules leniently, so an app that has worked on a thin licence will need a premium one. It's the same blind spot behind a tenant full of flows no one has reviewed in years, which I cover separately in Power Platform governance for a small business.
The premium connectors small firms hit first
These are the ones that turn up in ordinary small-business builds, not exotic enterprise integrations.
| Connector | Tier | Why it catches people out |
|---|---|---|
| SQL Server / Azure SQL | Premium | The connector for "our own database" is almost never free |
| HTTP | Premium since Feb 2019 | Calls any web API; most flows eventually reach for it |
| Microsoft Dataverse | Premium | Microsoft's own recommended Power Apps data store, not included by default |
| Salesforce | Premium | Any CRM outside Microsoft's own products |
| SAP | Premium | Enterprise ERP connectors, as a rule, are premium |
| DocuSign / Adobe Acrobat Sign | Premium | E-signature tools people assume are basic utilities |
| Azure DevOps | Premium | Catches teams building their own internal tools |
| MySQL / PostgreSQL | Premium | Self-hosted, non-Microsoft databases, also need an on-premises gateway |
| Custom connector (any API you wrap yourself) | Premium by default | No native connector exists, so you build one, and it inherits the premium tier |
Standard workarounds that hold up
Plenty of the time, a standard connector does the same job for no extra licence cost. SharePoint lists handle most small-business record-keeping, a few hundred to a few thousand rows, basic relationships between them, approvals attached, and they cost nothing beyond the Microsoft 365 licence a business already has. That covers a large share of what firms reach for Dataverse or SQL Server to do, well before they need either one's extra depth.
Before reaching for the HTTP connector to talk to a specific service, check whether Microsoft already ships a dedicated standard connector for it. Outlook, Teams, OneDrive, Forms, Planner and Approvals are all standard and cover a lot of ground without a raw API call. Excel Online is standard too, and fine for something a handful of people update by hand rather than a system holding real transactional data.
Premium connectors are not a mistake. Some jobs genuinely need Dataverse's relational depth, or a real integration with Salesforce or SAP, and paying for that is the right call. Just know you are buying it, and put the ongoing per-user cost in the budget at the start, rather than finding it on an invoice after the build is live.
How to check the real cost before you build
Before a flow gets scoped, look up the tier of every connector it's likely to need against Microsoft's own connector reference, not a blog post, since the list changes. Then do the multiplication that decides it: the number of people who will run the flow, times the monthly premium licence cost, times twelve. That ongoing figure is often bigger across a year than the one-off build fee, and it's the number that should sit next to the build quote before anyone signs off on it.
This is exactly what I check during a Power Platform build: which connectors a flow or app needs, which tier they sit in, and whether a standard connector gets the same result without the ongoing per-user bill. If you're also weighing up whether the thing you need is a Power App at all, what a Power App actually costs to build and licence in NZ covers the build side of the same question. And if the premium connector is only there because a flow has to reach outside Microsoft, check whether Zapier or Make would sidestep the licence question altogether before you pay for Power Automate Premium.
Common questions
Is SQL Server a premium connector in Power Automate?
Yes. SQL Server, and Azure SQL alongside it, sit in Microsoft's premium connector tier, not standard. A flow that reads or writes to a SQL database needs a Power Automate Premium or Power Apps premium licence for every user who runs it, even though a database connector feels like basic plumbing rather than an add-on.
Does every user of a flow need a premium licence, or just the person who built it?
Every user who runs the flow or app needs the licence, the builder included. This is the rule that catches people out: the maker often has premium access through a trial or their own paid plan, tests everything successfully, then rolls it out to a team who don't have that licence and the flow fails or the invoice jumps.
Is the HTTP connector premium in Power Automate?
Yes. The HTTP connector, which calls almost any web API and is one of the most generally useful actions in Power Automate, has been a premium connector since February 2019. Building a flow around it commits every user of that flow to a premium licence.
Want your flow's real licence cost before you build it?
Free 30-minute call. Send me what you're trying to automate and I'll check which connectors it needs and what that costs monthly, before anyone builds anything.
Running a small firm and not sure this applies to you?
Send me what you have been quoted or what you plan to build, and I will give you a free written second opinion within two working days.