15364248-How To Integrate Unity Connection With Microsoft Office 365

How to integrate Unity connection with MS Office 365
Scope: This document covers the pre-requisites and configuration steps necessary to integrate Unity connection with Microsoft Office 365 to
achieve Single Inbox functionality. While I performed most of the steps in my setup however some of the steps may be extracted from other
people’s posts.
1) Pre-requisites:
1.1) Unity connection 8.6.2 or later.
1.2) DNS configuration on Unity connection to resolve to Hosted MS Exchange Server Hostnames.
1.3) Office 365 WAVE 15– Will work with Unity connection 8.6.2a (SU3) (i.e. 8.6.2.23900-10) or later. I was advised by some internal
Cisco folks to go with “UCSInstall_UCOS_8.6.2.24084-1.sgn.iso” as it’s more stable and tested with WAVE 15 but so far
“8.6.2.23900-10” is working fine for me.
1.4) If you need access to “UCSInstall_UCOS_8.6.2.24084-1.sgn”, please send an e-mail to “ucxn-o365-
[email protected]“and provide them with your CCO ID. Give them couple of days to respond. This version is not yet
available on Cisco.com.
1.5) Office 365 WAVE 14 – Will work the previous Unity connection 8.6.2 versions.
2) How to check if the customer is using Outlook 365 WAVE 15 or not:

2.1) The easiest way is to login to the Office 365 portal and see what layout you have. If it's blue and looks like the below image
then its wave 15, otherwise its wave 14.
2.2) Alternatively, you can check out this website that shows your pre-upgrade and post upgrade look:
http://office.microsoft.com/en-ca/help/am-i-using-office-365-after-the-service-upgrade-HA103982331.aspx
2.3) Another way is to ask when the customer signed up for Office 365. If customer created their office365 tenant after Feb 27th
2013 then it is Wave 15 (Exchange, Lync, and SharePoint 2013, not 2010).
3) Microsoft Office 365 side configuration:

3.1) Create an admin account in the Office 365 administration which Unity connection can use to login with to Office 365
environments. The admin account should not require a license it but confirm from Office 365 provider.
3.2) Assign the permissions to allow the account the ability to connect to the other mailboxes:
3.2)1. See the steps for "Assigning the Application Impersonation Management Role to Unified Messaging Services
Account..." and the "Accessing Office 365 Using Remote Exchange Management PowerShell" sections of the
Configuring Cisco Unity 8.6(2) and later and Microsoft Office 365 for Unified Messaging guide at:
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/unified_messaging/guide/85xcucumg025.html#wp1302097
3.3) Create a New Unified Messaging Service in the Cisco Unity Connection Administration.
3.3)1. Set Type to Office 365.
3.3)2. Specify a display name – Mandatory.
3.3)3. If you have a proxy server, enter in the proxy server address and port information.
3.3)4. Select the option to Search for Hosted Exchange Servers – Recommended.
3.3)5. If you would like to put the MS office 365 server specifically: smtp.office365.com.
3.4) Enter in the DNS Domain Name used for the Office 365 users
3.4)1. In a hybrid environment where you route emails between an on-premise Exchange organization and Office
365, specify the special onmicrosoft.com domain name (such as mycompany.mail.onmicrosoft.com). It is the
domain used to route email from your on-premise to Office 365.
3.4)2. Otherwise, if you are only using Office 365, try your domain name from your email addresses.
3.5) Set the Protocol Used to Communicate with Domain Controllers to Secure LDAP (LDAPS).
3.6) I am using the default settings here. The Active Directory Site Name blank and the Validate Certificates for Active Directory
Domain Controllers unchecked.
3.7) Enter in the account information for the new administrator account you created in Office 365.
3.7)1.1. The Username should be specified with the @domain i.e. user@domain.
3.8) Check the box for Access Exchange Email by Using Text to Speech (TTS) if you want that feature
3.9) Check the box for Access Exchange Calendar and Contacts if you want that feature.
3.10) Check the box for Synchronize Connection and Exchange Mailboxes (Single Inbox).
3.11) Save
4) After you have the Unified Messaging Service created, you can assign the service to the Unity users that
are on Office 365.
4.1) Edit the user account in the Cisco Unity Connection Administration
4.2) From the Edit drop-down menu, select Unified Messaging Accounts
4.3) Click Add New
4.4) Select the Office 365 messaging service you created
4.5) Have it use the corporate email address unless it doesn't actually match the email address for the user on Office 365.
4.6) Save
When you Test the Unified Messaging Account in the User's details, it will likely show that the "Server cannot be contacted by pinging." That
shouldn't be a problem and is normal in my experience. If it fails elsewhere, try testing again. I've had it fail once in a while when testing a user
only to pass on a second attempt.
5) Testing
5.1) I left a test voice-mail for one of the user and got the WAV file in his Office 365 inbox.
5.2) I haven’t tested view-mail on Office 365 yet, but basic Single Inbox functionality was working fine at this stage.

15364248-How To Integrate Unity Connection With Microsoft Office 365

Uploaded by

Copyright:

Available Formats

15364248-How To Integrate Unity Connection With Microsoft Office 365

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

15364248-How To Integrate Unity Connection With Microsoft Office 365

Uploaded by

Copyright:

Available Formats

How to integrate Unity connection with MS Office 365

2) How to check if the customer is using Outlook 365 WAVE 15 or not:

3) Microsoft Office 365 side configuration:

You might also like