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.

We are seeing new AI-assisted scenarios across Dynamics 365 apps and Power Platform, from natural language queries to automated decision-making. As a direct result, Microsoft Dataverse, the underlying data platform for Dynamics 365 and Power Platform, is seeing rapid growth in metadata, solution artifacts, and contextual data.

This shift is driving a new class of workloads that require significantly more storage capacity than traditional systems. As a direct result, we received customer feedback that over time the base entitlement for business apps was not sufficient to get started, which was a hinderance to innovation. Starting in December, we are implementing two updates to address customer concerns:

1. Increasing baseline Dataverse capacity across business applications (Dynamics 365 and Power Platform). This includes an increase to tenant included capacity (specifics can be found on page 43 of the December Issue of the Dynamics 365 Licensing Guide under “Default subscription capacity included per tenant”). These changes ensure customers have the headroom to scale new scenarios without hitting limits. Whether you’re building Copilot experiences, orchestrating workflows, or enabling agentic apps, Dataverse now provides flexibility and capacity to support your innovation.
2. Simplifying the overall storage entitlement across Dataverse and Dynamics 365 ERP applications to make capacity planning easier. This flexibility creates the foundation needed for agentic ERP at scale.

Impact on your Dynamics 365 ERP data storage licensing

For ERP customers using Dynamics 365 Finance and Operations apps, the key update is that default storage capacity is increasing and will now be reported as a shared entitlement across both the ERP operational store and Dataverse. This change gives customers greater flexibility to allocate storage where it’s needed most. Instead of managing separate pools, customers can now apply their storage entitlements seamlessly as ERP workloads grow.

• Before: Operations and Dataverse capacities were capped separately for the same F&O product.
• After: Storage capacity functions as one combined entitlement that can be used for either Dataverse or ERP (see “entitled capacity” in diagram below)

This matters most for Dynamics 365 Finance Premium and Supply Chain Management Premium customers, where the combined entitlement is materially higher than either footprint alone. The increase reflects the way ERP usage is evolving — with more execution context traveling alongside the transaction. In practical terms, this means:

• If AI-assisted approvals generate more annotations or reasoning context, that growth can be absorbed without Dataverse becoming a limiting factor.
• If supplier or operational workflows accumulate larger supporting files, attachments now draw from the full entitlement rather than a smaller segment.
• If orchestration or exception resolution produces more state and process history, it scales as part of ERP rather than hitting a cap early.

Under the previous entitlement model, Dataverse could fill more quickly than the ERP store even if total tenant capacity remained. Under the new model, capacity follows usage — not a system boundary.

Why this accelerates system-of-action ERP

When ERP is purely a system of record, storing the final outcome is enough. But when ERP becomes a system of action, it must also retain how and why an action was taken — not just what was recorded.

The contextual data that enables agentic execution can no longer sit at the edge of the system. It becomes part of the operational story. This update aligns the storage model with that reality, giving organizations the flexibility to modernize without re-engineering their data footprint or rethinking where contextual data is allowed to live.

Capacity now reflects the purpose of ERP in the AI era — not only documenting the state of the business, but helping drive what happens next.

Looking ahead: modernizing storage entitlements

By modernizing storage entitlements now, we are ensuring customers have the runway to support that growth — not after they hit constraints, but ahead of it. This removes friction from ERP transformation and positions organizations to move confidently toward AI-enabled operating models.

The latest Dynamics 365 Licensing Guide reflects the changes and no customer action is required. The updated entitlements will be reflected automatically in Power Platform admin center as the new model takes effect. As these capabilities roll out, customers will gain additional flexibility to grow agentic ERP workloads with confidence, knowing their storage model now matches the future of ERP. To learn more, please review the following resources:

• Review the updated licensing guide: Dynamics 365 Licensing Guide
• Read docs: Dataverse capacity-based storage overview – Power Platform | Microsoft Learn
• Read docs: Finance and operations storage capacity – Power Platform | Microsoft Learn

The post Flexible Dataverse capacity for apps and agents appeared first on Microsoft Power Platform Blog.

Previously, moving from the Power Pages VS Code for the Web editor to the desktop version involved several manual steps:

• Launching VS Code Desktop and signing into the correct environment
• Manually downloading the site source using Power Platform CLI or the Actions view
• Navigating to the appropriate folders and opening the project

These manual steps disrupted developer flow, slowed down iteration, and added friction, especially when collaborating in fast-paced fusion teams.

What’s new

With the latest Power Pages update, developers can now:

Open VS Code Desktop directly from VS Code for the Web, which automatically downloads your site’s source code and sets up a ready-to-code workspace.

This creates a zero-friction, one-click experience that gets developers coding in seconds with full local context, all without leaving the Power Pages design environment.

If you don’t have VS Code Desktop installed on your system, the feature will prompt you to install Visual Studio Code Desktop along with the Power Platform Tools extension. These components are required for the seamless transition and auto-download for source code to work. Once installed, you’ll be able to take full advantage of this one-click experience.

Why VS Code Desktop?

Switching to VS Code Desktop unlocks advanced capabilities such as:

• GitHub Copilot for AI-assisted coding
• Configuration file editing for fine-grained control
• Develop with Live Preview for real-time feedback
• Write and run unit/integration tests for robust application quality
• Access to a wide range of extensions for debugging, linting, and productivity

For detailed guidance on how Power Pages integrates with VS Code Desktop, including setup steps and best practices, check out the official documentation here.

We are looking forward to your feedback

This update is part of a broader effort to make Power Pages a first-class platform for both makers and professional developers, with seamless transitions between no-code, low-code, and pro-code experiences.

Whether you’re creating external customer portals, partner ecosystems, or secure data-driven applications, Power Pages now fits seamlessly into your workflow, from lightweight, zero-footprint browser tools to powerful desktop tools in your development environments.

Explore these new capabilities and share your thoughts and experiences. Your feedback is crucial in shaping the future of Power Pages.

The post Seamlessly Open VS Code Desktop from Power Pages VS Code for the Web with auto-download site code appeared first on Microsoft Power Platform Blog.

Why Use GitHub Spark + Codespaces and Host in Power Pages?

GitHub Spark is an AI-powered tool that generates single-page applications using natural language prompts, while Codespaces provides a pre-configured development environment in the cloud.

Power Pages serves as a secure, scalable, and enterprise-grade platform tailored for modern web development. With built-in capabilities for security, governance, analytics, and seamless integration across the Microsoft Power Platform ecosystem, it provides everything you need to build, manage, and scale professional-grade web applications efficiently. Together, these enable:

• AI-assisted site generation with GitHub Spark
• Instant cloud-based coding with GitHub Codespaces
• Seamless deployment to Power Pages using Power Platform CLI
• Built-in security, governance, analytics, and seamless Power Platform integration delivered through Power Pages

Hosting Your Site in Power Pages

Once your site is created using Spark and edited in Codespaces, you can deploy it to Power Pages using the Power Platform CLI.

Quick steps:

1. Use GitHub Spark to generate your site template.
2. Open the project in GitHub Codespaces.
3. Customize your site using React or other SPA frameworks.
4. Deploy using pac pages upload-code-site.

To explore the complete step-by-step guide, refer to the document: Tutorial: Create and deploy a single-page application using GitHub Spark and Codespaces.

Demo

Key Resources

• Tutorial: Create and deploy a single-page application using GitHub Spark and Codespaces.
• Create single-page application in Power Pages
• Power Pages sample sites

The post Build and deploy a single-page application in Power Pages using GitHub Spark and Codespaces appeared first on Microsoft Power Platform Blog.

Aligning to the official GPT-5 announcement yesterday, makers using generative pages will have access to new GPT-5 model, which offers significant improvements in code generation quality, performance, and reliability. To give optimal flexibility, we’ve added a model selector to the experience—allowing you to choose between GPT-4.1 and GPT-5 depending on your needs. This update started rolling out yesterday.

What’s new with GPT-5 in generative pages?

• Improved code generation quality: Better syntax, smarter layout handling, and fewer rendering errors.
• Fewer failures: Higher success rates for generated pages, even in complex scenarios.
• Enhanced performance: Faster generation times during the page creation process.

In addition to giving access to the new GPT-5 model, this release includes several minor enhancements to improve usability and reliability:

• An expanded context window to reduce lost requirements in longer sessions
• Better fallback styling to preserve model-driven app design
• Ensured retention of image attachments during retries
• More informative error messages for invalid requests
• Conditional warnings when another user is editing the same page
• Improved undo/restore behavior for error and retry scenarios

This update reflects our commitment to making AI-native app development intuitive, flexible, and enterprise-ready.

Explore the documentation here to learn more and start building with GPT-5 today.

The post Generative pages get better with GPT-5: Improved quality, enhanced performance appeared first on Microsoft Power Platform Blog.

What’s New?

Power Pages now supports creating and deploying complete single-page applications through a code-first approach. This means developers can:

• Build modern React applications with full control over the frontend experience
• Use AI-powered coding assistants to accelerate development
• Use Power Pages Web APIs to perform data operations
• Deploy SPAs directly to Power Pages environments using the Power Platform CLI
• Maintain enterprise-grade security and governance

This represents a significant shift from traditional Power Pages development, offering developers flexibility while leveraging the platform’s security, governance, and scalability.

Prerequisites

Before diving in, ensure you have:

• Power Platform CLI version 1.44.x or later
• A Power Pages site on version 9.7.4.x or later

Demo

Key Features and Benefits

1. AI-Assisted Development

Developers can leverage next-generation AI tools like GitHub Copilot agent to transform their work. Instead of writing repetitive boilerplate code, developers can use natural language to describe what they want to build, letting AI handle the implementation details.

2. Modern Frontend Framework Support

Power Pages SPA sites are built using React, enabling developers to:

• Create responsive, dynamic user interfaces
• Implement complex state management
• Use the vast ecosystem of React components and libraries
• Build truly interactive experiences without page refreshes

3. Streamlined Deployment Process

The Power Platform CLI provides simple commands for uploading and downloading SPA sites:

# Upload your SPA to Power Pages
pac pages upload-code-site --rootPath "./my-app" --compiledPath "./build" --siteName "Contoso App"

# Download an existing SPA for editing
pac pages download-code-site --path "." --webSiteId "your-site-guid"

4. Enterprise Governance and Security

Despite being client-side applications, Power Pages SPAs maintain the platform’s robust security and governance:

• Full support for identity providers (Microsoft Entra ID, Microsoft Entra External ID, etc.)
• Table permissions and web roles enforcement on API calls
• Access to user context for personalized experiences
• Public and private site configurations

We are looking forward to your feedback

This feature enables professional developers to build sophisticated frontends while leveraging Power Pages’ backend capabilities, Power Pages is bridging the gap between low-code and pro-code development. Your feedback is crucial in shaping the future of this feature. We want to hear from you!

Check out the official documentation and the sample React site code to begin your journey into modern Power Pages development.

The post Build Modern Single-Page Applications in Power Pages (Preview) appeared first on Microsoft Power Platform Blog.