Source note · Web proxies and TLS inspection that break UC clients
Microsoft states that TLS break and inspect and proxy authentication are incompatible with both the Optimize and Allow categories of Microsoft 365 endpoints, so Allow endpoints sent to a proxy must be listed there to bypass further processing.
Checked 2026-10-14
For example, TLS break and Inspect and Proxy Authentication are incompatible with both the Optimize and Allow category endpoints.
- Vendor
- Microsoft
- Product
- Microsoft 365
- Subsystem
- endpoint categories
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- current as of 2026-10-14
- Checked
- 2026-10-14
Sources
- Managing Microsoft 365 endpoints — Microsoft · tier 2 current vendor documentation · Use a PAC file for direct routing of vital Microsoft 365 traffic, paragraph beginning 'Separately if you choose to only do direct routing'; also Proxy server bypass processing of Microsoft 365 network traffic
Cite this note
APA
WarmTransfer. (2026, October 14). Web proxies and TLS inspection that break UC clients: source note tls-inspection-uc-clients-m365-optimize-allow-no-tls. WarmTransfer. https://warmtransfer.net/knowledge/claims/tls-inspection-uc-clients-m365-optimize-allow-no-tls
BibTeX
@misc{warmtransfer-claim-tls-inspection-uc-clients-m365-optimize-allow-no-tls,
title = {Web proxies and TLS inspection that break UC clients: source note tls-inspection-uc-clients-m365-optimize-allow-no-tls},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/tls-inspection-uc-clients-m365-optimize-allow-no-tls},
note = {Source note tls-inspection-uc-clients-m365-optimize-allow-no-tls, checked 2026-10-14}
}