You’re offline. This is a read only version of the page.
2
Hi Power Platform Community,
I'm working on integrating Azure AD B2C as the default identity provider for my Power Pages site (using the default domain). I’ve set up a new environment with a blank Power Page to avoid caching issues from earlier attempts, but I’m running into a 401 Unauthorized error when clicking the Sign in button.
Hi KevSynapthrive,
I’m seeing the same issue when integrating itsme as a custom IDP in Power Pages – it simply won’t work. Given that itsme is used successfully by millions of Belgians, this integration unquestionably has to function correctly.
A few details on my end:
I suspect the root cause lies within Power Pages itself.
I raised an initial support request with Microsoft in November 2024, but their subcontractor couldn’t resolve the problem.
I’ve just submitted a fresh service request today, though I’m doubtful we’ll progress if it remains with the same team.
Has anyone managed to get itsme up and running in Power Pages, or know how to escalate this to a specialised Power Pages identity team?
Any pointers would be greatly appreciated.
I'm now encountering an immediate 502 - Web server received an invalid response error when clicking "Sign In" on my Power Pages site configured to use Azure AD B2C as the external identity provider. The Azure AD B2C login screen never appears.
Here’s a full breakdown of what I’ve tried:
Share
Report
All responses (
Answers (
/signin-oidc) to the app registration. I have also tried with the default redirect URI. Neither works."accessTokenAcceptedVersion": 2 in the app’s manifest./authorize URL with all required parameters (client_id, p, redirect_uri, etc.) — it loads the B2C screen when run directly, but that also shows an error too "AADB2C90068: The provided application with ID '<removed>' is not valid against this service. Please use an application created via the B2C portal and try again."Configured a new identity provider with:
Correct authority (using domain-based format, not tenant ID)
Correct client ID from the B2C tenant
Proper redirect URI
Correct Default Policy ID
Valid issuer set to match B2C
Login and registration claim mappings using standard OIDC claim URIs
Re-published the Power Pages site multiple times
Verified the LoginButtonAuthenticationType site setting matches the authority
Set the UsePortalErrorPage setting to true (still no descriptive error shown)
Deleted and fully recreated the identity provider and all related site settings to eliminate caching issues
Confirmed all claim mappings and site settings match expected formats
Validated no trailing slashes or case mismatches in site settings
Completely deleted power page and tried again
Created a totally different developer environment and started over
Power Pages site is in a developer environment and currently set to private (requires login)
Using Azure AD B2C free tier
M365 tenant is on Business Basic plan
Whether private Power Pages sites in developer environments have known limitations with external identity providers
Whether there's any backend service sync, feature flag, or portal limitation that could explain why the OIDC flow is not initializing properly
Any additional diagnostic tools or telemetry that can be enabled for deeper visibility
#1
WarrenBelz
146,631
Most Valuable Professional
#2
RandyHayes
76,287
Super User 2024 Season 1
#3
Pstork1
65,964
Most Valuable Professional
