Unable to use route in base URL

[rcarrigan]

We're preparing to deploy a new Power Apps Portal to our custom domain, but we're running into an issue. We want the portal to be based off a specific route (e.g. example.com/en-us/portal/*) rather than the root of the domain (e.g. example.com/*). We've figured out how to add the locale specification (e.g. 'en-us') by configuring multilingual, and we've made all assets (files, pages, etc.) children of the 'portal' page, so the correct pages load when you navigate around the site (e.g. navigating to example.com/en-us/portal/child-page-1 correctly displays 'child-page-1'). Unfortunately, all OOB assets (CSS files, JS files, authentication pages) fail to load (404) because the portal is trying to access them from the root of our custom domain, which points to an entirely different web server.

Preferably, we'd want to change the base URL for the portal to include the route ('/portal') after the locale specification, as that would most likely fix all 404 errors, but this doesn't seem possible within Power Apps Portals.

Has anyone encountered this issue before? If so, please let me know how you were able to resolve the issue.

[ragavanrajan]

Hi @rcarrigan 

It is possible to change the base URL. 

Official link here

From my experience. It is always the best practice to keep your assets under the (/) root. However try changing the baseurl 

Hope it helps. 
------------

If you like this post, give it a Thumbs up. Where it solved your request, Mark it as a Solution to enable other users to find it.

[rcarrigan]

Hi @ragavanrajan , thank you for your suggestion, but changing the base URL (aka Website Primary Domain Name) to include the '/portal' route (aka partial URL) doesn't have any effect. I'm continuing to do research in the Power Apps Portals/Power Pages docs, but so far it seems like our only options are either:

1. live with the 404 errors generated by OOB resources not being found, PLUS use an alternate authentication process, or
2. add a CNAME DNS record which directs requests for 'portal.example.com' to 'exampleportal.powerappsportals.com'

This limitation somewhat makes sense, as directing website traffic to different servers based on the route rather than a subdomain is uncommon, however considering Microsoft does this exactly AND develops Power Apps Portals/Power Pages, I would have expected an OOB solution for this scenario.

If anyone else has any suggestions, I welcome them. I will also make sure to update this thread once we have decided on a solution.

[rcarrigan · Accepted solution]

Unfortunately, it is not possible to change the base URL of a Power Apps Portal / Power Pages website to include a partial URL (e.g. example.com/en-us/portal/*). This is most likely due to DNS limitations, as there is a similar restriction there.

My solution/workaround was to configure a subdomain for the website (e.g. portal.example.com) instead.