Power Pages Auth Governance: What Changes for Integrators

Article image
22 Nov 2026
9 min
Enterprise
Automation
Implementation

Microsoft began rolling out new authentication governance controls for Power Pages in public preview on November 9, 2026. The feature lets Power Platform admins allow or block individual authentication protocols and OAuth 2.0 identity providers for an entire environment from the admin center, instead of leaving that decision inside each site's own settings. For integrators, the practical change is this: a tenant-wide policy flip you did not make can now silently disable the identity provider your Power Pages portal depends on to log users in.

What is Power Pages authentication governance?

Power Pages authentication governance is a set of admin center controls that let a Power Platform administrator restrict which external authentication protocols and OAuth 2.0 identity providers (IDPs) are permitted across an environment's Power Pages sites, overriding whatever individual site makers have configured locally. The new preview, announced November 9, 2026, is managed from Manage > Power Pages > Governance settings > Authentication providers in the Power Platform admin center, where an admin can set an allow or block list by protocol and IDP, apply it at the environment level, and carve out exceptions for specific sites.

This is not Microsoft's first governance lever for Power Pages authentication. A coarser, binary control, "Enable external authentication providers," reached general availability back in March 2025: admins could turn external auth on or off tenant-wide, full stop. The November 2026 preview is more granular. Instead of an all-or-nothing switch, admins can now permit, say, Azure AD B2C while blocking a generic OpenID Connect provider, or allow one specific OAuth 2.0 IDP and reject the rest, all without touching the site itself.

What changed on November 9, 2026

Before this preview, authentication provider configuration for a Power Pages site lived almost entirely at the site level. A maker (or a developer on an integration team) set up an external identity provider by editing Site Settings records in the Portal Management app, things like Authentication/OpenIdConnect/OpenId_1/Issuer for an OpenID Connect provider's issuer URL, client ID, and related metadata. Whoever built the site owned the authentication configuration end to end.

The new governance layer sits above that. It does not replace site settings, it polices them. A site can still have a fully configured OAuth 2.0 provider in its site settings, but if a tenant admin has not added that provider (or that protocol) to the allowed list in governance settings, the login flow using it can be blocked at the environment level regardless of what the site itself says.

That is the structural shift integrators need to understand: authentication for a Power Pages portal is no longer fully determined by the people who built the portal.

Why this matters for integrators

If you build or maintain a Power Pages portal that authenticates users against an external system, a few things are now true that were not true before November 2026:

  1. A tenant-level policy change can break your login flow without touching your site. An admin tightening governance settings for an unrelated reason, say, standardizing on one corporate IDP, can remove your portal's protocol or provider from the allowed list as a side effect.
  2. The failure is quiet. There is no code change, no deployment, no site settings diff to point to. Users just start seeing authentication errors, and the first instinct of whoever is on call is to check the integration code, not a governance policy that changed somewhere else in the tenant.
  3. Exceptions exist but are opt-in, not default. The preview supports per-site exceptions to an environment-wide policy, but someone has to know to request one before the policy change rolls out. If nobody flags the dependency in advance, there is no exception to fall back on.

For an ISV shipping a Power Pages portal to multiple customer tenants, or an enterprise integration team running a customer-facing portal against a CRM, ERP, or document system, this turns authentication from "something we configured once" into "something we need to monitor, because someone else now controls part of it."

The specific failure mode: a policy change breaks a portal nobody touched

Picture a Power Pages portal that authenticates customers through a third-party OAuth 2.0 identity provider, then uses that authenticated session to call out to a backend system, maybe to pull account data, submit a form, or kick off a document workflow. The portal has worked for a year. Nobody on the integration team has opened the site settings in months.

Then a tenant admin, working through a security hardening pass after the November 2026 preview becomes generally available, builds an allow list of "approved" IDPs for the environment and does not know this particular portal exists or what it depends on. The portal's OAuth 2.0 provider is not on the list. Logins start failing. The integration team gets paged, checks recent deployments (there are none), checks the OAuth app registration (unchanged), and burns hours before anyone thinks to check Power Platform governance settings.

This is the same category of problem as a platform quietly changing an auth requirement underneath an existing integration, the kind of change HubSpot and Microsoft also pushed through in October 2026 and that broke connections nobody had touched. The fix in both cases is the same: know exactly what your integration depends on before the platform changes the rules, not after.

How to audit your Power Pages authentication dependencies before this rolls out further

Do this now, while the control is still in public preview, rather than after it reaches general availability (targeted for January 2027):

  1. List every Power Pages site in the tenant and its authentication method. For each site, open Site Settings in Portal Management and record which protocol is configured: OpenID Connect, OAuth 2.0, SAML 2.0, or the Power Pages default (Microsoft Entra ID / local accounts).
  2. Identify the specific identity provider, not just the protocol. "OAuth 2.0" is not specific enough. Record the actual IDP, Okta, Auth0, a customer's own Azure AD B2C tenant, a proprietary OAuth server, whatever it is.
  3. Confirm with your Power Platform admin whether governance settings are enabled for the environment. Ask directly whether the authentication governance preview is turned on, and if so, what the current allow or block list contains.
  4. Request an explicit exception for anything not already on the allow list, rather than assuming it will be grandfathered in. The preview supports per-site exceptions, but they have to be requested.
  5. Add a governance-settings check to your incident runbook. If a Power Pages login flow fails and nothing in the site or the IDP changed, checking the admin center's authentication governance settings should be step one, not step five.
  6. Treat this as a recurring audit, not a one-time task. Power Pages is built on Dataverse, and Microsoft has been steadily extending admin-center governance across the platform. The pattern of centralizing something that used to live per-resource shows up elsewhere too, for example in how Dataverse MCP guardrails travel (or don't) between n8n and agent runtimes. Whoever owns the integration should own the dependency list, kept current.

What this means if your portal triggers downstream workflows

Power Pages portals are rarely just login pages. Many exist specifically to collect an authenticated user's input and trigger something downstream, a CRM record update, an approval process, or a document signing flow. If your portal is the front end for a process that eventually calls out to something like Docusign Workflow Builder (formerly Maestro) to generate and send an agreement, an authentication block does not just stop a login. It silently stops whatever automation depended on that session ever firing in the first place.

That is the same class of silent failure that a webhook relay layer like Baton is built to catch on the Docusign side, verifying delivery, retrying failures, and logging what actually fired instead of assuming it did. An authentication governance block upstream and a dropped webhook downstream look different in the logs, but they share the same root problem: a dependency changed somewhere you weren't watching, and the first sign of trouble is a user complaint, not an alert.

FAQ

Does the November 2026 Power Pages authentication governance preview replace site-level authentication settings? No. Site-level settings (configured in Portal Management's Site Settings) still define how a site authenticates. The new governance controls sit above site settings and can block a protocol or provider at the environment level even if a site is already configured to use it.

Is this the same as the "Enable external authentication providers" setting from 2025? No. That setting, generally available since March 2025, is a tenant-wide on/off toggle for external auth as a category. The November 2026 preview is more granular: it lets admins allow or block specific protocols and specific OAuth 2.0 identity providers, not just external auth in general.

When does this feature reach general availability? Microsoft's Power Platform release plan lists a November 2026 preview date with a planned general availability date of January 2027, though preview timelines can shift.

Who should request an exception if a needed identity provider gets blocked? Whoever owns the Power Pages site or the integration it supports should request the exception through their Power Platform admin, ideally before a tenant-wide policy change is enforced, not after users start reporting login failures.

What should ISVs building Power Pages portals for customers do differently now? Document the exact authentication protocol and identity provider each deployed portal uses, and build a step into onboarding or support that confirms the customer's tenant has that provider on its governance allow list, rather than assuming default settings will cover it.

Next step

If you are responsible for a Power Pages portal that authenticates against an external system and feeds a downstream workflow, audit the dependency now rather than after the preview reaches general availability. If that downstream workflow runs through Docusign, talk to the fluidlabs team about how we build and run integrations that keep working when the platforms underneath them change the rules.

Other articles
Get in touch

Tell us what Docusign needs to talk to

Thirty minutes with an engineer. Within 48 hours you get a scoped plan and a fixed price in writing, or a straight “you don't need us.” No charge, nothing to sign.

Talk to an engineer →

or email us at hello@fluidlabs.com