The Azure AD App Proxy now supports publishing applications using custom domain names!
This has been the single biggest request from customers and we're excited to make it available. Up until today, every application is published under a domain name that is provided and maintained by us: msappproxy.net. We take care of the certificates and DNS records for this domain. Your application is instantly published, securely in high scale and high availability guarantied. We are going to keep this quick and robust experience going forward. But, many customers want to be able to use their own domain name for published applications. The main benefit of custom domains is that your employees, partners and customers will now see branded URLs that looks familiar to them. This new capability also enables existing apps to seamlessly work with the same URLs both internally and externally. This will solve many application compatibility problems and will make all links work all the time. For example, let's consider collaboration site with its internal and external URLs being https://docs.contoso.com/ . If an employee is accessing it from your corporate network, the internal DNS will route him directly to this server. If the employee is working at a Starbucks, the public DNS will direct them to Azure AD Application Proxy which, after authentication and authorization, will let them access this app with an SSO experience. This also means that if a user receives an email or notification with embedded link to a document on that site (e.g. https://docs.contoso.com/2015budget.aspx ), the link will work in either location. To use a custom domain here's what you do:You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.