Quick answer. Selecting a Power Platform implementation partner for a regulated enterprise starts with a shortlist scored, before any RFP, on seven checkable criteria: governance and Center of Excellence capability, managed-environment discipline, application lifecycle management maturity, government-cloud experience, US-based delivery, licensing-tier fluency across the whole platform, and a named exit and handover model. There is no independent ranking of Power Platform partners to lean on, so the shortlist has to be scored on evidence from each firm’s past programs, collected by the buyer directly, the same way it would be for any Microsoft workload. A firm that can only evidence one component, most often Power Automate flow-building, is answering a narrower question than a program-wide governance engagement, and the two are not interchangeable.
Three firms are on the shortlist, and all three describe themselves with the same words: governance, Center of Excellence, managed environments, ALM. The words do not separate them. What separates them is whether each firm can show the thing it names from a program it has already delivered, in an artifact you can inspect, before an RFP goes out. This guide sets out what to ask for, how to cut the shortlist on the answers, and where i3solutions sits on the same test.
Why There Is No Ranking to Lean On, and What to Test Instead
When a shortlist has to be defended to an audit committee, a vendor’s own list of vendors is not evidence, and there is no independent ranking of Power Platform implementation partners to cite in its place. So the ranking has to be built from what each firm can show.
The test that does most of the work is simple. A firm that can show a Center of Excellence model, environment separation with promotion through managed solutions, an ALM pipeline, and a named exit plan is answering a different, larger question than a firm that can only show flows it has built, and a shortlist that does not test for the difference will keep scoring both the same way.
Microsoft makes the same point from the platform side. Its Power Platform Center of Excellence (CoE) Starter Kit overview states: “Managing a CoE requires more than tools.” A firm that describes its governance as a list of tools, with no operating process from a past program, has told you what it would install, not how it would govern.
The Shapes of Firm on a Power Platform Shortlist
Most shortlists mix firms that were never built to do the same job, which is why their pitches read alike and their programs end differently. Five shapes turn up often:
- A flow-automation shop, strong on Power Automate builds, with governance left to the client.
- A large systems integrator for which Power Platform is one line among many workloads, where the team that sells is not always the team that delivers.
- A staffing-led firm that supplies individual makers or contractors by the hour, with the program design left to the buyer.
- A regional Microsoft partner whose depth is in one workload, such as Power BI reporting or Dynamics 365, with Power Platform work added around it.
- A delivery partner that runs Power Apps, Power Automate, Power BI and Dataverse as one governed program, with environments, policies, pipelines and an exit plan designed together.
No shape is disqualifying on its own. The shape tells you which criteria a firm is most likely to fail, and that is where to press first.
Seven Criteria That Decide a Power Platform Partner Ranking
Every firm on the shortlist already claims all seven of these in its own materials, so each one is written below as the evidence to ask for from a program the firm has already delivered, rather than the capability to look for.
Governance and Center of Excellence capability. Ask for the governance model the firm ran on a past program: who held the tenant and environment admin roles, how data policies were set and changed, and how new makers were brought in. Microsoft’s Data policies page describes the intent: “Create data policies that act as guardrails to help reduce the risk of users unintentionally exposing organizational data.”
Microsoft’s CoE Starter Kit transition page states: “The Power Platform CoE Starter Kit is no longer actively maintained.”
As of September 2026, Microsoft Learn also states that the kit’s core capabilities are part of the Power Platform admin center and that the kit will not be enhanced with new capabilities, so a candidate’s governance plan should say how it uses the admin center, not only a toolkit Microsoft has stopped enhancing.
Managed-environment discipline. Ask for the environment layout from a program the firm has already delivered: which environments it stood up, what each one was for, and who could make changes in each. Microsoft’s Power Platform environments overview says an environment “also serves as a container to separate apps that might have different roles, security requirements, or target audiences.” Microsoft’s Managed environments overview describes managed environments as “a suite of premium capabilities that allow admins to manage Power Platform at scale with more control, less effort, and more insights.” A firm that has only ever built in one environment has not yet shown this criterion.
Application lifecycle management maturity. Ask for the release history of a program the firm has already delivered: what source control held, who approved each production deployment, and one release that was rolled back. Microsoft’s ALM overview states: “Solutions are the mechanism for implementing ALM; you use them to distribute components across environments through export and import.” A firm that can describe a pipeline but cannot produce a release history from a past program is describing ALM it has not yet shown.
Government-cloud experience. Ask which Power Platform components the firm has delivered in which cloud on past programs, component by component, because the answer is rarely the same for all four. Microsoft’s Power Apps US Government page states: “There are exceptions to the principle of maintaining product functional parity within the US Government clouds.” Evidence for Power BI in GCC High is not evidence for Power Apps or Dataverse there, so score each component on its own.
US-based delivery. When residency, export control or a contract clause governs who may work in the tenant, ask for the named people from a recent comparable program, where they were based, and whether any part of that delivery was subcontracted. Where no such requirement applies, treat US-based delivery as a preference, not a gate. Whether a requirement applies is a question for your contracting officer and your own compliance counsel, not for the partner.
Licensing-tier fluency across the whole platform. Ask the firm to show how it placed users, apps and flows across license types in a past program, and how it handled a change that moved an app from one license type to another. Microsoft’s Managed environments overview ties governance to licensing: “Managed environments are included as an entitlement with standalone Power Apps, Power Automate, Microsoft Copilot Studio, Power Pages, and Dynamics 365 licenses.” A firm that answers with a price sheet rather than a placement is answering a procurement question, not this one.
A named exit and handover model. While the shortlist is still being cut, ask for the exit model the firm used on a past program, in writing: how that engagement ended, who on the client side took over each admin role, and which clause of the contract governed it. Then ask that client what happened in the final month. Every firm on the list should answer this, not only the one you favor.
A Power Platform Shortlist Rubric to Apply Before the RFP
The rubric is for the weeks before an RFP goes out, while the shortlist is still being cut and each firm can be asked for evidence without a formal response. It is this guide’s own tool, built on the seven criteria above.
| Criterion | Evidence to request before the RFP | What does not count |
|---|---|---|
| Governance and Center of Excellence capability | The governance model from a past program: admin roles, data policy changes, maker onboarding | A list of governance tools |
| Managed-environment discipline | The environment layout from a delivered program, with who could change what in each | A layout drawn for this shortlist only |
| Application lifecycle management maturity | The release history of a delivered program, including one rollback | A pipeline described but never run |
| Government-cloud experience | Which components were delivered in which cloud on past programs, one by one | One component’s record offered for all four |
| US-based delivery | Named people from a comparable program, where they were based, and any subcontracting | A statement of policy with no names |
| Licensing-tier fluency | How users, apps and flows were placed across license types | A price sheet |
| A named exit and handover model | The exit model from a past program in writing and a reference from that ended engagement | A promise to cooperate at the end |
The rubric has no weights and no points. For each criterion that applies to your program, record what the firm showed. A firm that cannot show evidence on an applicable criterion leaves the shortlist before the RFP; a firm that shows evidence on every applicable criterion goes forward. Which criteria apply is your call: government-cloud experience matters only if the program runs in a government cloud.
What a Firm That Only Does Power Automate Can Answer For
A firm with a strong record of Power Automate builds may be exactly right for a flow-automation project and still be the wrong choice for a platform program. It can usually evidence flows, connectors and the pipelines that carried them. It often cannot evidence an environment layout across app types, Power BI governance, Dataverse design, or licensing across the whole platform, because its engagements never needed them.
If your need really is flow automation, Best Power Automate Development Companies sets out how to rank that narrower shortlist, and Top Power Automate Consultants for Government Contracting narrows it again for government contractors.
Where i3solutions Fits on This Rubric, and Where It Does Not
A guide that tells buyers to demand evidence has to hold its author to the same test, so here is what i3solutions can show against the criteria, stated as the record states it. i3solutions has been a Microsoft partner since 1997. i3solutions is one of the top 5% of Microsoft worldwide partners. i3solutions is a Microsoft Solutions Partner.
Against the criteria, criterion by criterion:
- Governance and Center of Excellence: i3solutions governs client Power Platform tenants with the Center of Excellence Starter Kit, tenant-level and environment-level DLP policies, and managed environment controls.
- Government cloud: i3solutions has deployed Power BI inside a GCC High tenant and inside Azure Government for a federal customer.
- Managed environments: i3solutions runs client Power Platform work on a multi-tenant Center of Excellence model with separate Dev, Test, UAT, and Production environments promoted through managed solutions.
- Licensing: i3solutions implements Power Platform licensing across Power Apps per-app and per-user plans, Power Automate per-flow and per-user plans, and the Microsoft 365 default entitlements where app complexity is low.
- Application lifecycle management: i3solutions delivery includes ALM practices with Power Platform pipelines or Azure DevOps integration, environment separation strategies, and change control processes.
- US-based delivery: Delivery is senior and US-based. i3solutions offers it through its IT staff augmentation services for exactly the regulated contexts where residency and clearance govern.
- Exit and handover: i3solutions delivers partner-led Microsoft delivery as a three-phase engagement, each phase producing artifacts the enterprise keeps, designed to reduce Microsoft delivery risk at each stage rather than discover it at the end. i3solutions structures partner-led delivery as the Delivery Accountability Model, which evaluates and assigns ownership across four dimensions.
Where i3solutions is not the right fit: a single app with no governance conversation, bought on the lowest hourly rate, is not what this delivery model is built for. The government-cloud record stated here is Power BI only; for Power Apps, Power Automate or Dataverse in a government cloud, ask i3solutions for the evidence the same way you would ask any firm on the list.
To engage i3solutions directly once your shortlist is scored, see Hire U.S.-Based Power Platform Developers and Microsoft 365 Experts. The wider practice is described at Power Platform Development Services.
When This Rubric Is the Wrong Tool
A shortlist rubric solves one problem, and four situations call for something else:
- The engagement really is a single flow-automation project, not a platform program: start with the Power Automate guides above.
- An RFP is already out and you need qualification questions, not a ranking: Vendor-Qualification Questions for a Power Platform Center of Excellence RFP picks up with its six scoring areas once this rubric’s seven criteria have done their job and the shortlist is set.
- The estate spans several Microsoft workloads beyond Power Platform: Microsoft Delivery Partner Selection Mechanics covers selection across workloads.
- The open question is whether to use an outside firm at all: In-House IT Staff vs a Third-Party Firm for Power Apps: Which Do You Actually Need? covers that decision.
How to Run the Selection
Order matters more than any single question, because once pricing is on the table every later answer gets read through it:
- Cut the long list to firms whose shape fits a platform program rather than a single component.
- Send each firm the seven evidence requests in writing before any RFP.
- Score the answers on the rubric before any pricing conversation.
- Remove any firm that answers a governance question with a feature list instead of a process description.
- Take the firms that remain into the RFP.
How i3solutions Answers
If i3solutions is on your shortlist, hold it to the same seven requests, criterion by criterion, before any RFP. The answers above are where that conversation starts, and the gaps named above are where it should press.
Contact a senior Power Platform architect
Key Takeaways
The short version, for the meeting where the shortlist is decided:
- There is no independent ranking of Power Platform implementation partners; the ranking comes from evidence the buyer collects.
- Seven criteria decide it: governance and Center of Excellence capability, managed environments, application lifecycle management, government cloud, US-based delivery, licensing and a named exit model.
- Score the shortlist before the RFP, with no weights: a firm that cannot show evidence on an applicable criterion leaves the list.
- Test government-cloud experience component by component, and test the exit model before signing.
Frequently Asked Questions
Is there an independent ranking of Power Platform implementation partners?
No. There is no independent ranking to cite, so score the shortlist yourself on seven criteria: governance and Center of Excellence capability, managed-environment discipline, application lifecycle management maturity, government-cloud experience, US-based delivery, licensing-tier fluency and a named exit model, asking each firm for evidence rather than a description.
What separates a Power Platform implementation partner from a Power Automate development firm?
Scope. An implementation partner runs Power Apps, Power Automate, Power BI and Dataverse as one governed program, with environments, policies, pipelines and an exit plan designed together, while a Power Automate development firm builds flows. Each can be the right choice, for a different project.
What should a Power Platform partner be able to show about government-cloud experience?
Evidence component by component. According to Microsoft Learn, there are exceptions to the principle of maintaining product functional parity within the US Government clouds, so a record with Power BI in GCC High is not evidence for Power Apps, Power Automate or Dataverse there. Ask which components the firm delivered in which cloud.
Does a Power Platform partner need to be US-based?
Only when your program requires it. When residency, export control or a contract clause governs who may work in the tenant, US-based delivery is a gate, so ask for the named people, where they are based and whether any work is subcontracted. Whether a requirement applies is a question for your contracting officer and compliance counsel.
How do we test a Power Platform partner’s exit model before signing?
While the shortlist is still being cut, ask for the exit model the firm used on a past program, in writing, including who on the client side took over each admin role and which clause governed the end of the engagement, then ask that client what happened in the final month. Hold the same model to your own contract before signing.
Has i3solutions run a full Power Platform Center of Excellence engagement, or only components of one?
The record is stated once, row by row, under each criterion in the section on where i3solutions fits on this rubric, so read it there against the seven criteria. Its government-cloud record is Power BI only, so ask for evidence on any other component in a government cloud.
