How to Configure Cisco Unity Unified Messaging with Microsoft 365 OAuth2
Question details
The user needs to configure Unified Messaging on Cisco Unity Connection 14.x using Microsoft 365 OAuth2 and is experiencing failures during Autodiscover testing and dummy account validation.
- Product
- Cisco Unity Connection & Microsoft 365
- Device & OS
- not provided
- Scenario
- Setting up integration between Cisco Unity Connection and Microsoft 365 Exchange Online using modern OAuth2 authentication protocols.
- Observed behavior
- Configuration fails during Autodiscover testing, with issues pointing toward the dummy service account, client secret, or Exchange Online API permissions, preventing successful unified messaging setup.
Ensure you have global administrator access to your Microsoft Entra ID (formerly Azure AD) for app registration and API consent, as well as administrator access to the Cisco Unity Connection portal.
Create a New Unified Messaging Connection
Recreating the connection from scratch is often the most effective way to resolve persistent configuration conflicts after updating OAuth details.
If changing authentication modes does not resolve the Autodiscover failure, Cisco TAC often recommends establishing an entirely new connection to ensure legacy settings are not causing conflicts.
Log into the Cisco Unity Connection Administration interface with your administrator credentials.
Navigate to the Unified Messaging settings and create a new unified messaging service connection using your updated Microsoft 365 OAuth2 app registration details.
Use the bulk operations tool within the Unity admin portal to migrate your existing users so they utilize the newly created connection.
Modify the default user template to ensure all new user accounts are automatically assigned to this new connection.
Troubleshoot Autodiscover and App Registration Settings
Fix Autodiscover testing failures by verifying your Entra ID app permissions and Unity dummy account settings.
Update Service Account Configuration in Unity
Ensure the service account specified in newer Unity versions precisely matches the account used for Autodiscover.
Looking for a Lightweight Office Suite Alternative?
While troubleshooting complex Microsoft 365 Exchange and server integrations, you might find that you just need a straightforward, hassle-free office suite for your daily document work. WPS Office provides a powerful, free alternative to Microsoft Office desktop apps with high compatibility and zero complex tenant configurations.
- 1. Download the Installer: Visit the official WPS Office website and download the free installation package for your operating system.
- 2. Install the Application: Run the downloaded installer and follow the on-screen instructions to set up WPS Office on your computer.
- 3. Start Creating Documents: Open WPS Office to instantly start creating, editing, and saving your documents without needing complex administrative setups.

Frequently Asked Questions
Why does Autodiscover fail during Cisco Unity Unified Messaging setup?
Autodiscover testing often fails due to incorrect dummy service account credentials, missing Exchange Online API permissions, lack of tenant-wide Administrator Consent in Entra ID, or an expired Client Secret.
Where do I change the service account name in newer Unity versions?
In Cisco Unity Connection 14.x and newer, the service account name can be modified directly within the Unified Messaging service or connection configuration page under the unified messaging settings.
What API permissions are required for Microsoft 365 OAuth2 integration with Unity?
You must grant the application permissions to access Exchange Online APIs, specifically those required for reading and managing unified messaging data, and you must grant admin consent for these permissions in the Microsoft Entra ID portal.
How do I apply a new Unified Messaging connection to all existing users?
After creating the new connection, navigate to the bulk operations feature in the Cisco Unity Connection Administration interface to update all existing users to the new connection. Be sure to also update the default user template for future accounts.




