Microsoft Power Pages security dashboard showing authentication settings, web roles, permissions, and Copilot’s recommendations.
Microsoft’s Power Pages Security Agent brings conversational assistance to authentication and authorization setup inside Design Studio. Makers can ask it to inspect sign-in settings, explain access risks, and propose configuration changes—with explicit approval required before it applies updates. Microsoft’s documentation still labels the feature preview, an important qualification for anyone considering production use.

The appeal is straightforward: less hunting through configuration screens, more help understanding what a setting actually does. But an easier interface does not remove the need to decide who should have access to what.

Microsoft Power Pages security dashboard showing authentication settings, web roles, permissions, and Copilot’s recommendations. What the security agent helps configure​

Microsoft’s feature description covers both sides of access control: authenticating users and deciding what those users can access afterward. For authentication, the planned assistance includes reviewing identity-provider settings and recommending improvements to token configuration, redirect settings, and session controls. For authorization, it describes recommendations for web roles and data permissions, including read-only and owner-only access.

Microsoft Learn documents support for Microsoft Entra ID, OpenID Connect, and SAML 2.0 authentication configuration and troubleshooting. It also describes assistance with web roles, page permissions, and Dataverse table permissions. The agent uses the site’s configuration to explain findings and recommend changes rather than offering only generic advice.

The distinction matters: a working login is not proof of appropriate data access. Microsoft’s security guidance treats page permissions, web roles, table permissions, and API configuration as connected parts of the authorization model.

Preview now, November remains a target​

Roadmap item 577809 lists the feature as In development, with an April 2026 preview window and a November 2026 general-availability target. Its stated scope is the web platform in Worldwide Standard Multi-Tenant environments, with automatic enablement for admins, makers, and marketers. Microsoft cautions that roadmap release dates are estimates and can change.

Microsoft’s release plan also carries a date worth noting: the 2026 release wave 1 Power Pages plan listed the security agent (“Configure authentication with security agent”) with an April 2026 public preview and a June 2026 general-availability target, but without a released marker. The August 2026 general-availability date belongs to an adjacent, unrelated feature on the same page (“Unify Power Pages authorization by merging web role with Dataverse security role”), not the security agent. Since Learn still labels the security agent a preview feature, the plan’s June 2026 target appears to have slipped; it should not be treated as evidence the feature has already reached general availability.

The practical status is preview, not a confirmed production launch. Microsoft Learn says preview features are not intended for production use and may have restricted functionality. November 2026 remains a forecast.

How to evaluate it safely​

Microsoft’s Power Platform announcement provides the basic access path and recommends development or test environments, followed by the organization’s normal application lifecycle management process. For makers evaluating the preview, the workflow is:

  • Open the test site in Power Pages Design Studio.
  • Navigate to the Security workspace.
  • Open the Security Agent chat panel.
  • Describe the review or configuration task in natural language.
  • Examine the proposed changes and their explanation before approving.
  • Review the agent’s confirmation of what changed, then validate before deployment.

Start with a review rather than a broad instruction to “fix everything.” Microsoft documents prompts for investigating sign-in failures and identifying excessive access. An explanation-first approach makes the approval checkpoint more useful: approval should represent a decision, not merely another button to click.

What to check before approving permissions​

Microsoft’s broader Power Pages security guidance supplies useful checks beyond the feature announcement:

  • A hidden page is not a secured page. Restricted pages need page permissions.
  • Global table access deserves scrutiny. It grants associated web roles access to every record in the table; Microsoft recommends relationship-based access for sensitive business data.
  • Anonymous table permissions mean public access. Grant them only where a business requirement explicitly calls for it.
  • Production authentication should use a supported external identity provider, rather than Power Pages local authentication.

A sensible validation exercise is to test both permitted and forbidden actions: can the intended user reach the required records, and is an unrelated user denied? That is an implementation recommendation based on Microsoft’s least-privilege guidance—not a claim of firsthand testing.

Finally, continuous monitoring should not be confused with autonomous remediation. Microsoft documents recurring security scans and traffic monitoring as related capabilities whose findings can feed the agent’s guided investigation. Configuration changes still require approval.

The promising part is easier access to security expertise and configuration context. The boundary is equally important: the agent can help explain and implement a policy, but the organization must still decide whether that policy is right.


Correction (October 23, 2026): an earlier version said an archived release-plan page listed August 2026 for the security agent’s general availability and warned it was no longer maintained. Microsoft’s 2026 release wave 1 plan actually lists the security agent (“Configure authentication with security agent”) with a June 2026 general-availability target (no released marker); the August 2026 date belongs to a different feature on the same page. The conclusion that preview is the practical status is unchanged.

 

References

  1. Power Pages: Design studio - Configure authentication with security agent Microsoft 365 Roadmap 2026-10-22T23:45:34.691127Z
  2. Introducing Power Pages Security Agent (Preview): Configure and Secure Your Sites with AI microsoft.com
  3. Configure authentication with security agent | Microsoft Learn learn.microsoft.com