We have created a way for you to access your on-premises applications in your channel through pinned tabs. This can include your SharePoint sites or other business applications.
This flow is made possible using the Azure Active Directory Application Proxy. Many customers currently use Application Proxy to provide single sign-on (SSO) and secure remote access for web applications hosted on-premises. These flows don’t use a DMZ or VPN – all traffic goes through a light-weight agent on-premises that only uses outbound connections. You can learn more about the Application Proxy flow in our documentation.
Below are the steps for adding these applications to your channel. Please note that Application Proxy does require an Azure Active Directory License, and many O365 customers already have Azure Active Directory Premium. Learn more.
The connection to the on-premises applications is made through a light-weight on-premises component, the “connector”. To configure Application Proxy, you need to install a connector on-premises. Instructions on doing so can be found here.
Once you’ve enabled the connection to your on-premises network, you need to publish the application with the external URL that you will use to pin the application to your channel. The steps for publishing an application can be found here. Before continuing to step 3, please confirm that the external URL you published is working as expected.
Finally, you can pin the application to your channel. To do so:
You can now use the tab to access the application directly from your channel!
If you’d like to learn more about Application Proxy or have any questions on this scenario, you can reach out to the team at firstname.lastname@example.org. You can also always leave your questions and comments here on this blog as well!
Azure Active Directory
Harshini Jayaram is a program manager on the Azure Identity team focused on Application Proxy. She joined Microsoft after graduating from MIT with a double major in computer science and management science. Prior to her current role she was on the Distribution and Services Platform (DSP) team, the team responsible for Windows Update among other services. In her time there, Harshini owned all DSP telemetry from client instrumentation and infrastructure through reporting and access, including for the Windows 10 and Anniversary Update launches.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.