web

You’re offline. This is a read only version of the page.

News and Announcements icon

Power Platform CommunityForums Power Pages Why does local SPA dev...

Power Pages

Suggested Answer

Why does local SPA development require Public site visibility?

(0) Share

Report

Report

Posted on by CU11031005-0

The current SPA local development guidance requires setting site visibility to Public in order to enable localhost development and hot reload. This feels inconsistent, because a local developer workflow depends on a visibility mode intended for production-ready, internet-facing sites. Since Public site visibility is reserved for production scenarios, using it as a prerequisite for local SPA development is confusing and counterintuitive. Is this really the expected design, or are there plans to introduce a dedicated developer/localhost mode for non-production environments?

Categories:

Customize & extend

I have the same question (0)

All responses Img

All responses (2)

Answers Img

Answers (0)

Suggested answer

Lucas001 2,529 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi @CU11031005-0,

this as far as I know is the current standard for the options localhost development and hot reload. Otherwise you would just not be able to get any kind of authentication which is blocked when a page is private.

For example when using a tool like clarity or google analytics on a private site, you won't be able to see any traffic. The entire page is locked behind the "cloud-side authentication gate".

If you are using Ai to develop it you probably can download some sample entitiy schemas and let Ai create sample data, obviously not the same as a page directly connected to dataverse.

I've not heard about anything being released soon towards that topic.
You can still try submitting an idea here: https://ideas.powerpages.microsoft.com/d365community/forum/1edba0ec-30cf-ec11-a7b5-000d3a545c96

Hope that helps.

Was this reply helpful? Yes No
Suggested answer

DP_Prabh 201 on at

Like (0)

Report
Copy link

Link copied!

Hi @CU11031005-0,

As Lucas mentioned, the current guidance requires the site visibility to be set to Public to enable user authentication and support localhost development. I agree that this can feel counterintuitive, since the Public setting is typically associated with production, internet-facing sites rather than development workflows.

In a similar scenario, I explored a workaround using MSAL-based authentication for a proof of concept. I implemented custom authentication with MSAL and tested it locally. Since Power Pages roles are associated with the Contact table, we used an admin app where administrators could add user details to the Contact table and assign appropriate roles whenever a new user was added in Azure AD. This allowed users to access the local development pages and see content based on their assigned roles.

This approach worked for development and testing purposes, but it requires manual management and was mainly used as a POC, so it’s not an ideal long-term solution. It would be much more efficient if users authenticated via MSAL could automatically be mapped to Contacts and inherit the appropriate Power Pages permissions, rather than requiring manual updates.

I hope this workaround provides some useful context or ideas while working with the current setup.

Was this reply helpful? Yes No

Join the conversation

Helpful resources

News and Announcements

Welcome to the Power Platform Communities

Quick Links

Subscribe to this forum!

Stay up to date on forum activity by subscribing.

Leaderboard > Power Pages

#1

Lucas001 21 Super User 2026 Season 1

#2

CN-06091549-0 18

#3

oliver.rodrigues 17 Most Valuable Professional

Last 30 days Overall leaderboard

Featured topics

Solution to LinkedIn Authentication in Power Apps Portals

Welcome to the Power Pages forum!

Product updates

Microsoft Power Platform Community release plans