Doc EF-INS-11811 · Power Platform for federal teams: what it does and where it stops

20+ years in business

US-owned · SDVOSB

Sheet Insights

Insights

Power Platform for federal teams: what it does and where it stops

This covers what each part of the Power Platform does, where low-code fits for a federal team, and where it stops.

We have done Power Apps, Power Automate, Power BI and SharePoint development and training for a federal budget office since 2019, as a subcontractor. Our Microsoft stack is SharePoint, Power Apps, Power Automate, Microsoft 365 and Teams, and we use Power BI and SQL Server for data and reporting.

The parts, in plain terms

  • Power Apps. A suite of apps, services and connectors, plus a data platform, for building custom business apps. Apps come in two kinds, canvas and model-driven. They can use data in Microsoft Dataverse or in other sources such as SharePoint, Microsoft 365, Dynamics 365 and SQL Server, and developers can extend them with code and custom connectors (Microsoft Learn).
  • Power Automate. Workflows for repetitive tasks and business processes. Cloud flows run automatically, on demand or on a schedule (flow types). Desktop flows are Microsoft’s robotic process automation (RPA). They can drive legacy applications such as terminal emulators as well as modern web and desktop applications (desktop flows).
  • Power BI. Microsoft’s business analytics platform. Power BI Desktop is for modeling data and building reports, the Power BI service is for publishing and sharing, and a mobile app is for viewing reports (Power BI overview).
  • Dataverse. The data store behind much of the platform. Access combines business units with role-based, row-based and column-based security, and business rules on a table validate data no matter which app wrote it (Dataverse overview).
  • Connectors. A connector is a strongly typed representation of a REST API, which makes that API easier for makers to use in low-code apps, flows and chatbots (data policies). Connectors expose actions (“create a file”) and triggers (“when a new item is added”). Some are prebuilt and some you build yourself (connectors overview). Most governance work lands here.
  • Copilot Studio. Microsoft’s low-code studio for building AI agents (Copilot Studio). It replaces Power Virtual Agents. Classic chatbots built in Power Virtual Agents can be copied and converted into Copilot Studio agents (conversion).

Where low-code fits

Microsoft positions Power Apps as a way to turn manual business operations into digital, automated processes (Power Apps overview), and desktop flows as a fit for rule-based tasks (desktop flows).

In our view, low-code fits best when the users already work in Microsoft 365 and SharePoint, the data set is modest, the process is a form, an approval or a tracker, and the people who own the process can help maintain it after it ships. That last point is why training matters as much as the build, and why our budget office work covers both.

Where it stops

Data volume and delegation. In a canvas app, Power Apps tries to hand each query to the data source (delegation). If any part of a query cannot be delegated, Power Apps pulls only the first 500 records and runs the query locally. You can raise that limit to 2,000. Past it, results can be quietly wrong: a filter will not find record 501, and an average covers only the first 500 records. Microsoft’s advice is to set the limit to 1 while testing, so anything that cannot be delegated shows up right away. Dataverse, SharePoint and SQL Server are among the sources that support delegation (delegation overview).

Licensing. Some Microsoft 365 licenses include limited Power Apps and Power Automate rights meant for Microsoft 365 data and standard connectors. They do not give the same rights as standalone premium licenses (licensing and SKUs). Premium connectors, Dataverse tables, on-premises data gateways and custom APIs are examples of features that make an app premium, and model-driven apps use Dataverse and are premium by default. Microsoft says that starting February 2027 it will enforce premium license checks it had applied leniently, including apps in managed environments and model-driven apps (licensing FAQ). Effective January 2, 2026, the Power Apps per app SKU stopped being available to new customers through some purchasing channels; availability for existing customers and Cloud Solution Providers varies. The practical point: decide on the licensing model before you design the data layer, because a choice like “store it in Dataverse” changes who needs which license.

Release management. Power Platform ALM moves apps, flows and tables between environments as solutions, and every environment involved needs a Dataverse database. Microsoft recommends source control as the source of truth (ALM overview). If the team needs a dev, test and production path, plan for it from the start.

Governance: environments and data policies

Environments. An environment is a container for an organization’s apps, flows, chatbots and data. An app can connect only to data sources in its own environment, and each environment can have zero or one Dataverse database. Every tenant gets a default environment that cannot be deleted. Every user who signs up for Power Apps is added to its Maker role, and Microsoft says it has no backup guarantees and should not be used for production workloads (environments overview). Microsoft suggests renaming it to something like “Personal Productivity Environment” so its purpose is clear (securing the default environment).

Data policies (often called DLP policies). Admins use data policies to control which connectors makers can use. If a policy blocks a connector, a maker cannot save an app or flow that uses it, and existing apps and flows that break the policy are suspended (data policies). Connectors sit in Business, Non-business or Blocked groups. New connectors land in Non-business by default. For the default environment, Microsoft recommends making Blocked the default so new connectors stay unusable until an admin reviews them. Sharing an app with “Everyone” is off by default, and Microsoft recommends keeping it off (securing the default environment).

Managed environments. A set of premium admin features, including sharing limits, usage insights, solution checker, IP firewall and customer-managed keys (managed environments). Once an environment is managed, all active use in it requires a qualifying license, including users running standard apps (licensing FAQ).

The government clouds: GCC, GCC High and DoD

Microsoft runs separate US Government versions of Power Apps and Power Automate (Power Apps US Government, Power Automate US Government). In all three, customer content is physically segregated from the commercial service and stored in the United States, and Microsoft administrator access to it is restricted to screened personnel who are US citizens (Power Apps US Government).

CloudWhat Microsoft says it meets or aligns withNotes
GCCFedRAMP High, DoD DISA IL2, criminal justice (CJI) data requirementsUses public Microsoft Entra ID for identities
GCC HighDISA SRG IL4Available since September 2019; for DoD contractors and federal agencies on Microsoft 365 GCC High; requires Microsoft Entra Government
DoDDISA SRG IL5Available since April 2021; DoD entities only

Each cloud has its own sign-in URLs: makers in GCC use make.gov.powerapps.us rather than make.powerapps.com. Microsoft says it strives for feature parity with the commercial service and publishes a summary of the exceptions (Power Apps US Government). Power BI has its own list. For example, Power BI for US government is not available as a Free license, and Azure Maps is not available in GCC, GCC High or DoD (Power BI for US government).

“Meets all federal security requirements” is not a real claim

You will still see it said that Power Apps meets all federal security requirements. No product does that for you. Here is what Microsoft actually says (Power Apps US Government):

  • Power Apps US Government is designed to support FedRAMP accreditation at the High impact level, and FedRAMP artifacts are available for agencies to review when they decide whether to grant an Authority to Operate (ATO). Power Apps is authorized as a service within the Azure Government FedRAMP ATO. That covers the service, not the app your team builds on it: the agency still grants the ATO for your system.
  • Client applications, including the web client and the Power Apps mobile apps, are outside the accreditation boundary, and government customers are responsible for managing them.
  • Third-party services reached through connectors may store or process your data outside the government cloud, and are not covered by Microsoft’s compliance and data protection commitments for the service.

So the security of a Power Platform app depends on the cloud you are in, the connectors your data policies allow, who can share what, and the agency’s own authorization. Your team owns each of those decisions.

What we would tell a federal team starting out

What we would do first, based on the guidance above:

  • Pick the cloud first (GCC, GCC High or DoD), because URLs, identity and feature availability differ.
  • Write the data policy before the first production app, and treat the default environment as personal productivity only.
  • Check delegation early, with the row limit set to 1.
  • Decide licensing and the data store together.
  • Budget time for training the people who will own the apps.

Sources

  1. Microsoft Learn: What is Power Apps?
  2. Microsoft Learn: Types of Power Automate flows
  3. Microsoft Learn: Introduction to desktop flows
  4. Microsoft Learn: What is Power BI?
  5. Microsoft Learn: What is Microsoft Dataverse?
  6. Microsoft Learn: Connectors overview
  7. Microsoft Learn: Overview of Copilot Studio
  8. Microsoft Learn: Converting Power Virtual Agents chatbots to Copilot Studio agents
  9. Microsoft Learn: Understand delegation in a canvas app
  10. Microsoft Learn: Power Platform licensing and SKUs
  11. Microsoft Learn: Power Apps licensing FAQ
  12. Microsoft Learn: ALM with Power Platform
  13. Microsoft Learn: Environments overview
  14. Microsoft Learn: Secure the default environment
  15. Microsoft Learn: Data policies
  16. Microsoft Learn: Managed Environments overview
  17. Microsoft Learn: Power Apps US Government
  18. Microsoft Learn: Power Automate US Government
  19. Microsoft Learn: Power BI for US government customers