Making a site multilingual used to mean choosing an i18n library, extracting every string, building a language selector, and testing right-to-left layouts by hand. Now you name the languages, approve a plan, and the plugin does the rest.

What’s new

• /add-localization skill. Add or extend multilingual support in React, Vue, and Angular sites.
• AI-generated or blank translations. Let the agent translate your content, or create blank translation files for your own translators.
• Built-in right-to-left support. The skill audits your layout, applies logical CSS, and verifies both the layout directions in a real browser.
• Localization during site creation. /create-site now asks whether you want more languages, and hands off to /add-localization without leaving the flow.

See it in action

How it works

Run the skill from your project folder:

/add-localization Add French, German, and Arabic

1. Plan. The skill detects your framework and opens a plan in your browser listing the languages, package, and files to change. Nothing changes until you approve it.
2. Build. It installs the package, extracts strings into translation files, translates them, and adds a language selector.
3. Verify. It builds your site and tests every language in a real browser, including language switching and right-to-left layouts. A language that fails stays hidden from visitors until it’s fixed.
4. Review and deploy. You review the result, then deploy with /deploy-site.

Things to know

• /add-localization localizes your site’s user interface. It doesn’t add languages to your Dataverse environment or translate Dataverse records. Dataverse and Power Pages system messages remain in English or selected language.
• Localization for Astro sites isn’t available yet.

Get started

Install or update the plugin. The installer also updates the Power Platform CLI and turns on automatic updates.

Windows (PowerShell):

iwr https://raw.githubusercontent.com/microsoft/power-platform-skills/main/scripts/install.js -OutFile install.js; node install.js; del install.js

macOS, Linux, or Windows (cmd):

curl -fsSL https://raw.githubusercontent.com/microsoft/power-platform-skills/main/scripts/install.js | node

Then run /add-localization in an existing power pages SPA site, or run /create-site and say yes when it offers more languages.

Resources

• Power Pages plugin on GitHub
• Agentic site authoring

The post Go multilingual with the Power Pages plugin appeared first on Microsoft Power Platform Blog.

Until now, /create-site built each site from the ground up, giving you the flexibility to create highly customized and branded experiences. With templates, you can skip the ground-up build for common business scenarios, starting with a complete, production-ready site in minutes and then customizing it to fit your needs.

What’s new

• Smart template matching. Describe the site you want, and /create-site recommends a matching template and framework variant.
• Preview before you build. See the recommended template before anything is created, then choose to use it or build your site from scratch.
• Guided provisioning. /create-site imports the Dataverse solution, uploads the site, applies sample data, and shows progress through a live status page.
• Two templates to start. Choose from the 311 Citizen Services Portal or Supplier Invoice Portal today, with more templates on the way.

Why start from a template

• Spend less on AI credits. Recreating the 311 Portal from scratch can consume significant AI credits. Starting from the template requires only a few dollars in AI credits for the initial creation, while still giving you a complete foundation to customize.
• Go from idea to site in minutes. Generating a full site from scratch can take more than an hour. A template gets you up and running in minutes.
• Meet accessibility standards from day one. Templates are WCAG 2.2 compliant out of the box, so your site is ready for production right away.
• Ship with confidence. Templates are free of known code vulnerabilities at release, and we patch and republish them whenever new issues are found.
• Build on best practices. Every template uses a responsive layout and follows recommended patterns for Power Pages.

Code site templates give you a ready-made starting point without limiting customization. Continue building with the plugin or edit the code directly to make the site your own.

Available templates

Each template includes the site code, a Dataverse solution, and sample data, so your site works end to end as soon as it’s provisioned. Both templates are available as React variants today. More templates are coming soon!

How it works

1. Discover. Describe the site you want. /create-site matches your intent to a template and framework variant.
2. Confirm. The skill runs pre-flight checks and shows you a preview of the template. Choose to continue with the template or create your site from scratch.
3. Provision. The skill imports the Dataverse solution, uploads the site, and applies sample data. A live status page shows you the progress as it happens.
4. Go live. The skill activates your site and opens it in the browser.
5. Customize. The skill asks what you’d like to change next, so you can keep building right away.

Here’s what that looks like in practice:

You: "/create-site A portal where residents can report potholes and track their requests"

Plugin: 
        → Matches your request to the 311 Portal template (React) and asks for confirmation
        → Runs pre-flight checks and opens a template preview
        → Imports the Dataverse solution and uploads the site
        → Applies sample data and shows live provisioning status
        → Activates the site and opens it in your browser
        → Asks what you'd like to customize next

Get started

Install or update the plugin

Run the installer script to get the latest Power Pages plugin and Power Platform CLI. The script installs all Power Platform plugins, updates PAC CLI to the latest version, and turns on automatic updates.

Windows (PowerShell):

iwr https://raw.githubusercontent.com/microsoft/power-platform-skills/main/scripts/install.js -OutFile install.js; node install.js; del install.js

macOS, Linux, or Windows (cmd):

curl -fsSL https://raw.githubusercontent.com/microsoft/power-platform-skills/main/scripts/install.js | node

Try it out

Run /create-site and describe the site you want. If a template matches, you’ll see a preview before anything is created.

Resources

• Power Pages plugin on GitHub
• Power Pages samples and template catalog
• Contribute a template
• Power Pages documentation

The post Create Power Pages sites in minutes with SPA templates appeared first on Microsoft Power Platform Blog.

With general availability, Modern List is now the default list experience for newly created Power Pages sites. Existing classic lists remain unchanged, so that your organization can transition at their own pace. This release also introduces support for custom JavaScript through the Power Pages Client API, giving you more flexibility to tailor list experiences to business needs.

Extend Modern List with Custom JavaScript

Makers can continue to configure Modern List in the Power Pages design studio by selecting Dataverse views, enabling record actions, and applying styles. When a scenario requires more advanced behavior, developers can extend the same list with custom JavaScript instead of replacing it with a separate data grid.

Using the Client API, developers can:

• Access the rows and columns loaded in a Modern List.
• Read raw and formatted row values.
• Respond to list loading, row selection, and cell selection events.
• Show, hide, or style rows and columns.
• Customize column headers, tooltips, and cell display text.

For example, a customer service site could highlight high-priority requests, apply different styles based on status, or respond when a user selects a record. These customizations retain the list’s existing Dataverse views, actions, filtering, and security configuration.

Get started

Add a Modern list to a newly created site or convert an existing list to Modern List on an existing site.

Learn more:

• Add a list in Power Pages
• Power Pages Client APIs

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 Modern List in Power Pages is now generally available 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 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:

Power Platform

Build hands-on Power Platform and AI expertise with Power Series

Developed by the Power CAT team, Power Series is now available with 20 hands-on labs that help customers, partners, and field teams build practical Power Platform and AI skills at their own pace. Drawing on the team’s experience delivering enterprise customer workshops, Power Series brings that expertise into a reusable, self-service learning experience.

Learners gain hands-on experience choosing the right capabilities, building working solutions, and making design decisions based on their business needs and solution complexity. The outcome: practical skills and greater confidence to apply Power Platform and AI to real projects, from modernizing applications and automating processes to governing solutions.

Power Apps

Build polished canvas apps faster with fluent screen templates

Start new canvas app experiences faster with six additional ready-to-use screen templates based on fluent 2 patterns along with recently shipped 3 fluent templates. These templates give makers responsive layouts, editable controls, and practical starting points for common app scenarios. Add one from the new screen experience, connect your data, and customize the design instead of building every screen from scratch.

These templates are a replacement of previous out of box templates built on classic controls.

Additional improvements to modern controls and update from classic to modern controls

Update controls faster. Makers can now update eligible controls in bulk from the control-update surface instead of repeating the process one control at a time. Update all works on the current screen, can enable the required modern-control settings, and preserves the familiar Studio undo and redo experience. Review affected formulas after updating because property names, enum values, and behaviors may change.

More modern controls and quality improvements. The newly released progress bar supports determinate and indeterminate experiences, Power Fx-driven values, semantic colors, theme-aware styling, and accessible progress semantics. The modern avatar and spinner are also available, with improved interaction and upgrade behavior. Continued quality work makes date picker interactions and reset behavior more reliable and preserves formulas that reference checkbox, rating, and toggle.

Agentic apps

Generally available: refreshed model-driven apps UI, plus display density in public preview

The next wave of UI modernization for model-driven apps arrives with version 2609.1. The header and navigation refresh feature reaches general availability, and the new display density feature enters preview. Together they deliver a cleaner, more efficient layout across the app shell, forms, and views, increasing your working area, reducing the time you spend navigating pages, and aligning the experience with modern Microsoft 365 design patterns.

Header and navigation refresh brings a modern app header with simplified layout and improved spacing, a streamlined sitemap that’s easier to scan, and noticeably more working space on forms. The command bar is now the only element fixed at the top of the page, with the summary area and form header scrolling alongside the rest of the form. Once the form header scrolls out of view, a condensed sticky header attached to the bottom of the command bar is shown. At GA, the experience remains opt-in so makers control adoption. Apps that already have the feature enabled get these enhancements automatically.

Display density (preview) answers a longstanding customer request to fit more content into model-driven app pages. Three levels are available — comfortable (the default), cozy, and compact — so users can tighten the interface to match how they work. An app setting lets customers set the default level for their users or turn the feature off entirely, and users can adjust their own density through personal settings. Display density requires the header and navigation refresh feature and is enabled by default once that feature is on.

AI powered development

Generally available: canvas authoring agent plugin for AI-assisted app building

The canvas authoring agent plugin is now generally available, giving makers and developers a new way to work with Power Apps canvas apps using agent-assisted development workflows. With the authoring agent plugin, makers can more easily create, inspect, and update canvas apps through agent-driven interactions with their favorite coding agent, helping accelerate common app-building tasks while keeping makers in control. Learn more about the agent here.

This update is part of our continued investment in making canvas app creation faster, easier, and more approachable. By bringing agentic authoring and MCP support to canvas apps, makers can use modern AI development patterns to move from idea to working app more quickly, iterate on app structure and controls, and streamline parts of the authoring process that previously required more manual effort.

Generally available: vibe code entire model-driven apps with the app-builder skill

Generative pages gave makers an AI-assisted way to build individual pages in model-driven apps. The new model app-builder skill extends that approach to the whole application, and it’s now generally available. Used with an AI code generation tool such as GitHub Copilot CLI or Claude Code, it builds and edits model-driven apps from natural-language requirements.

You start by describing the business process or app you need. The skill turns your requirements into an application plan that you review before it makes any changes. It starts with user personas and the jobs they need to accomplish, and then extends to cover a growing list of model-driven app artifacts including:

• Tables, columns, relationships, and sample data
• Forms, views, and charts
• Generative pages for experiences that go beyond standard forms and views
• A sitemap with custom icons for each table
• JavaScript validation rules on forms
• Security roles based on the planned personas and data access needs
• Business process flows (recently added)
• Business rules (recently added)

No app artifacts are created until you approve the build plan. The skill also works on editing your existing apps. Everything it produces is a standard Power Apps and Dataverse artifact, so you can keep iterating with the skill or switch to the Power Apps studio designers whenever you prefer.

Embed a generative page directly inside a model-driven app form

Generative pages are no longer limited to standalone pages in your app’s navigation. You can now add a generative page to a model-driven app form so that it appears within a section or tab, letting an AI-generated experience sit right alongside the standard fields on a record.

Build the generative page to accept the recordId input parameter, and when a user opens a record, the form automatically passes the current record ID to the generative page for you. The page knows which record it’s on from the moment it loads. This unlocks the mixed layouts makers have been asking for, keeping the out-of-box form for structured data entry and dropping in a purpose-built generative page for the part of the record that needs a richer, more tailored view.

Public preview: generative pages can now use data from Power Platform connectors

To date, generative pages have been built on Dataverse tables, but now they can reach further. Connector support (preview) lets a generative page use data outside of Dataverse through the Power Platform connector ecosystem. If the data your scenario needs already lives in SharePoint, SQL, or any other connected service, you can build a page against it directly.

Connector support works in both authoring experiences by targeting existing connection references in the environment. In the generative page designer, configured connectors are available through add data > connectors, where you select the connection reference and choose the data the page should use. With AI code generation tools, describe the data you want, and the agent walks you through selecting the right connector and adding the binding so it deploys with the page.

Power Automate

Quick start cards make it easier to begin automating from the Power Automate home page

New quick start cards on the Power Automate home page provide clear, actionable entry points for common automation scenarios. Users can move directly into creating a flow without first navigating menus or searching through the template gallery. By bringing relevant starting points to the home page, this experience helps new users discover what they can automate while giving experienced users a faster path from idea to flow.

Server-side search helps users find flows faster

Searching in My Flows is now faster and more reliable with server-side search. Instead of filtering only the flows already loaded in the browser, Power Automate sends the search request to the service and returns matching flows from the complete list of available flows in the current environment. This improvement is especially helpful for users who manage large numbers of flows. It provides more complete results while reducing the time and effort required to locate a specific flow.

Learning updates

Training paths and labs

Updated training

• Application lifecycle management for the Power Platform
• Solution Architect: Design Microsoft Power Platform solutions

Power Apps maker

New

• Build and edit model-driven apps with AI code generation tools (preview)
• Column visualizations for grids in Power Apps
• Convert a vibe app to a code app
• Plan your latency for Link to Fabric

Updated

• About table relationships for Microsoft Dataverse
• Add and configure a subgrid component on a form with Power Apps
• Add and configure controls in canvas apps
• Add the calendar control to tables in model-driven apps with Power Apps
• Add the rich text editor control to a model-driven app with Power Apps
• Add, configure, move, or delete components on a form
• App navigation in model-driven apps with Power Apps
• Avatar Modern Control in Canvas Apps: Properties and Examples
• Azure Synapse Link Advance Configuration
• Azure Synapse Link for Dataverse trouble shooting guide
• Best practices: Collaborating and co-developing apps using Power Apps
• Business skills overview
• Change release channels for model-driven apps
• Checkbox modern control in Power Apps
• Choose finance and operations data in Azure Synapse Link for Dataverse
• Combo box modern control in canvas apps – Power Apps
• Common issues and resolutions for solution checker
• Complex tables requiring Power Apps licenses
• Component library
• Configure a row summary for a model-driven app
• Configure structured content in the rich text editor (preview)
• Configure your environment and link to Microsoft Fabric
• Create and edit canvas apps with AI code generation tools
• Create and edit generative pages with AI code generation tools
• Create and edit virtual tables with Microsoft Dataverse
• Create and use business skills
• Create new data columns in Dataverse
• Create or edit a Power BI embedded system dashboard
• Create or edit filters in model-driven app views
• Create or edit model-driven app main forms in Power Apps
• Create or edit model-driven app quick create forms in Power Apps
• Date picker modern control in canvas apps – Power Apps
• Define and query hierarchical data with Microsoft Dataverse
• Design a custom page for your model-driven app with Power Apps
• Display custom icons alongside values in list views with Power Apps
• Dropdown modern control in canvas apps – Power Apps
• Edit table records directly from another table’s main form with Power Apps
• Example: Create and customize a model-driven app form
• Export Microsoft Dataverse data in Delta Lake format
• FAQ about generative pages in model-driven apps
• FAQ for Power Apps vibe experience (preview)
• Frequently asked questions when transitioning from legacy data integration services to Fabric link and Azure Synapse Link for Dataverse
• Generate a page using natural language with model-driven apps in Power Apps
• Get started with formulas in canvas apps
• How to create performant Power Apps
• Importing and exporting data
• Improve component performance, stability, and reliability with solution checker
• Invoke a function using Power Platform
• Known issues with custom pages in a model-driven app
• Manage data retention policies in Microsoft Dataverse
• Model-driven app form properties in Power Apps
• Model-driven app interface design overview in Power Apps
• Number Input modern control in canvas apps – Power Apps
• Overview of the model-driven app designer
• Overview of the new Power Apps vibe experience
• Productive main form design in model-driven apps
• Progress Bar Modern Control in Canvas Apps: Properties and Examples
• Prompt columns in Microsoft Dataverse
• Receive Azure Synapse Link for Dataverse notifications in Power Apps
• Recent modern control updates in canvas apps – Power Apps
• Release channel for your model-driven app
• Responsive design guidelines in Power Apps
• Sharing a model-driven app – assigning security roles and privileges
• Spinner Modern Control in Canvas Apps: Properties and Examples
• Steps to building a model-driven app
• Tables in Microsoft Dataverse
• Text Input modern control in canvas apps – Power Apps
• Toggle modern control in Power Apps
• Transition from legacy data integration services to Fabric link and Azure Synapse Link for Dataverse
• Troubleshooting common issues with link to Fabric with Microsoft Dataverse
• Use managed identities for Azure with your Azure data lake storage
• Use plans to create AI-Powered business solutions with Copilot
• Use the model-driven app main form and its components in Power Apps

Power Apps user

New

• Enable the modern, refreshed look for model-driven apps on mobile (preview)
• Power Apps native mobile apps overview (preview)
• Quickstart: Your first Power Apps native app
• Troubleshoot issues in the native mobile app (preview)
• Use Power Apps on mobile devices

Updated

• About dialog for model-driven apps
• Advanced find
• Basic navigation in a model-driven app
• Create and manage personal views on a grid page
• Explore data on a grid page
• How do I find and run apps in Power Apps?
• Known issues and limitations for Dataverse for Teams
• Modern, refreshed look for model-driven apps
• Run apps in a web browser
• Search for records by using Dataverse search
• Understand the email experience in model-driven apps
• Use model-driven apps in Power Apps
• View your user profile
• Work with business processes in model-driven apps

Power Automate

New

• Assign a user license to a flow owned by a service principal
• Call Microsoft Copilot Studio agents from Power Automate
• Create a User-credential Mapping

Updated

• Add images to email messages
• AI Builder actions reference
• Approvals in Microsoft Teams
• Automation adoption best practices overview
• Automation Center of Excellence strategy with the Automation Kit
• Automation CoE Strategy
• Automation Kit Release Notes
• Automation Kit setup checklist
• Build and certify custom connectors
• Business process flows overview
• Configure Automation Kit
• Configure the automation kit environment variables
• Control center desktop flow audit logs
• Control Center desktop flow monitoring
• Control Center desktop flow scheduler
• Control Center Historical Voluminous Data Monitoring
• Convert a time zone
• Copilot in Power Automate
• Create a process from normalized schema
• Create an approval from a chat or channel
• Create an Object‑centric event log
• Create and test an approval workflow with Power Automate
• Create desktop flows
• Create flows for popular email scenarios in Power Automate
• Create flows that post adaptive cards to Microsoft Teams
• Create flows using the Power Apps app in Microsoft Teams
• DLP impact analysis for desktop flows
• Explore the cloud flows designer
• Export a solution
• Export OCPM semantic model into Fabric workspace
• Extract data from SAP GUI UI by using Power Automate
• Feedback and support for the Automation Kit setup guidance
• Flow exception rules framework
• Frequently asked questions about the automation kit setup guidance
• Get started with Copilot in Power Automate for desktop
• Get started with Power Automate in Windows 11
• Get started with the process mining capability
• How to build custom actions in Power Automate for desktop
• How to use the Automation Kit
• Ingest an object-centric event log
• Install Power Automate
• Install the automation kit using the command line
• Install the Workflows app in Microsoft Teams
• Introduction to desktop flows
• Limitations and resolutions for issues in the Automation Kit
• List of date and time operations
• List of string operations
• Manage desktop flows
• Manage Power Automate for desktop on Windows
• Microsoft Power Platform automation maturity model details
• Microsoft Power Platform automation maturity model overview
• Normalized schema JSON authoring
• On-premises data gateway
• Optimize flow performance
• Optional setup steps depending on your configuration
• Overview of adaptive cards for Teams
• Overview of process mining and task mining in Power Automate
• Overview of process mining in Power Automate
• Overview of the Automation Kit
• Overview of the Automation Kit test case guidance
• Overview of the Control Center
• Overview of using Outlook and Power Automate
• Power Automate console
• Power Automate for enterprise developers, ISVs, and partners
• Prepare processes and data
• Prerequisites for automating SAP GUI-based workloads
• Prerequisites to install and use the automation kit
• Record with Copilot for desktop flows (deprecated)
• Regions overview for Power Automate
• Run a desktop flow in picture-in picture
• Run SQL queries on Excel files
• Run unattended desktop flows
• Secure your data
• Set up sequential approvals
• Set up the automation kit control center
• Set up the automation kit main components
• Set up the automation kit satellite components
• Set up the automation kit scheduler
• Set up the Automation Kit security roles and permissions
• Share a cloud flow
• Share/export a desktop flow
• Sign up and sign in
• Support for service principal owned flows
• Update or roll back Power Automate for desktop
• Use AI Builder in Power Automate
• Use data operations in Power Automate
• Use Markdown language to format Power Automate approvals
• Use no-code RPA with SAP GUI in Power Automate Desktop
• Use Power Automate flows in Microsoft Teams
• Validate data by using the SAP ERP connector
• Variable data type properties
• What is Power Automate?
• Work queues actions
• Work with desktop flows using code

Power Pages

New

• Manage Exemptions for Power Pages Sites
• Power Pages security best practices
• Rotate SSL certificates for Power Pages sites
• Use WAF JavaScript challenge and CAPTCHA

Updated

• Access user and website details with server objects
• Add a custom domain name
• Add AI features in a list (preview)
• Add an agent – overview
• Add an agent from the setup workspace
• Add forms
• Add text
• Ask Copilot questions in Power Pages
• Available Liquid objects
• Build an agent from a form
• Configure Microsoft Entra ID Authentication for Power Pages Agent
• Configure user authentication for an agent
• Control use of Generative AI features for users (preview)
• Copilot for site creation
• Copilot hub for Power Pages
• Create a site with Power Pages
• Create an AI-generated color theme using Copilot
• Create and manage server logic in Power Pages
• Customize your agent
• Important upcoming changes and deprecations in Power Pages
• Known issues for Power Pages
• Manage agent provisioning
• Migrate standard data model sites to enhanced data model
• Multistep forms
• Overview of the Power Pages portals Web API
• Power Pages connectivity to a Microsoft Dataverse
• Roles required for Power Pages administration
• Security agent (preview)
• Set column permissions
• Set up an OpenID Connect provider
• Tutorial: How to add a rich text component to a form

Power Platform administration

New

• Automate procurement order acknowledgment matching with Copilot Studio and SAP
• Coca-Cola Andina improves HR support for frontline workers with Copilot Studio
• Connect Dataverse Git integration to Azure DevOps
• Connect Dataverse Git integration to GitHub
• Connect Power Apps to a centralized data warehouse with Dataverse virtual tables
• COSMO CONSULT improves sales operations and data quality using Copilot Studio agents
• Environment routing for apps
• Integrate Dynamics 365 finance and operations apps with Power Platform
• Manage Copilot Credits allocations programmatically
• Manage costs for agents powered by the GitHub Copilot harness
• Manage service updates for unified environments
• Manage SharePoint document visibility in Dataverse solutions
• Migrate legacy meetings to Microsoft Teams with a conversational agent
• Understand agent counts across admin surfaces

Updated

• Add a Microsoft Dataverse database
• Admin user management unification for Finance and Operations in Power Platform admin center (preview)
• Administration mode
• Advanced connector policies
• Automate deployments with Dataverse Git integration and pipelines in Power Platform
• Best practices for server-side synchronization
• Block unmanaged customizations in Dataverse environments
• Build tool tasks
• Business continuity and disaster recovery
• Buy Power Automate licenses
• CommandBar control reference
• Concentrix modernizes invoice processing with Power Platform and AI
• Configuration Migration tool in Power Platform
• Connect and disconnect Dataverse from a Git repository by using code
• Connect Dataverse Git integration to a Git provider
• Continuous access evaluation
• Control guest access to Microsoft Power Platform environments
• Control user access to environments with security groups and licenses
• Copilot Agent Kit real-world examples
• Copilot Studio reference architectures and solution ideas
• Create cross-tenant isolation reports
• Creator Kit – overview (preview)
• Custom contact center solution with Copilot Studio agent
• Data storage and governance in Power Platform
• Dataverse capacity-based storage details
• Dataverse capacity-based storage overview
• Deploy pipelines as a service principal or pipeline owner
• Design a reliability testing strategy recommendation for Power Platform workloads
• DetailsList control reference
• Deutsche Bahn empowers citizen developers with Power Platform
• Dunaway streamlines city code research with Copilot Studio
• Elastic compute for finance and operations apps
• Environment routing
• Epiq streamlines employee onboarding with Power Automate, Microsoft Dataverse, and AI Builder
• Exchange Online cross-tenant authentication
• ExpandMenu control reference
• Export data to Application Insights
• Extract and analyze agent conversation transcripts
• EY uses Power Platform to automate customer payment processing
• FAQs about source code integration
• Forward mailbox vs. individual mailboxes
• Geo-to-geo migrations
• Get started with a SharePoint site template
• GitHub Actions for Microsoft Power Platform
• Global Secure Access for Copilot Studio agents
• Grupo Bimbo standardizes global audit processes with Copilot Studio
• Healthcare Patient Support Agent
• Holland America Line transforms customer experience with Copilot Studio
• How to reset a password
• Icon control reference
• Identity and access management
• Important changes (deprecations) coming in Power Platform
• Invite users with Microsoft Entra B2B collaboration
• John Cockerill streamlines enterprise business processes with Power Platform
• Licensing overview for Microsoft Power Platform
• Licensing requirements for managed environments
• Lloyds Banking Group bridges language barriers with Power Apps and Azure AI services
• Manage Copilot Credits and capacity for Copilot Studio
• Manage Power Apps
• Manage privacy and security settings
• Manage your maintenance window
• Metrics and recommendations for Copilot Studio
• Microsoft 365 environment for recurring Copilot prompts
• Microsoft Dataverse reference architectures and solution ideas
• Microsoft Power Fx overview
• Microsoft Power Fx Tables: Records, Columns, and Formulas
• Microsoft Power Platform Build Tools for Azure DevOps
• Overview of Dataverse Git integration
• Overview of Power Platform activity logging and auditing in Microsoft Purview
• Overview of Power Platform and Copilot Studio reference architectures
• Overview of unified admin experience for finance and operations apps
• Pay-as-you-go meters
• Performance testing recommendation for Power Platform workloads
• Plan for deployment and administration
• Power Apps licensing FAQs
• Power Apps reference architectures and solution ideas
• Power Automate licensing FAQ
• Power Automate reference architectures and solution ideas
• Power Pages architecture key concepts and solution ideas
• Power Platform admin center overview for administrators
• Power Platform and Copilot Studio real-world case studies
• Power Platform and Dynamics 365 macro region geography
• Power Platform environments overview
• Power Platform inventory
• Power Platform inventory sample queries
• Power Platform inventory schema reference
• Power Platform licensing FAQs
• Power Platform URLs and IP address ranges
• Power Platform white papers
• PowerShell support for Power Apps and Power Automate
• Programmability and extensibility – What’s new or changed
• Recommendations for designing a deployment failure mitigation strategy
• Recommendations for designing and creating a monitoring system
• Recommendations for standardizing tools and processes
• Recover a recently deleted environment
• Requests limits and allocations
• Role-based security roles for Dataverse
• Rules for environment groups
• Secure the default environment
• Security enhancements for user sessions and access management
• Singapore Civil Defence Force implements digital solutions using Power Platform and Copilot Studio
• Solution YAML source control format reference
• Source control operations
• System Settings General tab
• T-Mobile empowers customer service representatives using Power Apps and Copilot Studio
• Telecom provider mobilezone modernizes service delivery using Microsoft Copilot Studio
• Tenant-level analytics for Power Automate
• Tenant-to-tenant migrations
• The City of Montréal enhances citizen engagement with Copilot Studio
• Tiendas CUADRA delivers always-on customer service and product discovery with Copilot Studio
• Travel concierge using generative AI with Copilot Studio
• Tutorial: Perform a transaction-less copy between environments
• Understand Variables in Microsoft Power Fx
• View and manage on-premises data gateways
• View license consumption for finance and operations apps
• View licensing and capacity recommendations
• View Microsoft Dataverse and model-driven app activity logs in Microsoft Purview
• View Power Apps activity logs in Microsoft Purview
• View Power Automate activity logs in Microsoft Purview
• View Power Pages activity logs in Microsoft Purview
• View Power Platform admin activity logs in Microsoft Purview
• View Power Platform connector activity logs in Microsoft Purview
• View security recommendations
• What’s new in Microsoft Power Platform guidance
• What’s new in the Power Platform and Copilot Studio Architecture Center
• When premium flows are subject to license enforcement

Power Platform developer

New

• Handle errors and enable HTTP diagnostics
• Manage administration mode in a unified developer environment
• Microsoft Dataverse plugin for AI coding agents (preview)
• Microsoft Dataverse plugin for AI coding agents reference (preview)
• Power Apps CLI Command Reference
• Power Apps CLI environment variables
• Publish Power Apps Code Apps with a Service Principal

Updated

• Activity (ActivityPointer) table
• Activity table (Microsoft Dataverse)
• Add a Dataverse action or function to a code app
• Add Power Automate flows to a code app
• Analyze plug-in performance (Microsoft Dataverse)
• Apply business logic using code (Microsoft Dataverse)
• Asynchronous client operations
• Client-Side Scripting Best Practices for Model-Driven Apps
• Code Components
• Code components application lifecycle management
• Code components for canvas apps
• Code Components for Model-Driven Apps
• Code Components: Best Practices and Guidance
• Compose HTTP Requests and Handle Errors
• Configure Form Query String Parameters in Model-Driven Apps
• Create a Custom API in Power Apps (Microsoft Dataverse)
• Create a custom API with solution files
• Create a Developer Environment with the Power Apps Developer Plan
• Create a Model-Driven App Field Component
• Create and Update Choices (Option Sets) Using the Web API
• Create and update column definitions using the Web API
• Create and Update Table Definitions Using the Web API
• Create and use custom APIs (Microsoft Dataverse)
• Create canvas app dataset component in Microsoft Dataverse
• Create Custom Messages in Microsoft Dataverse
• Create elastic tables using code
• Custom virtual table data providers (Microsoft Dataverse)
• Customize Model-Driven Apps Using Code
• Customize Table Definitions (Microsoft Dataverse)
• Customize the Editable Grid Control
• Customize Views in Model-driven Apps
• Debug Code Components During Development
• Debug plug-ins (Microsoft Dataverse)
• Debug Web Resources with Fiddler Auto Responder
• Define Ribbon Display Rules (Model-Driven Apps)
• Delete Data in Bulk to Reduce Storage Use
• Developer Tools for Model-Driven Apps
• Developers: Best practices and guidance for model-driven apps
• Developers: Best practices and guidance regarding plug-in and workflow development for Microsoft Dataverse
• Developers: Get started with Microsoft Dataverse
• Developers: Understand terminology in Microsoft Dataverse
• Discover user organizations (Microsoft Dataverse)
• Elastic Tables for Developers
• Email activity tables (Microsoft Dataverse)
• Execute multiple requests using the SDK for .NET (Microsoft Dataverse)
• Export, Edit, and Import the Ribbon in Model-Driven Apps
• Generate early-bound classes for the SDK for .NET
• Get Started with the Dataverse Web API Using C#
• Getting started
• Handle exceptions in a plug-in (Microsoft Dataverse)
• How to Sign in and manage accounts with the Power Apps CLI – Power Apps
• How to: Analyze data requests and responses
• How to: Application Lifecycle Management (ALM) for code apps
• How to: Connect to Copilot Studio
• How to: Connect your code app to Azure SQL
• How to: Connect Your Code App to Data
• How to: Connect Your Code App to Dataverse
• How to: Create a Connection from the Power Apps CLI
• How to: Embed a Code App in an Iframe
• How to: Get context data
• How to: SharePoint operations
• How to: Use Environment Variables in Code App Data Sources
• HTML Web Resources for Model-Driven App Extensions
• IFRAME Component with Bound Map Coordinates
• Impersonate another user (Microsoft Dataverse)
• Impersonate another user using the Microsoft Dataverse Web API
• Import Data (Microsoft Dataverse)
• Install and Configure Microsoft Power Platform CLI
• Install Power Platform CLI with .NET Tool
• Introduction to solutions
• JavaScript Web Resources for Model-Driven Apps
• Logging and tracing (Microsoft Dataverse)
• Long-term data retention
• Manage Microsoft Dataverse Customer Tables
• Manage Telemetry Settings for the Power Apps CLI
• Optimistic concurrency (Microsoft Dataverse)
• Override Default Open Behavior of Data Rows in Grids
• Package a Code Component in a Solution File
• Power Apps Code Apps Architecture for Development and Runtime
• Power Apps Code Apps: Features and Requirements
• Power Apps Component Framework Community Resources
• Query data
• Quickstart: Create a Code App Using the Power Apps CLI
• Quickstart: Execute a Dataverse SDK for .NET Request in C#
• Quickstart: Web API with client-side JavaScript and Visual Studio Code
• Reference Dataverse Schema Definitions by Name or MetadataId
• Register a WebHook
• Relationship management
• Request credentials to access D365 product database
• Ribbons in Model-Driven Apps: Definitions and Types
• Sample: Create a basic plug-in (Microsoft Dataverse)
• Send In-App Notifications Within Model-Driven Apps
• System configuration
• Troubleshoot Adding a Data Source
• Troubleshoot Power Apps CLI Issues with Zscaler
• Tutorial: Define a custom event in a component
• Tutorial: Update a plug-in (Microsoft Dataverse)
• Tutorial: Use dependent libraries in a component
• Update and delete table rows using the Web API (Microsoft Dataverse)
• Use Client API Grid Context in Model-Driven Apps
• Use IFRAME and Web Resource Controls in Model-Driven Apps
• Use metadata to customize tables and columns
• Use SQL to Query Data With the Dataverse Web API
• Use the SDK for .NET
• Use wildcard characters in conditions for string values
• User and team tables (Microsoft Dataverse)
• View developer resources page for your Power Apps and Microsoft Dataverse environment
• Web API Data Operations Samples
• Work with Dataverse Data Using Python SDK
• Work with Microsoft Entra ID group teams (Dataverse)
• Workflow to write, deploy, debug, and troubleshoot X++ code across multiple environments
• Write Telemetry to your Application Insights resource using ILogger (Microsoft Dataverse)

AI Builder

Updated

• End of AI Builder credits
• Overview of licensing

Power Platform connectors

Updated

• Add multiple authentications on a custom connector
• Create a custom connector from an OpenAPI definition
• Create a custom connector from scratch
• Create a custom connector with an OpenAPI extension
• Custom connectors overview
• Update your certified connector

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

• Customer Self‑Service Portal
• Employee Self‑Service Portal
• Community Portal
• Partner Portal

New sites using these templates could be provisioned on EDM since June this year. This utility is meant for supporting migration for existing SDM sites across to EDM.

What’s new

• General availability – The migration utility is now GA. It moves an existing site’s supported configuration and related records to EDM, then switches the site to serve from the migrated configuration.
• Dynamics 365 templates support – Sites created on the four Dynamics 365 portal templates can now be migrated to EDM. These templates are now supported for EDM, similar to Starter layout 1–5, Application processing, Blank page, Program registration, Schedule and manage meetings, and FAQ.
• Enhanced customization report – Before making any changes, the utility generates a report identifying all customizations that depend on SDM tables, giving you a clear view of what requires attention before migration.
• Status checks and rollback – The utility lets you check migration status before switching the active data model and revert the site to SDM if validation identifies a critical issue.

Why this matters

• Modern ALM – Site configuration becomes solution-aware and lives in Dataverse solutions, so you can ship a site alongside the apps, flows, and tables it depends on, and promote it with environment variables and Power Platform Pipelines.
• Faster provisioning – Sites on EDM provision significantly faster than SDM sites.
• Automatic platform updates – Enhancements, bug fixes, and security patches ship automatically. The manual package updates that SDM requires will not be needed for EDM.
• Future investment – New Power Pages features are built on EDM. Migration from SDM to EDM allows you to use these newer features in your sites.

How to get started

Prerequisites

• Microsoft Power Platform CLI version 2.11.2 or later.
• Dataverse base portal package CDSBasePortal 9.3.2607.x or later.
• Power Pages Core package PowerPages_Core 1.0.2605.x or later.
• Ensure your site’s template is supported and that the corresponding EDM Template is installed.
• Ensure you have the appropriate access to perform the migration, such as the System Administrator, Dynamics 365 Administrator, or Power Platform Administrator role.
• If your environment is in administration mode, ensure background operations are enabled.

Then follow the step-by-step guidance on Microsoft Learn to generate the customization report, run the migration, verify status, and switch your site to the Enhanced Data Model.

Learn more

• Migrate standard data model sites to enhanced data model – https://learn.microsoft.com/en-us/power-pages/admin/migrate-enhanced-data-model
• Enhanced Data Model overview – https://learn.microsoft.com/en-us/power-pages/admin/enhanced-data-model
• Install Microsoft Power Platform CLI – https://learn.microsoft.com/en-us/power-platform/developer/cli/introduction

We’d love to hear your feedback! Share your thoughts in the Power Pages community forum. If there are other site templates you would like us to support on the Enhanced Data Model, please let us know there.

The post Enhanced Data Model Migration Utility Now Generally Available, with Dynamics 365 Portal Templates Support appeared first on Microsoft Power Platform Blog.

Today we’re excited to announce a major milestone for makers: canvas apps coauthoring with agents is now generally available.

This capability unlocks the exponential speed of agentic development in the canvas apps you know and love, allowing you to build beautiful apps with access to your favorite data sources with over 1400 connectors and rich governance controls. Now generally available, you can bring agent-assisted authoring into production workflows with confidence – while retaining control over how, when, and where AI participates. Ask an agent to handle large, complex, or repetitive updates, then switch to direct editing when you want precision—or simply want to conserve your token budget.

Your app. Your workflow. Your control.

Canvas apps coauthoring with our agentic plugin lets people and agents contribute to the same app through a shared authoring model. You can ask an agent to create a screen, connect data, or update formulas, then step in to review and refine the result yourself. You can also begin with a manually authored app and bring in an agent later. What’s more – you choose what harness – this plugin works with your favorite coding agents.

This flexibility also gives you direct control over your token budget. Use tokens where an agent creates the most value, such as generating related screens or applying a pattern across an app. Make small changes—like adjusting a label, color, or property—directly. Move between the two approaches as often as the work and budget requires.

The result is still a traditional canvas app, so the direct-editing, connector ecosystem, governance, testing, security, accessibility, and deployment practices you already use continue to apply.

What agents can help you do

The canvas apps authoring plugin gives agents a dedicated toolset through an MCP server. Agents can:

– Create and modify canvas apps and screens

– Inspect available controls, connectors, and data sources

– Understand data-source schemas

– Add and configure controls

– Write and update Power Fx formulas

– Validate changes and synchronize them with a live coauthoring session

For example, you might ask an agent to create a responsive request-management screen, review generated controls and formulas, connect to an approved data source, and manually tune the layout. For a broader change, you could ask the agent to complete and validate a refactor, freeing you to do other work and review the results when convenient.

App source is represented in readable files, making agent contributions visible and reviewable. You can inspect what changed, make targeted edits, and retain oversight throughout the process.

Coauthoring—not autopilot

We designed this capability to give makers the most leverage, not remove them from app development. The agent is a collaborator that can take on well-defined work while *you* remain the author.

General availability means now you can make agentic collaboration part of your production development practices with all your current production canvas workloads, without having to start over. You decide what to delegate, what to edit yourself, and where to spend your tokens – all without giving up the control and governance of canvas apps.

The post Turbocharge your canvas development with the canvas authoring agent plugin – now generally available! appeared first on Microsoft Power Platform Blog.

• Customer Self‑Service Portal
• Partner Portal
• Employee Self‑Service Portal
• Community Portal

When you provision a new site using any of these templates, it’s automatically built on the Enhanced Data Model with Bootstrap 5. No additional configuration is needed.

What’s new

• Enhanced Data Model (EDM) for key D365 templates is now generally available. New sites created with any of the four supported templates are automatically provisioned on the EDM, giving you the same modern architecture that Power Pages starter templates already use.
• Bootstrap 5 out of the box – All four templates have been migrated from Bootstrap 3 to Bootstrap 5, delivering improved responsiveness, accessibility, and alignment with current Power Pages UI standards.
• Full Design Studio and Management App support – The Power Pages Design Studio and Power Pages Management app fully support the new EDM‑based templates, including all updated attributes, relationships, forms, and views. Your authoring and customization experience remains seamless.

Why this matters

• Faster provisioning – Sites on EDM provision significantly faster, reducing the time from template selection to a live development environment.
• Streamlined ALM – Website configurations are solution-aware and stored in Dataverse solutions, with support for Environment Variables and Power Pipelines for deployments – making it easier to transport customizations across environments using standard application lifecycle management processes.
• Faster platform updates – Enhancements and bug fixes are delivered more efficiently on the Enhanced Data Model. Customers are not required to actively manage Power Pages solutions to stay up to date, feature updates and security patches are automatically shipped to ensure ongoing security and compliance.
• Modern, accessible UI – Bootstrap 5 brings a responsive grid system, improved accessibility defaults, and a cleaner component library, helping you deliver a polished experience to customers, employees, and partners without additional front‑end work.

With these four templates now on EDM, Dynamics 365 portals benefit from the same platform‑level investments and future enhancements as all other Power Pages sites.

Important: This update applies to newly provisioned sites only. Existing sites on the standard data model continue to operate without impact. Migration tooling for these four Dynamics 365 templates is not yet available but is coming soon.

How to get started

Prerequisites

• Sign in to the Power Platform admin center.
• Go to Manage > Environments > Select your Environment > Resources > Power Pages sites and ensure the Switch to enhanced data model toggle is turned on for your environment.
• Verify your environment has Power Pages Core Package v1.1.2602.230 or later. For upgrade steps, see Update the Power Pages solution.

Create a new site

1. Open the Power Pages home page.
2. Select Create a site.
3. Choose one of the four supported Dynamics 365 templates and select ‘Choose this template’.
4. Fill in the required details and select ‘Done’.
5. Your new site is provisioned on EDM with Bootstrap 5 automatically.

Learn more

• Enhanced Data Model overview – https://learn.microsoft.com/en-us/power-pages/admin/enhanced-data-model
• Power Pages Management app – https://learn.microsoft.com/en-us/power-pages/configure/portal-management-app

We’d love to hear your feedback! Share your thoughts on the Power Pages community forum.

The post Enhanced Data Model and Bootstrap 5 Now Available for Dynamics 365 Portal Templates appeared first on Microsoft Power Platform Blog.

First introduced in preview, Server logic was designed to simplify how makers and developers implement server-side operations. With GA, Server logic is now ready for enterprise production workloads, backed by strengthened governance, improved extensibility, and the reliability customers expect from Power Platform.

Alongside GA, we’re also announcing two important enhancements that further reinforce enterprise readiness:

• Governance control to disable external calls
• Support for unbound Dataverse custom actions

Governance control to disable external calls

Security and compliance are critical considerations for enterprise applications. Many organizations require strict control over outbound connectivity to ensure adherence to internal policies and regulatory requirements.

With GA, administrators can now disable external calls from Server logic layer.

Support for unbound Dataverse custom actions

Extensibility is key to building scalable and reusable solutions. With GA, Server logic now supports unbound Dataverse custom actions, enabling deeper integration with your existing business logic layer.

Get started

Server logic is now available for production use in Power Pages. Whether you’re enhancing an existing site or building a new application, you can take advantage of its capabilities to deliver more intelligent, secure, and governed experiences.

• Server logic overview
• Server objects
• Tutorials
• Disable external service calls from server logic

The post Announcing General Availability (GA) of Server Logic in Power Pages 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.