What changes in Skype, when you move your voicemail to the Cloud, with an Office365 Mailbox.


Hello all, I found myself in a situation recently. A deployment person completed a hybrid deployment of Exchange, where Voicemail was supposed to be in the cloud. However, the voicemail did not work.

The issue was the company allowed the Deployment person to complete all the deployment steps, except as it pertains to Skype for Business.

This put me in an odd position. I did not intuitively know what commands needed to be run. I verified It was not just me. It turns out, it is extremely difficult to come into a complex hybrid setup, and feel comfortable, running commands.

So since this article is all shell commands, how about a cool picture of me at Ignite! See below. If you at a Microsoft event, Check out the Spark 360 booth! Very cool pictures!





After more then a week of getting the back information, Myself and David McCullough of Dell EMC (we both work for Dell EMC), finally came to a set of commands to run.

So please remember. This is not the entirety of steps you need. This is just the Skype for Business steps you need for basic voicemail for Unified Messaging Online.

For Skype

Create a hosting provider

1. New-CsHostingProvider -Identity “Exchange Online” -Enabled $True -EnabledSharedAddressSpace $True -HostsOCSUsers $False -ProxyFqdn “exap.um.outlook.com” -IsLocal $False -VerificationLevel UseSourceVerification

2. Invoke-CsManagementStoreReplication

3. Get-CsHostingProvider –localstore

Configure Voice Messaging

1. New-CsHostedVoicemailPolicy –Identity CloudUM – Destination exap.um.outlook.com -Description “O365 Voicemail” -Organization “yourdomain.onmicrosoft.com”


Configure Office 365

1. Create the Dial Plan Skype  – See this link- Creating the Dial Plan “Skype” look under Configuration of Office365

2. When you create this Dial Plan – A policy will create automatically.

In the Skype environment

These commands are on a per Dial Plan Basis.

Take the results of this command (the identity from the fist command and put into the second command)

new-csexumcontact -displaynumber “+15141234567” -sipaddress “sip:voicemail_o365@yourdomain.com” -registrarpool poolync.yourdomain.com -ou “ou=Exchange UM Contacts,dc=yourdomain,dc=com”

Replace the yellow area, with the results from the get-cshotsedvoicemailpolicy  command. The Contact command above, should specify a policy Identity. you can use that below :

Grant-cshostedvoicemailpolicy –identity  “CN={234731ac-9dda-4037-9acb-cd5e4be08163},OU=Exchange UM Contacts,DC=yourdomain,DC=com” –policyname CloudUM

Grant Users the Policy

Grant-cshostedvoicemailpolicy –identity “User Name” –policyname CloudUM

Set-CsUser -HostedVoiceMail $True -Identity “User Name”

Final step is you must enable Voicemail, once they have been moved over to office 365. So the user will be Disabled for UM when they are On premise. Next, perforn the steps above. Finally, Enable the user for Unified Messaging, once they are moved to Office 365 for Unified messaging.

Now if you go any further, you risk setting your self up for Skype Cloud Hybrid. For that, take a look at this article by CanitPro. They will show you the steps go all the way, creating a Skype connection to Office 365, which will be the classic Skype Hybrid Setup. What I describe above, is how you just enable Unified Messaging, for Exchange Office 365 Users.

This is a very fine line, you want to be aware of. Don’t configure Skype Hybrid, when you are trying to get Unified Messaging, in Office 365.

Thank you,




Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s