Custom domains are essential for branding and trust. When you set up a Power Pages site, Microsoft provides a default URL such as:
https://yoursite.powerappsportals.com
But for most organizations, using a custom domain like:
https://www.yourcompany.com
is critical for professional presence, improved SEO, and consistency across your digital assets.
Let’s explore how to configure and manage custom domains for Power Pages, step by step and in depth.
1. Understanding Domain Management in Power Pages
Microsoft Power Pages supports custom domains via Azure Front Door and Azure DNS, which act as intermediaries to securely route and manage traffic. You can also bring your own domain from any domain registrar (like GoDaddy, Namecheap, etc.).
2. Prerequisites
Before adding a custom domain, ensure you have the following:
- A Power Pages site already set up and running
- Admin permissions to the Power Platform Admin Center
- Access to your DNS provider’s settings panel
- A purchased custom domain (e.g.,
yourcompany.com)
3. Steps to Configure a Custom Domain
Step 1: Navigate to Power Platform Admin Center
- URL: https://admin.powerplatform.microsoft.com
- Select your environment
- Click Resources > Power Pages sites
- Select your site
Step 2: Go to the ‘Custom Domains’ Tab
- Click on Manage Domains
- Click + Add custom domain
You’ll see a window prompting you to enter your desired custom domain (like www.yourcompany.com).
Step 3: DNS Validation via TXT Record
To verify ownership of your domain, you’ll be given a TXT record to add to your DNS provider:
- Record Type: TXT
- Host/Name: (usually
@or the root domain) - Value: Provided by Microsoft (a long string)
✅ Add this TXT record in your domain registrar’s DNS panel
⌛ Wait 10–15 minutes (can take up to 48 hours) for DNS propagation
After successful verification, the domain status in the Admin Center will turn to “Verified.”
Step 4: CNAME Mapping
After verification, Microsoft will prompt you to configure CNAME records to map the domain to Power Pages:
- Record Type: CNAME
- Name:
www(or subdomain prefix) - Value: Provided target like
yoursite.region.portal.azurefd.net
Make sure your TTL is low during testing (300 seconds).
Step 5: Enabling HTTPS (SSL/TLS)
Once DNS is set correctly:
- Power Pages will automatically provision an SSL certificate
- Status will change to Secure
- Microsoft uses Azure-managed certificates (via Azure Front Door)
You don’t need to buy SSL separately, but you can manage custom certificates if required via Azure.
4. Optional: Redirect Root Domain to Subdomain
If you’re using www.yourcompany.com for the portal, and you want users to also reach your site by typing just yourcompany.com, configure the following:
- Use your DNS provider to create a 301 redirect from root domain to
www.yourcompany.com - This may require URL forwarding or an A record setup pointing to a static IP or redirect service
5. Managing and Editing Domains
In the Admin Center:
- You can view all linked custom domains
- Set a primary domain
- Remove, add, or replace domains
Best practice: always test the new domain before making it the primary.
6. Troubleshooting Tips
| Issue | Resolution |
|---|---|
| DNS validation fails | Ensure the TXT record is correctly added and propagated |
| CNAME not resolving | Double-check record syntax and DNS TTL |
| HTTPS not enabling | Wait a few hours or force refresh in Admin Center |
| Certificate mismatch | Delete and re-add the domain, or manage certs via Azure |
7. Security Considerations
- SSL is mandatory for all custom domains in Power Pages
- Always verify your DNS entries are not overwritten
- Use role-based access to restrict who can modify domain settings
8. Best Practices
- Use www subdomain instead of root for better compatibility
- Keep a backup of your DNS settings before making changes
- Use short TTLs while configuring, then increase after everything is stable
- Monitor using Azure Front Door metrics or Application Insights