Email Signature Manager version 5.x
Email Signature Manager version 6.x
Email Signature Manager version 7.x
This article describes how to resolve common problems when deploying signatures to Office 365.
In some circumstances, deployment of signatures to Office 365 can fail, even when the service account has been properly configured. In the Status Monitor, you see the following information:
Deploying signature '<My Signature>'.
User data loaded from Active Directory.
Installing to Outlook.
Installing to OWA.
Updating via Exchange Web Services at 'https://outlook.office365.com/EWS/Exchange.asmx'.
Failed to install signature via EWS: Failed to set the signature in OWA through Exchange Web Services
Errors were encountered deploying the signature.
When using the Test Office 365 Connectivity dialog, you receive one of the following error messages:
- Unable to determine any identities for the user to query the autodiscover service
- The impersonation principal name is invalid
These failures occur because there is either missing or incorrect information on the user's Active Directory account; without this information, the user cannot be identified correctly on Office 365.
The user's account must have the correct primary email address (as configured in Office 365) configured on their Active Directory account. For example, when looking at the details of a user in Office 365, you will see the following:
The listed Primary email address must be set in E-mail property of the the user's Active Directory account:
Note: To keep accounts synchronised automatically between your local domain and Office 365, you may wish to consider deploying the Microsoft Domain Synchronisation tool; more details can be found in the following Technet article: