Posted in

[Power Platform: Block Public Non‑Production Power Pages]

by ailona•

Microsoft Power Platform now lets admins block non-production Power Pages sites from being made public. Using PPAC governance controls, admins can restrict trial and developer environments, apply selective targeting policies, and maintain production site behavior while preventing accidental external exposure.

Microsoft added a governance control in the Power Platform admin center. Tenant admins can now restrict making non-production Power Pages sites public.

Main feature/change and impact

Tenant admins can configure a PPAC setting to prevent makers from switching non-production Power Pages sites to Public. This applies only to trial and developer environments and does not change production site behavior. If a non-production site is already public, it stays public until set back to Private. Once set to Private under the restriction, it cannot be made public until the policy is changed.

Practical implications

Admins gain a simple guardrail to prevent accidental exposure of test content and sensitive data. The control supports selective targeting so policies can apply to chosen environments. Makers will see a clear access-restricted message in Power Pages Design Studio when the option is disabled. Changes take effect immediately after admins save the policy in PPAC, requiring no code changes.
“We’re introducing a new governance control in Power Platform admin center (PPAC), that lets tenant admins restrict whether non-production sites can be set to public.”
To configure, sign in to the Power Platform admin center and navigate to Manage > Power Pages > Governance controls. Select “Set site visibility to public access” for non-production sites, choose the target environment, and save. The default policy when available is ‘None’, which prevents makers from making non-production sites public until an admin explicitly changes it. Review your tenant setting promptly to avoid unexpected impacts. Closing paragraph: This governance control reduces the risk of accidental public exposure of development sites. Admins should evaluate environments and enable targeted policies where needed. Verify settings in Power Pages Studio and monitor maker requests for exceptions.

Key points from the article:

  • Admins can restrict non-production sites from being set to public.
  • Control is configured in the Power Platform admin center (PPAC).
  • Restriction applies only to trial and developer environments.
  • Existing public non-production sites stay public until set to private.
  • Targeting options enable selective policy application per environment.

    • Related Coverage:

    From the Microsoft Power Platform Blog