Power Platform API and SDKs: From UX-First to API-First

Power Platform: Evolving from UX-First to API-First

Microsoft is transforming Power Platform administration by moving from a user interface (UX)-first model, centered around the Power Platform Admin Center (PPAC), to an API-first ecosystem. Every capability in PPAC will now be mirrored by a public, well-documented API—enabling developers and admins to build scalable, automated, and intelligent solutions with greater flexibility.

Key Enhancements:

1. Unified Power Platform API Gateway

  • A single gateway will host all internal APIs.
  • Enables centralized audit logging, granular role-based access control (RBAC), and a consistent developer experience across all management features.

2. Developer-Centric SDKs

  • Official C# SDK launched at Microsoft Build 2025.
  • More SDKs coming in TypeScript, Python, and via Logic Apps & Power Automate connectors, all auto-generated using Microsoft Graph’s Kiota tool for reliability and standardization.

3. CLI & PowerShell Integration

  • Command-line tools are being aligned with Azure Resource Manager (ARM) practices.
  • Will include service principal and managed identity support, plus a cloud shell experience in PPAC.

4. Model Context Protocol (MCP) Support

  • MCP enables deeper AI integration and automation.
  • Initial MCP support is being rolled out in CLI for list/get operations.
  • Future integration in Power Platform for Admins V2 connector within Copilot Studio will allow AI-driven management workflows across environments.

This evolution empowers developers, admins, and makers to manage Power Platform with greater intelligence, automation, and security—creating a control plane that is both human- and AI-understandable. Microsoft invites the community to participate, share feedback, and stay up to date through the Power Platform Community and SDK/API release notes.

Apply Job