Cisco tech note 118828, updated June 2025, still describes connecting Unity Connection to Office 365 with a service account that holds the ApplicationImpersonation role and whose credentials are entered on the unified messaging service, which conflicts with the Release 15 guide's statement that only OAuth2 is supported.
disputed · Checked 2026-09-30
- Vendor
- Cisco
- Product
- Cisco Unity Connection
- Subsystem
- unified messaging
- Deployment
- on-premises
- Region
- not restricted
- Release range
- printed as Release 8.x and later
- Status
- disputed
- Checked
- 2026-09-30
Sources
- Configure Unity Connection for Office 365 — Cisco Systems · tier 2 current vendor documentation · Configure > Office 365 steps 4-8; Configure > Unity Connection > Account Used to Access Exchange
Cite this note
APA
WarmTransfer. (2026, September 30). Setting up Unity Connection single inbox with Microsoft 365: source note unity-connection-single-inbox-setup-technote-impersonation. WarmTransfer. https://warmtransfer.net/knowledge/claims/unity-connection-single-inbox-setup-technote-impersonation
BibTeX
@misc{warmtransfer-claim-unity-connection-single-inbox-setup-technote-impersonation,
title = {Setting up Unity Connection single inbox with Microsoft 365: source note unity-connection-single-inbox-setup-technote-impersonation},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/unity-connection-single-inbox-setup-technote-impersonation},
note = {Source note unity-connection-single-inbox-setup-technote-impersonation, checked 2026-09-30}
}