The Microsoft Exchange Connector allows you to integrate your non-Zendesk email servers, based on Microsoft Exchange, directly into your Zendesk Support instance. This is ideal for Microsoft customers looking to connect their online Microsoft 365 or Exchange servers and leverage their Exchange/Outlook workflows.
The main advantage of this solution is that it allows you to send and receive email traffic to and from your customers using your domain’s email services, while ensuring encrypted and secure relays to and from Zendesk.
Microsoft Exchange is the server powering all Microsoft email products, including Microsoft 365. Therefore, the Zendesk Microsoft Exchange Connector is compatible with the online version of all Microsoft email products. The connector is incompatible with Exchange Server on-premise. In this situation, the Authenticated SMTP Connector may be a better option.
This article includes the following topics:
- About the Exchange Connector
- Considerations
- Important information about email headers
- Connecting your Microsoft Exchange account
About the Exchange Connector
Using an Exchange API, the Microsoft Exchange Connector allows you to fetch email from an Exchange inbox and automatically convert email messages to tickets. The API is also leveraged to deliver outbound email from Zendesk to your Exchange mailbox.
Figure 1: Email flow with the Microsoft Exchange Connector
Zendesk Support frequently checks for new email in your Exchange inbox. Only new, unread email messages in the inbox will be converted into tickets. Ticket notifications will be sent from your Microsoft email address.
Considerations
- CCs and followers must be turned on in your account.
- We recommend testing this feature in your Zendesk sandbox environment before using it in production.
Important information about email headers
Email headers, (such as To, From, CC, and Reply-To) contain important data and metadata about an email message.
Your administrator may want to change email headers for several reasons. However, it’s important to note that some header fields should never be altered since they are critical for ensuring the correct delivery and integrity of the message. Changing standard headers at the account's email domain before outbound sending is not supported. Any issues that emerge as a result of this should be investigated and corrected at the external domain.
The below headers should persist throughout the outbound relay process:
Auto-Submitted: auto-generated
X-Auto-Response-Suppress: All
X-Mailer: Zendesk Mailer
X-Zendesk-From-Account-Id: ******
X-Zendesk-Email-Id: ************************
Changing your email header fields doesn’t change how Zendesk works; it only changes how you send your outbound messages and how you might receive responses. The relationships between the requester, agents, and CCs in the email and subsequent ticket should not change.
The Exchange Connector doesn't give you the ability to send email on behalf of your Zendesk system support addresses (example: support@yoursubdomain.zendesk.com).
Connecting your Microsoft Exchange account
You must be a Zendesk administrator to connect your Exchange account to Zendesk.
When you connect to your Exchange account, make sure you sign in to the Exchange account you want to connect to. If you sign in to a different Exchange account in the same browser as your instance of Zendesk Support, you will connect to the wrong account.
To connect to your Microsoft Exchange account
- In Admin Center, click Channels in the sidebar, then select Talk and email > Email.
- In the Support addresses section, click Add address, then click Connect external address.
- Select Microsoft Exchange Connector.
- Click Continue to Microsoft.
You will be redirected to Microsoft. - Click Accept to approve access to that email account.
You may need to sign in to Microsoft using your account credentials for that email address. - Click Accept, then click Done.
Your Zendesk instance is now connected to your Microsoft account. If you want to connect to multiple accounts, repeat these steps.
7 comments
Willem Auret
Hi All
I keep getting the same error for 2 days now. No idea why. As soon as I want to “add” an address it gives me this error:
0
Shaun Murray
If we set this up can we continue to use emails through Zendesk side by side with this connector?
To clarify - We already have some email addresses set up using our domain through Zendesk but we would like to try this with one email address. Would that be possible?
Our company uses MFA on our exchange accounts. Does this work with Microsoft's MFA?
Thank you!
1
Jacek Sałacki
Shaun Murray
connections are set up per each email address separately. So, you may have, for example
support@yourdomain.com configured with forwarding method
billing@yourdomain.com configured using Exchange Connector.
When it comes to MFA, it is transparent for us. Exchange Connector uses OAuth to get authorisation to access Exchange mailboxes.
1
Christopher Spitler
Does this connector support accessing shared mailboxes?
0
Jacek Sałacki
Christopher Spitler thanks for that comment.
We are not preventing any type of mailboxes to connect using Exchange Connector, until one can log-in using as a user associated with that mailbox. For shared mailboxes it means that you would need to create credentials for this mailbox and use those credentials while creating connection.
0
Christopher Spitler
Thanks, Jacek. I applied a few days ago for the EAP, so when I get access I will try this and see if it works.
0
Sumie Tonooka
I am currently testing in the EAP. I would like to confirm two things regarding this document.
1. It is stated in the 'Considerations' section that 'CCs and followers must be turned on in your account.' Is it necessary to enable 'followers' as well? In our environment, 'followers' are disabled, so we would like to know if it is truly necessary to enable them and why that is the case.
2. In the section 'Important information about email headers,' it states that the email header
should be present. However, these headers were not included in the test email. We did not remove any email headers. Are there specific conditions under which this header is included? Is it a problem if it is not present?
0