Hi maxwell.2k19,
Great questions! Here's a breakdown for both scenarios:
1. Development Environments
The Entra ID / Azure AD Application Developer role is not what's needed here that role relates to registering app registrations in Azure AD and won't grant Power Pages creation rights.
For a user to create a Power Pages site in a Development environment, they need the System Administrator security role assigned within that specific environment. You can configure this via:
> Power Platform Admin Center → Environments → [Your Environment] → Settings → Users + Permissions → Security roles
Note that the user who created the Developer environment is automatically its admin, but other users need to be explicitly assigned.
2. Default Environment
The same principle applies users need the System Administrator security role in the Default environment to create a Power Pages site. While all licensed users typically receive the Environment Maker role in the Default environment by default, this role alone is generally not sufficient to provision a new site.
A few other things worth checking:
- Power Pages capacity — Your tenant needs Power Pages capacity allocated. If no capacity is available, site creation will be blocked regardless of permissions.
- Tenant-level environment creation settings — Under Power Platform Admin Center → Settings, check "Who can create production and sandbox environments", as this can indirectly affect site provisioning.
- License check — M365 E5 includes some Power Platform capabilities, but Power Pages may require additional licensing depending on authenticated vs. anonymous site usage.
Kindly accpet the answer if it helps and solve your issue.
Many Thanks!
Best Regards,
Jerald Felix
8
Share
Report
All responses (
Answers (
