{"id":44518,"date":"2026-05-01T18:09:04","date_gmt":"2026-05-01T12:39:04","guid":{"rendered":"https:\/\/www.inogic.com\/blog\/?p=44518"},"modified":"2026-05-04T09:53:36","modified_gmt":"2026-05-04T04:23:36","slug":"step-by-step-guide-to-controlling-public-access-for-non-production-power-pages-sites","status":"publish","type":"post","link":"https:\/\/www.inogic.com\/blog\/2026\/05\/step-by-step-guide-to-controlling-public-access-for-non-production-power-pages-sites\/","title":{"rendered":"Controlling Public Access for Non-Production Power Pages Sites: Step-by-step Guide"},"content":{"rendered":"

\"Public<\/p>\n

While working with Power Pages across Development and UAT environments, one recurring risk becomes obvious, non-production portals can accidentally be switched to public access, exposing incomplete pages, test forms, and even sample data to external users.<\/p>\n

To address this, Microsoft has introduced a tenant-level governance control that allows administrators to restrict whether non-production Power Pages sites can be made publicly accessible.<\/p>\n

This feature acts as an additional security safeguard by ensuring that unfinished or testing websites are not unintentionally exposed to the internet. Below are the implementation details and how this governance setup works.<\/p>\n

Use Case <\/strong><\/h3>\n

Let us consider an example. For instance, you are creating a Power Pages website for a bank. The developer and his\/her colleagues develop various modules of the website such as login pages, application forms for loans, and others. While developing, your colleague publishes the website by mistake. In this case, the website will be accessible to everyone who has the URL address. Everyone on the Internet will be able to visit the site just by using the link. In case this option is enabled, users will not be able to make the site public unless they have the required administrative permissions. This means even if someone tries to change the site visibility, it will be restricted and require proper admin approval. This adds an extra layer of security and helps prevent accidental exposure of the site<\/p>\n

Note: When the feature is initially enabled, the policy set by default is ‘None’. Therefore, no site is visible externally.<\/em><\/strong><\/p>\n

\"Step-by-stepStep-by-Step Implementation<\/strong><\/h3>\n
    \n
  1. Redirect and sign in to the Power Platform Admin Center<\/strong>.<\/a> \"Step-by-step<\/li>\n
  2. Set Governance Controls<\/strong> option: Manage \u2192 Power Pages \u2192 Governance Controls\"Step-by-step<\/li>\n
  3. From the dropdown, select:
    \n\u201cSet site visibility to public access for non-production sites\u201d\"Step-by-step<\/strong><\/li>\n
  4. Select the environment where you want to apply this governance control.\"Step-by-step<\/li>\n
  5. Configure Policy Value<\/li>\n<\/ol>\n

    Choose one of the site visibility options based on your requirements:<\/p>\n