---
title: "Cisco Voice - Setup O365 Unified Messaging with Cisco Voicemail"
slug: "cisco-voice-setup-o365-unified-messaging-with-cisco-voicemail"
tags: ["calltower", "public"]
updated: 2026-09-18T13:42:27Z
published: 2026-09-18T13:42:27Z
canonical: "learn.calltower.com/cisco-voice-setup-o365-unified-messaging-with-cisco-voicemail"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://learn.calltower.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Cisco Voice - Setup O365 Unified Messaging with Cisco Voicemail

Goal: To Create an Account in Office 365 and Setup Access for Voicemails

Purpose: This account will be used to retrieve voicemails from the users inbox via the CallTower Voicecube Voicemail System

1. Login to Office 365 with Admin Credentials using this URL [https://admin.microsoft.com](https://admin.microsoft.com)
2. Navigate to Users>Active Users>Add a User
3. Create the user account with the username umadmin[@domain.com](mailto:cto365admin@domain.com) (username format is just an example), (no license or administrator role is needed)
4. Make sure the password for the user account is set to never expire (instructions are [here](/v1/docs/ms-o365-admin-never-expire-user-password) if needed) and no MFA is set.
5. Provide the username and password to the CallTower Project Manager
6. Navigate to Admin Centers>Exchange>Permissions>Admin Roles
7. Create New Role with ApplicationImpersonation and add the account that was just created as a member as shown in the screen shot below.

![clipboard_e1176142c100dd53e0aa701bf53d8b812.png](https://cdn.us.document360.io/4662144b-ab1f-4796-8b7b-e9f9c609894f/Images/Documentation/clipboard_e1176142c100dd53e0aa701bf53d8b812.png?sv=2026-02-06&spr=https&st=2026-11-05T00%3A13%3A27Z&se=2026-11-05T01%3A13%3A27Z&sr=c&sp=r&sig=McdCuCFiDuRO3dPzxdFz%2Feelb9yWW2VL6dGCMYbx63Q%3D)

> [!NOTE]
> Important Note:
> 
> The user account will use basic authentication make sure that there is not a Conditional Access policy blocking Legacy Authentication and if there is, make sure the account is excluded.