Skip to content

Commit 061ac99

Browse files
authored
Merge pull request #110585 from japere/patch-71
removed limitation on using a proxy for backend
2 parents 348adec + 3233e5d commit 061ac99

File tree

1 file changed

+0
-4
lines changed

1 file changed

+0
-4
lines changed

articles/active-directory/manage-apps/application-proxy-faq.md

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -45,10 +45,6 @@ No, this scenario isn't supported. The default settings are:
4545

4646
For recommendations, see [High availability and load balancing of your Application Proxy connectors and applications](application-proxy-high-availability-load-balancing.md).
4747

48-
### Can I place a forward proxy device between the connector server(s) and the back-end Application server?
49-
50-
No, this scenario isn't supported. Only the connector and update services can be configured to use a forward proxy for outbound traffic to Azure. See [Work with existing on-premises proxy servers](https://docs.microsoft.com/azure/active-directory/manage-apps/application-proxy-configure-connectors-with-proxy-servers)
51-
5248
### Is TLS termination (TLS/HTTPS inspection or acceleration) on traffic from the connector servers to Azure supported?
5349

5450
The Application Proxy Connector performs certificate-based authentication to Azure. TLS Termination (TLS/HTTPS inspection or acceleration) breaks this authentication method and isn't supported. Traffic from the connector to Azure must bypass any devices that are performing TLS Termination.

0 commit comments

Comments
 (0)