CloudVoiceMail

Microsoft have stated that they would retire Exchange Online UM on 28th February 2020 and it would be replaced by Cloud Voicemail. https://docs.microsoft.com/en-us/skypeforbusiness/plan/exchange-unified-messaging-online-migration-support This morning at 2:51am (29th Feb) we received the following email from Office 365 Message Centre. Ensure you have configured the Cloud Voicemail prereqs. https://docs.microsoft.com/en-us/skypeforbusiness/hybrid/plan-cloud-voicemail. One of the main requirements is a SfB Hybrid which was not required for Exchange Online UM integration. It’s still not clear what has happened to customers who have not done this. Does CVM work without a Hybrid? ...

To configure Cloud Voicemail, you should follow this guide from Microsoft: https://docs.microsoft.com/en-us/skypeforbusiness/hybrid/configure-cloud-voicemail Before I started writing this post, I knew that -Tenant should be -TenantID in SfBs 2019 (TenantID = Your Office 365 TenantID). I have successfully configured customers with CVM using this method. When trying to get a screenshot from a working environment -TenantID was missing! Doing some further investigation it looks like the latest SfBs 2019 CU removes -TenantID (and even -Tenant) from the Set/New-CsHostedVoicemailPolicy cmdlet. ...

There doesn’t appear to be any obvious way to check if you have been migrated from Exchange Online UM to Cloud Voicemail in O365, other than calling your Voicemail box and checking to see if the announcement is different. I have been through various settings in O365 Remote PowerShell for different customers and can’t find anything concrete (Sorry SfBo customers). SfB Server customers can use the Skype for Business Monitoring Reports to identify if users have been migrated. Calls diverted to Voicemail will show RTCC/7.0.0.0 LyncTeamsGateway/1.1.319.0 rather than RTCC/5.0.0.0 MSExchangeUM/15.20.2686.025. But that’s not very fun, so here is a script to do it for you: ...