Microsoft Teams Dynamic Object doesn't include all required Teams assets

[indeliblelibel]

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.

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.

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?

R81.10 

Rule: Source:" Any" Destination: "Internet" Services and Applications: "Microsoft Teams, Microsoft Teams-download, Microsoft Teams-editing, Microsoft Teams-posting, Microsoft Teams-upload, Microsoft Teams-Web Tab"  Action: "Accept"

Log shows HTTPS inspection of the following URL's at the time the browser fails to load Teams:

statics.teams.cdn.office.net

img.teams.skype.com

Microsoft lists skype.com as part of the Microsoft Teams infrastructure.

https://learn.microsoft.com/en-us/microsoft-365/enterprise/urls-and-ip-address-ranges?view=o365-worl... 

[Chris_Atkinson]

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?

Have you reported / investigated this with TAC?

@Micky_Michaeli