In this post we are going to look at some of the under the hood of Microsoft Teams. During the keynote it was mentioned over and over again it was “Skype”. But what does that mean? You might ask, this is a business product so it must be built on top of Skype for Business but that isn’t the case at all.
So let’s look at each modality.
If we send a message we see two different JSON events. First, we see a typing command to update the team so they know I’m in the processing of replying.
Then when the message is actually sent we see this JSON message.
So there are a few items of note that we should discuss at this time:
- This is absolutely not Skype for Business under the hood. Microsoft has talked about the next gen Skype Consumer network and this is clearly go to that environment.https://st-client-ss.msg.skype.com/v1/users/ME/conversations/19%3A2a9ad786-8a9b-409c-a29a-19666d549187_fabf899c-a61b-44a3-9623-d269342541b4%40unq.gbl.spaces/messages
- This is all driven via JSON and web services. If you look at the language that is being used this is a very modern interface that is be used by several other players in the market.
Audio and Video Sessions
When you join an Audio/Video session we can see a very similar JSON setup experience. First, here is sent to the Teams Server. Some interesting URLs.
And here is the response:
Again, we see the full URL here: https://api.conv.skype.com/conv/
So again, we see the entire meeting experience is built on top of the Skype Consumer network. So the key item to know is that Teams sits on that next generation Skype Consumer network and is most likely one step to a much larger consolidation.