With that in mind, what follows are pieces of information I was able to gleam, with the caveat that the information will be updated/corrected later on, as Microsoft begins to release official information that will supersede the info I have here. Given that this information will begin to come out over time as Microsoft enhances Teams with the IT-policy controls and documentation that existed for Skype4B, I realized that some insights can be gathered by some old-fashioned manual work: that’s right…simple network traces have proven to be hugely informational and provides a peek into the inner-workings of Teams. The back-end processes and infrastructure of Microsoft Teams is a bit of a mystery with limited technical information when compared to Lync/Skype for Business. While much can be said about the pros & cons of this approach, the end result is that customers and partners (myself included) must change and adapt. The big news that Microsoft intends to (eventually) sunset Skype for Business Online in favor of Microsoft Teams has once again significantly altered the trajectory of partners and customers consuming Microsoft’s communications services.
Ignite 2017 has turned out to be quite the stir for Unified Communications…err…I mean, Intelligent Communications. For me, that' s good enough for a temporary work-around.Updated – Including direct references to Ignite content relevant to architecture However, the above addresses have been stable for at least the last year or two. I realize these are static addresses and that Skype addresses are potentially dynamic. Just put them as destination addresses in a separate policy that does not have SSL inspection turned on. (Credit to for the script and address info.) If you don' t want to enter all 107 unique Skype addresses into the firewall, you can come close by using these class C' s: These Skype IPs can be found by running this BASH script:įor i in do dig +short dsn$i. done | sort | uniq There appears to be a Skype login problem (at least with my config) if SSL certificate inspection is turned on. I have a workaround in place for now by whitelisting all the IP' s associated with Skype logins.
I have an open ticket with FTNT on this issue. I' m replying to my own post in case anyone else finds this useful.
0 kommentar(er)
