Forum Discussion
AAD Application Proxy and B2B Users
Hi, I assume you are looking to use the app proxy for organizations with on-premises apps which are using Windows authentication. We are currently working on the documentation for this scenario which should be posted to docs.microsoft.com shortly. In principle, creating an account in a AD domain corresponding to a user in Azure AD, including a guest user, would enable the app proxy to match the user coming in from Azure AD and use KCD for impersonation and permit that user to then access Windows integrated authentication, however there are a number of account lifecycle subtleties here. So even if you see the app proxy is able to permit the communication flow, I'd suggest waiting for the documentation as there are a number of deloyment considerations and best practices to look at (e.g., what container to put the users in, when to deprovision the user from AD, how to avoid RID exhaustion and end user confusion about "All authenticated users" etc) Feel free to reach out to us if you have additional questions. Thanks, Mark
I Tested this in my lab today and made things work for guest access to on premises applications via Integrated authentication as well as federated authentication by creating a shadow user in the on-premises directory.
However, the UPN passed back to my on-premises applications seems to differ in each case.
Federated Authentication seems to be passing my original UPN:
guest.user@guestdirectory.com
while Application Proxy is passing my guest UPN from the test tenant:
guest.user_guestdirectory.com#EXT#@mydirectory.com
So for now, I ended up having two different Accounts in my on-premises directory. I thought about using a different attribute, but application proxy only gives me a limited choice and I think UPN is still the most convenient pick.
Any Ideas on how to overcome this?
Has there been any progress on the documentation or is any guidance available.
- https://docs.microsoft.com/en-us/azure/active-directory/b2b/hybrid-cloud-to-on-premises