Changing AppPortal to use FQDN instead of <servername>/esd

[TeriStevenson]

We installed AppPortal back in 2015 using just the server name and set a DNS alias for it.  Edge was just implemented company wide nd when users access the site either by using the DNS alias or <servername>/esd they get the Not Secure warning in the browser.  They're asking if App Portal can use the FQDN instead of them having to set an override security restriction in Edge (Microsoft Edge Browser Policy Documentation | Microsoft Docs).

What changes would we need to make on the App Portal side if we chose to use the FQDN?  Would it require changing any application pools or web config file?

[CharlesW · Accepted solution]

Ultimately, App Portal should not care if a DNS Alias or a FQDN is used to access the site.. I've always been under the impression that an alias is used more for end user convenience, than anything else. Obviously, it also facilitates changing servers down the road, as you only need to change the DNS alias to point to the new server.. About the only thing that you would have to change in App Portal, if you wished to eliminate the use of an alias would be to set the "Site DNS Alias" setting under settings->website..  This setting is predominately used to build links in notifications, but it is also used for a few small maintenance items in App Portal..