Choosing a Power Platform partner is less about who can build a Power App and more about who will stop you ending up with four hundred of them that nobody owns. Almost any Microsoft partner will build you something. Fewer will tell you how environments, data policies and licensing are going to work before the first app goes live, and that conversation is the one that decides what the programme looks like in three years.
This guide covers what to evaluate, how to read the Microsoft accreditations, the licensing questions that change the economics, and the warning signs we found going through the published material of UK Power Platform consultancies in November 2026.
Partner badges are genuinely informative if you know what they mean, and most buyers do not.
Solutions Partner designations cover six areas: Business Applications, Data and AI, Digital and App Innovation, Infrastructure, Modern Work and Security. They are earned through delivered work, certifications and customer success measures rather than bought. A handful of UK partners hold all six; most hold two or three. Breadth is not automatically better, and a partner holding three relevant designations may suit you more than one holding six across areas you will never use.
Specialisations sit beneath designations and are much more specific. For Power Platform the one that matters most is Low Code Application Development under Business Applications. Intelligent Automation is the relevant one for process work. These are a sharper signal than the parent designation.
Advanced Partner status for Power Applications is a distinct accreditation some UK partners hold and is directly relevant.
Business Applications Inner Circle is a Microsoft programme limited to a small number of partners worldwide, based on performance. It indicates scale and Microsoft relationship rather than Power Platform specialism specifically.
Certification counts are worth asking about but worth treating carefully, for reasons covered below.
Power Platform licensing has three parts that catch organisations out, and all three change which design makes sense.
Standard versus premium connectors. Standard connectors are included with Microsoft 365. Premium connectors, which includes Dataverse and most line-of-business system connections, require a paid Power Apps or Power Automate plan. An app design that quietly depends on a premium connector changes your per-user cost across everyone who touches it.
Per-app versus per-user plans. These work out very differently depending on how many apps each person uses. A per-app plan suits a small number of people using one app; a per-user plan suits a wider rollout. Getting this wrong in either direction is expensive.
Dataverse capacity. Storage is allocated and consumed, and capacity is chargeable beyond the entitlement. Ask how your data volumes map to capacity before the design is fixed.
Ask for licensing to be worked out during discovery and modelled against your real user numbers. Microsoft's prices are published on their own site and change periodically, so a partner quoting a fixed per-seat figure from memory is a mild warning sign in itself.
A Centre of Excellence is the operating model for low-code in your organisation, not a piece of software. It is the set of decisions about which environments exist, who is allowed to create apps, what data those apps may connect to, how they are reviewed and who owns them.
It does not have to be elaborate. For a lot of organisations it comes down to three environments, a data loss prevention policy and a named owner. Microsoft publishes a Centre of Excellence starter kit that handles the monitoring side, but the policies and ownership decisions have to be yours, and a partner who hands you the starter kit and calls it governance has not done the work.
Ask any partner to describe their environment strategy for an organisation your size. One who answers with a diagram has done it before. One who says governance is important and moves on has not.
Going through the published material of UK Power Platform consultancies, a few patterns are consistent.
Nobody publishes day rates or project prices. Not one of the UK partners reviewed publishes indicative Power Platform pricing. That is normal for this market and it makes pricing the single most useful question on a first call, because rates vary more across these firms than capability does.
Centre of Excellence offerings vary from explicit to absent. Some partners publish a named CoE service with environment strategy and data classification spelled out. Others fold governance into a general assessment. A few do not mention it at all. Since this is the part that determines whether the programme survives, it is worth filtering on.
Public sector routes differ. Some UK partners hold G-Cloud listings, which matters if you procure through frameworks. Framework status is easy to verify directly on the Digital Marketplace rather than taking a website's word for it.
Two things came up often enough in this research to be worth passing on, because both are easy to check and both tell you something.
Statistics that display as zero. More than one UK partner site shows counters reading "0+ deployments" or "0% improvement", which is an unpopulated field rather than a real figure. It is a small thing, but a stat block nobody has noticed is broken suggests nobody is maintaining the page it sits on.
Figures that disagree across a single site. Certification counts, MVP numbers and award tenure frequently differ between a partner's homepage, their partner page and their FAQ. That is usually pages written at different times rather than anything worse, but if a number matters to your evaluation, ask them to confirm it rather than citing it from the site.
Neither is disqualifying. Both are reasons to verify rather than assume.
| Your situation | What to look for |
|---|---|
| Automation around your intranet, Teams and documents | A Microsoft 365-led consultancy that already understands your content and permissions context |
| Large public sector programme with security requirements | Published police, NHS or local authority work, plus a verified framework listing |
| You have maker sprawl and need to regain control | A named Centre of Excellence offering with environment strategy and data classification |
| Work centred on Dynamics 365 or an Azure data estate | A Business Applications or Azure-led partner rather than a collaboration-led one |
| Procuring through a framework | Check the Digital Marketplace directly rather than relying on the website claim |
Our Power Platform work sits inside a wider Microsoft 365 practice rather than standing alone. The usual starting point is an organisation that has built or migrated an intranet and found the processes around it still running on spreadsheets, email chains and paper forms.
That means the permissions, content structure and governance are usually already sorted by the intranet work before any app is built, which removes the most common cause of Power Platform programmes going wrong. We work licensing out during discovery rather than at the end, and we offer a managed service and ongoing support afterwards rather than handing over and leaving.
If you want to talk through where Power Platform fits alongside your Microsoft 365 setup, book a call with our team.
They design and build business applications and automated workflows using Power Apps, Power Automate, Power BI, Power Pages and Copilot Studio, and set up the environment strategy, data policies and ownership model that keep them maintainable. The build is the visible part; the governance decides whether it lasts.
The operating model for low-code in your organisation: which environments exist, who can create apps, what data they may connect to, how apps are reviewed and who owns them. Microsoft publishes a starter kit for the monitoring, but the policies and ownership decisions have to be yours.
No UK partner reviewed publishes day rates or project prices, so you will need to ask. Beyond the build, factor in licensing, because premium connectors and Dataverse capacity change the running cost significantly and are easy to miss at proposal stage.
The Low Code Application Development specialisation under Business Applications is the most directly relevant, followed by Intelligent Automation for process work and Power Applications Advanced Partner status. These are sharper signals than the number of Solutions Partner designations a firm holds.
It helps when the automation touches SharePoint, Teams or your intranet, because permissions and content structure are the same problem. It matters less when the work centres on Dynamics 365 or an Azure data estate.
Set up environments, data loss prevention policies and a clear process for who can build what, before the first app rather than after the fortieth. Sprawl is not caused by people building apps; it is caused by nobody deciding in advance where they are allowed to build them or what happens when the builder leaves.