04-01-2019 02:08 PM
04-01-2019 02:08 PM
I'm looking for clarification about the "Voicemail is now available for all VoIP-enabled users in Microsoft Teams" announcement published on March 29 in the Office 365 Message Center.
First, can someone explain what "VoIP-enabled user" means? I'm guessing it means a user with a Teams license but no Phone System license. Am I correct about that?
Can calls to a Phone System Auto Attendant or a Call Queue be routed to these "VoIP-enabled" users?
We've been looking for a solution for departments needing a shared voicemail. Could we assign a Teams license to a shared mailbox and redirect calls from an Auto Attendant to it? Or forward a call from a Call Queue when the caller has been waiting for a certain amount of time?
04-01-2019 04:25 PMSolution
A VoIP enabled user is any user that is enabled to make audio calls both between users in the organisation and over federation. So yes, I concur with your summary so long as their setting are not changed from the default - "a user with a Teams license but no Phone System license"
Call agents require a Phone System licence to be able to receive calls.
At the moment I don't believe shared Mailboxes can be enabled for VM.
04-01-2019 04:26 PM
This is an exciting announcement. Any idea on what the functionality will look like for users without Exchange Online (using Exchange on-prem)?
04-01-2019 05:43 PM - edited 04-01-2019 05:43 PM
This is only set to work with Cloud Voicemail, not Exchange UM. MS Teams users have always been enabled for Cloud Voicemail though, Exchange UM was never an option there.
Cloud Voicemail will be able to deposit the voicemail for the user in a mailbox be it online or on-premises.
04-02-2019 04:25 AM
Is it really correct that the user does not need a phone system license or a calling plan? The information is a bit unclear I think? Also is it possible to leave a voicemail by just calling using Teams or do you need to call using a phone number?
04-02-2019 08:31 AM
@Nathan Berger Assuming the experience is the same as it is for users with a Phone System license, a user with an on-prem mailbox will only receive the voicemail in their Outlook mailbox. Teams will indicate that a voicemail has been received with an entry in the Activity feed, but when you click on it you will just get a message saying "We can't get your voicemail right now".
Note that the voicemail emails have a Return-Path address of the form firstname.lastname@example.org. If you are using a third-party spam filter that blocks incoming messages with a spoofed Return-Path, you will need to whitelist the SMTP servers listed at https://docs.microsoft.com/en-us/office365/enterprise/urls-and-ip-address-ranges.
04-23-2019 10:59 AM
Random but trying to troubleshoot 2/14 users who cannot access their voicemail via Teams, it always says "we can't get your voicemail right now". We migrated to Office 365 and Exchange in the cloud in 2016... Based on your description I was wondering if there could be some glitch where it thinks the user still has an on-prem mailbox or something? Grasping at straws here. As you described also, the two users see the voicemail in their activity feed and have no trouble getting the voicemail emails in Outlook but they still cannot access Voicemail in the Teams Desktop app. All our users re on E5 plans w/ Phone System and have domestic calling plans.
04-30-2019 07:17 AM
Any luck with the voicemail issue? We are experiencing the same. It seems to have worked properly about a month ago, but now voicemails don't appear in the Teams app, only Outlook.
05-16-2019 06:33 AM
Re-provisioning the user accounts via PowerShell worked.
Here are the instructions to re-provision a user using PowerShell:
Run the PowerShell application as administrator.
$User = Get-MsolUser -UserPrincipalName "email@example.com" | Select ObjectId
Redo-MsolProvisionUser -ObjectId $User
You will need to use your App password to connect.