Quick update here that we’re still planning to do this. It will take us some time to complete, but we’ve heard your feedback and know how important it is.
In the meantime we would love to hear more about the type of data points you would like to see.
35 votesunder review · 3 comments · Azure Active Directory » Application Proxy · Flag idea as inappropriate… · Admin →
We are looking at enabling a feature that focuses on supporting CORS preflight requests between two applications. This works by allowing you to configure the response and have App Proxy handle it on behalf of the app.
A pre-requisite for this feature to work is that the user must be able to authenticate into the second application in order to avoid a CORS issue from the login flow into the second app.
To avoid this the user will have to make sure they have already accessed the 2nd application before the CORS request, and has valid credentials. This should work for wildcard apps and can also be achieved by adding a fake link / image to the 2nd application in the first application.
We would love to get your feedback on this requirement and if this is something that will fit your use case.
An error occurred while saving the commentAnonymous commented
We too have a SaaS that needs to do a CORS access to our on-premises server which is exposed through Azure AD App Proxy with pre-auth enabled. We're getting 403 errors when CORS pre-flight requests are being sent. It would be great if there's a way to allow such traffic to passthrough
Thank you for all the votes. We need more feedback on your scenarios. If you would like to get in touch with us for a discussion, please fill this form: https://aka.ms/ApplicationGatewayCohort
This capability is under review. Thanks for the input.
/Shantaram – Program Manager