<?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 Microsoft Teams client - IP of GP network adapter impacting location-based emergency calling in GlobalProtect Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/microsoft-teams-client-ip-of-gp-network-adapter-impacting/m-p/1225247#M6619</link>
    <description>&lt;P&gt;When at campus our Teams clients are associated with the GP interface IP, which is causing an issue with our dynamic emergency calling that utilizes subnets and WAPs to provide 911 dispatch the proper location of the caller (Ray Baums Act).&amp;nbsp; We have split-tunnel to the Microsoft Teams IP ranges, but the local Teams client is still associating with the GP interface IP.&amp;nbsp; &amp;nbsp;We have reasons to keep GP always on but also need compliance with Ray Baums Act.&amp;nbsp; Any insights on how to address this?&amp;nbsp; Thanks!&lt;/P&gt;</description>
    <pubDate>Mon, 31 Mar 2025 19:24:21 GMT</pubDate>
    <dc:creator>jt.elliott</dc:creator>
    <dc:date>2025-03-31T19:24:21Z</dc:date>
    <item>
      <title>Microsoft Teams client - IP of GP network adapter impacting location-based emergency calling</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/microsoft-teams-client-ip-of-gp-network-adapter-impacting/m-p/1225247#M6619</link>
      <description>&lt;P&gt;When at campus our Teams clients are associated with the GP interface IP, which is causing an issue with our dynamic emergency calling that utilizes subnets and WAPs to provide 911 dispatch the proper location of the caller (Ray Baums Act).&amp;nbsp; We have split-tunnel to the Microsoft Teams IP ranges, but the local Teams client is still associating with the GP interface IP.&amp;nbsp; &amp;nbsp;We have reasons to keep GP always on but also need compliance with Ray Baums Act.&amp;nbsp; Any insights on how to address this?&amp;nbsp; Thanks!&lt;/P&gt;</description>
      <pubDate>Mon, 31 Mar 2025 19:24:21 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/microsoft-teams-client-ip-of-gp-network-adapter-impacting/m-p/1225247#M6619</guid>
      <dc:creator>jt.elliott</dc:creator>
      <dc:date>2025-03-31T19:24:21Z</dc:date>
    </item>
    <item>
      <title>Re: Microsoft Teams client - IP of GP network adapter impacting location-based emergency calling</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/microsoft-teams-client-ip-of-gp-network-adapter-impacting/m-p/1250729#M7322</link>
      <description>&lt;P&gt;This was the fix posted by another user. Did you happen to find a fix for this?&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;P&gt;We have resolved the issue by adding route 24.24.24.24/32 in the excluded routes of GlobalProtect split tunnel settings.&lt;/P&gt;
&lt;P&gt;We received this suggestion by PA support, and it worked! We really can't understand why (what is 24.24.24.24/32?????) but it worked.&lt;/P&gt;
&lt;P&gt;I hope it will be useful for someone else.&lt;/P&gt;</description>
      <pubDate>Mon, 23 Mar 2026 16:23:58 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/microsoft-teams-client-ip-of-gp-network-adapter-impacting/m-p/1250729#M7322</guid>
      <dc:creator>MikeFlippinCSA</dc:creator>
      <dc:date>2026-03-23T16:23:58Z</dc:date>
    </item>
  </channel>
</rss>

