<?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 Dynamic Object doesn't include all required Teams assets in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Microsoft-Teams-Dynamic-Object-doesn-t-include-all-required/m-p/159054#M27803</link>
    <description>&lt;P&gt;We added a specific rule allowing traffic for the dynamic objects "Microsoft Teams" and various sub-objects relative to Microsoft Teams, but upon attempting to connect to a Microsoft Teams meeting, or even to navigate to Microsoft's website to download the Teams client as an end user I am seeing logs being subject to SSL Inspection and the browser cannot load the page, never-ending spinning icon.&lt;/P&gt;&lt;P&gt;I cross-referenced Microsoft's published site list for Microsoft Teams and learned some of the required URL's are not part of the Checkpoint Dynamic Object for Microsoft Teams.&lt;/P&gt;&lt;P&gt;Who controls these dynamic objects and how can we get them updated so they function as intended without us having to manually manage bypass exception URL's?&lt;/P&gt;&lt;P&gt;R81.10&amp;nbsp;&lt;/P&gt;&lt;P&gt;Rule: Source:" Any" Destination: "Internet" Services and Applications: "Microsoft Teams, Microsoft Teams-download,&amp;nbsp;Microsoft Teams-editing,&amp;nbsp;Microsoft Teams-posting,&amp;nbsp;Microsoft Teams-upload,&amp;nbsp;Microsoft Teams-Web Tab"&amp;nbsp; Action: "Accept"&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Log shows HTTPS inspection of the following URL's at the time the browser fails to load Teams:&lt;/P&gt;&lt;P&gt;statics.teams.cdn.office.net&lt;/P&gt;&lt;P&gt;img.teams.skype.com&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Microsoft lists skype.com as part of the Microsoft Teams infrastructure.&lt;/P&gt;&lt;P&gt;&lt;A href="https://learn.microsoft.com/en-us/microsoft-365/enterprise/urls-and-ip-address-ranges?view=o365-worldwide#skype-for-business-online-and-microsoft-teams" target="_blank"&gt;https://learn.microsoft.com/en-us/microsoft-365/enterprise/urls-and-ip-address-ranges?view=o365-worldwide#skype-for-business-online-and-microsoft-teams&lt;/A&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 07 Oct 2022 23:51:51 GMT</pubDate>
    <dc:creator>indeliblelibel</dc:creator>
    <dc:date>2022-10-07T23:51:51Z</dc:date>
    <item>
      <title>Microsoft Teams Dynamic Object doesn't include all required Teams assets</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Microsoft-Teams-Dynamic-Object-doesn-t-include-all-required/m-p/159054#M27803</link>
      <description>&lt;P&gt;We added a specific rule allowing traffic for the dynamic objects "Microsoft Teams" and various sub-objects relative to Microsoft Teams, but upon attempting to connect to a Microsoft Teams meeting, or even to navigate to Microsoft's website to download the Teams client as an end user I am seeing logs being subject to SSL Inspection and the browser cannot load the page, never-ending spinning icon.&lt;/P&gt;&lt;P&gt;I cross-referenced Microsoft's published site list for Microsoft Teams and learned some of the required URL's are not part of the Checkpoint Dynamic Object for Microsoft Teams.&lt;/P&gt;&lt;P&gt;Who controls these dynamic objects and how can we get them updated so they function as intended without us having to manually manage bypass exception URL's?&lt;/P&gt;&lt;P&gt;R81.10&amp;nbsp;&lt;/P&gt;&lt;P&gt;Rule: Source:" Any" Destination: "Internet" Services and Applications: "Microsoft Teams, Microsoft Teams-download,&amp;nbsp;Microsoft Teams-editing,&amp;nbsp;Microsoft Teams-posting,&amp;nbsp;Microsoft Teams-upload,&amp;nbsp;Microsoft Teams-Web Tab"&amp;nbsp; Action: "Accept"&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Log shows HTTPS inspection of the following URL's at the time the browser fails to load Teams:&lt;/P&gt;&lt;P&gt;statics.teams.cdn.office.net&lt;/P&gt;&lt;P&gt;img.teams.skype.com&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Microsoft lists skype.com as part of the Microsoft Teams infrastructure.&lt;/P&gt;&lt;P&gt;&lt;A href="https://learn.microsoft.com/en-us/microsoft-365/enterprise/urls-and-ip-address-ranges?view=o365-worldwide#skype-for-business-online-and-microsoft-teams" target="_blank"&gt;https://learn.microsoft.com/en-us/microsoft-365/enterprise/urls-and-ip-address-ranges?view=o365-worldwide#skype-for-business-online-and-microsoft-teams&lt;/A&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 07 Oct 2022 23:51:51 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Microsoft-Teams-Dynamic-Object-doesn-t-include-all-required/m-p/159054#M27803</guid>
      <dc:creator>indeliblelibel</dc:creator>
      <dc:date>2022-10-07T23:51:51Z</dc:date>
    </item>
    <item>
      <title>Re: Microsoft Teams Dynamic Object doesn't include all required Teams assets</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Microsoft-Teams-Dynamic-Object-doesn-t-include-all-required/m-p/159061#M27808</link>
      <description>&lt;P&gt;Usually the list is 1:1 aligned to that provided by Microsoft to my knowledge, is it there under a different section or entirely missing?&lt;/P&gt;
&lt;P&gt;Have you reported / investigated this with TAC?&lt;/P&gt;
&lt;P&gt;&lt;a href="https://community.checkpoint.com/t5/user/viewprofilepage/user-id/22913"&gt;@Micky_Michaeli&lt;/a&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 08 Oct 2022 11:55:33 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Microsoft-Teams-Dynamic-Object-doesn-t-include-all-required/m-p/159061#M27808</guid>
      <dc:creator>Chris_Atkinson</dc:creator>
      <dc:date>2022-10-08T11:55:33Z</dc:date>
    </item>
  </channel>
</rss>

