We’re making this change because of how our customers actually work. Few organizations run a single Microsoft product in isolation. Dynamics 365, Power Platform, Microsoft 365, Microsoft 365 Copilot, and custom agents built in Microsoft Copilot Studio increasingly operate together to power business processes, employee productivity, and AI transformation. Bringing this content together means you can see what is coming across all of these products in one view, filter it to your own environment, and plan across products.

Moving from release waves to always-on disclosure
Alongside this move, we’re also changing when roadmap information appears. We’re retiring the twice-yearly release wave 1 and release wave 2 model in favor of continuous publishing. We’ll publish new capabilities as soon as plans are committed and ready to share, rather than holding them until the next scheduled wave.

Once published, each roadmap item remains current as it progresses through In Development, Rolling Out, and Launched, with status and rollout information updated as plans evolve. In practice this means most capabilities will appear on the roadmap sooner than they would have under the wave calendar, and you follow them all the way through delivery rather than losing sight of them after publication.

Working with AI at Work roadmap data
We have designed the AI at Work roadmap to support planning, not just browsing. You can:

Filter roadmap views to the products that matter most to your organization.
Export complete or filtered roadmap views to a CSV file.
Subscribe to updates through RSS.
Share roadmap links directly with stakeholders.
Search and organize roadmap content using feature IDs and advanced filters.
Download the AI at Work roadmap guide to learn how to read and use the roadmap.

For teams that would rather query the roadmap than browse it, the Release Communications MCP Server pulls roadmap information directly into your own AI tools and workflows. Organizations can use it to generate customized roadmap views and planning materials, or to integrate roadmap data into existing tooling and business processes.

What’s not changing
This transition changes how Microsoft communicates upcoming innovation. It doesn’t change how our products are built, released, or deployed.

Products with established release schedules will continue to follow those schedules.
Message Center remains the source for tenant-relevant change notifications.
Microsoft Learn remains the home for product documentation and implementation guidance.

Transition milestones at a glance
When What happens
September 2026 New Dynamics 365, Power Platform, and Dataverse capabilities begin publishing to the AI at Work roadmap.
September 2026 to November 2026 Existing roadmap content with public preview or general availability (GA) date of June 1, 2026 or later will transition to the AI at Work roadmap experience. Ongoing updates and transition notifications will be communicated through Message Center.
By November 15, 2026 The transition completes and Release Planner retires. The AI at Work roadmap becomes the primary destination for public roadmap information.

How to prepare for the transition
The transition will take place over the coming months, and there are a few simple steps you can take now.

Explore the AI at Work roadmap. Spend a few minutes reviewing the AI at Work roadmap and setting filters for the products and cloud environments your organization uses.

Subscribe to updates. See the AI at Work roadmap guide to learn how to use RSS to follow filtered roadmap views and continue using Message Center for changes specific to your tenant.

Update planning references. If your teams rely on release plan links, bookmarks, or internal roadmap documentation, begin updating those references to point to the AI at Work roadmap. Transition guidance will be available throughout the migration period.

Set your own review rhythm. Release wave 1 and release wave 2 gave organizations a fixed moment twice a year to gather stakeholders and plan the period ahead. We recommend establishing a recurring review, monthly or quarterly, depending on how quickly your organization adopts new capabilities, built on a saved filter and an RSS subscription.

AI at Work roadmap transition FAQ
Q. Will there be a September 2026 release wave 2 announcement or release wave 2 release plan?
A. No. New capabilities will be disclosed on the AI at Work roadmap as they become committed, rather than grouped into a twice-yearly release wave announcement.

Q. Will all existing Dynamics 365 and Power Platform roadmap content move to the AI at Work roadmap?
A. Roadmap content with a public preview or general availability date of June 1, 2026 or later will transition to the AI at Work roadmap. Earlier content remains available in existing release plans on Microsoft Learn for historical reference.

Q. What happens to release plans on Microsoft Learn?
A. Beginning in September 2026, new release plans will no longer be published to Release Plans on Learn. Existing release plans will remain available for historical reference, and Microsoft Learn will continue to serve as Microsoft’s documentation platform.

Q. Can I still export roadmap information?
A. Yes. See the AI at Work roadmap guide to learn how to export complete or filtered roadmap views to CSV. Organizations can also use the Release Communications MCP Server to integrate roadmap data into your own AI tools and workflows.

Q. Will my saved views in My Release Plans carry over?
A. Personalized saved views will no longer be available after Release Planner retirement. Personalized saved views are not available on the AI at Work roadmap.

Q. How will I see what has changed since I last looked?
A. The roadmap highlights new and updated capabilities, and both RSS and Message Center can notify you as changes occur.

The post One always-on roadmap: Dynamics 365, Power Platform, and Dataverse join the AI at Work roadmap appeared first on Microsoft Power Platform Blog.

The Power Platform Community has always been defined by people who share what they know, help one another succeed, and turn creative ideas into meaningful solutions. From October 27-29, 2026 at the MGM Grand in Las Vegas, solution makers from all around the world will come together to learn, connect, and build what’s next with Microsoft 365 Copilot, agents, apps, automation, and data.  

More than 200 sessions. Dozens of hands-on workshops. Three days of keynotes. Onsite AI and agent certifications. And one global community building what’s next with AI. 

Whether you’re exploring AI in your business, building with low code, developing professional solutions, or leading enterprise-wide transformation, PPCC is your best opportunity to gain practical skills, meet the people shaping the platform, and return to work on Monday ready to make an impact.  

Learn. Build. Make it real.

Technology is moving quickly, but PPCC is about more than keeping up—it’s about getting ahead.  

Hear directly from Microsoft leaders, product teams, engineers, and community experts about the future of Copilot, Copilot Studio, Power Apps, Power Automate, Power BI, Power Pages, and Dataverse. 

At PPCC, you’ll learn how agents, apps, workflows, automation, and trusted data systems can work together as complete, governed business solutions. Learn how other organizations are moving from promising AI experiments to secure, production-ready solutions, and discover practical approaches you can apply immediately. 

At PPCC, every person  can find a path forward: 

• Discover new product capabilities directly from the teams creating them, and see them live for the first time. 
• Learn how to design, build, secure, govern, and scale AI-powered solutions. 
• Connect with people solving similar challenges across roles, industries, and skill levels. 

We’ll do more than show what is possible. This is where product meets hands-on learning, and where your next big idea can become something real. 

Go deeper with the people building the platform

The conference will open with Charles Lamanna, Executive Vice President at Microsoft, sharing a forward-looking view of Copilot, agents, the platform, and how these technologies are changing what every organization can build.  

Attendees will also hear from Microsoft product leaders, including Ryan Cunningham, Corporate Vice President of Copilot Studio & Power Platform, along with Microsoft engineers, product managers, enterprise practitioners, MVPs, and community experts. 

Across keynotes, product talks, innovation sessions, breakouts, and roundtables, speakers will share what they are building, what they are learning, and what your organization needs to know to turn innovation into business value.  

Come ready to ask questions, challenge your thinking, and learn directly from the people helping define the future of AI-powered solution development.

From promising ideas to production-ready AI solutions

The PPCC 2026 session catalog reflects how dramatically solution building is evolving.  

Attendees can explore Copilot-first app design, multi-agent systems, agent evaluation and governance, intelligent automation, enterprise architecture, adoption, and more. 

The common thread is moving from isolated experiments to complete solutions. PPCC will show how Copilot and agents can work with apps, workflows, automation, and trusted data to help organizations modernize processes, extend what teams can build, and operate AI responsibly at scale. 

The opportunity isn’t simply to add AI to an existing process. It’s to reimagine what the process, and the people responsible for it, can accomplish. 

Turn inspiration into hands-on experience

Great ideas become far more valuable when you know how to put them into practice. 

Full-day workshops on October 25, October 26, and October 30 create space to go deeper with guided, hands-on learning. Attendees can add one, two, or three workshops to their conference passes to build an experience around their goals.

PPCC will also offer onsite AI and agent certification opportunities designed to help attendees validate their skills and continue advancing their careers. 

Whether you’re creating your first solution or establishing architecture and governance for an enterprise program, you can leave Las Vegas with the knowledge, practical experience, and greater confidence in what you can build next.

Keep building with the community 

The PPCC maker community is incredibly unique and special, turning the conference into more than a set of sessions. It’s a place to meet people facing similar challenges, learn directly from practitioners, and find ideas you can carry back into your own work. 

At PPCC, those connections happen everywhere. Explore solutions and meet experts in the Expo Hall. Discover what fellow makers are creating in the Makers Market. Find experts and community leaders in the Community Lounge. Continue the conversation through meetups, networking activities, and the Night Market. 

These aren’t simply breaks between sessions. They are opportunities to find collaborators, learn from someone who solved the challenge you’re facing, and build relationships that continue long after the conference ends. 

And on Wednesday, October 28, 2026 we’re turning up the energy with an exclusive attendee celebration featuring a live performance by Pitbull. 

Don’t just watch the next era of AI-powered solution building take shape. Come help us shape it.

Plan your PPCC week

• October 25–26, 2026: Pre-conference full-day workshops. 

• October 27–29, 2026: Keynotes, sessions, roundtables, product talks, certifications, Expo Hall, Makers Market, Community Lounge, and community events. 

• October 30, 2026: Post-conference full-day workshops. 

Join us in Las Vegas

Standard registration pricing is available through August 18, 2026 and teams can save up to 20% with group discounts. Choose a conference pass or add workshops to create the experience that best fits your goals. 

Explore the agenda, meet the speakers, and register for PPCC 2026.

Planning your stay? Book your hotel at the MGM Grand. 

We can’t wait to learn, connect, and build what’s next with you at #PPCC26 in Las Vegas!

The post Register now for PPCC 2026: Come for the learning, stay for the community appeared first on Microsoft Power Platform Blog.

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

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

Bring Your Logic to Liquid

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

Get started

To learn more and start building:

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

We are looking forward to your feedback

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

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

AI changes how business data is used

Consider a manufacturer using AI in procurement, finance, and supply chain operations. A procurement leader wants agents to reconcile invoices, flag supplier exceptions, and update case records without adding manual review to every transaction. A platform administrator must support growth in transaction volume and data while keeping storage within entitlement, limiting each agent to the records and actions it needs, and preserving evidence of material changes.

The administrator needs to answer practical questions each week. Which environments and tables are growing? Which records still support an active process? Which records must be retained for audit or regulatory review? Which users and agents can read or update them? Can the team recover a deleted record and explain who changed it?

AI increases the frequency of these decisions because automated processes can read and change business data continuously. The governance job is to keep the data useful for the business process while managing capacity, access, retention, recovery, and evidence.

AI raises the cost of poor data hygiene. Old, inactive, inaccurate, or incomplete records may once have sat unused and created only storage cost. When agents can retrieve that data, use it to answer questions, and take action, its quality can affect the result. Administrators need to govern how much data is retained and whether it is accurate, relevant, and appropriate for agentic use.

Data growth requires clear ownership and policy

Across industries, data administrators share a common set of operating needs:

• Data ownership. Connect each data set to an owner and a defined business purpose.
• Access model. Define which users and agents should be able to view or change the data.
• Lifecycle model. Decide whether data should remain active, move to long-term retention, or be deleted on a schedule.
• Review schedule. Revisit the policy regularly to confirm the data, access model, and lifecycle treatment still support the business process.

These needs take different forms across industries.

Healthcare: A records administrator must keep clinical records available for care, legal holds, and required retention periods while identifying older, inactive records that no longer need to remain in active storage. The job is to reduce active storage use without weakening access controls or record availability.

Retail: A commerce platform owner must absorb seasonal growth in orders, service cases, files, logs, and agent interactions. The job is to identify which data still supports returns, service, fraud review, or analytics, then apply retention and deletion policies by record type rather than carrying every seasonal peak forward.

Financial services: A security or compliance lead must approve how an agent accesses customer and transaction records. The job is to grant the minimum required privileges, record consequential changes, and produce evidence for internal review or audit.

Manufacturing: A platform administrator must manage the records generated by procurement and supply chain agents. The job is to trace capacity growth to specific environments and tables, assign a business owner, retain records required for supplier or financial review, and recover records deleted by a person or automated process.

Dataverse capabilities for data governance

Dataverse provides governance controls that prepare business data for agentic access, including storage management, access controls, audit history, lifecycle management for inactive and deleted data, and environment governance.

The following actions provide a practical starting point for organizations expanding AI use across business applications.

• See what is driving storage. In the Power Platform admin center, review tenant and environment usage across database, file, and log capacity, then drill into the environments and tables consuming the most storage. Review Dataverse capacity reporting.
• Retain inactive data without keeping it active. Create Dataverse long-term retention policies for eligible table records that must remain available for audit, legal, regulatory, or limited inquiry purposes. Retained data stays secured by Dataverse and becomes read-only. Understand long-term retention and set a retention policy.
• Create a recovery window before deleting data. Administrators can enable deleted-record keeping for 1 to 30 days and restore supported records deleted manually, automatically, singly, or in bulk. Use this as a safety net for lifecycle actions: establish that data is inactive or safe to delete, validate scope and dependencies, and configure recovery before acting. Configure and use deleted-record recovery.
• Constrain who can see and change business data. Dataverse security roles define access to apps, tables, records, and data operations; roles can be scoped through access levels, teams, and business units. Review security roles and privileges.
• Preserve evidence of consequential changes. Dataverse auditing can record the creation of records, updates, deletes, sharing changes, security-role changes, and user access when configured. Audit data consumes log capacity, so audit scope and retention should be deliberate. Configure Dataverse auditing.
• Apply supported governance rules across environments. Power Platform environment groups let administrators apply available managed governance rules across selected managed environments, including documented security, sharing, AI, backup-retention, and application-lifecycle settings. Not every Dataverse data-governance control is available as an environment-group rule, so verify the current rule catalog before defining centralized policy. Explore managed governance.

Administrators must configure these controls and align them with business, legal, security, and records-management requirements. Audit scope affects log capacity. Retention and deletion policies require clear record ownership. Security roles require periodic review as applications and automated processes change.

Establish clear accountability for data governance

Use a shared operating model: platform administrators should define and enforce the governance process, while business owners classify data and select the correct policy. Platform administrators should define policy by record type and intended use, configure available controls, review the organization’s posture on a regular schedule, and address exceptions or unusual growth.

Business owners should identify the purpose, sensitivity, operational value, and retention requirements of records. Security, compliance, legal, and records-management teams should define additional access, evidence, and retention requirements. This operating model combines human decisions with product configuration. Dataverse can enforce configured access, auditing, retention, recovery, and environment settings; the organization remains responsible for classifying data, selecting the correct policy, reviewing exceptions, and confirming that controls meet business and regulatory needs.

Use Dataverse as the governed business data layer

Dataverse applies storage reporting, lifecycle controls, role-based security, auditing, and recovery to the business records used by applications and automated processes. This provides a consistent control model for data stored in Dataverse. Administrators use the Power Platform admin center to manage environments, capacity, security settings, auditing, and deleted-record recovery. Makers configure table-level retention policies in Power Apps. Organizations remain responsible for policy decisions, ownership, testing, and ongoing review.

Recommended next steps

Open Dataverse capacity reporting and identify the environments and tables using the most database, file, and log storage. Assign a business owner to each material source of growth and classify the data as active, inactive but required, or eligible for deletion.

Test one control in a nonproduction environment. Options include a long-term retention policy, a revised security role, a scoped audit configuration, or a 1-to-30-day deleted-record recovery window. Document the owner, policy basis, expected capacity or risk outcome, test result, and recovery procedure.

Prepare the data foundation for AI

AI increases the number of automated processes that use business data and the frequency with which that data changes. Capacity management, retention, access control, auditing, and recovery should therefore be reviewed as part of every production AI deployment that uses Dataverse.

Organizations can begin with the controls already available in Dataverse. A documented operating process, clear ownership, and regular review provide the foundation for broader AI adoption.

Learn more: Review capacity reporting, long-term retention, security roles, auditing, deleted-record recovery, and managed governance.

The post Your Company Is Racing to Deploy AI. Is Your Data Ready? 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:

Building modern apps

Generally available: the data grid modern control — a fluent UI grid with search, sorting, selection, and rich column types

The data grid modern control is now generally available for canvas apps. Built on fluent UI, data grid gives makers a high-performance, data-dense view of tabular data with a built-in search experience. Columns are generated automatically when you connect a data source, and each column can be unlocked for per-column customization with Power Fx formulas. GA rounds out the core interaction model: sortable columns, single and multi-row selection (with an optional selection column), column resizing, and a rich set of column types — text, number, phone, email, hyperlink, and button columns — plus formula-driven cell content for lookups, images, and complex fields. The control ships with built-in accessibility (keyboard navigation and screen-reader support) and fluent theming that stays consistent with the rest of your app, and it now works across a broader range of data sources than the preview. A wave of reliability and authoring fixes (selection stability, sorting, column ordering, and data-grid-in-gallery/component scenarios) landed as part of the GA push.

Data grid is the fluent-based successor to the classic table/data table experience, and a table → data grid update path helps makers move existing apps forward rather than rebuilding. It’s a distinct new control, not a forced replacement.

Modern toggle and checkbox get improvements with consistent properties, tooltips, and true read-only view mode

The modern toggle and checkbox controls have been improved as part of modern controls. Both now follow the same cross-control naming conventions as the rest of the modern set — FontColor → Color, FontSize → Size, and the FontItalic/Underline/Strikethrough renames — and FontWeight now uses typed enum values (FontWeight.Bold, etc.) for IntelliSense and compile-time validation. Toggle’s LabelPosition is also now a typed enum (LabelPosition.Before / LabelPosition.After). Both controls gain a new tooltip property, and DisplayMode.View now renders a genuinely read-only state that shows the value without allowing interaction — consistent with the other updated modern controls. They also expose far more output properties than the previous versions, so you can reference their state in formulas across your app. Checkbox behavior inside galleries (Checked/OnCheck reliability) is improved.

If your app uses a previous version, you’ll see an update notification on the control in Power Apps studio; the migration guide lists each property rename so you can update formula references.

The modern form control gets modern data cards plus binding, formula, and reset fixes for more reliable form building

The modern form experience received a round of functional improvements. Improved data cards are now enabled, so forms built on modern controls render their fields through the updated data-card infrastructure. Alongside that, we fixed data-card binding and formula behavior, so field values, defaults, and Power Fx inside cards evaluate correctly. This makes modern forms behave predictably for real data-entry scenarios.

We also corrected ResetForm and date picker reset behavior: resetting a form now reliably clears and restores field values, including date fields, which is core to edit/new-record form lifecycles. Together these changes make the modern form a dependable foundation for form-driven canvas apps, working end to end with the other updated modern controls.

New fluent 2 app templates give makers a polished, modern-controls starting point for canvas apps

Makers now have new fluent 2-based templates that provide a ready-to-use, professionally designed starting point for canvas apps — built on modern controls and fluent patterns instead of a blank screen. New screen templates include a hub landing page, a feature landing page, and a list page, and the existing modern gallery templates were refreshed to use modern controls throughout.

Because the templates are assembled from the modern control set, apps you start from them inherit consistent fluent theming, built-in accessibility, and the ongoing quality investment in modern controls — so makers get a good-looking, maintainable app faster.

New and improved modern controls: a rating control, richer text styling for card, and an expanded 180-icon library

The modern controls catalog also grew and got richer. A brand-new rating modern control (built on fluent UI v9) lets users give star-based ratings with half-star precision, custom icons (not just stars), and full color customization defaulting to your app’s brand color. It’s a new control — classic rating keeps working unchanged.

The card control gained text-customization properties — fill, plus TitleColor / SubtitleColor / DescriptionColor and TitleSize / SubtitleSize / DescriptionSize.

The modern icon control’s library was expanded from ~56 to ~180 icons, reaching parity with the classic icon set. Classic icon.* values are automatically mapped to their fluent equivalents, so existing usage lights up with the broader set.

Deprecating older fluent UI (hero) controls in custom pages and Teams apps and their upgrade path to the modern controls

Makers who built with the earlier fluent UI (“hero”) controls in custom pages and Teams apps now have a documented upgrade path to the modern controls. The guidance explains how the upgrade works, which properties carry over, and where behavior differs, so you can move to the actively-invested modern control set with confidence. Because some hero properties don’t have a one-to-one equivalent on the modern controls (for example certain color/theming settings), the guidance is explicit about what transfers and what to check after upgrading — reducing surprises and protecting maker trust during migration.

Modern controls are the forward path for canvas and custom-page authoring, while classic controls remain supported for organizations with their own design systems.

Power Automate

Share process license capacity across multiple flows with flow groups

Flow groups are now available in Power Automate. They let you share the capacity of one process license, or 250,000 actions per day, across up to 25 solution-aware cloud flows, helping you make better use of capacity across flows with moderate, predictable usage.

Go to more > flow groups to create a group, add flows, and monitor shared capacity. A flow group uses one process license. When a flow needs more capacity, you can assign process licenses directly to that flow for dedicated capacity.

Share process license capacity with flow groups

Build and manage cloud flows from your AI coding agent with the Power Automate plugin

The Power Automate plugin is now available in the Power Platform skills marketplace for GitHub Copilot CLI and Claude Code. It brings common Power Automate tasks into your terminal, so you can create, edit, run, and debug cloud flows through a natural language conversation.

Ask the plugin to build a flow from a description, update an existing flow, investigate a failed run, or help select a working environment and manage connections. Review and test generated definitions and changes before you enable or publish a flow.

Power Pages

Public preview: secure your Power Pages sites with the new security agent

Security agent (preview) is a new AI-powered assistant built into the Power Pages security workspace that helps makers review, configure, and strengthen site security using natural language. Whether you’re reviewing your site’s security posture, configuring authentication and authorization, managing application security settings, or troubleshooting sign-in issues, security agent provides site-specific guidance based on your current configuration. The agent explains findings in plain language, recommends remediation steps, and always requests your approval before making configuration changes, helping you secure your sites faster while staying in control.

Learning updates

Training paths and labs

New

• Audit and retain Dataverse data in Power Platform
• Configure the Dataverse security model in Power Platform
• Deliver solutions with pipelines in Power Platform
• Describe the business value of Microsoft Power Platform
• Drive adoption and transform culture in Power Platform
• Ensure availability and resilience in Power Platform
• Explore the fundamentals of Microsoft Power Platform
• Extend ALM with Git and CI/CD in Power Platform
• Govern AI-enabled resources in Power Platform
• Govern data policies in Power Platform
• Manage environments in Power Platform
• Manage operations and monitoring in Power Platform
• Secure tenants and environments in Power Platform

Updated

• Core components of Power Pages
• Create tables in Dataverse
• Customize a canvas app in Power Apps
• Describe Microsoft Dataverse
• Describe Power Platform governance and administration
• Describe the business value of Microsoft Power Platform
• Explore Power Pages design studio
• Get started with model-driven apps in Power Apps
• Get started with Power Apps canvas apps
• Get started with Power Automate
• Identify basic Microsoft Power Apps capabilities
• Identify Microsoft Power Automate components
• Publish, share, and maintain a canvas app
• Solution Architect: Design Microsoft Power Platform solutions
• Integrate with Dataverse and Azure

Power Apps maker

New

• Configure structured content in the rich text editor (preview)
• Customize Microsoft 365 Copilot in Power Apps (preview)
• Dataverse semantic model frequently asked questions (preview)
• Fine-tune semantic model signals (preview)
• Form modern control in canvas apps – Power Apps
• Manage semantic model glossary entries (preview)
• Overview of Dataverse semantic model (preview)
• Rating modern control in canvas apps – Power Apps
• Regenerate semantic model (preview)
• Upgrade Fluent UI Controls to Modern Controls

Updated

• Add Microsoft 365 Copilot chat for app users in canvas apps (preview)
• Add Microsoft 365 Copilot for app users in model-driven apps
• Business skills overview
• Card modern control in Power Apps
• Choose finance and operations data in Azure Synapse Link for Dataverse
• Column data types in Microsoft Dataverse
• Configure a lookup component on a form
• Configure the Dataverse model context protocol (MCP) server
• Configure your environment and link to Microsoft Fabric
• Connect to Dataverse with model context protocol (MCP)
• Connect to Dataverse with model context protocol FAQ
• Connect to Dataverse with model context protocol in Microsoft Copilot Studio
• Connect to Dataverse with model context protocol in non-Microsoft clients
• Create a business rule in Microsoft Dataverse
• Create a canvas app with data from a list
• Create an Azure Synapse Link for Dataverse with Azure Data Lake in Power Apps
• Create an Azure Synapse Link for Dataverse with your Azure Synapse Workspace
• Create and edit generative pages with AI code generation tools
• Create and use business skills
• Create Apps, Data, and Plans With Power Apps Vibe
• Create custom help pages for model-driven apps
• Customize and build your mobile app using the wrap wizard
• Customize Microsoft 365 Copilot in Power Apps
• Data Grid modern control in canvas apps – Power Apps
• Design a custom page for your model-driven app
• Edit form and Display form controls in Power Apps
• Enable preview tools and features in Dataverse MCP server
• Export Microsoft Dataverse data in Delta Lake format
• 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
• Icon modern control in canvas apps – Power Apps
• Link your Dataverse environment to Microsoft Fabric and unlock deep insights
• List of controls available for model-driven apps
• Modern controls and properties in canvas apps
• Power Apps grid control in Power Apps
• Prompt columns in Microsoft Dataverse
• Query and analyze the incremental updates with Azure Synapse Link for Dataverse
• Recent modern control updates in canvas apps – Power Apps
• Release channel for your model-driven app
• Table control in Power Apps
• Transport Azure Synapse Link for Dataverse configuration
• Understand canvas-app forms
• Use environment variables in Power Platform solutions
• Use managed identities for Azure with your Azure data lake storage
• Use modern themes in Power Apps
• Use the Fluent UI controls in Power Apps app in Microsoft Teams
• What is Dataverse intelligence?
• Configure a row summary for a model-driven app
• Types of tables

Power Apps user and mobile

New

• Configure sensitivity labels for emails
• Use sensitivity labels in emails

Updated

• Assign a row to someone else
• Install the Power Apps mobile app
• Mobile offline limitations for canvas apps
• Modern, refreshed look for model-driven apps
• Use Microsoft 365 Copilot in canvas apps (preview)
• Use Microsoft 365 Copilot in model-driven apps

Power Automate

New

• AI-assisted UI automation repair (preview)
• Create a process from normalized schema (preview)
• Create and manage a flow group
• Normalized schema JSON authoring
• PGP cryptography reference for Power Automate for desktop
• Share Process license capacity with flow groups
• Trigger actions reference

Updated

• Actions reference
• Change the owner of a cloud flow in Power Automate
• Cloud flow error code reference – Power Automate
• Create an Object‑centric event log
• Create flows from your phone in the Power Automate mobile app
• Create widgets for instant flows
• Customize layouts in the process intelligence experience
• Data loss prevention (DLP) policies
• Explore the cloud flows designer
• Filter by attribute values in the process intelligence experience
• Filter by edge in the process intelligence experience
• Filter by timeframe in the process intelligence experience
• Filter by variant in the process intelligence experience
• Filtering overview in the process intelligence experience
• Flow Checker
• Governance in Power Automate for desktop
• Ingest an object-centric event log
• Limits of automated, scheduled, and instant flows
• Manage approvals in the Power Automate mobile app
• Manage cloud flows in the Power Automate mobile app
• Manage tabs in the process intelligence experience
• Manage variables and the variables pane
• Monitor your flows
• OCPM process overview
• Operator role for Power Automate
• Overview of cloud flows
• Overview of object‑centric process mining
• Power Automate mobile app overview
• Process capacity
• Process intelligence experience overview
• Receive notifications in the Power Automate mobile app
• Run a desktop flow in picture-in picture
• SAP GUI automation actions reference for Power Automate for desktop
• Self-healing (preview)
• Submit a cloud flow template to the Power Automate gallery
• Support for service principal owned flows
• Tags in desktop flows
• Understand flow failure notifications in Power Automate
• Use donut charts in the process intelligence experience
• Use filters in OCPM analysis
• Use horizontal bar charts in the process intelligence experience
• Use KPI (key performance indicator) cards in the process intelligence experience
• Use line charts in the process intelligence experience
• Use process maps in the process intelligence experience
• Use statistical grids in the process intelligence experience
• Use variant DNA in the process intelligence experience
• Use vertical bar charts in the process intelligence experience
• Visualization cards overview in the process intelligence experience
• Visualize processes
• Work with desktop flows using code
• Secure data used in cloud flows

Power Pages

New

• Column security profile (preview)
• Enable enhanced authorization (preview)

Updated

• Add a custom domain name
• Add a search component
• Add AI features in a list (preview)
• Add AI-generated code using Copilot (preview)
• Add an agent available in Microsoft Copilot Studio
• Add an agent from the setup workspace
• Add an AI-generated form using Copilot
• Advanced Settings
• Build an agent from a form
• Configure a site with Content Delivery Network
• Configure managed rules in Power Pages WAF
• Configure Microsoft Entra ID Authentication for Power Pages Agent
• Configure Omnichannel with Power Pages site agent
• Configure Web Application Firewall custom rules
• Connect to Power Pages MCP server
• Copilot hub for Power Pages
• Create an AI-generated web page using Copilot
• Create and deploy a single-page application in Power Pages
• Customize your agent
• Enhanced data model
• Get started with the Power Pages plugin for GitHub Copilot CLI and Claude Code
• Implement privacy protections
• Known issues for Power Pages
• Migrate Power Pages website configuration
• Overview of developer capabilities
• Overview of the Power Pages portals Web API
• Overview of the Security workspace
• Power Pages connectivity to a Microsoft Dataverse
• Power Pages security
• Security agent (preview)
• Set column permissions
• Set table permissions in Power Pages
• Set up DocuSign integration
• Set up telemetry monitoring
• Sign up for a free trial
• Tutorial on how to use Power Platform CLI with Power Pages
• Use Power Platform pipelines with Power Pages
• Web Application Firewall overview

AI Builder

Updated

• AI Builder in SharePoint with document processing overview – AI Builder
• Licensing and Copilot Credits

Power Platform connectors

Updated

• Get your connector certified – Overview
• Verified publisher certification process

Power Platform administration

New

• Automate bill copy requests with Power Platform
• Configure authentication for agents (preview)
• Configure channel publishing and connected agent access (preview)
• Copilot Agent Kit real-world examples
• Environment group rules gallery
• Grupo Bimbo standardizes global audit processes with Copilot Studio
• Integrate Dataverse with enterprise data in Microsoft Fabric using a medallion architecture
• Integrate Outlook and SAP with Power Apps
• Manage advanced connector policies programmatically
• Manage healthcare stakeholder engagement with Power Platform
• Power Platform inventory sample queries
• Set up Power Platform managed identity version 1 for Dataverse plug-ins
• Configure sensitivity labels for emails

Updated

• Access audit data with Azure Synapse Link and Power BI
• Actions Overview
• Admin deployment page
• Admin user management unification for Finance and Operations in Power Platform admin center (preview)
• Administer the catalog
• Administration mode
• Advanced connector policies
• Allow external language models for generative responses
• App object in Power Apps
• Auto-claim policies for Power Apps licenses
• Auto-claim policies for Power Automate licenses
• Automate service order lifecycle and SLA governance with Power Platform
• Automatic deletion of Power Platform environments
• Automation of tasks with PowerShell
• Back up and restore environments
• Block unmanaged customizations in Dataverse environments
• Business continuity and disaster recovery
• Compliance
• Configure Dataverse search for your environment
• Configure pipelines using a custom host
• Connector endpoint filtering (preview)
• Continuously optimize performance recommendation for Power Platform workloads
• Control user access to environments with security groups and licenses
• Control which apps are allowed in your environment
• Conversation diagnostics in Azure Application Insights
• Copilot Studio reference architectures and solution ideas
• Create alerts for your resources
• Create and manage masking rules
• Create pipelines using the platform host
• Create users
• Daimler Truck transforms policy management with Power Apps, Dataverse, and managed environments
• Data policies for managed environments
• Data protection and privacy
• Dataverse capacity-based storage details
• Dataverse capacity-based storage overview
• Dataverse Git integration setup
• Deep dive on specific licenses
• Default OrgDBOrgSettings for server-side synchronization
• Define roles and responsibilities
• Design a reliability testing strategy recommendation for Power Platform workloads
• Deutsche Bahn empowers citizen developers with Power Platform
• Develop a tenant environment strategy to adopt Power Platform at scale
• Dynamics 365 service description
• Enable cross-geo solution deployments in Power Platform
• Enable maker welcome content
• Enable managed environments
• Ensure data retention and mobility
• Environment groups
• Environment management capabilities
• Environment routing
• Establish a security baseline recommendation for Power Platform workloads
• Establish effective application lifecycle management practices
• Explore Power Platform and SAP integration
• Export data to Application Insights
• FAQs about source code integration
• Filter, Search, and LookUp functions
• Geo-to-geo migrations
• Hierarchy security
• How managed solutions are merged in Power Platform
• Identity and access management
• Implement a scalable notification system with Power Platform
• Implement reactive governance controls
• Important changes (deprecations) coming in Power Platform
• Integrate Power Platform with SAP for data management
• Integrating SAP with Power Platform FAQs
• IP firewall in Power Platform environments
• Issues and FAQs about pay-as-you-go plans
• Licensing
• Limit sharing
• Manage and govern the default Power Platform environment
• Manage Power Apps
• Manage Power Platform adoption at scale
• Manage your customer-managed encryption key
• Managed availability
• Managed environments overview
• Managed operations
• Metrics and recommendations for Power Apps
• Microsoft Azure Virtual Network support
• Microsoft Dataverse reference architectures and solution ideas
• Modernize applications with Power Platform
• Monitor the health of your resources
• Monitor with the CoE Power BI dashboard
• Move apps from the default environment (preview)
• Move data across regions for Copilots, AI agents, and generative AI features
• Notifications for Business & Industry Copilot services
• Overview of pipelines in Power Platform
• Overview of Power Platform and Copilot Studio reference architectures
• Overview of unified admin experience for finance and operations apps
• Performance testing recommendation for Power Platform workloads
• Plan mission critical workloads
• 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 and Copilot Studio real-world case studies
• Power Platform and Dynamics 365 datacenter regions
• Power Platform and Dynamics 365 macro region geography
• Power Platform Center of Excellence (CoE) Starter Kit overview
• Power Platform inventory
• Power Platform inventory schema reference
• Power Platform licensing FAQs
• Preview and experimental AI models
• Programmability and Extensibility – Power Platform API – 2020-10-01 – List tenant settings (preview)
• Programmability and extensibility – What’s new or changed
• Recommendations for standardizing tools and processes
• Requirements to integrate SAP with Power Platform
• Role-based security roles for Dataverse
• Safeguarding Dataverse sessions with IP cookie binding
• Secure a development lifecycle recommendation for Power Platform workloads
• Securely access customer data using Customer Lockbox in Power Platform and Dynamics 365
• Security overview
• Set a default pipeline
• Set up Application Insights with Power Automate
• Set up default sync filters for multiple users for appointments, contacts, or tasks
• Set up Power Platform managed identity for Dataverse plug-ins or plug-in packages
• Set up virtual network support for Power Platform
• Solution checker enforcement in managed environments
• Solution ideas for Power Platform and Copilot Studio
• Special system users and application users
• Telemetry events for model-driven apps
• Tenant settings
• Tenant-to-tenant migrations
• The City of Montréal enhances citizen engagement with Copilot Studio
• Track, manage, and scale Copilot adoption in the Power Platform
• Tutorial: Assign roles to service principals (preview)
• Types of Power Automate licenses
• Unified environment types and templates for finance and operations apps
• Usage insights
• Use /mention to link to business records
• View and download Dataverse analytics
• View license consumption for Power Apps (preview)
• View license consumption for Power Automate (preview)
• View licensing and capacity recommendations
• View Microsoft Dataverse and model-driven app activity logs in Microsoft Purview
• View operational efficiency recommendations
• View security recommendations
• What’s new in Microsoft Power Platform guidance
• What’s new in the Power Platform and Copilot Studio Architecture Center
• Authenticating to Power Platform services
• Best practices for server-side synchronization
• Configure user security in an environment
• Connect Gmail accounts, POP3 email server, or SMTP email server by using credentials specified by a user or queue
• Connect to Exchange Online
• Connect to Exchange Server (on-premises)
• Connect to IMAP or POP servers
• Delete users from an environment
• Integrate (synchronize) your email system
• Manage user settings as a Microsoft Power Platform administrator
• Managed security
• Server-side synchronization between customer engagement apps and email servers
• Set up server-side synchronization of email, appointments, contacts, and tasks

Power Platform developer

New

• How to: Create a connection from the CLI (preview)
• How to: Sign in and manage accounts with the Power Apps CLI – Power Apps
• Push a code app into a solution from the CLI (preview)
• Quickstart: Build a code app with GitHub Copilot
• Use SQL to Query Data With the Dataverse Web API

Updated

• Access external web services (Microsoft Dataverse)
• Add Power Automate flows to a code app (preview)
• Analyze plug-in performance (Microsoft Dataverse)
• Authenticating .NET applications (Microsoft Dataverse)
• Build and package plug-in code
• Column definitions
• Continuous integration and deployment
• Create and use custom APIs (Microsoft Dataverse)
• Create Workflow Extensions for Microsoft Dataverse
• Delete Data in Bulk to Reduce Storage Use
• Frequently asked questions
• How to: Add a Dataverse action or function to your code app
• How to: Connect your code app to data
• How to: Quickstart with npm CLI (preview)
• Microsoft Power Platform developer tools
• Migrate from Power Apps Test Engine to Power Platform Playwright samples
• Power Apps code apps overview
• Power Apps Developer Plan Guide: Features and Benefits
• Power Platform Playwright Samples Overview
• Query data
• Retrieve a table row using the Web API
• Specialized columns using code
• Supported customizations for Microsoft Dataverse
• System configuration
• Transition client applications to Dataverse ServiceClient
• Tutorial: Create workflow extension (Microsoft Dataverse)
• Tutorial: Write and register a plug-in (Microsoft Dataverse)
• Understand dashboards: Dashboard components and FormXML (model-driven apps)
• Use an alternate key to reference a record
• Use Microsoft Dataverse Web API functions
• Use OAuth authentication with Microsoft Dataverse (Dataverse)
• Use SQL to query data (Microsoft Dataverse)
• Verifying access in code (Microsoft Dataverse)
• View data with visualizations (charts) (model-driven apps)
• Visual Studio and the .NET platform
• Work with Microsoft Entra ID group teams (Dataverse)
• Write a custom Azure-aware plug-in (Microsoft Dataverse)
• Write a plug-in (Microsoft Dataverse)

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

AI agents are beginning to play a larger role in everyday business processes—from researching prospects and updating records to supporting outreach and follow-up. As organizations explore these possibilities, it is helpful to have a clear and manageable way to understand which agent is taking action and what it is permitted to do. 

Microsoft Entra Agent ID and Dataverse agent users offer a new identity foundation for these scenarios. Together, they help organizations give each agent a dedicated identity for accessing Dataverse, assign appropriate security roles, and maintain visibility into the agent’s activity. 

This approach can help teams introduce agent-based experiences thoughtfully, with clearer separation between people, applications, and autonomous agents.

What is Microsoft Entra Agent ID? 

Microsoft Entra Agent ID extends Microsoft Entra with identity constructs designed for AI agents. Instead of treating an agent as an anonymous automation or sharing a generic application identity, an organization can give the agent an individually identifiable, policy-controlled identity with its own permissions and audit trail. 

How Dataverse agent users complete the model 

When an agent needs to work with business data in a Dataverse environment, an administrator creates a Dataverse agent user associated with the agent’s Entra identity. The agent user becomes the security principal inside that environment, where it can be assigned dedicated, least-privileged Dataverse security roles. 

• Authenticate the agent: Establish a distinct enterprise identity for the agent. 

• Authorize only what it needs: Assign Dataverse security roles aligned to the agent’s intended tasks. 

• Separate duties: Distinguish agent activity from human users and conventional application integrations. 

• Audit agent actions: Attribute data access and changes to the agent identity. 

• Manage the lifecycle: Apply administrative ownership and governance as the agent is created, updated, or retired. 

Why this matters 

Agent identity turns governance into an architectural capability rather than an afterthought. Security teams gain clearer accountability, administrators can enforce least privilege, and makers can build agentic experiences on a foundation designed for enterprise access and compliance. 

Example: Sales Development Agent 

Consider a Sales Development Agent that helps a sales organization keep up with a large volume of prospects. The agent can continuously research leads, prepare personalized outreach, follow up, and hand promising leads to sellers. To do that responsibly, it needs access to CRM data—but it should not inherit broad permissions or operate under a shared identity. 

How the identity-enabled flow works 

1. The agent receives an Entra agent identity. The identity establishes the agent as a distinct nonhuman actor that the organization can manage and govern. 

2. The Power Platform administrator adds the agent to Dataverse. A Dataverse agent user is created and associated with the Entra agent identity. 

3. The Power Platform administrator assigns a purpose-built security role. For example, the role can permit the agent to read and update eligible leads, create activities, and record outreach outcomes—without granting access to unrelated tables or sensitive fields. 

4. The agent works within those permissions. It researches assigned leads, evaluates fit, generates or sends approved outreach, follows up, and updates lead status according to the configured sales process. 

5. Actions remain attributable. Administrators can distinguish changes made by the agent from those made by a seller or a conventional application user. 

Get started with the public preview 

Start in a non-production environment and identify one well-bounded agent scenario. Define the data and operations the agent needs before assigning permissions. 

1. Create or enable the agent identity through a supported Microsoft agent creation experience. 

2. In the Power Platform admin experience, add the Entra agent identity to the target Dataverse environment as an agent user. 

3. Assign a dedicated Dataverse security role that follows least-privilege principles. 

4. Test expected and denied operations, and verify that the agent’s actions are visible in your audit and monitoring processes. 

5. Document the business owner, security owner, intended purpose, and retirement process for the agent. 

Preview reminder: Preview capabilities are intended for evaluation and may have restricted functionality. Validate availability, licensing, regional support, and current documentation before adopting the capability for production workloads. 

Build agents the enterprise can trust 

The next generation of business applications will include people and agents working side by side. Microsoft Entra Agent ID and Dataverse agent users help make that collaboration secure by design: every agent can have a recognizable identity, only the access its role requires, and an auditable record of its work. 

Explore the public preview, test a scoped scenario such as sales development, and share your feedback with the Power Platform community. What business process would you entrust to an agent with its own governed identity? To Learn more: 

• Microsoft Entra Agent ID documentation | Microsoft Learn 
• Dataverse Agent User: Create Entra agent users (preview) – Power Platform | Microsoft Learn 

The post Secured and Governed your AI Agents: Microsoft Entra Agent ID for Dataverse  appeared first on Microsoft Power Platform Blog.

We are announcing that Prompt Columns in Microsoft Dataverse is now Generally Available. Prompt Columns enable makers to use natural language to generate AI-powered classifications, summaries, recommendations, and other insights directly from business data. Unlike traditional AI experiences, the generated insights are persisted within Dataverse tables, making them immediately available to applications, workflows, analytics, and agents across the Power Platform.

From Shipment Delays to Actionable Insights

See how Ashley, a supply chain operations manager, uses Prompt Columns to solve her business challenge. 

Here are the key takeaways:

• By leveraging AI’s ability to interpret free-form business data, Ashley uncovers insights that traditional rules and formulas cannot derive. She can then create additional Prompt Columns that build on those results, such as assessing business severity and operational risk based on the root cause, shipment status, and delay duration. 
• Insights are persisted directly within her business data and they become reusable across business processes. Ashley can create supplier performance scorecards, track recurring delay patterns by supplier or region, automatically escalate high-risk shipments through workflows, build dashboards that surface operational risks, and enable Copilot agents to answer questions such as “Which suppliers are causing the most critical delays and why?” 
• Natural language configuration empowers any maker to apply AI directly to business processes, reducing the expertise and development effort traditionally required to unlock value from AI. Ashley doesn’t need to build machine learning models, write code, or integrate external AI services. 

The result is faster identification of operational risks, reduced manual effort, more informed decision-making, and AI-generated intelligence that continuously powers business processes.  

Enterprise Impact Across Core Business Scenarios 

Here are some common Prompt Column scenarios:

• Sales Effectiveness and Revenue Growth: Analyze lead and opportunity data, classify intent and likelihood to convert, summarize customer needs, and recommend next actions, helping sales teams prioritize high-value opportunities, personalize engagement, and improve conversion rates. 
• Risk Management and Compliance: Flag compliance risks, detect escalation signals, and classify interactions by risk level. Regulated industries can potentially transition from manual sampling to AI-assisted monitoring, with the potential to reduce exposure. 
• Supply Chain and Operations Optimization: Analyze supplier records, purchase orders, shipment data, inventory exceptions, and quality inspection notes to classify delays, defects, and recurring vendor issues by severity, enabling faster resolution and more proactive supply chain management. 
• Customer Experience and Retention: Analyze customer feedback to identify satisfaction trends, churn risks, and product improvement opportunities. AI driven classification, sentiment analysis, and personalized recommendations may help organizations proactively intervene, personalize engagement at scale, and strengthen long‑term customer loyalty. 
• Financial Services Fraud Detection and Prevention: Classify risk and identify anomalies, with the expectation of reducing false positives, accelerating investigations, and improving overall regulatory posture. Financial institutions may strengthen fraud prevention by analyzing transactions, communications, and account activities in near real time. 

Prompt Columns: Key Capabilities Drive Enterprise Value 

Strategic Cost Optimization: Configurable filter logic ensures prompts execute only on high‑value records such as priority customers, critical transactions, or specific risk profiles. Organizations reduce AIB or Copilot credit consumption while maximizing business impact. 

Monitor Every Execution: Prompt Column activity is logged in Power Automate’s AI Builder Activity experience, where makers and admins can view execution history, monitor consumption, and review prompt activity. This provides visibility into how Prompt Columns are being used and the credits consumed across your environment. 

Execute AI Only When It Matters: A prompt is executed when one or more of its defined input columns change on the entity to which the Prompt column belongs. If relevant data isn’t updated, Prompt Columns doesn’t execute, eliminating unnecessary cost.

Flexible Execution Control: Enable or disable individual prompts without deleting columns or losing historical data. Pause execution during maintenance, testing, or budget cycles, then reactivate instantly.

Extended Data and Context Awareness: Define prompts on lookup fields and activity types such as emails, for a richer understanding of each record. 

Scale Without Performance Compromise: Prompt execution runs asynchronously, decoupling AI processing from real-time transactions. Systems remain responsive while thousands of records are processed per hour. This gets rid of the traditional trade-off between intelligence and performance. 

Transform Your Enterprise

Start your AI journey with Prompt Columns in Microsoft Dataverse, and turn AI into a permanent business advantage. Learn more:

• See the Public Preview blog for Prompt Columns: http://approjects.co.za/?big=en-us/power-platform/blog/2025/08/04/prompt-columns/
• Prompt columns learn docs: https://learn.microsoft.com/power-apps/maker/data-platform/prompt-column 
• Overview of prompts learn docs: https://learn.microsoft.com/ai-builder/prompts-overview 
• Prompt FAQ: https://learn.microsoft.com/ai-builder/faqs-text-generation 
• Monitor AI Builder models and prompts learn docs: https://learn.microsoft.com/en-us/ai-builder/activity-monitoring

The post Prompt Columns in GA: Turning Business Apps Data into Persisted AI Insights appeared first on Microsoft Power Platform Blog.

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

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

Installing Dataverse plugin for coding agents in ChatGPT and Codex

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

Additional Resources

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

GitHub Copilot: Dataverse | Awesome GitHub Copilot

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

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

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

Today, we’re excited to introduce Security Agent (Preview), an AI-powered assistant built directly into the Security workspace of the Power Pages Design Studio. Using natural language, you can work with Security Agent to review, configure, and strengthen their site’s security without navigating multiple settings or manually piecing together configuration details.

A conversational way to manage site security

The Security Agent is available directly within the Security workspace as a conversational assistant. Simply describe what you want to accomplish, and the agent analyzes your site’s current configuration, explains its findings, recommends security improvements, and when appropriate helps apply configuration changes after your approval.

Because the agent is grounded in your site’s actual configuration, every recommendation is tailored to your site requirements rather than just generic security guidance.

Try prompts such as:

• Review my site’s security.
• Configure Microsoft Entra ID authentication for my site.
• Restrict the Sales Team role’s permissions to their own accounts only.
• Why can’t my site users sign in?
• Which tables can anonymous users access?
• Add a Content Security Policy that allows scripts.

What Security Agent can help you do

Security Agent simplifies and accelerates the most common security activities performed during Power Pages authoring.

Review your site security posture

Assess your site’s overall security using natural language conversation. The agent reviews authentication settings, authorization configuration, security settings, vulnerability scan findings, and site configuration to identify issues such as overly broad access, anonymous data exposure, missing security protections, and authentication misconfigurations.

Configure authorization

Create and manage table permissions, web roles, and page permissions through natural language instructions. The agent recommends appropriate permission scopes, validates relationships, and helps implement least-privilege access across your site.

Configure and troubleshoot authentication

Configure identity providers such as Microsoft Entra ID, Entra External ID, Azure AD B2C and OpenID Connect, SAML 2.0 based providers on your site. The agent validates authentication settings, diagnoses common sign-in issues, and recommends configuration updates to resolve authentication problems.

Configure application security

Review and configure Content Security Policy (CSP), HTTP security headers, CORS, cookie settings, and other application-level protections to help align your site with security best practices.

Why Security Agent?

Instead of navigating multiple configuration pages or searching documentation, you can use Security Agent to:

• Review their site’s security posture in a single conversation.
• Understand security insights in plain language.
• Configure authentication and authorization more efficiently.
• Apply recommended security best practices with confidence.
• Stay in control through approval-based configuration changes.

Built on real-world security patterns

Security Agent applies security patterns derived from real-world Power Pages use cases and common customer scenarios. It helps identify issues such as overly permissive access, authentication misconfigurations, invalid permission relationships, missing security settings, and other common configuration mistakes before they become production issues.

Whether you’re configuring a new site or reviewing an existing deployment, the agent helps reduce the effort required to diagnose and resolve complex security problems.

You stay in control

Security Agent never applies configuration changes automatically. Every proposed change requires your explicit approval before execution. Before making any update, the agent explains what will change and why, allowing you to review recommendations with confidence. After the action completes, the agent confirms exactly what was updated.

We recommend using Security Agent in development or test environments and promoting approved changes to production through your standard ALM process, such as Power Platform Pipelines.

Get started

Getting started is simple:

1. Open your site in Power Pages Design Studio.
2. Navigate to the Security workspace
3. Open the Security Agent chat panel.
4. Start a conversation using natural language, e.g., “Review my site’s security.”

We want your feedback

Security Agent is currently available as a Preview feature, and your feedback will help shape its future direction.

Share your feedback through the Power Pages Community Forum or submit feature ideas through the Power Pages Ideas portal.

The post Announcing the Power Pages Security Agent (Preview): Your AI Partner for Site Security appeared first on Microsoft Power Platform Blog.

Today, we are excited to share that the Dataverse plugin is now available in the Cursor Marketplace, giving Cursor users a direct path to build with Microsoft Dataverse from inside their preferred AI coding experience.

Bring Dataverse expertise into Cursor

The Dataverse plugin teaches coding agents how to work with the Dataverse MCP server, Python SDK, PAC CLI, and Dataverse CLI. Instead of switching between documentation, admin portals, CLI references, and scripts, developers can describe what they want to accomplish and let the agent route the task to the right tool.

For example, developers can ask Cursor to help show open opportunities over a specific value, create or update Dataverse tables and columns, import a CSV into contacts or accounts, generate sample data for testing, export or import a solution, review security roles and user access, or diagnose schema and data issues in a Dataverse environment.

The plugin includes specialized skills for connection setup, data operations, metadata authoring, queries, solution lifecycle, environment administration, and security. Each skill provides the agent with tested patterns, safe defaults, and tool-selection guidance so developers can stay focused on the business problem rather than the mechanics of each underlying tool.

Built for real enterprise environments

Dataverse is the trusted data platform behind Dynamics 365 and Power Platform. That means any AI-assisted development experience must respect the same security and governance model customers already rely on.

The Dataverse plugin is designed around least-privilege access. It respects existing Dataverse security roles, field-level security, ownership-based sharing, and environment-level controls. It also follows documented authentication patterns and avoids passing prompts, tool arguments, or record data to external services. For MCP access specifically, the plugin works within the existing Dataverse MCP authorization model, including developer authentication, tenant admin consent, and environment allowlisting.

This makes the plugin useful not just for demos or prototypes, but for real enterprise development workflows where security, auditability, and correctness matter.

Getting started in Cursor

Getting started in Cursor is simple. The Dataverse plugin is available directly from the Cursor Marketplace, making it easy for developers to add Dataverse expertise to their AI coding workflow. Once installed, developers can ask Cursor to connect to Dataverse and the plugin guides the agent through setup, authentication, MCP registration, and environment verification. From there, developers can describe what they want to build or manage in natural language and Cursor can use the Dataverse plugin to route the task through the right tools. The same Dataverse plugin experience is also available for GitHub Copilot and Claude Code, giving developers a consistent way to work with Dataverse across their preferred coding agents.

Setup experience in Cursor:

References

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

GitHub Copilot: Dataverse | Awesome GitHub Copilot

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

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

The post Dataverse Plugin for Coding Agents Now Available in Cursor Marketplace appeared first on Microsoft Power Platform Blog.