Applies to Product - Power Pages
What’s happening?
Customers experience warning messages when accessing their PowerPages website after configuring a custom domain.
Reason:
The warning message "ERR_CERT_COMMON_NAME_INVALID" appears, indicating a potential issue with the SSL certificate or domain configuration.
Resolution:
- Verify that the custom domain is correctly set up in the PowerPages environment. Add a custom domain name | Microsoft Learn
- Ensure that the CNAME mapping is created from the custom domain URL to the powerappsportals URL.
- Check if the custom domain is associated with any existing portals within the tenant. If it is, ensure it has been removed from those portals before adding it to the new portal.
- Confirm that only one custom domain can be mapped to a portal at a time.
- Ensure that the hostname of the SSL certificate matches the custom domain being added.
- Check if there are any TXT records associated with the custom domain. If there are additional TXT records (other than those provided by Microsoft), remove them and attempt to add the custom domain again.
- Follow the specific instructions from the certificate provider for exporting the SSL certificate as a password-protected PFX file.
- For enabling AFD on the custom domain, refer to the relevant documentation for PowerPages. Set up Azure Front Door with Power Pages sites | Microsoft Learn
