Microsoft Phone System Voicemail with Teams

-

Recently Microsoft started changing their Office 365 environment utilizing more Azure based service. One of the first services moved into an Azure model was the Exchange Voicemail service. It now resides in Azure.

This service as a product is now named Microsoft Phone System Voicemail.

The works with Skype for Business and Teams in the following setups with either PSTN Calling (Microsoft cloud based PSTN) or PSTN Hybrid Voice (PSTN On-Premise)
Calling Plan
Hybrid Voice (PSTN On-Prem)
Skype for Business
YES
YES
Teams
YES
NO



Next, we need to consider the correlation with Exchange UM and Phone System Voice Mail.

Voicemail Option with Skype for Business and Teams

Exchange UM
Phone System Voicemail

Exch UM On-Premise
Exch UM online
User Mbx homed Exch On-Premise
User Mbx homed Exch Online

SfB On-Premis
YES
YES
NO
NO
SfB Hybrid with On-Prem PSTN (user on-prem)
YES
YES
NO
NO
SfB Hybrid with On-Prem PSTN (user online)
NO
NO
YES
YES
SfB Online with Phone System + Calling Plan
NO
NO
YES
YES
SfB Online with PSTN On-Prem (CCE)
NO
NO
YES
YES

Microsoft Teams is undergoing change until end of 2018. The next table might change
Teams + Phone System + Calling Plan
NO
YES
NO
YES
Teams + Phone System + PSTN On-Prem )*
NO
YES
NO
YES

)* Teams is not supporting CCE, an On-Premise PSTN cannot be use. The Teams Road Map states an availability for 2018, where Teams will support a native SBC with PSTN On-Premise

Note:
If a user is homed on Exchange On-Premise. Make sure the Exchange Plan 2 license is NOT enabled and further ensure DNS, Azure AD Sync and OAuth is correctly setup.




Configuration Phone System Voicemail

Phone System voicemail don’t need any configuration. It is automatically activated with Office 365 Tenant activation. If the user is provisioned correctly with the correct license and is enabled for Enterprise Voice with a phone number, then Phone System Voicemail will automatically be enabled and configured in the background.

 Verifying the user’s enablement for Phone System Voicemail:

 Get-CsOnlineUser | fl Alias,EnterpriseVoiceEnabled,Lineuri,Hostedvoicemail, hostedvoicemailpolicy

 The HostedVoiceMail parameter needs to be: $TRUE


Activating a user’s Phone System Voicemail:

Set-CsUser -Identity user@yourtenantdomain.com -HostedVoiceMail $true

Phone System Hosted Voicemail Policy


NOTE:
The Hosted Voicemail Policy “Businessvoice” is a Default Policy that exists in O365 by Design. This policy will be automatically applied for any user who is Enabled for Phone System with Calling Plan.
When a user is enabled for Enterprise Voice with an LineURI set, the Hosted Voicemail Policy attribute will also be automatically provisioned for the user (this process might take some time for newly created or moved users, sometimes up to 4 hours).
In case you find that the user still doesn’t have  attribute populated with "businessvoice" then you CANNOT manually set this attribute using remote PowerShell as the command to do this is NOT available in SFB Online PowerShell.

Get-CsHostedVoicemailPolicy




Phone System Voicemail Transcription

 Voicemail transcription is enabled by default for all organizations and users; however, you can control it by using the Set-CsOnlineVoicemailPolicy and Grant-CsOnlineVoicemailPolicy cmdlets.

 Get-CsOnlineVoicemailPolicy


Comments

Post a Comment

Popular posts from this blog

Cannot join external Lync Meeting: Lync Edge Server Single IP Address (Lync Edge Server Single IP Web Conferenceing Problem)

-
Image
Lync Edge Server FQDN and IP PORTS (Version 1.2, Update 26.11.2014) As we all know, we can configure Lync Edge Server in several way. 1) Single Edge Server with a SINGLE IP ADDRESS 2) Single Edge Server with MULTIPLE IP ADDRESSES (3x IPs) 3) Multiple Edge Server in a Pool, with MULTIPLE IP ADDRESSES (Zx 3 IPs) Regardless what we are going to configure, there are common / well-known TCP Port necessary making Lync work, which are: Access: Port: 443 and 5061 Conferencing: Port: 443 and (444) AV: Port: 443 (I have not listed other ports, e.g. STUN or the dynamic port range. This is not required for the topic discussed here) External FQDN with single IP address: What can we see here? If we are going to choose a single IP address, we would have TCP Port overlapping. Therefore the only way avoiding this is assigning other ports. Additionally we will also see and are reminded that Lync highly depends on DNS. If we have single IP, we must have use single, unique FQDN fo
Read more

MFA with Guest Access and different tenants settings

-
Image
There is an update regarding MFA Multi Factor Authentication. If you are guest with a different Tenant, the MFA Settings are now reflecting the settings of all tenants in a different way. Each MFA setting is reflected and you can setup your MFA device as per tenant and the admin settings allow. Login to your Profile in Office 365/ Azure AD: https://account.activedirectory.windowsazure.com/r/#/profile or https://myapps.microsoft.com Go to your PROFILE: Sign in to https://myapps.microsoft.com Select your account name in the top right, then select profile. Select Additional security verification. If might be happen, your admin hast configured MFA, so you wouldn't see this menu. Simply switch the tenant to the guest tenant where you need to configure MFA. Once you go back to your profile and you will find the MFA device and other settings a usual:
Read more

Skype for Business, Lync and Exchange Web Services (EWS) and different DNS Domains- Exchange crawling e.g. for presence

-
Image
Hi all, (This is an updated version 2.2: 09 .07.201 5 ) This blog entry is valid for Lync 2010, Lync 2013 and Skype for Business Server. Generally, I'll write a new blog article, since the conversion history over multiple device and other service have change with Skype for Business 2015 Server. Once this written, I post the link here. there is always confusion in how Lync is crawling Exchange Web Services (EWS). Generally it is necessary to understand how DNS must be implemented: Just remember, identify if you have DNS Split configuration, different internal and external DNS names and what are your SMTP and SIP Domains. Very often you find in Lync/ Exchange deployments an issue, where the Lync configuration show up with empty: EWS Internal URL EWS External URL and EWS Information = EWS not deployed Therefor Exchange Web Service are not connected deployed and several Lync Integration Features are not working, e.g. Presence Information based on your Outlook Calendar.
Read more