Managed Power Platform Governance and Support

It is a recurring monthly service in which IT Partner operates your existing Power Platform tenant: environment and DLP connector-policy management, triage and fixes for failing flows and apps inside a 4-hour monthly allowance, an orphaned-app and ownership watch, a license and capacity watch, a monthly governance dashboard review, a monthly maker office hour, and a monthly report. It costs a flat $750 per month for the tenant, with no long-term commitment.

Organizations running ten or more production apps and flows — built by their own makers, by us, or by anyone — with no Power Platform administrator on staff. If a flow stopped when its maker left, a connector deprecation caught you by surprise, or nobody can say what the default environment contains, this plan is the missing role.

Up to 4 engineer-hours per calendar month of flow and app fixes and small changes — connection re-authorization, replacing deprecated actions, repairing connection references and environment variables, correcting expressions and error handling, small tweaks, solution imports between environments — with any single item sized at 2 hours or less. We track time to the quarter-hour and itemize it in the monthly report. Unused hours do not roll over. Fixing something we configured, and Microsoft service incidents, never count against it.

You get a written quote first, never a surprise invoice. Small overflow runs hourly at $175 through Custom Business Apps and Process Automation, pre-approved by you; a rebuild, a redesign, or a net-new app or flow is quoted as a fixed-price project through the development services. If you find yourself exceeding the allowance most months, we will say so and propose a larger plan rather than billing overflow indefinitely.

Direction. The development services build: a new approval flow, a new app, a custom connector, an Access migration — scoped, quoted, delivered. This plan runs what exists: policy, ownership, failures, licenses, capacity, and the makers who keep building. Most clients use both — the build channel for new work, the plan so that what was built keeps working after the project team leaves.

Less than it was. Microsoft has stated that the CoE Starter Kit is no longer receiving feature investments or updates — its GitHub repository was archived in July 2026 — and now points to the Power Platform admin center's built-in Inventory, Usage, Monitor, and Actions experiences for the same visibility. If you already run the kit, we keep it running and review its dashboards for as long as it remains useful; we do not deploy it fresh, and the admin center is our primary source either way.

No. Onboarding includes a light governance baseline — an environment map, a DLP policy inventory with gaps named, admin roles, capacity and license posture, and an ownership register — which is enough to operate safely. A full Center of Excellence standup, with environment strategy, DLP design, and a maker onboarding process, is a separate fixed-price project, Power Platform Governance and Center of Excellence Setup; many clients run it first and hand the result to this plan, but it is not a prerequisite.

Data-loss-prevention policies in the Power Platform admin center classify connectors — business, non-business, blocked — per environment, and they are the single most effective control over where your data can flow. We keep the classification deliberate, apply policies to new environments, answer every connector request inside the month with a written yes, no, or 'yes in this environment', and make sure a maker whose flow is blocked gets an explanation and a route rather than a dead end.

An app or flow whose owner has left, been disabled, or changed roles. Flows in particular run on their owner's connections, so a departure can stop a production process days or weeks later with no warning. Each month we find these items, reassign them to a named business owner with a co-owner, or retire them on your decision — before they fail rather than after.

Premium licenses and pay-as-you-go reconciled against actual use; apps and flows that need a premium, per-app, or Process license and do not have one; Managed Environment licensing consequences; and Dataverse database, file, and log capacity plus Power Platform request consumption against your entitlements. The point is that a licensing or capacity purchase is a decision made on evidence, a month early, not a warning banner in the admin center.

One 60-minute session a month, open to your makers. They bring the flow that will not run, the design they are unsure about, the connector they cannot use — and leave with an answer, a pattern, or a ticket. Answers are recorded so the community learns once. It is not a training course; the Power Apps App in a Day Workshop is the training course.

No — that is Dynamics 365 Administrator on Demand. The two share Dataverse, so this plan watches the capacity pool and the environments, while security roles, business units, and application configuration for Sales, Customer Service, or Business Central are administered there. Many clients run both.

We govern the environments and connectors agents live in — DLP, ownership, capacity — but not the agents themselves. Building an agent is Custom Agent Development with Microsoft Copilot Studio; running and optimizing agents is Managed AI Agent Operations and Optimization. The three fit together without overlapping.

First response within 1 business hour — IT Partner's published support SLA. We publish our monthly support statistics for every month since December 2023, including the months we missed, so you can verify the record instead of trusting the sentence.

Least-privilege GDAP that you approve — Microsoft's granular, time-bound partner access model, including the Power Platform administrator role. Our default request is Microsoft's standard starter relationship; anything more is requested per task and expires. We never ask for standing Global Administrator, and our default access policy is published for you to compare against what we actually request.

A flat $750 per month for the tenant, billed monthly, with no long-term contract: stop any month, and all we ask is payment of previously approved invoices. No lock-in in either direction is a published IT Partner term — it is also why the monthly report has to keep earning the renewal.