Hi, in this document under "Common URLs for all locations" you effectively recommend we exclude *.blob.core.windows.net from TLS intercept. Although you also state "Do not disable security monitoring or inspection of these URLs, but allow them as you would other internet traffic" that is misleading as we know Defender ATP uses certificate pinning at the client level. Therefore TLS intercepting some (all?) of these sites may break Defender ATP connectivity to the MS cloud service. Can you please explicitly state which of these URLs rely on certificate pinning and/or remove *.blob.core.windows.net from the list and explicitly call out the blob storage URLs required like done here: https://docs.microsoft.com/en-us/windows/security/threat-protection/windows-defender-antivirus/configure-network-connections-windows-defender-antivirus#allow-connections-to-the-windows-defender-antivirus-cloud-service
Thank you
⚠Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
@phillym - Thank you for submitting feedback.
I will get this issue over to the Win10 ITPro writing team for investigation.
Thank you for reporting and making the docs better. Much appreciated.
I made a note to request the team to update this when the work is complete.
@mjcaparas - Can you please share your insights on this issue?
Thank you.
Hi @phillym - reaching out engineering team. I'll try and update the topic shortly.
@mjcaparas - Do you have any updates on this?
Thank you.
cc: @kenwith
Hi @mypil and team,
Do we have any updates on this?
Thanks!
phillym
@phillym - I have already reached out to the author @mjcaparas to get some updates on the progress of this issue.
We will let you know as soon as we get some response. Thank you for your patience.
The page has been updated: