# Power Automate Premium Connector Licensing | AvantIT > One SQL Server action can turn a standard Power Automate flow premium, and instant flows bill every user who runs them, not just the flow owner. Canonical: https://www.avantit.pt/en/newsletter/premium-connector-bill-nobody-sees-coming/ Source: AvantIT — https://www.avantit.pt (Microsoft Partner, Matosinhos, Portugal) --- [All editions](https://www.avantit.pt/en/newsletter/) AvantIT Insider · Edition 2 # The Premium Connector Bill Nobody Sees Coming ![Arsénio Ferraz] Arsénio Ferraz 2026-09-07 7 min ![AvantIT Insider cover: the premium connector bill nobody sees coming, on Power Automate connector licensing] A client builds a simple instant flow in Power Automate, started by a button. It works for months on standard connectors, until someone adds one SQL Server action to pull a customer record, and every single employee who runs that flow suddenly needs a premium license. Nobody flagged it at design time. Nobody flags it until the invoice, or the "this flow will be turned off" banner, shows up. This week also brought a genuinely useful update to Copilot in SharePoint, so we cover both: one licensing trap to watch for, and one new capability worth trying this week. ## What shipped (and what’s going away) Copilot in SharePoint: personal skills now come with evaluations. Personal skills, reusable Copilot instructions saved as a markdown file in your OneDrive that follow you across every SharePoint site instead of being tied to one, reached public preview in August and are rolling out worldwide in December 2026. This month’s update adds the ability to measure and improve those skills over time, and Copilot in SharePoint now delivers more consistent, predictable cards in chat, making approvals and next steps easier to scan. What this means for a PME: an executive who builds a “turn this document into a concise briefing” skill once can reuse it on every site they work in, without recreating it each time. It is a small feature, but it is the kind of thing that quietly changes how much value a Microsoft 365 Copilot license actually delivers day to day. SharePoint now tells AI assistants how to build HTML that actually works. Every Microsoft 365 tenant now has a tenant-specific HTML guidance page, so any AI assistant, Cowork, GitHub Copilot, Copilot Studio, or another agent, can be pointed at it for up to date instructions on building HTML that renders correctly inside SharePoint’s sandbox, including HTML that stays live-linked to a SharePoint list. The guidance page itself is available now, but the underlying capability it documents, native HTML pages in SharePoint, is still in targeted release rather than full general availability, with broader rollout expected around October 2026. AI assistants normally generate standard web HTML, and SharePoint’s content security policy silently breaks a lot of it, so this solves a real, specific pain even before the wider rollout completes. For anyone at AvantIT prototyping AI-generated dashboards or reports for a client, this is worth pointing your tooling at directly rather than debugging sandbox failures by trial and error, and worth confirming a given client’s tenant actually has HTML pages turned on before promising it. Purview adaptive scopes get a lifecycle refinement. Adaptive scopes for SharePoint DLP, which target sites dynamically based on attributes instead of a manually maintained list, are gaining lifecycle status controls (Message Center MC1450128, Roadmap ID 568785). This is entering public preview from mid-September 2026, expected to complete by early October, with worldwide general availability following between mid-October and mid-November 2026. Administrators will be able to choose whether inactive or soft-deleted site owners count toward scope membership; new scopes will default to evaluating active owners only. If a client already uses adaptive scopes, this is worth watching for over the next two months rather than acting on immediately, since it is still in preview. ## In focus: connectors, standard vs premium, the per-user cost that shows up late The situation. A Power Automate flow starts simple: trigger from a SharePoint list, send an email, update a record. All standard connectors, no licensing conversation needed. Then the business requirement grows, someone needs to pull data from an external database, call a third-party API, or write to Dataverse directly, and the flow now touches a premium connector. According to Microsoft’s own licensing documentation, whether that becomes everyone’s problem or just one person’s depends on how the flow is triggered, and that distinction rarely comes up before the flow is already in production. The options. There are really three paths once a flow needs a premium connector: (1) redesign to avoid it, often by routing the external call through a different, already-licensed system; (2) accept the premium requirement and license accordingly; or (3) if the process has grown past “quick automation” into something with real business weight, move it into Power Apps and Dataverse, where licensing is clearer and governance tooling is built for scale. The criteria. Stay standard-only when the flow’s entire path lives inside Microsoft 365: SharePoint, Teams, Outlook, OneDrive triggers and actions. Go premium, deliberately, when the integration genuinely needs an external system, an ERP, a SQL database, a bespoke API. Move to Power Apps and Dataverse once a “flow” has quietly become a business process with several stakeholders, audit requirements, or a need for proper application lifecycle management. The hidden cost. Per Microsoft’s Power Automate licensing documentation, automated and scheduled flows run under the flow owner’s license context, so one Premium license on the owner can cover the whole flow. Instant flows, the kind a button or a form submission starts, run under the license of whoever invokes them: if that flow touches a premium connector, every person who triggers it needs their own Premium license, or the flow needs a Process license assigned directly to it instead of licensing people individually. This distinction is easy to miss at design time, because the person building the flow almost always already has the right license and never sees the problem the way an unlicensed colleague will. There is a second trap worth knowing about: Microsoft periodically reclassifies connectors from standard to premium, as it did with the SQL, Azure, and several Dynamics 365 connectors, which means a flow that was fully standard when it shipped can become a licensing problem later without anyone changing a single action in it. The recommendation. We check the connector list, and how the flow is triggered, before we design, not after. For any flow with a premium connector, we default to either a Process license on the flow itself or a single dedicated service account, rather than assuming every invoking user is already covered, and we document that decision so nobody rediscovers the licensing boundary the hard way during an audit. A real example. An accounting firm we advised had an expense submission flow, an instant flow employees started from a button in Power Apps, running fine on standard connectors for over a year. A well-meaning addition, a SQL Server lookup to validate vendor IDs against an old finance system, turned it into a premium flow. Because it was instant, not automated, every employee who submitted an expense needed their own Power Automate Premium license, not just the flow’s owner. Nobody noticed until the finance director asked why the Power Automate line item on the Microsoft invoice had jumped. Assigning a single Process license to the flow instead of licensing every employee solved it in an afternoon and brought the cost back down. ## Do this week - Try the new tenant-specific SharePoint HTML guidance page with whatever AI assistant you use for prototyping, and compare it against HTML you generated before this update. - If your organisation or a client already has Copilot in SharePoint licenses in use, ask one power user to try building a personal skill this week; it costs nothing to test and the value compounds the more sites someone works across. - Pull your organisation’s list of active Power Automate flows and check for any premium connector actions (SQL Server, HTTP, Dataverse, and similar) that were added after the flow first went live. If any of this needs a second pair of eyes, [avantit.pt](https://www.avantit.pt/) is a good place to start. This edition was first published in the [AvantIT Insider newsletter on LinkedIn](https://www.linkedin.com/pulse/premium-connector-bill-nobody-sees-coming-ars%C3%A9nio-ferraz-ixa9e/). Comments and discussion happen there. Share: [Subscribe on LinkedIn](https://www.linkedin.com/pulse/premium-connector-bill-nobody-sees-coming-ars%C3%A9nio-ferraz-ixa9e/) ## Other editions [Edition 1 Microsoft Graph Toolkit Retires in 8 Days. Then What? A component library many SharePoint teams quietly rely on stops being supported on August 28. In the same week, an on-premises SharePoint authentication bypass went from proof-of-concept to active exploitation in under 24 hours.](https://www.avantit.pt/en/newsletter/microsoft-graph-toolkit-retires-graph-sdk-vs-pnpjs/) [See all editions](https://www.avantit.pt/en/newsletter/) ### Get the next edition by email One edition a week on Microsoft 365, SharePoint, Power Platform and AI applied to SMEs. Subscribe You can unsubscribe at any time using the link in the footer of every email. ### Does this apply to your tenant? Talk to us and we will go through your specific case, no commitment. ### Send us a message Fill out the form below and we will get back to you shortly. Name Email Company Phone Role ( optional ) Select Executive / Board IT / Technology Finance Operations Human Resources Marketing / Sales Other Company size ( optional ) Select 1-5 employees 5-25 employees 25-50 employees 50-100 employees 100-500 employees 500-1000 employees 1000+ employees Service of Interest Select a service Software Development SharePoint Intranets Power Platform Data & AI Consulting Support Message I would like to occasionally receive AvantIT content about Microsoft 365, Power Platform and automation. We use your details only to answer this enquiry. [Privacy Policy](https://www.avantit.pt/en/privacy/) Send Message