Teams is coming – it’s going to Skype for Business Online – which we know – though the Skype for Business server will still be there for on-prem use. Teams works arguably better in a purely online scenario, since Skype for Business has its roots in a different era, where infrastructure was nearby and closely managed,
The Lync / OCS / LCS application family has been with us for a while now, and Skype for Business is largely a 2015-era re-branding and update of Lync, which itself dates back to 2010.
Back in the OCS days, it was assumed you had a server on-premises (style note – the opposite of “in the cloud” is “on-premises”, ie in or on the premises you have, possibly abbreviated to “on-prem”. It is definitely not, ever, “on-premise”. If you are on-premise, that means you’re in agreement with a point of view, not that you still run your own datacent(re|er)…), not an assumption that you’d make today, with flexible working and Wi-Fi everywhere.
Anyway, as well as having on-prem kit that’s quite possibly connected to a physical phone system, Lync/S4B largely assumed your client (wired to a LAN) connected to a local server. That communicated to other clients and servers in the same environment (mostly) and, maybe via a gateway, to the outside world for the POTS. How cool it was to click a link in the communicator client, and next thing your desk phone was calling that number!
As Teams imminently starts to replace Skype for Office 365 customers, we’re seeing lots of best practice guides and other resources for successful adoption. Further Teams ToWs will follow as well – in fact, if you have one you’d like to share, please write it up and send it over.
This week’s tip focuses – or rather doesn’t – on a very cool trick when using Teams for video calling: the ability to blur your background, so as to remove distractions for other parties in the call. There’s a great short video ad illustrating the feature, here. See it in action here.