<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: URL access issue in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/url-access-issue/m-p/1229168#M124305</link>
    <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/317139"&gt;@SA.Kushal&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;Assuming that you've taken packet captures and verified that you aren't seeing any return traffic, the next step is looking at the upstream. It could be that the resource you're attempting to access has just blocked all of Azure's IP ranges due to past malicious activity that they just don't want to deal with, or it could be that Azure itself is dropping the outbound traffic. &lt;/P&gt;
&lt;P&gt;Off hand, I'm not sure that Microsoft actually blocks any &lt;EM&gt;outbound&amp;nbsp;&lt;/EM&gt;traffic natively and have never heard of it doing so. I would assume that the issue is simply that the resource has either blocked your outbound IP specifically for some reason, or just has some wider blocks against Azure in general. Depending on your relationship with that service you may or may not have any true recourse here.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 15 May 2025 16:48:30 GMT</pubDate>
    <dc:creator>BPry</dc:creator>
    <dc:date>2025-05-15T16:48:30Z</dc:date>
    <item>
      <title>URL access issue</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/url-access-issue/m-p/1229167#M124304</link>
      <description>&lt;P&gt;&lt;SPAN&gt;we have one legal category url where it’s not working checked on palo and found no return traffic .So palo support told need to check with upstream as we didn’t find issue on our azure too as we use azure public IP.As we don’t manage any CDN we don’t have visibility.l weather they are blocking our azure public IP or not any suggestions?&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 15 May 2025 16:32:44 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/url-access-issue/m-p/1229167#M124304</guid>
      <dc:creator>SA.Kushal</dc:creator>
      <dc:date>2025-05-15T16:32:44Z</dc:date>
    </item>
    <item>
      <title>Re: URL access issue</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/url-access-issue/m-p/1229168#M124305</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/317139"&gt;@SA.Kushal&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;Assuming that you've taken packet captures and verified that you aren't seeing any return traffic, the next step is looking at the upstream. It could be that the resource you're attempting to access has just blocked all of Azure's IP ranges due to past malicious activity that they just don't want to deal with, or it could be that Azure itself is dropping the outbound traffic. &lt;/P&gt;
&lt;P&gt;Off hand, I'm not sure that Microsoft actually blocks any &lt;EM&gt;outbound&amp;nbsp;&lt;/EM&gt;traffic natively and have never heard of it doing so. I would assume that the issue is simply that the resource has either blocked your outbound IP specifically for some reason, or just has some wider blocks against Azure in general. Depending on your relationship with that service you may or may not have any true recourse here.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 15 May 2025 16:48:30 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/url-access-issue/m-p/1229168#M124305</guid>
      <dc:creator>BPry</dc:creator>
      <dc:date>2025-05-15T16:48:30Z</dc:date>
    </item>
  </channel>
</rss>

