Power Platform Assistant

Your agent for building solutions with Microsoft Power Platform — covering Power Apps, Power Automate, Power BI, Power Pages, and Copilot Studio with enterprise governance best practices.

When to Use This Agent

Choose Power Platform Assistant when:

• Building canvas or model-driven Power Apps
• Creating Power Automate workflows (cloud flows, desktop flows)
• Designing Power Pages portals for external users
• Implementing Copilot Studio virtual agents
• Establishing Power Platform governance, DLP policies, and environments

Consider alternatives when:

• You need custom .NET development — use a .NET developer agent
• You need Azure infrastructure — use an Azure specialist agent
• You need Power BI specifically — use a Power BI agent

Quick Start

Copy
# .claude/agents/power-platform.yml
name: Power Platform Assistant
model: claude-sonnet
tools:
  - Read
  - Write
  - Edit
  - Bash
  - Glob
  - Grep
description: Microsoft Power Platform specialist for Power Apps, Power Automate, Power Pages, and governance

Example invocation:

claude "Design a Power Platform solution for employee expense approvals — canvas app for submission, Power Automate for approval workflow, and SharePoint list as the data source"

Core Concepts

Power Platform Components

Component	Purpose	Users
Power Apps	Build custom apps (canvas, model-driven)	Business users, citizen devs
Power Automate	Workflow automation (cloud, desktop, process)	All users
Power BI	Business intelligence and reporting	Analysts, executives
Power Pages	External-facing websites	Customers, partners
Copilot Studio	Virtual agents and chatbots	Support, HR, IT
Dataverse	Data platform with security and logic	Enterprise data

Solution Architecture

┌───────────────────────────────────────┐
│          Power Platform Solution       │
├───────────┬───────────┬───────────────┤
│ Power App │ Automate  │ Power BI      │
│ (UI)      │ (Process) │ (Analytics)   │
├───────────┴───────────┴───────────────┤
│            Dataverse                   │
│   Tables │ Security │ Business Logic  │
├───────────────────────────────────────┤
│           Connectors                   │
│ SharePoint│ SQL │ Graph │ Custom APIs  │
└───────────────────────────────────────┘

Configuration

Parameter	Description	Default
app_type	App type (canvas, model-driven, pages)	canvas
data_source	Backend data (dataverse, sharepoint, sql, custom)	dataverse
environment	Environment strategy (dev, test, prod)	dev
governance	Governance model (open, managed, restricted)	managed
license_type	License tier (per-app, per-user, premium)	per-user

Best Practices

1. Use Dataverse over SharePoint lists for enterprise solutions. SharePoint lists work for simple scenarios, but Dataverse provides proper relational data modeling, row-level security, business rules, and calculated fields. The upgrade from SharePoint to Dataverse later is painful — start with Dataverse for anything beyond a simple list.

2. Build solutions in a development environment, not production. Create a dev environment, build and test there, then export as a managed solution and import to production. This prevents accidental changes to production and enables proper ALM with version control.

3. Use environment variables for connection references. Don't hardcode connection strings or API URLs in flows and apps. Environment variables make solutions portable across environments without reconfiguration.

4. Implement DLP policies before users start building. Data Loss Prevention policies control which connectors can communicate. Without policies, a citizen developer could accidentally build a flow that sends company data to a personal email. Define policies proactively.

5. Follow the Power Apps component framework for reusable UI. Build PCF (Power Apps Component Framework) controls for complex, reusable UI elements. Canvas app components are limited; PCF controls offer full TypeScript/React capabilities.

Common Issues

Canvas app performance degrades with many controls and data calls. Loading all data on app start, excessive OnVisible formulas, and too many gallery controls cause slow apps. Use Concurrent() for parallel data loads, implement pagination for large datasets, and reduce the number of data sources per screen.

Power Automate flows fail silently without alerting. By default, flow failures send an email to the owner — which is often ignored. Configure flow failure notifications in a shared channel, add error handling to every action, and use a centralized monitoring dashboard.

Solution import fails between environments. Solutions with unresolved dependencies, missing connection references, or environment variable mismatches fail during import. Always import dependencies first, create connection references before import, and use solution checker to validate before deployment.