Hi there! 👋
This is a known limitation of the Power Pages Design Studio, and Microsoft Learn documents it directly. Here's the full picture.
🔍 Why the Design Studio Blocks Guest Users
According to Roles required for Power Pages administration – Microsoft Learn:
"The platform uses the Microsoft Graph service to retrieve role information. Currently, Microsoft Graph does not support guest users."
This means even if your guest user has System Administrator and System Customizer roles correctly assigned in the environment, the Design Studio at make.powerpages.microsoft.com cannot verify their role membership via Microsoft Graph — so access is denied.
This is why the PAC CLI works fine (it doesn't go through the same Microsoft Graph role-check path), while the browser-based Design Studio does not.
✅ What the Docs Say Is Required to Edit a Site
Per Roles required for Power Pages administration – Microsoft Learn, to edit a website via the Design Studio, a user must be a System Administrator or System Customizer — but crucially, they must be a member user (not a guest) for those roles to be recognized by the Design Studio.
🛠️ Recommended Workarounds
Since guest users hitting the Design Studio is a platform limitation, here are the approaches:
- PAC CLI + VS Code — as you've already discovered, this works great for code-level editing without the guest user restriction.
- Portal Management app — guest users with the correct environment roles may still access the Portal Management model-driven app for configuration tasks that don't require the visual Design Studio.
- Convert the guest to a member — if possible, invite the contractor as a full member user in your Microsoft Entra ID tenant (rather than a B2B guest). Member accounts fully support the Design Studio role checks.
📋 References
Found this helpful? Please mark ✅ "Does this answer your question?" so others searching for the same issue can find it quickly. A 👍 on "Was this reply helpful?" or a ♥ Like is also much appreciated!
Raghav Mishra — LinkedIn | PowerAI Labs