"Deploying applications using the wildcards helps us ensure that our users have access to more of the resources they need."
Figure 1. Application Settings Including a Wildcard in the URLsAll applications in scope of the wildcard can be accessed by the same set of users and groups that are assigned to the application. Applications published through a wildcard need the same type of single sign-on method. Each of the published applications can be accessed by the users and groups that are assigned to the wildcarded application. If the application uses Windows Integrated Windows Authentication, you will also need a wildcard in the Single Sign-On settings if the SPN is not the same across applications.
Figure 2. Wildcard in Single Sign on settings for an application with Windows Integrated Authentication
The settings and access for the most specific URL always take precedence over wildcards. To learn more about how to exclude applications from a wildcard publishing, see our documentation . We believe wildcards will help you use Azure AD Application Proxy to give your users access to more of the resources they need. Wildcards can also help you ensure consistent access and settings for applications that share common requirements. Several of our private preview customers have told us that they plan to use wildcards to publish and manage dozens of applications at once! To learn more about wildcards and Azure AD Application Proxy, see the documentation . To begin publishing an application, sign in to the Azure AD Admin Center . If you have feedback or feature requests related to this new capability, please let us know in the Application Proxy section of our feedback forum . Or feel free to email us at firstname.lastname@example.org . Best regards, Alex Simons (Twitter: @Alex_A_Simons ) Director of Program Management Microsoft Identity Division
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.