Unified Messaging Guide for Cisco Unity Connection Release 15 - Configuring Unified Messaging

Publisher

Cisco Systems

URL

https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/15/unified_messaging/guide/b_15cucumgx/b_15cucumgx_chapter_01.html

Published

2026-07-01

Updated

unknown

Accessed

2026-09-30

HTTP status

200

License

Cisco proprietary documentation; no-redistribution; short excerpts and locators only

Source notes citing this source

• After the upgrade to 15SU4 or later converts an Office 365 unified messaging service from EWS to Graph API, the service may need up to 4 hours to become fully stable. in context
• For Office 365 unified messaging over Microsoft Graph, the Azure app registration needs the application (not delegated) permissions Mail.ReadWrite and Mail.Send, with admin consent granted. Calendars.ReadWrite and Contacts.ReadWrite are needed only for calendar and contact access. in context
• Because Cisco's procedure grants the Graph permissions in Microsoft Entra ID and Microsoft says Entra-granted permissions can only be constrained by Application Access Policies, the Application Access Policy is the scoping mechanism consistent with Cisco's documented setup, even though Microsoft describes it as replaced. inferred in context
• Cisco's task list for restricting the application to specific mailboxes creates a mail-enabled security group and runs New-ApplicationAccessPolicy with -AppId, -PolicyScopeGroupId and -AccessRight RestrictAccess in Exchange Online PowerShell, which requires the OrganizationConfiguration role. in context
• After adding the permissions, an administrator selects Grant admin consent for the tenant on the API permissions window. in context
• The registration steps must be repeated for each unified messaging service or cluster, and Cisco recommends a unique Application ID for each cluster. in context
• Registering a new application under Microsoft Entra ID > App registrations > New registration yields the Application (Client) ID and Directory ID that Unity Connection uses to configure unified messaging. in context
• On upgrade to 15SU4 the Resource URI of an existing Office 365 unified messaging service changes automatically from https://outlook.office365.com to https://graph.microsoft.com. in context
• For the Graph API integration the root certificate to upload is the one presented by https://graph.microsoft.com, whereas the EWS procedure used the one from https://outlook.office365.com/EWS/Exchange.ASMX. in context
• Cisco recommends uploading the certificate before the upgrade; if it is uploaded after the upgrade, the Connection Mailbox Sync service must be restarted. in context
• The Office 365 root certificate is uploaded in Cisco Unified Operating System Administration under Security > Certificate Management > Upload Certificate with the certificate name tomcat-trust. in context
• The client secret is created under Certificates & secrets and its value must be copied at creation time; otherwise a new client secret has to be created. in context
• Single inbox requires the class of service Licensed Features check box Allow Users to Access Voicemail Using an IMAP Client and/or Single Inbox. in context
• The Office 365 task list has the administrator configure DNS with the CLI commands set network dns and set network dns options, and recommends that Unity Connection use the same DNS environment in which Active Directory publishes its records. in context
• In the EWS task list used before 15SU4, the application is given the full_access_as_app application permission, and the guide says it must be the only permission assigned. in context
• After migrating from EWS to Graph during the upgrade to 15SU4 or later, the unified messaging service may need up to 4 hours to reach full stability. in context
• Starting with Release 15SU4, Unity Connection integrates with Microsoft Office 365 using the Microsoft Graph API instead of Exchange Web Services. in context
• For the Graph API integration the registered application is given the Microsoft Graph permissions Mail.ReadWrite and Mail.Send for the Mail feature. in context
• The same permissions table maps the Calendars feature to Calendars.ReadWrite and the Contacts feature to Contacts.ReadWrite. in context
• Unity Connection Release 15 supports only the OAuth2 web-based authentication mode for unified messaging with Office 365; Basic and NTLM modes are no longer supported. in context
• The Microsoft Graph permissions for Unity Connection must be of type Application, not Delegated. in context
• A unified messaging account is added for a user from Users > Users > the user > Edit > Unified Messaging Accounts > Add New, and the Test button on that account opens a Task Execution Results window with the test results. in context
• A unified messaging service is created in Cisco Unity Connection Administration under Unified Messaging > Unified Messaging Services > Add New. in context
• The Office 365 unified messaging service takes the Application (Client) ID, Directory ID, Client Secret, an AD Authentication Endpoint whose default is https://login.microsoftonline.com, and a Resource URI whose default for Graph is https://graph.microsoft.com. in context
• Certificate validation for the Office 365 connection is turned on with the Validate Certificates for Exchange Servers check box in Unity Connection Administration. in context

Cite this source record

APA

WarmTransfer. (2026, July 1). Unified Messaging Guide for Cisco Unity Connection Release 15 - Configuring Unified Messaging. WarmTransfer. https://warmtransfer.net/knowledge/sources/cisco-cuc15-um-guide-configuring

BibTeX

@misc{warmtransfer-cisco-cuc15-um-guide-configuring,
  title  = {Unified Messaging Guide for Cisco Unity Connection Release 15 - Configuring Unified Messaging},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/sources/cisco-cuc15-um-guide-configuring},
  note   = {Cisco Systems, accessed 2026-09-30}
}