Update troubleshooting-proxy-url.md

Access and session policies support IPv4 only for reverse proxy and Edge in-browser. If the request originates from an IPv6 address, IP address-based conditions in the policy will not be honored.

Author: DeCohen

CloudAppSecurityDocs/troubleshooting-proxy-url.md

@@ -45,7 +45,7 @@ So even though Fabrikam doesn't actually use Defender for Cloud Apps, they see t
 This kind of URL is expected and indicates that your organization applies extra security controls to protect business-critical data.
 
 > [!IMPORTANT]
-> Access and session policies support IPv4 only. If the request originates from an IPv6 address, IP address-based conditions in the policy will not be honored.
+>Access and session policies support IPv4 only for reverse proxy and Edge in-browser. If the request originates from an IPv6 address, IP address-based conditions in the policy will not be honored.
 
 They do this by using Defender for Cloud Apps, a solution for protecting your organization's cloud environment, to replace all relevant URLs, and cookies relating to cloud apps that you use.
 
@@ -62,4 +62,4 @@ If you don't recognize the remaining portion of the URL, such as **myurl.com**.m
 
 - [Protect apps with Microsoft Defender for Cloud Apps Conditional Access app control](proxy-intro-aad.md)
 - [Troubleshooting access and session controls for admin users](troubleshooting-proxy.md)
-- [Troubleshooting access and session controls for end-users](troubleshooting-proxy-end-users.md)
+- [Troubleshooting access and session controls for end-users](troubleshooting-proxy-end-users.md)