Applies to Product - Power Pages
What’s happening?
Customers are experiencing issues with custom domain configurations where the expected behavior is not occurring. Specifically, when accessing a custom domain (e.g., www.example.com), it may redirect to an unintended page, while the non-www version (e.g., example.com) works correctly.
Reason:
The underlying cause of this is often related to incorrect DNS settings, specifically the absence of necessary A records or CNAME mappings that point to the correct server. Additionally, there may be conflicts with existing TXT records or other domain configurations that prevent proper redirection.
Resolution:
- Ensure that an A record is created to point the custom domain to the appropriate Microsoft server.
- Verify that the CNAME mapping is correctly set from the custom domain URL to the Power Pages URL.
- Check for any existing TXT records associated with the custom domain. If there are duplicate or conflicting TXT records, such as those starting with "asuid," remove them to avoid issues.
- Confirm that the custom domain is not associated with any other existing portals within the tenant, as only one custom domain can be mapped to a portal at a time.
- If SSL certificates are involved, ensure that the hostnames match the custom domain being added and that the certificates are correctly configured.
- For further guidance, refer to the official documentation on setting up custom domains for Power Pages. Add a custom domain name | Microsoft Learn