Office 365

Microsoft announced some Office 365 certificate changes last year: https://learn.microsoft.com/en-us/microsoft-365/compliance/encryption-office-365-tls-certificates-changes?view=o365-worldwide If you’re using Microsoft Teams Direct Routing you need to apply a new root certificate to your SBCs. More specifically if your SBC has “TLS Mutual Authentication” enabled on the Teams SIP interface then you MUST make this change. I would recommend making this change anyway and ASAP! How to check if TLS Mutual Authentication is enabled? Log into your AudioCodes SBC, navigate to Setup > Signalling and Media > Core Entities > SIP Interfaces. ...

Big shout out to Kieran Lloyd for suggesting this: https://uk.linkedin.com/in/kieranlloyd Teams now has a Push To Talk feature on the desktop app by pressing {ctrl} +{ space}. This is a bit like a Walkie Talkie, holding the PTT keys will unmute you then automatically mute you again upon release. https://support.microsoft.com/en-au/office/using-audio-in-teams-17886394-9a9a-4f04-b4cc-e46589408b28 Whilst discussing Push To Talk, Kieran mentioned he had programmed one of his Logitech Mouse buttons to send {ctrl} + {shift} + M to mute and unmute Teams. He then mentioned he should configure another mouse button to send {ctrl} + {space} to use PTT with his mouse! ...

Here are the various errors I encountered helping a customer re-install Cloud Connector Edition and the fixes for them. Enabling credential delegation for NTLM on host machine. Enabling credential delegation for NTLM on host machine. The installation hangs whilst running “Enabling credential delegation for NTLM on host machine.” This fix is actually posted in the Q&A here: https://gallery.technet.microsoft.com/lync/Step-by-Step-Configure-23d8cd42/view/Discussions although the original poster does not confirm if the solution worked. I can confirm it does work. ...

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: ...

Over the past few days I have started getting an error when replying to people in Microsoft Teams. “Due to an org policy change, you can enjoy a richer chat and calling experience. Continue your conversation here.” I’m not 100%, but I think I know why this is happening. In my organisation everyone is in “Islands” mode (ignoring my own advice here in Step 2 and 3): /2019/05/17/skype-for-business-server-to-microsoft-teams-in-10-steps/ I am one of a few users in Teams Only mode, i.e. I can no longer use SfB to initiate IMs and Calls. My SfB client is now only used to join SfB meetings. ...

If you have used Lync or Skype for Business, you will be familiar with the “Tag for Status Change Alerts” feature, AKA Tagging. If you’re not familiar, have you ever signed into SfB and someone IMs you straight away? You were most likely tagged! This feature has been missing from Microsoft Teams and has over 600 votes on User Voice: https://microsoftteams.uservoice.com/forums/555103-public/suggestions/18925360-tag-for-status-updates The last updated, posted by Alex on 07/02/2019 stated " I’m excited to announce that this feature is in internal testing, and should be coming soon! Thanks! “ ...

When connecting to Microsoft Teams or Skype Online ( https://docs.microsoft.com/en-us/office365/enterprise/powershell/manage-skype-for-business-online-with-office-365-powershell) you may experience the following error: Unable to discover PowerShell endpoint URI At C:\Program Files\Common Files\Skype for Business Online\Modules\SkypeOnlineConnector\SkypeOnlineConnectorStartup.psm1:114 char:9 + throw $resources.DiscoveringEndpointFail + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : OperationStopped: (Unable to disco...ll endpoint URI:String) [], RuntimeException + FullyQualifiedErrorId : Unable to discover PowerShell endpoint URI This occurs when your Office 365 Admin Account is not an onmicrosoft.com account. To resolve you need to specify the -OverrideAdminDomain switch on New-CsOnlineSession and specify your default O365 onmicrosoft domain. E.g: ...

Over the past month, I have had a few different SfB Server (On-Premises) customers report issues Federating with Skype Online (O365) customers. This includes customers who have SfB Hybrids and users homed online. The On-Premises customers have O365 tenants for other services and I always tell non-hybrid Skype On-Prem customers to ensure they don’t assign any Skype Online licenses to users. If they assign an E3 or E5 they should un-check the “Skype Online” license box and for many years, this has worked fine. ...

A Teams upgrade can’t be approached like a Lync 2013 >Skype for Business 2015 upgrade. These upgrades are Technology driven, 99% of the work is done by IT. Your end users probably received an email saying “From tomorrow morning your Lync client will now look like Skype ” and that’s about as much involvement as they had. Your Teams upgrade needs to be business driven, it’s a new way of way of working. ...

I get asked this quite frequently. What features are available between Teams and Skype for Business? First I must clarify that interop does not work in Islands mode. If you’re in SfB and Teams Islands, then you will experience quirky issues. You must be in one of the following modes: Teams Users = Teams Only Mode SfB Users = SfB Only, Collab Mode or Collab & Meetings Basically, if you’re in Islands today, before you move anyone to Teams Only, you need to move all users to one of the SfB Only modes, or face a broken interop model ...