Skype for Business Online Being Retired in July 2021

So....the news we've been expecting for a long time has finally been announced - Skype for Business Online is being retired in July 2021.

Not a huge surprise, we all knew it would happen at some stage, but two years away should be long enough for any business using Skype for Business Online to be able to get their migration to Microsoft Teams planned and executed. If you want to know about the options for migrating to Microsoft Teams, the migration routes are explained here.

It's important to note though that Skype for Business Server (the on-premises version) is not affected by this announcement.

What else has been announced?

There are some other snippets in the Microsoft announcement:

  • Dynamic E911: this is a big deal for US-based organisations, and is an improvement over what is currently offered within Skype Online. In the US, if you call the emergency services, your call needs to be routed to one of over 6,000 Public Safety Answering Points, or PSAPs, depending on where you are. Right now, this can be configured with Microsoft Teams using Calling Plan, but only in a static manner, that is, your call will be routed to a particular PSAP based on your configured location for your DID number. So if your configured location is New York but you're on a work trip to California, your call will still be routed to New York. With dynamic E911, Teams will be able to work out where you are located and route the call correctly. This is now promised for the end of 2019.
  • Retention periods down to 1 day: again, for some customers, this is a Big Deal. Some customers' legal departments do not want yet another place where data can be stored which needs to be included in any Discovery request. It's a big issue because Skype for Business doesn't really store 'chat' data (it's just sent from one client to the other), so there never was anything to 'Discover' (it was just stored on each client, and you could easily configure the client not to keep chat data). Again, this is promised for the end of 2019.
  • Teams to Skype Consumer interop: possibly something of an edge case, but clearly enough customers made enough noise to Microsoft that they have now promised to deliver this by first quarter 2020.
  • Contact Centre Integration and Compliance recording: this isn't a new announcement as it was actually announced earlier this month. There's no specific timeframe for this as yet, however.

Comments

Post a Comment

Popular posts from this blog

Microsoft Whiteboard and Teams

Image
If you've tried to use the preview Whiteboard in Teams , you might have been a bit frustrated by its limitations. Currently, you can 'ink' - but that's about it. If your handwriting (with a mouse, anyway....) is as bad as mine, that's not great if you want to put text on your whiteboard. There also doesn't appear to be a way, from Teams, to export your creation. But there is a (relatively) easy workaround to get more functionality, it is actually documented in the Microsoft article Use Whiteboard in Microsoft Teams . Step 1 - install the Windows 10 Microsoft Whiteboard app from the Microsoft Store. Step 2 - Once it's installed, run the Whiteboard app and sign in with your Office 365 credentials, then close Whiteboard. Step 3 - Start your Teams meeting, click on the Share button and share a whiteboard (sometimes that menu item isn't immediately visible - scroll to the far right). Step 4 - Open the Windows 10 Whiteboard app, and you'll
Read more

Poly CCX Phones and Time

Image
  Came across an annoying issue with Poly CCX Teams phones this week, so worth documenting here briefly to save others the same pain. In short: The phones log into Office 365 and MUST have the time accurate to within 5 minutes, otherwise they will not log on. Indeed, if they drift, they will stop working. Out of the box, they will try and get time over NTP from time.windows.com, and fall back to north-america.pool.ntp.org. If you do not have port 123 open to the Internet from the network where the phones will sit, then you can get them to look at an on-prem NTP server, but there is a major gotcha.  You can configure DHCP scope option 42 to point at your on-prem NTP server (usually, in a Windows environment, a local domain controller) however that's not enough - you also need to tell the phone NOT to override this setting: because out of the box, it does . So to get a phone working in such an environment, you may need to follow these steps (assuming you do have Scope Option 42 appro
Read more

Facebook Portal - and Zoom

Image
 I've been doing some evaluation this week on a Facebook Portal unit - and especially using it with Zoom. These days, lots of us are spending lots of time on Zoom calls for social and other purposes, but my own use-case was to see how easy it would be to use with Zoom for an 89-year old friend, who has never used a tablet or anything similar. I have to say - I'm really impressed with it. You can catch some details in my YouTube video: About Portal Facebook have a number of different-sized Portal units - you can see the different types here . You can use them to make and receive calls on Facebook Messenger and WhatsApp. I tried the 10"Portal unit and subsequently bought my own Portal Mini 8" unit. Getting Started The unit is very attractively boxed. Physical setup is just a matter of plugging in the (proprietary) power cable at the back, using a giant plug which also acts as the stand. There is also a USB-C socket hidden away at the back, next to the woofer. I didn'
Read more