Trying to get exposure to azure app proxy by publishing ECP (Exchange Control Panel) via app proxy. Publishing OWA (Outlook Web App) is easy, and just a matter of using the /owa virtual directory in the url. The difficulty with the ECP is that it uses a separate virtual directory, but authenticates using the /owa/auth/logon.aspx page.
The closest I've come is to set up an OWA and ECP "application", with an internal URL of https://ex2016.contoso.internal/owa
respectively. Likewise, external URL's are https://owa-contoso.msappproxy.net/owa/
When I do this, going to the ecp url routes me to the owa auth page (as expected), however once I authenticate it loops back to the owa auth page again.
Any ideas? I've tried setting the 2 apps with just the root url and then sneaking in the homepage via this method (https://blogs.technet.microsoft.com/applicationproxyblog/2016/04/06/setting-the-right-link-for-application-proxy-applications-in-the-azure-ad-access-panel-and-office-365-app-launcher/
) but all that does is try to redirect me to the actual hostname of the server.
Thoughts? Experience with this? TIA!