I’m excited to share three feature updates that will help you connect more on-premises resources to Azure AD for your remote users through Azure AD Application Proxy. As of today:
- Support for our first application using websockets, Qlik Sense, is in Public Preview!
- Application Proxy cmdlets in Powershell are generally available
- Wildcard application publishing is generally available
We hope you’ll try these out and let us know what you think!
Our first app using websockets, Qlik Sense, is in Public Preview
You can now publish several applications that connect using websockets. As one of our preview customers said:
“Enabling the websockets feature was as easy as the rest of our Application Proxy deployment.”
To join this preview, make sure you have the newest Connector, version 1.5.612.0, or download it here. Before going any further, be sure your websocket application uses a Connector Group that only includes these Connectors.
The websocket application doesn’t have any unique publishing requirements, and can be published the same way as all your other Application Proxy applications.
Qlik Sense is one of the most requested apps for use with our Application Proxy, so we’ve worked with the Qlik team to create a walkthrough for that deployment. We are excited to have this first app working for the public preview and once we’ve ironed out the kinks, we will expand to other apps.
If you have other applications you’d like us to support, let us know.
Application Proxy cmdlets are Generally Available (GA)
Using PowerShell helps you build and maintain a standardized and predictable process for deploying Application Proxy applications in your environment. The Application Proxy cmdlets we’ve had in public preview are now GA and available in our PowerShell module. Download the GA module or learn more about the cmdlets available in this release. The cmdlets include:
- Creating an application
- Viewing all Connectors in a specific Connector Group
- Configuring SSO settings for an application
- Most other administrative controls for Azure AD Application Proxy
Wildcard Application Publishing is Generally Available
Using wildcards(*) to publish many applications reduces your administrative work, reduces opportunities for error, and helps make your users more efficient. We previously announced the public preview for this feature. It is now GA.
To create a wildcard application, just publish the application the same way you would any other applications. With this new feature you can now include a wildcard (*) in both your internal and external URLs. All applications that are in scope of the wildcard can be accessed using Azure AD application proxy.
As always, if you have feedback or suggestions related to any of these features, please let us know in the Application Proxy section of our feedback forum. Or feel free to email us at firstname.lastname@example.org.
Alex Simons (Twitter: @Alex_A_Simons)
Director of Program Management
Microsoft Identity Division