What are Monitor Alerts?

Monitor alerts allow tenant and environment administrators to proactively monitor the operational health of their Power Platform resources and receive notifications when health metrics fall below thresholds they define. Instead of learning about problems from end users, admins can identify and address issues before they cause disruption. This reduces downtime and improves reliability across the organization.

What’s New with GA

Predefined alerts — protection with zero configuration

The biggest addition we’ve added is predefined alerts: a set of configured, Microsoft-authored alerts that are enabled by default for every tenant. These alerts automatically surface high-use canvas apps, model-driven apps, agents, desktop flows and cloud flows whose health has dropped below recommended baseline thresholds — with no setup required.

For example, predefined alerts will flag when:

• The availability of high-use canvas apps drops below 90%
• The availability of high-use model-driven apps drops below 90%
• High-use cloud flows are experiencing success rate degradation

Predefined alerts give admins an immediate signal on what matters most in their tenant, even before they’ve configured a single custom alert rule. Items can trigger these alerts regardless if they’re in a managed environment, and predefined alerts will encourage users to create their own alert rules to monitor these items against their own custom thresholds.

Redesigned Monitor overview page

We redesigned the Monitor overview page to be alerts-centric. When you land in Monitor, you now get an at-a-glance view of active alert conditions and resource health across your environments — making it faster to identify what needs attention and act on it.

Code app alerts

Custom alert rules now support alerting on your code apps in addition to canvas and model-driven apps. This gives admins deeper visibility into code app performance and the ability to catch performance degradation before it affects users’ day-to-day experience.

Work queue alerts (public preview)

Admins can now configure alerts for Power Automate work queues in Monitor, enabling proactive monitoring of work queue health alongside apps, flows and agents. This capability is launching in public preview alongside alerts GA.

How Monitor Alerts Work

Admins define threshold-based rules on Monitor metrics. For example, this can look like receiving an alert when a cloud flow’s success rate drops below a custom threshold, or when a canvas app’s availability falls below an acceptable level.

Monitor alerts evaluate alert rules daily after aggregating new metric data for your environments. When a metric breaches a threshold, admins receive an email notification with a direct link to the details that triggered the alert.

You can scope alert rules to an environment or individual item, configure multiple recipients per rule (including security groups), and manage all active rules and review triggered alert history from the Alert Rules view in Monitor.

What’s Supported

We’re excited for you to improve the operational health of your apps, agents and automations in Power Platform. Learn more about Monitor and how to create alerts here.

The post Power Platform Monitor Alerts Are Now Generally Available appeared first on Microsoft Power Platform Blog.

What came through clearly in that conversation is that most organizations aren’t struggling to adopt agents because the technology is unsafe. They’re struggling because their governance models were built for a world that no longer exists. 

While traditional security models still depend on a clear distinction between “inside” and “outside,” and that boundary absolutely still matters. What’s changed is the pace. Agents now move fluidly across apps, data sources, and workflows often spanning environments that were designed with autonomous or semi-autonomous systems in mind.

When building an agent or app can take minutes, imposing governance models built around week-long and manual review processes quickly break down. The challenge isn’t whether to govern—it’s how. Governance has to account for blurred boundaries and apply the right oversight so teams can move fast, without losing control. 

When governance strategies boil down to “lock everything down” or “we’ll figure it out later,” the outcome is predictable: either uncontrolled adoption or shadow IT with no visibility. Neither is a win. 

The governance questions every AI agent should answer

The most effective organizations aren’t trying to stop agents. They’re figuring out how to classify risk clearly and apply the right controls at the right time. 

If governance is just a list of things people can’t do, that’s not governance—it’s a backlog of workarounds waiting to happen. Disruptors and innovators always find a way – whether it’s inside the system or outside your line of sight. When there’s no supported path to do the right thing, shadow IT isn’t a failure of discipline, it’s the natural result. Constraints without alternatives don’t stop innovation, they just push it underground, encouraging shadow IT. 

Real governance sets boundaries that let teams move fast and stay safe: 

• What data sources an agent can access 

• How broadly can it be deployed or shared 

• What actions is it allowed to take 

• What identity does it run under 

• What level of oversight applies as risk increases 

A low-risk personal productivity agent is not the same as an agent connected to a core business system. Treating them as if they are leads to predictable points of failure. You either over restrict everything and stall innovation, or you under-protect what actually matters, leaving critical systems exposed. Governance only works when it reflects the real differences in risk. 

Risk isn’t binary—and AI governance needs a risk-based model

A practical way to make this operational is a simple risk-based model. Not theoretical. Operational. 

Think in terms of graduated risk zones: 

• Low risk: constrained, self-serve scenarios where people can build and use agents with tight guardrails—limited data access, limited sharing.  In this scenario, makers don’t need to open a ticket for every idea, and IT doesn’t have to micromanage. Teams can move quickly, building with confidence, without friction, and IT can stay out of the critical path,  

• Medium risk: broader sharing, more sensitive data, more meaningful actions. These scenarios trigger review and oversight—but without resetting momentum or forcing heavyweight governance on every idea. 

• High risk: business critical workflows tied to core systems. These need deliberate control from day one. Not “nobody can build,” but “the right people build inside the right boundaries, with the right oversight.” 

The point isn’t the labels. The point is clarity. Risk is contextual. Governance should be too. 

Where governance actually gets enforced: the platform

Governance only works when it’s enforced inherently by the platform, not layered on through policy decks, emails, or spreadsheets. 

That’s why a concept of managed platform matters: Make security, governance and operations part of the platform experience—inventory, usage insight, controlled sharing, connector governance, and lifecycle management—rather than an external process held together by best intentions. 

Managed environments—our practical adoption of the managed platform concept—are a Power Platform capability, not something limited to a single product or workload. Managed environments enable teams to manage apps, automations, pages, and even agents built in Microsoft Copilot Studio 

One of the cleanest controls is also one of the simplest: sharing limits paired with a clear on‑ramp. 

If someone builds something for themselves or for their immediate teammates, that’s one risk profile. If they want to share their solution more broadly, that’s a different one. The platform needs to distinguish between those cases. When it does, you can let people experiment freely—and require deliberate promotion, review, and accountability when something is ready to scale. 

Agents don’t create permission problems—they expose them 

This bears repeating, because it matters: agents generally operate as the calling user. They don’t magically gain new permissions. Which means agents don’t create access problems; they expose the ones you already have, faster. 

If users have overly broad permissions today, agents will too. That’s not an agent problem—it’s an identity and access discipline problem. Effective agent governance only works when it’s built on solid foundations. 

Trust by design, with verification built-in 

Strong proactive controls matter, but they’re not enough on their own. You still need reactive controls: monitoring, diagnostics, and audit trails, especially when agents take actions with compliance implications. 

Trust but verify still applies. Looking at the familiar expense-approval analogy: humans unintentionally approve things incorrectly all the time. We manage that risk with audits, compensating controls, and limits on blast radius. Agent risk should be treated the same way: know what happened, understand why it happened, and contain the impact when it doesn’t go as planned. 

The takeaway 

The future isn’t “agents everywhere with no control,” and it’s not “no agents because risk.” Both fail. 

The practical path is adaptive governance: classify risk clearly, enforce it through the platform, and create promotion paths so good ideas can scale without turning into tomorrow’s incident response. 

That’s how organizations stop playing defense. If you want to learn how you can start saying “yes” safely, please watch the full interview with Fernando. 

The post ​Building trustworthy AI: A practical framework for adaptive governance appeared first on Microsoft Power Platform Blog.

Data is the center of every organization. With millions of records deleted daily—whether through routine clean-ups, app usage, or retention policies—the risk of accidental or malicious data loss is real and costly. Lost data can disrupt operations, impact compliance, and harm reputation. 

To prevent this, we are excited to announce that the capability to restore deleted table records in Microsoft Dataverse in General Availability starting late April 2026 with additional enhancements based on feedback from customers and MVP community. Organizations have the assurance that they can recover from unforeseen data loss without disruptions, ensuring business continuity and customer trust. 

How Data Loss Happens 

Records can be deleted from multiple sources and understanding these data loss scenarios is essential: 

• Custom apps used by end users. End users often interact with apps directly, and accidental deletions can occur during everyday tasks.  

• Makers building solutions. Makers frequently experiment and iterate while creating apps and flows. During this process, records may be deleted unintentionally. 

• Admins running bulk delete jobs. Admins schedule clean-up jobs to optimize performance and storage. However, these automated jobs can sometimes remove data that later proves necessary. 

• Retention policies moving old data to managed data lakes. Older data moved to cold storage optimizes performance and reduces costs. However, restoring from cold storage can be slow and complex.  

Consistent Deleted Records Keeping 

Previously, deleted records keeping settings could vary by table, creating complexity for admins and uncertainty for users. For example, in environments with parent-child relationships, partial keeping of deleted records often meant incomplete recovery—leading to operational risks. 

To eliminate this complexity, deleted records keeping is now managed at the environment level. Admins can enable or disable deleted records keeping for all tables in an environment with a single setting by going to feature management.  

This change ensures: 

• Consistency: No more guessing which tables are covered. Every table in the environment follows the same deleted records keeping policy, reducing confusion and ensuring predictable outcomes. 

• Reliability: Full recovery of related records. Parent and child records are kept together, eliminating partial recovery scenarios and safeguarding data integrity. 

• Simplicity: Reduced administrative overhead. One setting replaces multiple table-level configurations, saving time and reducing the risk of misconfiguration. 

This streamlined approach to deleted records keeping turn a fragmented setup into a consistent, organization-wide safeguard. 

Admins with Full Control and Visibility 

With this update, admins in Power Platform Admin Centre (PPAC) gain complete authority over deleted record keeping and clean-up, along with clear visibility into storage usage: 

Optimize with Confidence

Admins can manage deleted record keeping periods (up to 30 days). Admins can make informed decisions to balance data safety with storage efficiency, tailoring deleted records keeping period to business needs.

Flexible Clean-Up Options

Admin can use the new “Delete All Records” button for quick purges or selectively delete records for granular control. Whether performing routine maintenance or responding to urgent storage constraints, admins have the tools to act swiftly. 

Visibility into storage used by deleted records 

Admins can now view the storage consumed by deleted records, enabling informed actions to manage database capacity. 

This approach not only empowers admins but also transforms deleted records keeping management into a strategic advantage—balancing data safety with cost efficiency and operational clarity. 

Business Benefits

These improvements aren’t just technical changes—they deliver tangible business benefits: 

• Reduced risk. Protect against accidental or malicious deletes with a reliable safety net. 

• Operational resilience. Restore critical data quickly to maintain continuity and avoid downtime. 

• Simplified governance. One setting for all tables means fewer surprises and easier compliance. 

With Dataverse, your organization gains a dependable safety net and the flexibility to stay in control of its data. To learn more:  

• Restore deleted Microsoft Dataverse table records – Power Platform | Microsoft Learn 
• Restore deleted records with code – Power Apps | Microsoft Learn 

The post Safeguard, Restore, and Manage Deleted Records in Microsoft Dataverse appeared first on Microsoft Power Platform Blog.

In a recent conversation I had with Dion Hinchcliffe at Futurum, we spent time unpacking a shift I’m seeing consistently across enterprises experimenting with AI. It’s not just about copilots or chat interfaces. It’s about something deeper: a change in how work is designed, governed, and operated when systems can reason and act with intent.

For decades, applications have been the primary interface between people and systems. Work meant navigating menus, filling out forms, and clicking through screens carefully designed to constrain what users could do. Productivity improvements came incrementally—better layouts, faster load times, and more automation behind the scenes—but the underlying engagement model stayed the same. People adapted to software.

That model no longer holds.

As organizations race to adopt AI, a new challenge is becoming clear: translating human intent into systems that can act autonomously—without sacrificing control, security, or trust. Intent-first development addresses that gap by reshaping how agentic applications are designed, governed, and delivered at scale.

Agents as the new interaction layer

Instead of teaching people how to use systems, we can let people express intent—and allow systems to determine how that intent is carried out. This is not about replacing all apps overnight. It’s about changing their role. Apps no longer need to expose every possible action through UI. Instead, they:

• Provide trusted capabilities the agent can invoke
• Enforce business rules and permissions
• Act as systems of record, not systems of navigation

As AI systems become capable of reasoning, acting, and adapting, organizations are beginning to rethink the relationship between humans and software. In an agentic model, the agent becomes the primary interaction surface. A user may no longer need to know which system to open or which workflow to follow. They can simply state what they want to achieve: open a purchase order (PO), resolve this case, prepare a customer briefing.

Behind the scenes, agents orchestrate the necessary steps across systems, policies, and data sources. Procurement rules are applied. Approvals are routed. Records are updated. The user expresses intent once; the system coordinates the work.

Agentic solutions aren’t eliminating applications, but they are changing how people engage with them. Apps are the trusted capabilities agents rely on—serving as systems of record, sources of authority, and enforcement points for business rules and permissions. Applications shift from user destinations to services agents invoke. Agents work because structure already exists.

Rethinking enterprise complexity: Orchestration over navigation

This shift becomes clearer when you look at everyday enterprise processes.

Take something as common as opening a purchase order. Today, that often means navigating multiple tools, involving several teams, and manually coordinating approvals. The complexity isn’t the work itself—it’s knowing how to move through the systems.

With an agent‑first approach, that complexity is inverted. A user can simply say they need to open a PO for a project. The agent determines which background agents are required—vendor management, policy validation, approvals—and orchestrates the process across systems without forcing the user to navigate them.

We see the same pattern emerging in CRM. Rather than sales teams manually updating records, agents can monitor emails, calls, calendars, and systems in the background—keeping data current and surfacing relevant context proactively. The agent becomes the interface to customer intelligence, while the CRM remains the authoritative store behind it.

The value here isn’t conversational UI for its own sake. It’s reducing cognitive load while preserving control.

Agents as the business logic and decision layer 

This shift also changes where business logic lives.

Traditional enterprise systems embed logic deep inside individual applications—rules, workflows, and decision trees hardcoded into each tool. That makes change expensive and reuse difficult. When requirements evolve, logic must be rewritten repeatedly across systems.

Agentic systems invert that model. Logic moves into a shared reasoning layer that sits above systems of record. Agents evaluate intent, context, and constraints, then determine which actions are required right now. Policies, best practices, and exceptions can be defined once and applied consistently across processes instead of being repeatedly embedded in individual applications.

This is where the economics of software start to change. Improvements to reasoning or decision quality can compound across organizational functions—HR, finance, operations, and customer engagement—without rebuilding each system individually. Business value shifts from static workflows to shared enterprise intelligence.

Headless agents as a new layer of digital labor 

Not all agents interact directly with people.

Many of the most impactful agents operate quietly in the background—monitoring systems, reacting to triggers, coordinating tasks autonomously. These “headless” agents update records, flag issues, generate reports, and escalate decisions only when human judgment is required.

Together, conversational and headless agents form a new layer of digital labor. Routine work is handled automatically. Humans stay focused on oversight, judgment, and exceptions. The agent doesn’t replace enterprise logic—it coordinates it.

Operating agentic systems at scale requires a control plane

One point Dion and I kept coming back to is this: the real challenge with agentic systems isn’t building the first one. It’s operating hundreds—or thousands—of them responsibly.

As agents scale across teams and geographies, the questions shift quickly. How do you maintain visibility into what agents are doing and why? How do you enforce security, policy, and compliance consistently as agents act across systems? How do you measure impact, cost, and effectiveness as usage grows?

Without a managed platform, intent first development becomes ungovernable at scale. Logic fragments. Visibility breaks down. Early experimentation turns into operational risk. Governance must mature alongside autonomy.

This is where enterprise readiness becomes decisive.

Governance, lifecycle management, observability, and control aren’t optional add‑ons. They’re the foundation that allows agents to operate safely and reliably. Successful enterprise adoptions hide complexity behind an interface that works the way people already think.  Agents don’t eliminate the need for structure—they depend on stronger, more explicit structure than traditional automation ever required.

From pilots to an enterprise operating model

Most organizations begin with pilots—and that’s the right place to start. But pilots stall when governance, ownership, and measurement are treated as afterthoughts.

The pilots that scale share common patterns: centralized policy management, clear accountability between IT and business teams, built-in monitoring, and an explicit path from experimentation to production. Governance isn’t what slows progress; it’s what gives leaders confidence to move faster.

Over time, this becomes more than a collection of use cases. It becomes an operating model. Work shifts from task execution to outcome driven orchestration. Processes move from periodic redesign to continuous optimization. Systems adapt as business intent evolves.

Building adaptive enterprise systems for an agent-first world

This shift isn’t about predicting the future. It’s about building systems that can adapt as it arrives.

Agentic transformation isn’t just a technical change. It’s an operational one—reshaping how work is designed, governed, and continuously improved across the enterprise. Organizations that invest early in the right foundations—clear intent, strong constraints, and disciplined scale—will be positioned to turn intelligent applications into a durable advantage, not a fleeting experiment.

The most successful organizations won’t ask how to bolt agents onto existing apps. They’ll ask how to redesign systems so agents can sit confidently at the front door—turning intent into action with trust, speed, and scale.

In an agent first world, applications remain systems of authority and agents simply coordinate how and when those capabilities are invoked. Apps evolve:

• From destinations → to services
• From user driven workflows → to agent orchestrated actions
• From “where work happens” → to “how work is made possible”

If you want to hear this thinking unpacked in more detail, I explore these ideas directly with Dion Hinchcliffe at Futurum—from agents as the new interaction layer, to why governance becomes more critical, not less, as autonomy increases. Our conversation gets into real enterprise examples, the challenges of moving beyond pilots, and what it actually takes to operate agentic systems at scale.

I encourage you to watch the full interview to hear how these concepts show up in practice and to learn how intent first development is shaping the future of enterprise AI.

The post From apps to agents: Rearchitecting enterprise work around intent appeared first on Microsoft Power Platform Blog.

Summary Welcome to the Power Platform monthly feature update! We will use this blog to share news in Power Platform from the last month, so you can find a a summary of product, community, and learning updates from Power Platform in one easy place. Now, let’s dive into what’s new in Power Platform:

Apps, agents and Copilot

Public preview: M365 Copilot chat in model-driven apps

Copilot chat is now available directly inside apps built with Power Apps, bringing the intelligence of Microsoft 365 Copilot into the flow of business processes.

This unified experience—currently limited to model-driven apps—lets users ask questions, reason over in‑app data, and connect insights from documents, communications, and collaboration—without leaving the application they’re working in. By embedding Copilot chat into low‑code apps, organizations can keep users in context and in flow, reducing app switching while accelerating decision‑making. Teams can also leverage powerful first‑party agents like Researcher and Analyst, as well as custom Copilot Studio agents, to analyze data, generate insights, and take informed action directly within their apps.

To manage Microsoft 365 Copilot chat for model-driven apps, start by learning how to manage Microsoft 365 Copilot chat. Power Platform administrators can set up and configure the Microsoft 365 Copilot chat feature for users in their environment and makers can then enable or disable Microsoft 365 Copilot chat for a specific model-driven app.

Public preview: Power Apps MCP and enhanced agent feed

We’re bringing Power Apps Model Context Protocol (MCP) Server and an enhanced agent feed into public preview. This is a step to enable better human-agent collaboration directly inside business applications with built‑in human supervision.

Power Apps MCP brings agentic features from apps to agents as tools – starting with data entry. Agents will be able to parse the unstructured data into forms that users use in apps and create records directly, as well as flag them for human review or action.

The enhanced agent feed provides a shared workspace for humans to oversee the agent activity—makers can provide granular visibility into agent actions for their users, use side‑by‑side comparison views for approvals, and direct navigation to in‑app records.

Building modern apps

Public preview: a new modern Card control

This new modern Card control helps makers build clean, responsive, and consistent UI layouts in canvas apps.

The modern Card control allows makers to present structured information—such as summaries, previews, and tiles—using a single layout‑aware control instead of composing multiple classic controls. Cards automatically adapt to vertical or horizontal layouts and align with Fluent UI design principles, improving visual consistency across apps.

By reducing layout complexity and improving responsiveness out of the box, the Card control enables faster UI composition while supporting accessibility and scalability across screen sizes.

Generally available: theme copy‑paste

With theme copy-paste it is it easy to reuse visual styles across canvas apps without manual reconfiguration.

Theme copy‑paste allows makers to copy and reuse a Canvas app’s theme—including colors, typography, and styling tokens—across other apps. These themes are copied as YAML which can also be edited manually by makers as text. This reduces repetitive setup and helps ensure consistent branding and visual identity across an app portfolio. 

By simplifying theme reuse, this update accelerates new app creation and supports design governance at scale, especially for teams managing multiple canvas apps across environments.

Generally available: confirm() function in canvas apps as a fluent dialog

The Confirm function displays a modal confirmation dialog over the current canvas screen, prompting the user to explicitly confirm or cancel before continuing. In canvas apps, there’s also a dismissal path (for example, clicking outside the dialog) that is treated as no action and returns blank.

The canvas experience is designed to align with Fluent dialog behavior and to respect the current app theme. You need to have modern controls turned on to get fluent dialog, else you will get a browser native dialog.

Managed platform

Public preview: move canvas apps and custom SharePoint forms out of the default environment

The default environment in Power Platform often becomes a shared space where makers build and test applications, leading to potential challenges with governance and organization. As resources accumulate in this environment without structured oversight, administrators may face difficulties managing security policies, tracking ownership, and maintaining compliance across their tenant.

We introduced a recommendation in Power Platform advisor, as a preview, that enables administrators to migrate certain canvas apps and custom SharePoint forms from the default environment to designated managed environments. The migration can be done manually from the Recommendations page under the Actions menu in the Power Platform admin center or automated using the Power Platform for Admin v2 Connector. When moving apps, administrators can choose to keep the original resource as is or restrict access to it by quarantining, or deleting it entirely.

This helps Power Platform administrators in implementing effective governance and DLP controls and establish clearer boundaries for app development.

Generally available: host and run code apps in Power Apps

We’re excited to announce that code apps in Power Apps are now generally available, empowering developers and IT alike at a moment when organizations are building more custom applications than ever. With the rise of AI‑accelerated and code‑generation‑assisted development, teams can build high‑quality web apps faster than before while IT faces mounting expectations around governance, security, and operational oversight. Code apps bridge that gap by giving developers full code‑first flexibility and giving IT the enterprise‑grade guardrails needed to manage a growing app landscape

Power Apps code apps bring the full strength of Power Platform to web developers. Build with popular frameworks (React, Vue, and others) in any code-first IDE, and deploy to Power Apps. Every code app automatically becomes a governed Power Platform asset, giving IT visibility and control without creating friction for developers. 

Learning updates

Training paths and labs

Updated training

• Create and customize sites with Power Pages design studio – Training
• Explore Power Pages design studio data and security features – Training
• Explore Power Pages templates – Training

Power Apps maker

New

• Use preview tools and upcoming features in Dataverse MCP server
• Use modern themes in canvas apps  

Updated

• Create or edit model-driven app web resources to extend an app
• Generate a page using natural language
• Overview of pipelines in Power Platform
• Admin deployment page
• Use table segmentation in solutions
• Add Microsoft 365 Copilot chat for app user in model-driven apps
• Overview of the new Power Apps vibe experience
• Create apps, data, and plans together using Power Apps vibe
• Card modern control in Power Apps
• Keyboard shortcuts for canvas apps
• Sign in to Power Apps

Power Platform administration

New

• Move apps from the default environment (preview)

Updated

• Virtual Network support overview
• Set up virtual network support for Power Platform
• Automatic deletion of Power Platform environments
• Microsoft 365 environment for recurring Copilot prompts
• Preview and experimental AI models
• Export data to Application Insights
• General availability deployment
• PowerShell support for Power Apps and Power Automate
• Environment routing
• Manage Copilot Studio credits and capacity
• Buy Power Automate licenses
• Restore deleted Microsoft Dataverse table records (preview)
• Dataverse capacity-based storage details
• Configure Dataverse search for your environment
• Track, manage, and scale Copilot adoption in the Power Platform
• Content security policy
• Continuous access evaluation (preview)
• Power Platform inventory
• Finance and operations storage capacity
• Permissions and roles for SharePoint document management tasks
• Allow external language models for generative responses
• View and manage on-premises data gateways
• System Settings Service tab
• Administrator analytics and reports for Microsoft Power Apps
• Microsoft Power Platform admin documentation
• Power Platform inventory API
• Discover what drives engagement in the Power Platform by using the Usage page
• Configure email resolution with the DoNotResolve flag
• Licensing and AI Builder credits
• Licensing and Copilot Credits
• End of AI Builder credits
• Workflows agent privacy and data subject request (DSR) FAQ

Power Platform developer

New

• Web API Query Data Sample (PowerShell)
• Web API Conditional Operations Sample (PowerShell)
• Web API Functions and Actions Sample (PowerShell)
• dataApi reference for generative pages
• RetrieveTimeZone sample (C#)

Updated

• Power Apps code apps overview (preview)
• How to: Connect your code app to data (preview)
• How to: Connect your code app to Dataverse (preview)
• navigateTo (Client API reference) in model-driven apps
• How to: Configure Content Security Policy (preview)
• Generate a page using natural language with model-driven apps in Power Apps
• Microsoft Power Platform CLI auth command group
• Dataverse SDK API Reference
• Microsoft Power Platform API reference

Power Apps user and mobile

Updated

• How mobile offline works in Power Apps
• Use Microsoft 365 Copilot chat in model-driven apps (preview)
• Optimize the offline profile
• Set up mobile offline for canvas apps
• FAQ for Dataverse search
• What is Dataverse search?
• Visualize data in a view with Copilot (preview)
• Customize and build your mobile app using the wrap wizard
• Prevent canvas app restarts in the Power Apps mobile app
• Check user access to a row
• Use Copilot’s form fill assistance feature in model-driven apps
• Use Copilot chat in model-driven apps
• Modern, refreshed look for model-driven apps
• Supervise agents in model-driven apps with agent feed

Power Pages

New

• Connect Power Pages server logic to Azure Function
• Power Pages Server Logic Debugging Guide

Updated

• Create an event registration page
• How to interact with Dataverse tables using server logic
• Power Pages server logic overview (preview)
• Advanced Settings (preview)
• Create and deploy a single-page application in Power Pages
• Set page permissions
• Security agent (preview)
• Add Copilot summarization to case page (Preview)
• Configure Omnichannel with Power Pages site agent
• Edit code with Visual Studio Code for the Web (preview)
• Use the Visual Studio Code extension
• FAQ for site search with generative AI
• Set up Microsoft Entra External ID with Power Pages

The post What’s new in Power Platform: February 2026 feature update appeared first on Microsoft Power Platform Blog.

With this preview, Microsoft Power Platform admins gain a clearer view into what drives engagement, which resources create the most impact, and where to focus efforts to accelerate adoption and value across the platform. To explore the experience, visit the documentation or simply head to the Power Platform admin center, select ‘Manage’ in the left navigation, and click on ‘Usage’ to bring up the new experience.

Why we built the new usage page

We heard customers’ feedback and requests for a reliable, unified view of usage across the platform. Organizations depend on Power Platform to accelerate digital transformation – and now, with the usage experience, they can:

• Understand adoption patterns
• Identify top-performing solutions
• Detect emerging opportunities or risks

The new usage page consolidates usage metrics across Power Apps, Power Automate, and Copilot Studio, giving admins a single pane of glass to see how apps, agents, and workflows are built and used in their organization.

What’s included in the public preview

During public preview, admins get access to a view featuring:

Summary view

A high-value snapshot of how your organization is engaging with the platform:

• Adoption over time – Track daily active usage over the last 28 days
• Usage by product – View aggregated usage across:
  • Power Apps → Active users launching apps
  • Power Automate → Flow runs
  • Copilot Studio → Agent sessions
• High-value resources – Quickly identify the top three apps, flows, and agents driving adoption

Detailed resource tables

Interactive, sortable tables let you explore usage trends across individual items, making it easy to identify which items are driving the most usage. The following item types are supported across Power Apps, Power Automate, and Copilot Studio:

• Power Apps – Canvas and model-driven apps
• Power Automate – Cloud flows
• Copilot Studio – Agents built in Copilot Studio

These tables help admins pinpoint trends, track growth, and troubleshoot issues at the resource level.

Get started today and shape the product

Visit the Learn documentation on usage page or go straight to your Power Platform admin center → Manage → Usage to learn more and explore the new Usage view.

We look forward to hearing how you use these insights to help your organization grow adoption and unlock even greater value with the Power Platform. And we’ll be continuing to build on this unified view leveraging your feedback – so don’t hesitate to share it with us.

The post Announcing the public preview of the new usage page in the Power Platform admin center appeared first on Microsoft Power Platform Blog.

Microsoft Power Platform is designed to meet that challenge. It empowers teams to build solutions faster, automate more processes, and scale across the business within a framework that puts security and governance first. With tools that are AI-ready and built for enterprise-grade environments from Copilot-assisted development to intelligent threat detection and posture management, the platform helps organizations move with both agility and control.

Let’s break down the facts about building secure, modern applications.

Fact: Low code does not mean low security

Despite the ever-growing usage and strong ROI, there are still people who think that low-code tools are not built for enterprise grade applications. Power Platform proves otherwise by delivering a comprehensive, layered security model designed to meet the demands of large organizations. As part of a managed security approach, the platform integrates governance and security controls directly into the development lifecycle ensuring that policies are consistently applied across environments.

From identity and access management to data protection and network security, Power Platform provides native capabilities that reduce risk without slowing innovation. Features like role-based access control, conditional access for individual apps, and data loss prevention policies are all included. Azure Virtual Network (VNet) helps keep apps and data private by creating a secure connection that blocks public internet access and limits traffic to only trusted sources.

Visibility and access control are central to this approach. Power Platform includes tenant-level analytics and inventory tracking that allow IT teams to monitor what’s being built, which connectors are in use, and whether apps are operating within approved environments. Advanced connector policies complement these tools by helping enforce data boundaries and prevent unauthorized connections, rather than providing direct visibility or access control. With tools like IP filtering, cookie binding, and role-based permissions, IT can ensure that only the right users have access to sensitive data. This helps prevent shadow IT before it starts giving teams a secure space to innovate while ensuring IT retains oversight.

The platform’s approach to security also extends to AI and agents. Security is enforced across all components of the platform, including apps and AI agents. As organizations adopt tools like M365 Copilot and Copilot Studio, Power Platform provides a secure foundation for building and deploying AI agents. These agents follow existing data loss prevention policies, access controls, and network protections, ensuring AI adoption does not create new exposure.

Power Platform also provides the flexibility to extend Copilot Studio agent protection beyond default safeguards with additional runtime protection. Organizations can choose to integrate additional monitoring systems such as Microsoft Defender, custom tools, or other security platforms for a defense-in-depth approach to agent runtime security.

Centrica, the UK’s largest retailer of zero-carbon electricity, is a good example of secure low-code innovation. With over 800 Power Platform solutions and 15,000 users, Centrica maintains enterprise-grade governance by embedding security, oversight, and controls into every stage of development.

Accenture also demonstrates how Power Platform helps reduce risk at scale. By giving more than 50,000 employees the ability to build within defined guardrails, the company reduced demand for short-term IT projects by 30%. Their approach to low-code governance helped them gain visibility into platform activity while supporting global collaboration. As one Accenture executive put it, “For us, we define shadow IT as things we cannot see or control when we need to. By standing up the platform and inviting our people to create and build—at its very core we have gained visibility into what people are doing and how they are connecting, which starts governance at the platform level.”

Fact: You do not have to outsource to be compliant

There is a perception that distributed development models increase compliance risk. Power Platform addresses this with centralized administration and clear visibility into who is building, what they are building, and how data is being used.

From the Power Platform admin center, IT teams can configure environments, enforce policies, and monitor usage across the entire organization. Tools like Dataverse audit logging, Microsoft Purview integration, and Lockbox support provide deep visibility into sensitive operations and data access.

Purview enhances compliance by enabling data classification, sensitivity labeling, and activity tracking across Power Platform environments. It also helps organizations enforce retention policies and ensure data governance requirements are met supporting alignment with global regulations like GDPR and HIPAA.

AI capabilities introduce new governance needs, which Power Platform meets with built-in support for risk assessment and proactive recommendations. Copilot capabilities also assist admins in identifying misconfigurations and streamlining compliance reporting.

Power Platform also integrates with Microsoft Sentinel and solution checkers to detect anomalies, surface vulnerabilities, and alert administrators to unusual behavior. Security posture management tools help teams assess and adjust configurations over time, helping organizations scale AI responsibly while maintaining strong governance.

PG&E is a case in point. With more than 4,300 developers and 300 Power Platform solutions, the company has embedded governance and risk management into its development lifecycle. This approach has helped PG&E achieve more than $75 million in annual savings, while ensuring that compliance and oversight remain strong.

Fact: You are not alone in your administering. You have guidance and support.

Another misconception is that managing low-code platforms at scale requires external tools or consultants. Power Platform includes everything needed to govern, secure, and scale app development from within your organization.

IT admins can use Power Platform admin center and advisor to receive AI-driven, real-time recommendations tailored to their environment. These insights help assess environment health, refine governance policies, and proactively manage security posture. Advisor also provides a security score, giving teams a clear view of how well they are securing their environments and a concrete way to demonstrate progress and accountability to leadership.

The platform is designed to adapt to each organization’s structure and needs. Recommendations can be dismissed when covered by other controls, and environmental groups allow governance to be tailored to specific business units or departments. This flexibility ensures that security doesn’t get in the way of progress but works alongside it.

Advanced features like test automation, environment isolation, and integrated observability help maintain consistent performance. VNet integration allows organizations to connect securely to on-premises systems without exposing resources to the public internet.

An example of one of leading automotive manufacturers highlights these capabilities. The company used VNet support in Power Platform to securely connect AI agents to internal systems without relying on an on-premises data gateway. The result was faster deployment, better compliance with internal security policies, and more than 3,000 hours saved through improved data access.

Start building secure, scalable solutions

Foster innovation while still maintaining security and governance principles. Microsoft Power Platform gives IT leaders and developers the ability to move quickly while maintaining the control their organizations require. With built-in governance, privacy protections, and AI-powered insights, teams can confidently scale low-code development without introducing risk. You no longer have to choose between innovation and security. With Power Platform, you can deliver both.

Explore real-world success stories and best practices. Visit the Power Platform site and follow this blog for the next article in the series breaking down the facts of the modern development.

The post Breaking down the facts about secure development with Power Platform appeared first on Microsoft Power Platform Blog.

Microsoft IT (MSIT), our internal IT team, has transitioned our makers from building in the shared Default environment to user-specific PDEs, unlocking innovation while maintaining compliance and security. This shift has created a clean separation between maker activity and system dependencies. By isolating personal and production assets, PDEs accelerate adoption and enable secure, independent development within governed boundaries.

Microsoft is seeing a 32% of month-over-month growth in personal productivity assets thanks to a new environment strategy…more flows, more agents, and more apps are created daily, and are much easier to govern.”
– Microsoft Digital

The Default environment challenge

Before Personal Developer Environments (PDEs), organizations (including Microsoft) relied on a single, tenant-wide Default environment for all makers. While this “one-size-fits-all” setup enabled rapid adoption and experimentation, it also surfaced important challenges that shaped our approach to secure innovation:

• Open to all = risk to data: The Default environment’s broad accessibility empowers users to build and share solutions freely. However, this openness can expose organizations to risks of oversharing and unintended data access.
• One size does not fit all: With everything in one bucket, IT struggled to enforce policies. Fine-grain data policies or role-based access control per app/team were nearly impossible. Admins had to choose between overly permissive settings or overly restrictive ones that stifled productivity.
• Unmanageable scale (no isolation): Over time, the Default environment accumulated an unsustainable number of assets. Think tens of thousands of workflows and apps. Monitoring this sprawl was difficult, and a mistake in one app or flow could impact everyone since solutions weren’t isolated.

By late 2024, these lessons led MSIT to recognize that the Default environment, while instrumental in driving early innovation, was no longer sustainable for secure, governed growth. Security and governance teams called for a new approach: one that would balance the freedom to innovate with the need for robust oversight. Clearly, a change was needed to balance innovation with governance.

MSIT’s solution: Personal Developer Environments via routing

MSIT’s answer was to give each maker their own environment instead of using Default. Enter Personal Developer Environments (PDEs): private, user-specific Power Platform environments with built-in guardrails.

How it works

When a user creates a new app, flow, or Copilot agent, the system automatically routes it to a personal environment (provisioning one on the fly if needed). The maker’s content is automatically placed in their PDE, not the tenant-wide default, with no extra steps required. This approach replaced one giant environment with micro-environments. Each PDE is tied to an individual user, providing isolation and clear ownership for every app/flow.

Key aspects of MSIT’s implementation included the following:

• Automatic provisioning: The first time someone builds an agent, app, or flow, a dedicated environment is spun up for them automatically. Subsequent solutions from that user go into the same personal environment.
• Controlled creation: All personal environments are created via the routing system, not manually. This prevents sprawl of unstructured human-created environments.
• Seamless user experience: Environment routing was optimized to be fast and transparent. Provisioning a new PDE takes only a few seconds, so end-users hardly notice any delay. They don’t have to manually select environments – it “just works,” with their agents, apps, and flows automatically created in the right place.
• Use of Environment Groups: All of the 100,000+ PDEs are mapped into an Environment Group that helps manage and enforce the IT policies on all these environments in a simple and unified manner.

By April 2025, MSIT formally transitioned away from using the Default environment internally. New agents, apps, and flows are now created in PDEs, which operate under a governed structure that enables safe and scalable innovation. In essence, Microsoft evolved from the unstructured nature of the Default environment to a more intentional and organized ecosystem of personal (and other governed) environments.

Results: Better control, more innovation at Microsoft

The transition to PDEs has been a resounding success within Microsoft.

We’ve streamlined governance. With thousands of smaller environments, MSIT can apply tailored policies per environment instead of one-size-fits-all rules. They eliminated the risky “one big bucket” and gained confidence that one app can’t accidentally expose everything. As one stakeholder put it, the new model provides “isolated risk and clear ownership” for each solution. IT support burden fell as well – issues are easier to troubleshoot when you know exactly which environment (and owner) is involved.

We’ve accelerated innovation. Importantly, moving to PDEs did not hinder usage – it accelerated it. Once environment routing kicked in, previously pent-up makers started creating solutions again, now that they had a safe space. Microsoft saw a surge in activity: new flow creation jumped by 32% month-over-month after PDE routing was enabled. At the same time, new activity in Default dropped to nearly zero – exactly as intended. In other words, people kept innovating (more than ever), but under the watchful guardrails of PDEs.

Finally, we’ve unlocked new features. The security and compliance teams are now on board with enabling advanced Power Platform features internally. For instance, capabilities that were previously on hold due to Default environment concerns (like certain Copilot AI features) can be rolled out because they run in compliant PDEs. This ensures new tools are adopted only in governed environments, which allows IT to say “yes” to innovation, rather than issuing blanket bans.

The PDE approach was indeed the right thing to do, and it’s making people happy by changing the paradigm of solution-building at Microsoft.

Benefits of PDEs and why you should consider this approach

Microsoft’s internal journey with PDEs demonstrates several tangible benefits that any organization can reap:

• Stronger security and compliance
• Isolation of risk
• No more one-size-fits-all
• Easy adoption of new features
• Simplified management

Stronger security and compliance

Instead of having all apps and flows in one uncontrolled space, each PDE can be locked down as needed. IT can apply fine-grain data policies and access controls on a per-environment basis, rather than crippling the entire tenant with one blanket policy. Sensitive data stays contained. If a flow misbehaves, it only impacts its own environment, not the whole company.

Isolation of risk

PDEs establish explicit ownership for each environment. IT always knows who is responsible for every PDE, making it easy to identify and contact the owner if issues arise. When the owner leaves or transitions, cleanup is straightforward – IT can quickly decommission the environment, ensuring no lingering risks or orphaned resources. This clarity streamlines support and governance, giving IT confidence that every environment is managed and accountable.

No more one-size-fits-all

With PDEs (and the Managed Platform), admins can tailor settings to different needs or departments. For example, an environment hosting sensitive finance apps can have stricter connector policies, while a developer’s personal environment might allow preview features. You no longer have to choose between too lax or too strict for everyone. Policies can be targeted where needed, leading to better productivity because people aren’t hindered by controls meant for others.

Easy adoption of new features

Want to enable Microsoft 365 Copilot or custom AI agents? With PDEs, it’s feasible within your compliance framework. At Microsoft, any Copilot agent must live in an approved environment (like a PDE) or it gets auto-deleted. By using PDEs, you help ensure that new tech is rolled out in approved, monitored spaces. This encourages experimentation with AI and automation, since IT can enforce policies at the environment level instead of banning new features outright.

Simplified management

Breaking one large environment into many doesn’t overload admins – it actually streamlines their job. Power Platform’s admin tools (the Managed Platform) provide summary insights. Each environment has a clear owner, so tracking down the person responsible for a workflow is straightforward. In short, PDEs let admins be more effective and proactive in governing the platform.

In summary, PDEs let you say “yes” to makers and “yes” to your security team at the same time. You create a safe space for every employee to innovate, and you maintain the oversight needed to protect the business.

Conclusion: embrace PDEs for secure empowerment

Microsoft, acting as “Customer Zero,” proved that moving from the Default environment to Personal Developer Environments can turn a governance headache into an innovation engine. By routing new apps and flows into personal environments, MSIT achieved the seemingly impossible: increased productivity with reduced risk.

The message to all Power Platform customers is clear: you don’t have to trade off control for creativity. PDEs provide a path to having both.

Over 4,500 customers have adopted PDEs as their new environment strategy. If you haven’t already, consider enabling Default Environment Routing in your tenant (available through Power Platform’s Managed Environments) to automatically create PDEs for your users.

Educate your makers about these personal environments – their own “sandbox with safety rails.” As we’ve seen at Microsoft, this approach can unleash a burst of new solutions in your organization, all built in a governed way. Your admins will breathe easier, and your makers will feel trusted and empowered.

Bottom line: PDEs allowed Microsoft to retire the “wild west” Default environment and usher in a new era of governed innovation. It’s a win-win for IT and makers alike. Now it’s your turn – embrace Personal Developer Environments and watch your organization innovate securely, at scale.

The post Personal Developer Environments: Secure, governed innovation in Power Platform appeared first on Microsoft Power Platform Blog.

Watch how easy it is to create an alert, catch a threshold breach, and take guided action—without living on dashboards.

Why Monitor Alerts Matters

When incidents hit, every hour counts. Historically, admins had to log into Monitor and scan metrics to catch issues on daily/weekly basis. Monitor Alerts changes that by letting you define what “healthy” means and notifying you daily when reality drifts below that bar.

Benefits include:

• Fewer surprises: Alerts only when conditions you care about are met.
• Faster response: Go straight from alert to action.
• Focus on fixes, not hunting for issues.

Where It Lives

Monitor Alerts are available in the following context:

• Audience: Tenant administrators and environment administrators
• Surface: Monitor in the Power Platform admin center
• Availability: Public preview
• Setup: None required—start using it immediately

Monitor already provides operational health metrics and actionable recommendations. Alerts add an early-warning layer so you can react before issues escalate.

What You Can Alert On

Monitor Alerts currently supports:

• Canvas apps
• Model-driven apps
• Cloud flows
• Desktop flows

Examples include:

• App load times exceeding thresholds
• Spikes in flow failures in critical environments
• Degradation in availability for executive-facing apps
• Error spikes in desktop flows

Quickstart (No Configuration Needed)

1. Open Power Platform admin center
2. Navigate to Monitor > Alerts
3. Create an alert: pick environment and resource type
4. Define condition: choose metric, set threshold, specify evaluation window
5. Add recipients (DL or named admins)
6. Save & test
7. Tune thresholds to balance sensitivity and noise

Best Practices

• Align thresholds to SLAs: Start with business expectations.
• Alert on trends, not blips: Use sustained windows to avoid alert fatigue.
• Route smartly: Send to on-call DL; add context in alert description.
• Pair with recommendations: Use Monitor’s insights to accelerate root cause analysis.
• Review regularly: Adjust thresholds as usage grows.

Learn more: Power Platform Monitor Alerts

The post Take Charge and Stay Ahead with Power Platform Monitor Alerts appeared first on Microsoft Power Platform Blog.

We believe our Leader placement and Customers’ Choice distinction reflect our years-long commitment to empowering everyone—from traditional developers to business users—to build transformative, enterprise-grade solutions with speed, intelligence, and confidence. 

2025 Gartner® Magic Quadrant™ for Enterprise Low-Code Application Platforms

Learn why Microsoft was named a Leader.

Read the report

Why this matters 

Agility, governance, and impactful AI adoption are non-negotiable in today’s enterprise landscape. Under the umbrella of Microsoft Power Platform, Microsoft delivers a leading, end-to-end suite for automation, agents, and AI-infused applications. 

With over 56 million monthly active users and a thriving global community, Power Platform helps organizations of all sizes accelerate innovation. Key differentiators we believe set us apart from other market players are:  

• AI is transforming work today, not tomorrow.
  With over 3 million agents built in FY25 alone,² we are witnessing firsthand the acceleration of development cycles by more empowered users. Our platform is delivering measurable results—such as 30% faster data entry in apps,³ and 60% higher success building with Microsoft Copilot in Power Apps. These results are demonstrating that AI acceleration is a current reality for both developers and business users. We are actively supporting our customers as they put AI to work every day through our robust community, investments in extensive documentation, and transparent product roadmap. We are helping our customers drive tangible business outcomes at-scale by making innovation accessible to all.
• The fully managed platform is making enterprise-grade scale and compliance, simple at any scale.
  With a foundation solidly on Microsoft Azure infrastructure, Power Platform offers benefits from streamlined security, operations, and management through a single admin center. We are making it easier than ever for you to confidently innovate and scale solutions globally with less effort while maintaining rigorous standards.
• Developer capabilities within Power Platform are purposefully designed to foster seamless collaboration between business and IT users, while simultaneously giving experienced, code-first developers the power to innovate on their own terms. Power Platform has demonstrated long-term reliability and a relentless commitment to innovation. We have not only pioneered the low-code movement but now lead the agentic transformation of modern development. Throughout this evolution, we have consistently kept professional developers at the heart of our product strategy. As a result, we’ve seen more developers than ever choosing Power Platform as their foundation for building sophisticated, scalable solutions. Developers are relying on the platform to help them drive real business impact and accelerate the future of their enterprise app development.  

Gartner predicts that by 2028, “Agentic AI will be implemented via enterprise LCAPs in four out of five businesses globally.”⁴ With where we are and where we’re headed with our roadmap, we’re convinced that Power Platform delivers the tools for enterprises to scale their AI strategy with all kinds of developers. 

Join us October 28 to 30, 2025 at the Microsoft Power Platform Community Conference to experience firsthand the energy of our innovation and the strength of our community, and let’s explore some of the reasons customers around the globe are choosing Power Platform as their trusted platform for transformation. 

Accelerate AI impact 

Power Platform is designed to empower all kinds of developers. Business users new to app development or seasoned professionals alike can build impactful solutions with speed and confidence.  

When it comes to accelerating development with AI, innovations like plans in Power Apps and generative pages are redefining what building an enterprise solution looks like. Plans are quickly becoming the standard for designing and orchestrating solutions to complex business problems. Generative pages simplifies app creation by reducing boilerplate or repetitive work and accelerating delivery through an intuitive “vibe-coding” experience—all backed by the reliability of Power Platform. Whether you are a business professional, technical specialist, or seasoned developer—you can effectively utilize the single platform that meets you where you are, adapts to your pace and your unique skill set, and opens the path for you to achieve your ambitions.  

“We’ve been working with the plans, and this has so much potential. You really see how it’s going to increase our speed to market and grow our footprint when it comes to our global team across the world.” 

Giada Binelli, Global Product Owner Low Code and Cognitive Services, The HEINEKEN Company

With agents integrated into apps from the ground up, Power Platform allows organizations to quickly bring impactful innovations to users. Our agentic assistance in apps is preferred by 85% of users over non-assisted data exploration or data entry.⁴ And the new agent feed creates a true hub for human-agent collaboration.

We’re proud to lead this product evolution in the full breadth of development happening on Power Platform. Microsoft is committed to harnessing the potential of AI in the development lifecycle and in user experiences. We are delivering agentic assistance through built-in functionalities, providing a fast gateway to impactful AI outcomes. 

Scale, governance, and confidence 

With a fully managed platform, organizations gain advanced lifecycle management, governance, compliance, and security capabilities. Our recent investments in Microsoft Copilot Studio and AI orchestration ensure large language model responses are managed securely and responsibly, empowering organizations to confidently embrace AI-powered development. The platform’s strong foundation mitigates risk and helps IT and business users maintain control and accelerate innovation across the enterprise—without compromising trust or oversight. 

“The managed platform capabilities on Power Platform have greatly simplified and improved our ability to govern at scale. It’s the best way to manage at a global level.”

Giada Binelli, Global Product Owner Low Code and Cognitive Services, The HEINEKEN Company

Built for developers 

We’re redefining application and technology development in the age of AI and helping enterprises chart their path to becoming Frontier Firms. We recognize the critical role traditional developers play in this transformation—that is why we continue to expand and add robust capabilities to support them in building sophisticated, scalable solutions.  

With native integration of advanced coding tools, extensibility through custom connectors, and seamless integration with Microsoft Azure services, developers have more power to leverage their existing skills to build complex enterprise-grade applications. 

Power Platform is not low-code—it’s low-code, code-first, agentic, generative, and fully governed innovation. It empowers modern developers to build sophisticated, impactful, enterprise-grade solutions that they can scale.  

We are helping our customers move from simply building artifacts, to solving problems and driving business outcomes. The rapid growth of our developer community and adoption of advanced features underscores the trust developers are placing in Power Platform to deliver mission-critical applications. 

Real customer success, real business impact 

Small startups and multinational enterprises alike drive innovation and operational efficiency with Power Platform. The following examples show how they leverage the platform’s abilities and deliver tangible business outcomes: cost savings, operational efficiency, and scalable innovation. 

• Deutsche Bahn Group licensed every employee with a Power Platform license. “It’s very easy to make your own app, and very fast,” says Thomas Czierpke, Head of Adoption and Change Management.
• Pacific Gas & Electric built over 300 complex solutions, saving over USD75 million annually. Their AI-powered chatbot alone saves USD1.1 million per year in helpdesk support.
• Cineplex automated customer service workflows reclaimed 30,000 hours and over USD1 million in just two years.
• Rabobank runs more than 2,500 Power Platform solutions across 38 countries. One of their key business processes that took three weeks now takes just three minutes.

Start your shift to the new way of working 

Whether you’re building mission-critical apps or automating everyday tasks, Power Platform is the right choice. It’s a complete suite of tools designed for innovating at scale and for driving your organizational shift toward the Frontier Firm, where people collaborate with agents, apps, and Microsoft Copilot to achieve greater productivity. 

Read the full Magic Quadrant™ report to see why Gartner named Microsoft a Leader and then join us at Microsoft Power Platform Community Conference to experience the community innovation firsthand.  

Let’s build what’s next—together.

Disclaimer: 

*Gartner is a registered trademark and service mark, and Magic Quadrant is a registered trademark of Gartner, Inc. and/or its affiliates in the U.S. and internationally and are used herein with permission. All rights reserved.  

Gartner does not endorse any vendor, product or service depicted in its research publications, and does not advise technology users to select only those vendors with the highest ratings or other designation. Gartner research publications consist of the opinions of Gartner’s research organization and should not be construed as statements of fact. Gartner disclaims all warranties, expressed or implied, with respect to this research, including any warranties of merchantability or fitness for a particular purpose. 

¹ This graphic was published by Gartner, Inc. as part of a larger research document and should be evaluated in the context of the entire document. The Gartner document is available upon request from Magic Quadrant™ for Enterprise Low-Code Application Platforms.

² Microsoft Fiscal Year 2025 Fourth Quarter Earnings Conference Call.

³ Internal Microsoft testing conducted in November 2024 on sample of 22 subjects.

⁴ Gartner®, Magic Quadrant™ for Enterprise Low-Code Application Platforms, July 28, 2025, Oleksandr Matvitskyy, Akash Jain, Kyle Davis, Adrian Leow.

The post Microsoft recognized as a Leader in the 2025 Gartner® Magic Quadrant™ for Enterprise Low-Code Application Platforms appeared first on Microsoft Power Platform Blog.