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.
