An examination of the final CNAME record shows that at least 11 separate IP addresses are available across the globe! Indeed, the domain is owned by Akamai and is part of their global CDN network. The resulting IP address is 40.117.100.83, but given the usage of CDN is in play, this IP address will vary for others across the globe. Two separate CNAME records are returned for this query: The DNS query response gives us the first clue that Microsoft’s usage of CDN networks has begun to creep into its UC (IC) platform. Upon application start, Teams initially performs a DNS A record query for: Microsoft doesn’t explicity document what FQDNs are used…but Wireshark or Message Analyzer will! For Teams, there is no hybrid support – you’re all-in within the cloud. The autodiscover process is (relatively) well documented and often times poorly understood (and implemented). Sign In Process Informationįor any seasoned Lync/Skype admin, we all know that specific DNS records are required in order for the client to discover the FQDNs for the pools the accounts is homed to. 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. Updated – Including direct references to Ignite content relevant to architecture

How to use wireshark to get ip 2017