In the past, developers working with Liquid in Power Pages were limited to a predefined set of platform-provided objects. While these objects provide powerful capabilities, developers often had to adapt their requirements to available constructs or implement custom logic in other layers.

As the next step in this journey, Server Logic can now be invoked directly from Liquid templates in Power Pages.

Bring Your Logic to Liquid

With this capability, you can invoke Server Logic directly from Liquid templates, effectively extending Liquid code with your own custom, server-backed capabilities. This removes the constraint of relying solely on built-in Liquid objects, while keeping business logic securely executed on the server. Combined with access to request and website context and Power Pages security capabilities, you can build dynamic, contextual experiences with consistent security and access control.

Get started

To learn more and start building:

• Server Logic overview
• Call Server Logic from Liquid templates
• Server objects and context

We are looking forward to your feedback

Your feedback is crucial in shaping the future of this feature. We want to hear from you!

The post Extend Liquid with Server Logic in Power Pages appeared first on Microsoft Power Platform Blog.

We’re excited to announce expansion of the Dataverse plugin across additional coding agent marketplaces, meeting developers where they already work. The plugin is now available for OpenAI and Codex. This adds to the existing support for Claude, Cursor, and GitHub Copilot. Regardless of which coding agent a team standardizes on, they get the same Dataverse expertise: intelligent skill routing, enterprise-grade guardrails, and a consistent natural-language experience across surfaces.

This expansion matters because it reduces adoption friction for customers and partners. Teams can keep their preferred coding agent while using a common Dataverse interaction model for data operations, schema work, solution lifecycle tasks, and environment administration. The result is faster onboarding, more repeatable delivery patterns, and clearer governance alignment without forcing toolchain consolidation.

Installing Dataverse plugin for coding agents in ChatGPT and Codex

The Dataverse plugin for coding agents is available in the marketplace in both the OpenAI and Codex experiences. Choose your preferred surface, go to Plugins, and search for Microsoft Dataverse.

Additional Resources

Cursor Marketplace: https://cursor.com/marketplace/microsoft-dataverse

GitHub Copilot: Dataverse | Awesome GitHub Copilot

Claude Code: https://claude.com/plugins/dataverse

Open-source plugin repo: https://github.com/microsoft/Dataverse-skills

The post Dataverse Plugin for Coding Agents: OpenAI and Codex Marketplace Expansion appeared first on Microsoft Power Platform Blog.

What is changing and why we are making this change?

Three things drove this refresh, all rooted in customer feedback and where the product is going.

1. The name no longer matched the product.

“Azure Synapse Link for Dataverse” was created when Azure Synapse Analytics was the only destination. Today, most new links go to Microsoft Fabric, and we ship updates to Fabric link on a far faster cadence than any other path. Keeping “Synapse” in the name was sending the wrong signal to customers evaluating their data architecture and was creating confusion in support tickets, partner conversations, and search results.

2. Fabric link creation was hidden in the wrong place.

In the old experience, the Azure Synapse Link page was where you went to see and manage your links, but its + New link button only created a Synapse link with your own storage. To create a Fabric link, you had to leave that page entirely, go to the Tables area, and choose Analyze > Link to Microsoft Fabric. Two surfaces, two mental models, and no clear signal that Fabric link was the recommended path. The new Link data page consolidates link management and link creation into one place, with Fabric link as the headline tile. The Tables > Analyze > Analyze in Fabric entry point still exists for in-context Fabric link creation, but Synapse link creation has been removed from the Tables page (Synapse links are now created only from the Link data page, under Other Links).

3. Authentication needs to get simpler and safer.

Workspace identity removes the most common Fabric link setup failure mode: misconfigured service principal permissions. It is also the path our security and platform teams recommend. Until now, it was an option you had to know to look for. The new wizard calls it out as the recommended choice and links straight to the Fabric docs for enabling it on your workspace. Workspace identity is configured on the Fabric workspace itself (outside Dataverse), so this is a one-time setup your Fabric admin does once per workspace, and every Dataverse link to that workspace benefits.

See the below video to see how you can setup Fabric Link using a refreshed user experience.

From “Azure Synapse Link” to “Link data”

The left navigation entry in the Power Apps maker portal is now Link data. The landing page groups your links under two clear sections:

• Fabric Links: the recommended path for new analytics workloads. See Configure your environment and link to Microsoft Fabric.
• Other Links: Azure Synapse Link with your own Synapse workspace and Azure Synapse Link with Azure Data Lake continue to work here without any change.

Existing links keep running. There is no migration step. Any Azure Synapse Link you already have will automatically show up under the Other Links section on the new Link data page; you do not need to do anything to move it. If your runbooks or internal documentation reference “Azure Synapse Link for Dataverse”, update them to point at Link data.

We are also consolidating where links get created. The New link entry point for Azure Synapse Link with Azure Data Lake on the Dataflows page now redirects to the Link data page. Wherever you start, link creation now lands in the same place.

The new Link data page in the left navigation of the Power Apps maker portal, with Fabric Links as the headline section and Other Links below.

A redesigned Fabric link wizard

Creating a Fabric link now starts from the Link data page itself (no more hopping over to the Tables area) and walks you through three steps:

1. Setup Configuration. Pick the Fabric workspace you want to link to and choose how to authenticate. Workspace identity is called out as the recommended option, with organizational account and service principal still available.
2. Select Tables. Pick the Dataverse tables to sync,
3. Review & Create Review your workspace, authentication, and table selections, then create the link.

The Setup Configuration step: pick your Fabric workspace and connect, with workspace identity called out as the recommended authentication.

The post-create experience drops you directly into a standalone Manage tables experience, reachable any time from the top command bar. You no longer have to click on the link to add or remove tables.

The standalone Manage tables option, reachable from the top command bar at any time.

Workspace identity is the recommended authentication

The Setup Configuration step calls out workspace identity as the recommended option and points you at the docs for enabling it. Service principal and organizational account continue to work and remain selectable from the same step. The trust model is documented in Authenticate with workspace identity.

One thing to know up front: workspace identity is a property of the Fabric workspace, not of the Dataverse link. You enable it once on the Fabric side, outside of Dataverse, via the Fabric workspace identity docs. Once it exists on the workspace, the Fabric link wizard can use it, and the Configure Fabric link to use workspace identity section shows how to wire it into an existing link.

What this means for your team

Fabric link is the strategic path. Link data puts Fabric link front and center in the UI and in our roadmap. If you are deciding where to invest for new analytics workloads, this is the option we are building on.

One consistent UX for every link. Whether you are creating a new Fabric link, managing an existing one, or maintaining a Synapse link, you start and end on the same Link data page with the same look, the same controls, and the same docs. Learn more: For the updated end-to-end setup walkthrough, see Link your Dataverse environment to Microsoft Fabric.

What is not changing

• Existing links keep working. No migration, no relink required.
• Azure Synapse Link, Azure Data Lake, and other targets are still fully supported under Other Links.
• APIs and admin automation for existing flows are unchanged. The rename is a UX and Information Architecture change, not a contract change.
• Pricing and metering are unchanged.

Looking ahead

Link data is the umbrella we will keep building under. Two improvements we are actively working on:

• Easier table selection. Picking tables one at a time is cumbersome for large environments. We are working on a faster, more flexible selection experience so you can get to the set you need with far fewer clicks.
• Multiple Fabric links to different workspaces. Today an environment links to a single Fabric workspace. We are adding support for creating multiple Fabric links from the same Dataverse environment to different Fabric workspaces, so different teams and workloads can each have their own target.

Beyond those, expect continued investment in Fabric link as the primary sync path (including the low-latency sync engine that is rolling out now) and more guided setup so customers always know which path to invest in.

We want your feedback

If you set up a new Fabric link in the next few weeks, we want to hear what worked and what did not in the new wizard, especially around workspace identity.

• Share feedback: post on the discussion in our Viva Engage community. Not a member yet? Sign up here.
• Try it now: create a new Fabric link from the Link data page in the Power Apps maker portal.

The post Announcing Link to Fabric UX refresh appeared first on Microsoft Power Platform Blog.

• Fresh, grounded data. Fabric gives your Copilot and AI agents direct access to live Dataverse records — no stale exports, no sync delays.
• Insight to action. Fabric analyzes the data; Dataverse acts on it — powering agents that don’t just answer questions, they complete workflows.
• Unified governance. The same data powering your reports powers your AI with consistent security and compliance across Power Platform and Fabric.

Whether you run customer engagement or finance and operations workloads, low-latency sync delivers a single, unified sync experience with dramatically improved throughput and reduced data freshness latency. 

The challenge: data freshness matters 

Organizations running Dynamics 365 and Power Platform rely on timely, accurate data to drive analytics, reporting, and downstream processes. Until now, syncing data from Dataverse to your analytics layer involved variable latency depending on the link type, workload size, and table configuration. For teams building dashboards, running operational reports, or feeding AI models, every hour of delay translates to decisions made on stale data. 

We heard this feedback clearly: you need your Dataverse data in Fabric faster, with less complexity, and with a consistent experience regardless of whether you’re running Dynamics 365 customer engagement apps, finance and operations apps, or custom Dataverse apps. 

What is Low-latency sync? 

Low-latency sync is the next generation of the Dataverse sync engine. It replaces the existing sync pipeline with a redesigned data path that reduces end-to-end latency for both initial sync and ongoing incremental (delta) sync operations. 

Key improvements: 

• Faster initial sync: Full table replication completes significantly faster, getting your historical data into Fabric sooner. 

• Blazing fast delta sync: Incremental changes flow from Dataverse to Fabric with significant improvements over traditional Fabric Link. Actual sync times depend on initial load, data churn, table sizes, and number of columns, but the performance gains are substantial across the board. 

• Higher throughput for finance and operations apps: Throughput increases to upwards of 1M+ records per hour per table*, up from the previous 100K to 700K range. 

*Performance observed in lab environments and simulated conditions. Actual throughput may vary depending on table size, region, data churn, and customer environment characteristics. 

Under the hood: fewer hops, better reliability 

Fabric Link vs Low-latency sync architecture. The diagram above illustrates the architectural change at the core of low-latency sync. 

Fabric Link (today) follows a three-step path: data is read from the Dataverse database, serialized to an intermediate CSV format, and then converted to Delta Parquet before being made available in your Fabric Lakehouse via a shortcut. 

Low-latency sync eliminates the intermediate CSV step entirely (see diagram above). Data flows directly from the Dataverse database to Delta Parquet, removing one full hop from the pipeline. 

This is not just a latency improvement. Removing the CSV serialization and deserialization step has a direct impact on reliability: 

• Fewer failure points. Each hop in a data pipeline is a potential point of failure. The CSV stage involves serialization, temporary storage writes, and reads before the Delta conversion can begin. Eliminating this step removes an entire class of transient errors (I/O failures, serialization bugs, storage throttling on intermediate files). 

• Reduced resource contention. The CSV stage consumes compute and storage resources that are no longer needed. This frees capacity for the operations that matter: reading from the source database and writing the final Delta Parquet output. 

• Simpler retry and recovery. With fewer stages, the sync engine has a shorter, more predictable pipeline to manage. When issues do occur, recovery is faster because there is less intermediate state to reconcile. 

• Consistent data format. Going directly to Delta Parquet means data is written once in its final format. This eliminates edge cases where CSV encoding differences or schema mismatches between the CSV and Delta stages could cause data quality issues. 

The result: faster sync times and a more reliable pipeline, with fewer operations that can go wrong between your Dataverse database and your Fabric Lakehouse.

What this means for your team 

• For data analytics and reporting teams. Your Fabric Lakehouse, dashboards, and Power BI reports get refreshed data faster. Reduced sync latency means the gap between a transaction in Dynamics 365 and its availability in your analytics layer shrinks significantly. This directly improves the accuracy and timeliness of operational and executive reporting. 
• For system administrators. Low-latency sync is designed as a drop-in improvement. We are releasing it in a controlled manner across stations, starting with early release stations and then expanding one station at a time on a weekly cadence. There is no separate opt-in experience. Once your station is enabled, new Fabric Link configurations can use the new sync engine through the same familiar setup experience in the Power Platform admin center. 
• For leadership and business stakeholders. Faster data replication means faster insights. Whether your organization tracks revenue, inventory, case resolution times, or customer engagement metrics, low-latency sync closes the gap between operational systems and the analytics that drive decisions. 

Performance at a glance 

• Customer engagement apps: Significant improvement in delta sync latency over traditional Fabric Link. 

• Finance and operations apps: Throughput upwards of 1M+ records per hour per table*. 

*Performance observed in lab environments and simulated conditions. Actual throughput may vary depending on table size, region, data churn, and customer environment characteristics. 

Tentative timelines 

These rollout windows are approximate and may change as we monitor health and progress through each deployment wave. 

Prerequisites for Finance and Operations

If you are running Finance and Operations (FnO) apps, verify prerequisites and minimum supported build requirements in the public documentation before enabling low-latency sync.

See: Low latency sync Link to Fabric Documentation

How to get started 

New Fabric Link customers 

1. Navigate to the Power Platform admin center. 

2. Set up a new Fabric Link for your Dataverse environment. 

3. If your station is part of the current rollout wave, low-latency sync is made available as part of the standard setup experience. There is no separate enrollment step or preview sign-up. 

4. If your station has not yet been enabled, no action is required beyond watching for rollout availability. Once enabled, you can complete setup and start syncing through the new engine. 

Existing Fabric Link customers (early access) 

If you want to start using low-latency sync, watch for availability in your station as the controlled rollout progresses: 

1. Unlink your existing Fabric Link profile. 

2. Relink and follow the same setup flow once your station is enabled for low-latency sync. 

3. Your profile will run on the new sync engine without a separate preview opt-in step once the rollout reaches your station. 

Note: Unlinking and relinking will trigger a full initial sync for all configured tables. 

How to confirm low-latency sync is enabled 

To confirm that your environment is running in low-latency mode, open the experience and select Azure Synapse Link from the navigation. On the link list page, if you see the Low-latency mode flag on your Fabric link, low-latency sync is enabled for that profile. 

Low-latency mode flag in Azure Synapse Link. Azure Synapse Link experience showing the Low-latency mode flag on the Fabric link profile. 

What about Synapse Link and Export to Data Lake? 

Low-latency sync applies to Fabric Link configurations. If you are currently using Synapse Link (BYOL/BYOS) or Export to Data Lake (COMO), here is what to expect: 

• Synapse Link (BYOL/BYOS): Continues to function as-is. We encourage customers to evaluate Fabric Link with low-latency sync for improved performance and a streamlined experience. 

• Export to Data Lake: Export to Data Lake has been deprecated and the service is being retired. We strongly recommend evaluating and moving over to Fabric Link with low-latency sync post GA. There is no further extension or exception process planned for the Export to Data Lake deprecation. 

Looking ahead 

Low-latency sync is a foundational step toward making Dataverse the most connected operational data platform. With all sync workloads consolidated on a single engine, we can deliver improvements faster, reduce operational complexity, and unlock new scenarios for real-time analytics and AI. 

We are actively working on expanded throughput optimizations to enable continued performance improvements for large-scale environments. 

We want your feedback 

Your feedback directly shapes the GA release and future roadmap. 

• Try it: If your environment is in an enabled station, set up or relink Fabric Link through the Power Platform admin center and evaluate low-latency sync. 

• Share feedback: Reach out to your Microsoft account team or join Viva Engage community to share your feedback.

• Learn more: https://aka.ms/lowlatencylearnmore 

The post Announcing Low-latency sync for Dataverse to Fabric in GA appeared first on Microsoft Power Platform Blog.

Companion post to our Build 2026 session: Microsoft Dataverse plugin: unleashing coding agents on the enterprise

Coding agents are powerful, but without domain tooling they hallucinate and produce broken solutions. The Dataverse plugin for coding agentssolves this by giving AI agents guardrailed access to tables, columns, relationships, views, security, and solutions.

In our Build 2026 session, we showed how a natural-language request triggers multi-step provisioning, data imports, and validation. This is all executed autonomously, through the plugin’s tool integration and patterns that make agent-driven Dataverse development reliable at scale.

To bring this to life, we built a series around Zava Coffee Co., a growing B2B roaster and distributor running on spreadsheets, email, and copy-paste. When it came time to modernize, they didn’t need a massive team and spend weeks in the the various portals. Instead, they installed the Dataverse plugin and described what they needed, in plain English, from a GitHub Copilot terminal.

This post, and accompanying video, walks through the three scenarios:

1. Maya, a developer building her first data model, app form and view
2. Riya, a Revenue Ops analyst running her CRM in natural language
3. Amara, a platform admin locking down security across two regions.

Scenario 1: Zero to App in One Session

Persona: Maya, Developer, new to Dataverse
Goal: Turn four operational spreadsheets into a working Dataverse application with schemas, relationships, and real data.

Maya had never touched Dataverse. She didn’t know her org URL, didn’t know what a publisher prefix was, and shouldn’t have to. She installed the plugin, typed one sentence “Connect me to my Dataverse environment” and the agent discovered her environments from her Microsoft identity, configured everything, and verified the connection.

Then she describes her roast batch tracking system in business terms: beans, batches, quality checks, orders, and the relationships between them. One prompt produced four tables with choice columns, lookups, a self-referential parent-batch relationship for re-roasts, a many-to-many between batches and orders, a main form, and a filtered view — all packaged in a solution.

The data import is where it gets real. Maya pointed the agent at the team’s four Excel files. No GUIDs anywhere, just business keys for a bean variety and batch numbers. The agent figured out dependency order, loaded parent tables first, resolved the self-referential re-roast links, split a comma-separated batch list into proper many-to-many associations, and left an unlinked order alone instead of erroring out. That’s a data pipeline, not a sample generator.

What the plugin solved: Maya went from zero Dataverse knowledge to a connected, working application that included schemas, relationships, forms, views, and three years of real operational history, all without opening the maker portal, reading a setup guide, or writing a single line of FetchXML.

Scenario 2: Talk to Your CRM in Plain English

Persona: Riya, RevOps Analyst
Goal: Run Friday pipeline prep in five minutes instead of forty-five minutes, no Advanced Find, no Excel pivots, no chasing teammates in Teams.

Riya already lives in a terminal. Every Thursday she preps Carlos’s sales pipeline review by pulling open deals, flag at-risk cafés, makes sure last week’s calls are logged. Today that’s forty-five minutes of Advanced Find queries, Excel exports, and detective work.

With the Dataverse plugin, she asked: “Show me Carlos’s open opportunities over $100K closing this quarter.” The agent looked up Carlos by name in the systemuser table, translated “this quarter” into a date range, and returned café names, deal names, dollars, and stages — no GUIDs, no statecode = 0, no estimatedclosedate syntax.

Then she asked for “cafés in Portland that haven’t reordered in 30 days.” That’s not a field, it’s a relationship plus date math. The agent joined accounts to closed-won opportunities, computed the gap, and handed Riya a clean call list.

The trust moment: When Riya said “Add a note to the Portland cafe opportunity,” the agent found the open deal on that account. She also logged a phone call on behalf of Carlos, the agent set the owner to Carlos (his call), marked it completed (already happened), resolved the contact as a participant, and linked it to the right account, all inferred from one sentence.

What the plugin solved: Riya collapsed 45 minutes of Advanced Find, Excel pivots, and manual activity logging into five minutes of conversational CRM access. Carlos got a cleaner pipeline review without doing anything differently.

Scenario 3: Manage Your Environment Like a Pro

Persona: Amara, Platform Admin
Goal: Draw security boundaries for two regions and three job functions, validate every line, and package it in a deployable solution.

Zava doubled in size and opened a Seattle hub. Amara’s problem: warehouse staff can see deal sizes, sales reps can see quality scores, and anyone can read customer lifetime value. She needed to draw lines and she wanted to describe the security model once, not click through six sections of the admin portal.

She connected with an admin posture: “Verify I have System Administrator privileges before we start.” The agent confirmed her role before offering to do anything destructive. Then she described the full security plan in one prompt: two business units (Portland, Seattle), three custom roles scoped appropriately, field-level security on the sensitive lifetime_value column, an access team template for cross-region collaboration, and three user assignments, all in a ZavaSecurity solution.

The invisible prerequisites: The agent enabled the column for field-level security at the schema level before creating the Field Level Security (FLS) profile. This step, when missed, produces no error and no audit entries. It assigned the profile to roles, because a created-but-unassigned profile does nothing. It added every security component to the solution explicitly, since roles and FLS profiles don’t auto-add.

Validation by impersonation: Amara asked the agent to simulate each user’s access. The result was a clear pass/fail table — Diego can read accounts but not lifetime_value (FLS), Marcus can read roast batches but not accounts (role), nobody can see across business units. Red Xs and Green checkmarks in all the right places, with the why annotated next to each cell. That’s the admin equivalent of a unit test. Allconfiguration confirmed in seconds, not browser-tab-per-user.

She then shared one record cross-region via the access team template. This was one sentence, no GUIDs and enabled three-layer column auditing (org, table, column) so future reads are logged.

What the plugin solved: In one session, Amara stood up two BUs, three roles, FLS with proper assignments, a team template, three user assignments, validated by impersonation, configured a cross-region share, and turned on auditing. Every component lives in a solution she can version and redeploy across environments.

Three Users, Three Jobs, One Unified Approach

The common thread across all three scenarios is : describe your intent in plain language, the agent translates it into the right combination of Dataverse operations. Maya never learned what a publisher prefix is. Riya never wrote FetchXML. Amara never opened the BU management UI. Each person brought a different problem and a different level of platform expertise and the same plugin met all three where they were.

The Dataverse Skills pluginis available now on the Claude and GitHub Copilot marketplaces. Install it, connect, and start building.

👉 Watch the full Build 2026 session:  Microsoft Dataverse plugin: unleashing coding agents on the enterprise 

Learn more about what’s new in Dataverse: aka.ms/DataverseMay2026

The post Microsoft Dataverse Plugin: Unleashing Coding Agents on the Enterprise – Microsoft Build 2026 appeared first on Microsoft Power Platform Blog.

Think about the last time you needed business data mid-flow—building a PowerPoint and needing the latest account details or drafting a follow-up email and wanting to confirm a record before hitting send.  You had to open a separate tab, navigate to the right view, find what you needed, and switch back – unnecessary context switching. That’s the gap we’re closing.

Starting today in preview, you can engage your model-driven apps in Microsoft 365 Copilot — giving users conversational access to their business data and giving makers a way to bring their app’s value into the flow of work. The connection is made through your app’s MCP server—a lightweight setup in Power Apps that’s automatically created and configured for your model‑driven app, registering it as an agent in Copilot and making its data available as conversational capabilities. The experience is built around three capabilities: out‑of‑the‑box grids and forms available now, and custom tools coming soon.

Grids — explore your data without leaving the conversation 

Ask Copilot a question about your business data — “Show me open accounts in the West region” or “Which cases were escalated this week?”— and it responds with an interactive grid drawn directly from your Power Apps data. Users can filter, sort, and scan records using the same views and permissions as the app itself. 

Selecting a record opens it inline, where users can review details, make edits, or keep the conversation going — asking follow-up questions, comparing records, or taking the next step without starting over. And when users need a full screen experience, a deep link is always available — one click takes them directly to the relevant view or record in the full app. 

Forms — create, view, and update records without leaving Copilot 

Forms go beyond read-only access. Users can create new records, view existing ones, or update fields—all directly in Copilot. Imagine receiving a supplier email and asking Copilot to create a new account record from it, or reviewing a contract in Word and logging the key details into your CRM without switching apps. 

Copilot surfaces the right form and, using the same underlying technology as the data entry agent in Power Apps model‑driven apps, intelligently predicts field values based on the context at hand — reducing manual input and making data entry feel effortless.

Available across the Microsoft 365 apps you already use 

These experiences aren’t limited to the Copilot chat canvas. They’re available in the Copilot surfaces across Microsoft 365—Word, Excel, PowerPoint, and more—so users can access and act on their business data right alongside the document, spreadsheet, or presentation they’re working in.

Imagine drafting a proposal in Word, opening Copilot directly within the application, and creating a new account record with fields prefilled from the document—without switching apps, without copy and pasting, without losing context.

Need to go deeper? Both grids and forms include a deep link into the full model-driven app. One click takes users directly to the relevant record or view—no navigation, no searching, context preserved. It’s not a context switch; it’s a handoff to exactly where they need to be.

Custom tools — coming soon 

For scenarios where a grid or form isn’t sufficient, makers can build custom tools — defining their own logic and UX to meet the specific needs of their users. 

Grids, forms, and custom tools are the foundation. As we learn from this preview, we’ll expand the ways makers can extend their apps into Copilot — across more surfaces, more scenarios, and deeper integrations with the Microsoft 365 ecosystem.  

Available now — get started today 

Your model-driven apps are now available in Microsoft 365 Copilot in public preview. Once a maker activates their app’s MCP server for a model-driven app, grids and forms will light up in Copilot automatically – no redesign required.

How to get started

1. Activate your app’s MCP server in Power Apps. This exposes your app’s data and experiences as callable capabilities in Microsoft 365 Copilot, with grids and forms surfacing automatically from your existing configuration. 

2. Download the app package generated by your app’s MCP. This package contains the agent definition and configuration needed to deploy your app’s experience to Microsoft 365. 

3. Deploy to Microsoft Teams or Microsoft 365. Upload the package to your tenant, and your users can immediately start interacting with your app’s data through Copilot—no further setup required on their end. 

Requires a Power Apps model‑driven app with Dataverse. This preview requires a Microsoft 365 Copilot license and a Power Apps Premium license. Custom tools—for exposing app‑specific actions beyond grids and forms—will be available in the coming weeks. Stay tuned!

The post Public Preview: Your business apps, now part of every conversation appeared first on Microsoft Power Platform Blog.

Three forces are converging. The interface layer is shifting to AI assistants. Agents handle workflow orchestration. And an intelligence layer is consolidating information across structured and unstructured sources. Together, these forces mark Frontier Transformation, where AI moves beyond basic efficiency to open new opportunities for creativity, innovation and growth.

This transformation also creates a new kind of business application: one that is integrated with the AI assistant people use every day, accessible to agents and grounded in the unique intelligence of each organization.

We call these agentic business applications. The applications themselves still reflect real business processes. But how people interact with them, how work moves through them and how they connect to the rest of the business is fundamentally different.

Today, we’re taking a significant step forward in bringing agentic business applications to life across Microsoft 365, Dynamics 365, and Microsoft Power Platform.

Interact with business applications inside Copilot

Microsoft 365 Copilot is becoming an interactive workspace for business applications. Dynamics 365 Sales, Dynamics 365 Customer Service, and custom apps built with Power Apps will surface directly as agents with rich UX inside chat in Microsoft 365 Copilot. Agents using Apps SDK and MCP Apps can also bring Microsoft partner apps into the conversation, including tools teams already use, like Adobe Express, Figma, and Wix. This is the interface layer shift in practice. Instead of switching between applications, users state what they need in Copilot and the system responds. You can review data and take action without leaving the conversation. Copilot becomes the place where work gets done.

As an example, a human resources (HR) employee can now call on their custom HR app, built with Power Apps, right within Copilot to compile a list of office locations with the highest new hire counts this quarter, viewing the results in an organized table with filter options. Additionally, they can prompt the application to show the results in a map view, all without leaving their Copilot interface.

Or a customer service representative can begin their day in Microsoft 365 Copilot by reviewing a summary of priority cases they need to focus on, easily viewing and updating their data from Dynamics 365 Customer Service.

Paused

Public preview for this capability will be available later this month for Power Apps, with availability for Dynamics 365 Sales and Dynamics 365 Customer Service launching in early April 2026. Throughout the next month, we’ll also introduce support for this capability across a handful of Microsoft partner apps, including Adobe Express, Adobe Acrobat, Base44, Box, Canva, Coursera, Figma, Miro, Monday.com, Optimizely, and Wix. All pre-built partner app experiences will be accessible via the Microsoft 365 Agent Store for users with Microsoft 365 Copilot.

Bring Copilot and agents into Dynamics 365 and Power Apps

The experience works in both directions. Microsoft 365 Copilot and agents like Researcher and Analyst will be accessible directly within Dynamics 365 Sales, Dynamics 365 Customer Service, and custom apps built with Power Apps. Employees get the same Copilot capabilities they trust across Microsoft 365 while staying grounded in their operational systems.

Customers can continue to benefit from pre-built agents in Dynamics 365, including Sales Qualification Agent, Case Management Agent, and Account Reconciliation Agent, which help teams automate routine work and focus on higher value decisions.

Consider a seller working in Dynamics 365 Sales who asks Researcher to generate a full account overview: customer relationship management (CRM) context, internal knowledge, and external research combined in one response, surfaced in place. The unit of value shifts from “find the right screen” to “get the answer and act.” This creates a more consistent experience across productivity tools and business applications. Work moves from insight to execution with less friction between systems.

Paused

Microsoft 365 Copilot in Dynamics 365 Sales, Dynamics 365 Customer Service, and canvas apps in Power Apps will be available in public preview by early April 2026. Microsoft 365 Copilot in model-driven apps built with Power Apps will reach general availability by early April 2026. A Microsoft 365 Copilot license is required. This experience with Power Apps also requires a Power Apps premium license.

Microsoft 365 Copilot in Power Apps allows us to ask questions and make decisions directly against our Dataverse data, while also combining insights from Microsoft 365 when needed. The experience now feels truly unified, allowing our users to summarize complex operational data, trigger actions, and seamlessly access insights. We’ve seen significant increases in the value provided to both our internal solutions and customer-facing products.Peter Kestenholz, Founder & Head of Innovation, Context&

Grounded in your organization’s intelligence with Work IQ

Underpinning all of this is Work IQ. Work IQ connects signals from Microsoft 365 with operational data from Dynamics 365 and Power Apps. It follows work as it happens across documents, meetings, chats, and business processes. This is the intelligence layer: the thing that resolves entities and relationships across structured and unstructured sources, so agents and Copilot share a common understanding of what is happening across the business.

Decisions discussed in a meeting or email can connect to live data in a business application. Changes in one place surface where attention is needed elsewhere. And because this intelligence is grounded in Dataverse and your organization’s own data, actions stay aligned to real processes and real context.

For example, when a pricing change is discussed in a meeting, Work IQ understands how that decision impacts active opportunities in Dynamics 365 Sales, surfacing the affected opportunities within Copilot for review.

Paused

Work IQ plays an important role in making business applications agentic. Without it, agents operate on partial information. With it, they act on the full context of the business.

Users with a Microsoft 365 Copilot license can experience Work IQ with Dataverse integration directly inside Power Apps, Dynamics 365 Sales, and Dynamics 365 Customer Service in public preview by early April 2026.

Learn more about how Work IQ uses Dataverse to ground Copilot in business data

See how it all comes together

Copilot, agents, and Work IQ come together as a system of work. Within that system lies a new generation of business applications: applications that understand context, respond to intent, and support execution where work actually happens. The business application stack is entering a significant architectural shift. What we’re announcing today is one step in that larger transition. We are building a platform where applications, intelligence and execution converge so teams operate with more clarity and less overhead.

You’ll see this foundation expand across Dynamics 365, Microsoft Power Platform, and Microsoft 365 as we bring more agentic capabilities into the flow of work. Agentic business applications are already taking shape.

• Tune in to the Microsoft Frontier Transformation digital event on March 9, 2026 at 8:00 AM PT.
• Register for the Business Applications Update event streaming on March 18, 2026 at 9:00 AM PT.

The post A new way of working is taking shape: Frontier Transformation appeared first on Microsoft Power Platform Blog.

This plugin is purpose-built for Power Pages. It understands table permissions, web roles, site settings, setting up authentication and Web API patterns. The code it generates is platform-aware, so you spend less time on manual configuration and more time building your site.

How it works

The plugin provides nine conversational skills covering the full lifecycle of a Power Pages single-page application (SPA) site. Here’s a typical end-to-end flow:

• Create your site (/create-site). Describe what you’re building, the pages you need, and your design preferences. The plugin scaffolds the project with your choice of framework (React, Vue, Angular, or Astro), installs dependencies, and opens a live browser preview.
• Deploy and activate (/deploy-site, /activate-site). The plugin builds your project, uploads it to Power Pages, and provisions a public URL.
• Set up your data model (/setup-datamodel). A specialized Data Model Architect agent analyzes your site’s code, checks your Dataverse environment for existing tables, and proposes a schema with an ER diagram. The plugin doesn’t create anything until you approve.
• Connect to live data (/integrate-webapi, /add-sample-data). The plugin scans your components for mock data and replaces it with production-ready API code, including typed clients, CRUD services, and framework-specific patterns. A Permissions Architect agent proposes table permissions and site settings for your review. You can also populate your tables with realistic test records.
• Add authentication and SEO (/setup-auth, /create-webroles, /add-seo). The plugin generates sign-in and sign-out functionality with Microsoft Entra ID, role-based access control, web role definitions, sitemaps, and meta tags.
• Deploy the final site (/deploy-site). A final deployment pushes your code, permissions, web roles, and site settings to your Power Pages environment.

Each skill works independently and checks its own prerequisites, so you can run them in any order. At every critical step, the plugin proposes changes and waits for your approval before it acts.

A typical end-to-end workflow

Get started

You need the following:

• Node.js 18 or later

• Power Platform CLI (PAC CLI) – latest version

• Azure CLI – latest version

• GitHub Copilot CLI or Claude Code

You also need a Power Platform environment with Power Pages and authenticated sessions for both PAC CLI and Azure CLI.

To install the plugin, open GitHub Copilot CLI or Claude Code and run the following commands:

/plugin marketplace add microsoft/power-platform-skills
/plugin install power-pages@power-platform-skills

After installation, run /create-site and describe what you want to build.

For the full walkthrough, see Get started with the Power Pages plugin for GitHub Copilot CLI and Claude Code.

Tip: New to GitHub Copilot CLI or Claude Code agentic coding tools?

Read Tips and best practices for guidance on writing effective prompts, sharing errors with context, building incrementally, and getting the most out of the plugin.

We are looking for your feedback

Your feedback helps us improve the developer experience on Power Pages. Share your thoughts and reach out on the Power Pages Community Forum. You can also submit ideas through the Power Pages Ideas portal.

The post Build Power Pages sites with AI using agentic coding tools (preview) appeared first on Microsoft Power Platform Blog.

Bringing apps and agents together for organizational transformation driven by human-agent collaboration

Today, we’re excited to bring the Power Apps MCP (Model Context Protocol) Server to public preview. The Power Apps MCP Server enables agents to automate repetitive app tasks, with human review and approval through the new task-centric enhanced agent feed. The Power Apps MCP Server also provides built‑in supervision tools that allow humans to review, assist, and take control of agent actions when needed.

Building on success: The journey from form fill assistance to MCP server

We introduced the agentic data entry in Power Apps some time back to speed up form completion with AI suggestions. The response from users was overwhelmingly positive, with high adoption and valuable feedback that shaped our vision for what came next.

Based on this feedback, we recognized an opportunity to extend these capabilities beyond a single-purpose agent. The result is the Power Apps MCP Server – the same proven technology that powers the in-app form fill suggestions – now available as a flexible MCP tool that can be used by agents across your organization and scale to meet enterprise demands. We’re starting with data entry and will be adding other create-read-update-delete operations over time, progressively expanding the app tools available to your agents.

The Power Apps MCP Server equips your agent with two types of capabilities:

1. Automate repetitive app tasks: agents can now use tools like form filling assistance initially built and refined in Power Apps. Just add and configure the MCP tool in your agent and point the invoke_data_entry tool to a shared mailbox, SharePoint folder, or other unstructured content source. The invoke_data_entry tool will extract the relevant fields from the source and create the corresponding records in your app, with built-in human review and approval in the agent feed.

2. Supervise agent activity: agents can now handoff control to humans for review, assistance, and steering through these MCP tools. This way business users can supervise agent activity in the agent feed. The tools give makers much more control over the tasks they want to publish to the agent feed and when they need agent-human handoff.

Agent feed reimagined with native MCP integration

To leverage the capabilities of the Power Apps MCP Server, we’ve completely overhauled the agent feed. This transformation gives makers more granualar control to shape the agent feed experience – deciding which tasks appear and how users track and interact with agent activity. The redesigned agent feed provides a shared collaborative space where humans and agents work together seamlessly:

• Makers have granular control over agent feed tasks surfaced to users.
• Users get a side-by-side comparison view for data entry tasks that makes it easy to review and approve agent actions.
• Direct navigation to specific records within your app for context-aware interactions
• Users can view agent performance metrics and insights in their app.

Turn your existing apps into agentic apps

With the Power Apps MCP Server, makers can bring AI agents directly into the apps their users already know and use. This allows business experts to easily supervise, collaborate with, and guide agents as part of their daily workflows. As a result, both traditional and new business applications evolve into agentic apps, delivering rich, agent‑enabled experiences, see details here.

State Farm reimagines claims processing

State Farm’s team processes dozens of claims estimates every day, each arriving in different formats with varied attachments and information structures. Manually reviewing and entering this data is time‑consuming and prone to errors.

With MCP powered agents and agent feed, these emails can be automatically analyzed to extract key field values, and any missing details are surfaced for human review before the records are created. Learn more in the Microsoft Ignite 2025 session.

Learn more, get started and share your ideas

We invite you to learn more about agent feed in our learn documentation and explore what it can do for your apps. The Power Apps MCP server is being made available in public preview starting with United States early release cycle environments  and will be gradually rolled out to other regions, following standard weekly deployment.

We’d love to hear your experience and feedback – share it in Community forum or connect with us directly. Let us know what you are building, where supervision is useful and what would you welcome as the next iteration on the agent supervision capabilities in the apps.

The post Public preview: Power Apps MCP and enhanced agent feed for your business applications appeared first on Microsoft Power Platform Blog.

The new Client API (Preview) addresses this by providing a stable, object-oriented $pages namespace. This allows developers to interact with site components using supported methods rather than hacking the DOM, ensuring reliability, maintainability, and upgrade safety.

What’s New: The $pages Object

Client API exposes a global $pages object that acts as the entry point for all client-side operations.

• Form & Control Manipulation: Programmatically get or set values, visibility, and disabled states for controls without guessing ID attributes.
• Multistep Form Navigation: Native methods like goToNextStep() and goToPreviousStep() to control user flow through complex wizard-style forms.
• Simplified Web API: A dedicated $pages.webAPI object that wraps Dataverse calls (Create, Read, Update, Delete) with clean async/await patterns, automatically handling the complexity of authentication headers.
• User & Session Management: Methods to trigger $pages.user.signIn() or signOut() and manage site languages dynamically.

How to Get Started

To use the Client API, you must ensure your logic runs only after the API is fully initialized. The $pages object is not available immediately on page load.

1. Initialize with onPagesClientApiReady

Use the new Microsoft.Dynamic365.Portal.onPagesClientApiReady function. The modern approach uses await to ensure a clean, sequential flow.

// Modern async/await initialization
let $pages = await Microsoft.Dynamic365.Portal.onPagesClientApiReady();
console.log("Client API is ready!");

2. Manipulate UI Controls (Read/Write/Hide)

Instead of searching for #element_id, use the forms collection to access controls securely.

// Get the API instance
let $pages = await Microsoft.Dynamic365.Portal.onPagesClientApiReady();

// Retrieve a specific form by ID
let form = $pages.currentPage.forms.getFormById('form_#1');

// Access controls
let controls = form.controls;

// Example: Hide the first control if it exists
if (controls.length > 0) {
    console.log(`Hiding control: ${controls[0].getName()}`);
    controls[0].setVisible(false); 
}

3. Interact with Dataverse (Web API)

Create and retrieve records using the simplified $pages.webAPI methods.

Note: Ensure you have configured Table Permissions and enabled the Web API for the specific tables you are accessing.

// Create a new Contact record
await $pages.webAPI.createRecord('contacts', { 
    firstName: 'John', 
    lastName: 'Doe' 
});

// Retrieve Accounts with OData query ($select)
let accounts = await $pages.webAPI.retrieveMultipleRecords('accounts', '$select=name&$top=3');
console.log(`Retrieved ${accounts.length} accounts.`);

We are looking forward to your feedback

Your feedback will help us continue to build on and improve the capabilities of this feature. We want to hear from you!

Please explore the Client API documentation and let us know your thoughts. You can submit your feedback and feature ideas on the Power Pages Ideas site.

The post Power Pages Client API (Preview): Native Client-Side Library for Forms and Data appeared first on Microsoft Power Platform Blog.