IT Professionals Archives - Microsoft Power Platform Blog

Extend Liquid with Server Logic in Power Pages

Nagesh Bhat — Tue, 11 Aug 2026 18:59:27 +0000

Since introducing Server Logic in Power Pages, our focus has remained consistent: help you bring business logic closer to the experiences you build, while keeping it secure, reusable, and easy to manage at scale.

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.

Your Company Is Racing to Deploy AI. Is Your Data Ready?

Tommy Graham — Tue, 11 Aug 2026 14:00:00 +0000

AI increases the volume, value, and use of business data. Dataverse gives administrators practical controls for capacity, retention, security, auditing, and recovery.

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.

What’s new in Power Platform: July/August 2026 feature update

Tiffany Treacy — Thu, 06 Aug 2026 15:00:00 +0000

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:

Get started with the latest updates today!

Jump into Power Apps, Power Automate, and Power Pages to try the latest updates, you can use an existing environment or get started for free using the Developer plan.

Join us at PPCC!

See these updates and more come to life at the Power Platform Community Conference 2026 – Join us October 27-29 at the MGM Grand in Las Vegas to discover how organizations are using agents, apps, and automations to drive business outcomes, build new solutions, and scale innovation. Connect with product experts, industry peers, and the community shaping what’s next.

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.

Learn more

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.

Learn more

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.

Learn more

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.

Learn more

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

Learn more

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.

Learn more

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.

Learn more

Learning updates

Training paths and labs

New

Updated

Power Apps maker

New

Updated

Power Apps user and mobile

New

Updated

Power Automate

New

Updated

Power Pages

New

Updated

AI Builder

Updated

Power Platform connectors

Updated

Power Platform administration

New

Updated

Power Platform developer

New

Updated

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

Secured and Governed your AI Agents: Microsoft Entra Agent ID for Dataverse

Paul Liew — Thu, 06 Aug 2026 14:00:00 +0000

Now in public preview: Microsoft Entra Agent ID and Dataverse agent users

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

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

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

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.

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.

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.

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

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

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

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

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.

Prompt Columns in GA: Turning Business Apps Data into Persisted AI Insights

Vaishanavi Mirapurkar — Wed, 29 Jul 2026 15:00:00 +0000

Every organization has valuable business insights hidden in customer feedback, support cases, supplier updates, emails, and other unstructured data. While AI can uncover these insights, they often remain trapped in one-time interactions. The real value comes when those insights become persistent business data that can be searched, reported on, automated, and used by agents to answer questions faster and with greater context.

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.

Dataverse Plugin for Coding Agents: OpenAI and Codex Marketplace Expansion

Kent Weare — Tue, 28 Jul 2026 16:57:55 +0000

The Dataverse plugin for coding agents brings the full power of Microsoft Dataverse directly into the developer’s coding environment. Instead of switching between browser tabs, documentation, and admin portals, developers can describe what they want in natural language and the plugin handles the rest. It routes each request through the right tool: Dataverse MCP server, Python SDK, PAC CLI, or Dataverse CLI. This allows developers to stay in flow and deliver production-grade results without mastering every tool individually. Built on an open-source skill architecture, the plugin enforces least-privilege security, follows documented authentication patterns, and respects existing Dataverse RBAC, making it safe for real enterprise environments from day one.

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.

Announcing the Power Pages Security Agent (Preview): Your AI Partner for Site Security

bipuldeora — Thu, 23 Jul 2026 07:11:02 +0000

Securing a Power Pages site often requires configuring authentication, authorization, permissions, and application security settings across multiple experiences. Whether you’re troubleshooting a sign-in issue, reviewing access permissions, or hardening your site’s security posture, finding the right configuration can be time-consuming and requires deep platform knowledge.

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:

Open your site in Power Pages Design Studio.
Navigate to the Security workspace
Open the Security Agent chat panel.
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.

Dataverse Plugin for Coding Agents Now Available in Cursor Marketplace

Kent Weare — Tue, 21 Jul 2026 15:00:00 +0000

AI coding agents are quickly becoming part of the way makers and developers build, extend, and manage business applications. With the Microsoft Dataverse plugin for coding agents, developers can bring Dataverse expertise directly into their coding environment and work through natural language to query data, design schemas, import records, manage solutions, and administer environments.

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.

Announcing Link to Fabric UX refresh

Anirudha Bakore — Mon, 20 Jul 2026 14:00:00 +0000

We are refreshing how you connect Microsoft Dataverse to your analytics stack. “Azure Synapse Link for Dataverse” is becoming Link data, a single home for every way you move Dataverse data out: Link to Microsoft Fabric, Azure Synapse Link, and other targets. Fabric link is now the headline path, the setup wizard has been redesigned around it, and workspace identityis now the recommended authentication option. The new experience is rolling out now and will be available worldwide by early August 2026.

What is changing and why we are making this change?

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

1. The name no longer matched the product.

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

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

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

3. Authentication needs to get simpler and safer.

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

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

How to setup Link to Fabric using refreshed UX

From “Azure Synapse Link” to “Link data”

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

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

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

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

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

A redesigned Fabric link wizard

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

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

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

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

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

Workspace identity is the recommended authentication

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

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

What this means for your team

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

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

What is not changing

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

Looking ahead

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

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

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

We want your feedback

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

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

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

Native Dataverse Authorization (Public Preview) for Stronger Security in Power Pages

Nagesh Bhat — Tue, 07 Jul 2026 15:06:13 +0000

We’re excited to introduce the public preview of Native Dataverse Authorization (Enhanced Authorization) in Power Pages.

This release brings a significant advancement in how external user access is secured and managed. Authorization is now enforced directly within Dataverse, providing stronger security, improved visibility, and more precise control while keeping the maker experience unchanged. This feature currently needs to be enabled at a website level.

What’s new in this release

Authorization enforced directly in Dataverse

Access decisions are evaluated where the data resides, ensuring consistent enforcement of security policies across all access scenarios and strengthening overall data protection. This helps reduce security gaps and ensures a more reliable access control framework.

Improved audit visibility of external users

Audit logs now reflect the actual external user performing actions. This enhances traceability, simplifies compliance reporting, and provides clearer operational insights. It also enables teams to investigate issues faster and maintain stronger accountability.

Column-level security support

Protect sensitive data with greater precision. Column security profiles allow you to control not only which records users can access, but also which specific fields are visible or editable. This ensures sensitive information is exposed only to the right users when needed.

Learn more: Column security profile (preview)

Custom Scope for granular access control

Introducing Custom Scope, enabling fine-grained, row-level access control based on business conditions. This allows you to define exactly which records each user can access, beyond traditional access models. It gives you greater flexibility to model real-world access scenarios with precision.

Learn more: Custom access type (Preview)

Seamless experience for makers

There’s no need to redesign your applications. Makers can continue using familiar Power Pages constructs while benefiting from stronger, platform-level enforcement behind the scenes. This allows teams to adopt enhanced security without impacting productivity or development workflows.

How it works (at a glance)

Native Dataverse Authorization brings Power Pages security closer to the Dataverse model through a simple alignment of concepts.

At a high level:

• Contacts are represented as Dataverse users: Each external user is represented within Dataverse, enabling access to be evaluated in a true user context.

• Web roles align with security roles: Roles defined in Power Pages align with Dataverse security roles, ensuring consistent role-based access control.

• Operations run in user context: All operations execute in the context of the signed-in user rather than a shared application identity, ensuring access is consistently enforced based on user permissions.

What to be aware of
If you have existing plugins or custom logic registered on Dataverse tables, they will now execute using the calling user’s permissions. In some cases, this may surface access-related errors where actions previously succeeded with elevated privileges. We recommend reviewing and validating such customizations to ensure they align with user-level access.

Getting started

Enable Native Dataverse Authorization in your Power Pages site and start exploring these enhancements:

• Enable enhanced authorization (preview)
• Column security profile (preview)
• Custom access type (Preview)
• Audit logging

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 Native Dataverse Authorization (Public Preview) for Stronger Security in Power Pages appeared first on Microsoft Power Platform Blog.