Applies to Product - Power Pages
What’s happening?
Customers experience issues when testing their Azure B2C login configuration, resulting in errors such as "IP not found" or being redirected to the default Microsoft 365 login page instead of the custom B2C login page.
Reason:
The underlying cause of this may relate to misconfigurations in the Azure B2C settings or the integration with Power Apps, leading to incorrect redirect URIs or flow configurations.
Resolution:
- Verify the configuration settings in Azure B2C to ensure they match the intended setup.
- Check the redirect URI used in the application and ensure it is correctly set to the custom B2C login page.
- Use the JWT.ms tool to test the user flow by adding the redirect URL https://jwt.ms in the Reply URL to validate the token response.
- If the JWT response is successful, it indicates that the B2C configuration is correct, and further investigation should focus on the Power Apps configuration.
- If issues persist, collect new network traces and HAR files during the login attempt and share them for further analysis.
- Ensure that only one flow configuration is active for the portal to avoid confusion with multiple configurations.
