How Premium Connectors Turn a Free Tool Into a Significant Licensing Event
Power Apps and Power Automate are included in Microsoft 365 E3 and E5 — which leads most organisations to assume they can build and deploy internal applications and automated workflows at no incremental cost. This assumption is correct as long as those applications and flows use only standard connectors. The moment a developer uses a premium connector, every user who runs that application or flow requires a paid Power Apps or Power Automate licence. In organisations with wide Power Platform adoption, this trigger can produce six-figure annual licence costs from a single development decision.
The challenge is structural: developers building on Power Platform are often not aware of the licensing consequences of connector selection, and there is no in-product warning when a premium connector is used in a way that will require paid licences for end users. The consequence arrives at true-up or EA renewal — at which point Microsoft's account team will present a licence gap that the organisation did not anticipate and has limited leverage to contest.
This guide covers the standard vs premium connector distinction, the specific connectors that most commonly trigger licensing events in enterprise organisations, the per-app vs per-user licensing decision, governance controls to prevent uncontrolled premium connector adoption, and how to approach Power Platform connector costs in EA negotiations.
Key stat: In our Power Platform licensing reviews, 67% of enterprise organisations with Power Platform adoption have at least one application or flow in production that uses premium connectors without appropriate user licensing in place. The most common trigger is the SQL Server connector (connecting to on-premises or Azure SQL databases) and the Dataverse connector used in Power Apps developed by citizen developers who assumed M365 inclusion was sufficient.
The Standard vs Premium Connector Distinction
Microsoft categorises connectors into three tiers: standard, premium, and custom. The tier determines the licensing requirement for users of applications or flows that include those connectors.
Standard Connectors (Included in M365)
Standard connectors cover Microsoft's core collaboration and productivity services. Users with any M365 commercial licence (E1, E3, E5, Business Basic, Business Standard, Business Premium, F1, F3) can build and run Power Apps and Power Automate flows that use only standard connectors without any incremental licence purchase. Standard connectors include: SharePoint, OneDrive for Business, Teams, Outlook, Excel Online (Business), Planner, Forms, OneNote, Word Online, Excel Online (OneDrive), Lists, People (M365 contacts), and the standard HTTP connector.
Premium Connectors (Require Paid Licence)
Premium connectors connect to data sources outside the standard M365 productivity stack. Any application or flow that uses even one premium connector requires all users of that application or flow to hold either a Power Apps Per User licence, a Power Apps Per App licence pass, or a qualifying Dynamics 365 or Power Platform standalone licence. Premium connectors include — and this list is non-exhaustive, as Microsoft adds and reclassifies connectors periodically — SQL Server, Azure SQL Database, Dataverse (when used outside M365 seeded environments), Salesforce, ServiceNow, SAP, Oracle, Adobe Sign, DocuSign, GitHub (some actions), Stripe, Twilio, Jira, Zendesk, Azure DevOps (full), Power BI Datasets, HTTP with Entra ID, and many others.
Dataverse is always premium outside seeded environments: The Dataverse connector requires a premium licence for Power Apps users unless the app is accessing a specific Dataverse for Teams environment (the lightweight M365-seeded version). If your developers are building Model-Driven Apps or Canvas Apps connected to the full Dataverse (outside Teams), all users require a paid Power Apps licence regardless of their M365 plan. This is one of the most common licence gap findings in our reviews.
Custom Connectors and Certified Connectors
Custom connectors — connectors to APIs that organisations build themselves — follow the licensing rules of the underlying connector category they use. If your custom connector calls a premium API internally, users need premium licences. Certified connectors (published by third-party ISVs and approved by Microsoft) may be standard or premium depending on their categorisation in the connector gallery.
High-Risk Premium Connectors in Enterprise Environments
The following connectors are responsible for the majority of unplanned premium licensing events in enterprise Power Platform deployments. Each warrants specific governance attention.
| Connector | Risk Level | Common Use Case | Licence Trigger |
|---|---|---|---|
| SQL Server / Azure SQL | Very High | Connecting Power Apps to existing business databases | All app users need Power Apps licence |
| Dataverse (full, non-Teams) | Very High | Model-Driven Apps, custom business applications | All app users need Power Apps Per User or Per App |
| ServiceNow | High | IT service management integrations, automated ticket creation | All flow users need Power Automate Per User |
| Salesforce | High | CRM integrations, lead and opportunity sync workflows | All flow users need Power Automate licence |
| SAP | High | ERP data access, procurement workflows | All app/flow users need paid licence |
| Power BI Datasets | Medium | Apps that read from Power BI semantic models | Requires Power Apps Per User (not per App) |
| Adobe Sign / DocuSign | Medium | Document signing workflows in Power Automate | All flow participants need Power Automate Per User |
| HTTP with Entra ID | Medium | Calling custom APIs with authenticated HTTP requests | Premium trigger; often used unknowingly by developers |
Per-App vs Per-User Licensing: Which Applies When
When a premium connector trigger occurs, organisations have two licensing paths: Power Apps Per App and Power Apps Per User. The right choice depends on the number of distinct applications a user runs and the breadth of Power Platform deployment across the organisation.
Power Apps Per App: Approximately £3.40–4.20/user/month per app pass (EA pricing). Each pass entitles a user to run one specific app that uses premium connectors (or access one Dataverse environment). Users who run three different premium-connector apps need three App passes. Per-App is cost-optimal when the majority of users access only one or two premium-connector applications, or when the deployment is narrow (a specific business unit).
Power Apps Per User: Approximately £16.50–19.50/user/month (EA pricing). Unlimited premium-connector apps for that user, plus full Dataverse access. Per-User is cost-optimal when users access three or more distinct premium-connector applications, or when broad Power Platform development is anticipated.
| Scenario | Apps per User | Cost per User per Month (EA) | Recommended Licence |
|---|---|---|---|
| Single business-specific app (e.g., warehouse scanning app) | 1 | £3.40–4.20 (Per App) | Per App pass |
| Two departmental apps (e.g., HR app + expense app) | 2 | £6.80–8.40 (2× Per App) | Per App passes (still cheaper than Per User) |
| Three or more apps across the organisation | 3+ | £10.20+ (3× Per App) vs £16.50 (Per User) | Evaluate Per User — break-even at approximately 4 apps |
| Power Platform power users / developers | Many | Per User clearly wins | Power Apps Per User |
The per-app accumulation trap: Organisations that start with Per App passes often end up purchasing more passes than a Per User licence would have cost. A user with five app passes at £4/pass/month is paying £20/month — above the Per User rate. Audit your per-app pass assignments annually and migrate users above the break-even threshold to Per User.
Power Automate Premium: The Overlooked Trigger
The premium connector licensing trigger applies equally to Power Automate flows — but it is even more likely to go undetected because flows often run in background without visible user interaction. A flow that sends a daily digest email from SharePoint (standard) costs nothing extra. A flow that creates a ServiceNow ticket based on a Teams message (premium connector) requires every user whose actions trigger that flow to hold a Power Automate Per User licence.
The challenge is the "per flow" vs "per user" distinction. If a licensed maker runs a flow that only they use, the maker's licence covers the flow. If the same flow is triggered by any user (through Power Apps, through a Teams button, or through an automated trigger based on user actions), all those triggering users need licences. This distinction is frequently misunderstood, and many Power Automate flows in production are non-compliant because they are triggered by unlicensed users.
Power Automate Per User (~£12–14/user/month EA) provides unlimited premium-connector flows for that user. Power Automate Per Flow (~£90–100/flow/month EA) licenses a specific flow for unlimited users — cost-optimal for high-user-count flows with a small number of premium connections.
Governance Controls: Preventing Uncontrolled Premium Connector Adoption
The most effective approach to premium connector licensing cost control is governance that prevents unplanned premium connector use in citizen development, rather than retroactively licensing production apps after the licence gap is identified. The following controls are standard in well-governed Power Platform environments.
Data Loss Prevention (DLP) Policies by Environment
Power Platform DLP policies control which connectors are available in which environments. Categorise connectors as Business (allowed), Non-Business (blocked), or Blocked outright. For environments where citizen developers without premium licences are building: block all premium connectors by policy. Create separate, licenced-access environments for premium connector development. This prevents the unintended introduction of premium connectors by developers who do not understand the licensing consequences.
Environment Tiering
Maintain at least three environment tiers: (1) a default environment where M365-included Power Platform is available for standard connector work, (2) a licensed development environment with premium connectors available to licenced developers, and (3) production environments with premium connector DLP policies matched to the licensed user population. This structure ensures that premium connector apps can only be deployed where the licensing is in place.
App Registry and Licence Review Process
Require that all Power Apps that use premium connectors are registered in a central application register before production deployment. The registration process confirms that the deploying team has identified the user population, confirmed their licence entitlement, and obtained IT sign-off. This is a procedural control rather than a technical one, but it prevents the most common licence gap scenario: a departmental team deploying a premium-connector app to their whole department without licensing them first.
Power Platform Centre of Excellence Starter Kit
Microsoft's CoE Starter Kit (a set of template Power Platform solutions) includes an application registry, environment management tools, and usage analytics that identify premium connector usage across the tenant. Deploying the CoE Starter Kit provides the visibility required for ongoing licence management. It is free; the only cost is the Dataverse capacity required to run it.
Negotiating Power Platform Connector Costs in Your EA
Premium connector licensing typically emerges as an EA negotiation topic in one of three ways: during true-up when a gap is identified, at renewal when Microsoft proposes adding Power Apps Per User for a large population, or proactively when an organisation plans a significant Power Platform deployment.
True-Up Gap Negotiation
If a premium connector licence gap surfaces during true-up, you have limited but real negotiating room. The options are: pay for the retroactive licence period (Microsoft's default position), negotiate a prospective-only approach (licensing from today forward, not back-dated), or commit to a Power Platform deployment plan as part of the EA renewal that justifies a more favourable commercial structure. Retroactive licensing back-dates are frequently waived or reduced in exchange for a forward commitment — this is the most common resolution in our client engagements.
EA Renewal Power Platform Structure
Build your Power Platform licence structure proactively in EA renewal rather than reactively. If you have an active citizen development programme, model expected premium connector adoption over the three-year term, and include appropriately structured Per App or Per User licences as a named EA line item. Negotiating Power Platform volume as part of a broader EA commit (M365 + Azure + Power Platform) typically yields 15–25% discount on Power Platform licences compared to mid-term standalone add-ons.
Per App vs Per User Optimisation in EA
At EA scale, negotiate a blended model: Per User licences for developers and power users, Per App passes for specific functional deployments with defined user populations. Include provisions for migrating users from Per App to Per User as adoption grows. The Per App pass volume is a useful EA lever — Microsoft will often provide better Per App pricing in exchange for a committed volume, which provides budget predictability for organisations scaling their Power Platform deployment.
FAQ
Does an M365 E5 licence allow premium connector use in Power Apps?
No. M365 E5 does not include Power Apps Per User or Per App rights. Even users with the most comprehensive M365 plan require a separate Power Apps licence to use apps with premium connectors. The only M365 plans that include some Power Apps rights are Business Premium (which includes a limited Power Apps for Microsoft 365 licence — standard connectors only) and specific Dynamics 365 plans that include Power Apps Per User.
Can we use the Dataverse connector in a Power Apps app without a premium licence?
Only in the limited Dataverse for Teams environment. Apps that connect to Dataverse for Teams (the lightweight version embedded in Teams) do not require premium licences. Apps that connect to the full Dataverse (outside Teams) — including any Model-Driven Apps or apps accessing a Dataverse database environment — require Power Apps Per User or Per App licences for all users.
If only 10% of our users access a premium-connector app, do we only need to licence those 10%?
Yes. Power Apps licensing is per-user — you licence the specific users who access premium-connector apps, not the entire tenant. A 5,000-user organisation where 200 users access a SQL Server-connected app needs 200 Power Apps licences, not 5,000. Managing the licensed user population (who has access to which premium-connector apps) is the operational discipline required to avoid over-licensing.
What happens if we don't licence premium connector users — is there a technical block?
There is no technical block. Microsoft does not enforce premium connector licensing at runtime — unlicensed users can run premium-connector apps without error. The licence gap is a contractual compliance issue, not a technical one. The consequence is a licensing audit finding or a true-up obligation at EA renewal, not a service interruption. This is why undetected gaps persist in organisations without governance controls.