Overview of Unity Connection Communication with Exchange Server
When you add a unified messaging service that defines the communication between Unity Connection and Exchange, you can select whether you want Unity Connection to communicate directly with a specific Exchange server or you want Unity Connection to search for Exchange servers.
The choice you make determines which Exchange mailboxes Unity Connection can access:
-
If you select a specific Exchange 2016 client access server, Unity Connection can access all Exchange 2016 mailboxes in the Exchange organization, but cannot access Exchange 2019 mailboxes.
-
If you select a specific Exchange 2019 client access server, Unity Connection can access all Exchange 2019, and Exchange 2016 mailboxes in the Exchange organization.
-
If you allow Unity Connection to search for Exchange servers, you need to give permissions to the Exchange servers. See the below section to grant permissions to the applicable Exchange server:
Granting Permissions for Exchange 2013, Exchange 2016 or Exchange 2019
Note |
If you want to select a specific Exchange server when you add a unified messaging service, you may need to add more than one unified messaging service to allow Unity Connection to access all mailboxes in the Exchange organization. Table 1 explains when you need to add more than one unified messaging service. |
Exchange Versions with Mailboxes That You Want Unity Connection to be Able to Access |
|||
---|---|---|---|
Exchange 2016 |
Exchange 2019 |
Office 365 |
Create the Following Unified Messaging Services |
No |
No |
Yes |
One for Office 365 server that you want Unity Connection to be able to access. |
No |
Yes |
Yes |
|
Yes |
Yes |
Yes |
|
Yes |
Yes |
Yes |
|
Yes |
No |
Yes |
|
Yes |
No |
No |
One for Exchange 2016. |
Yes |
No |
Yes |
|
No |
No |
Yes |
|
-
If you select to allow Unity Connection to search for Exchange servers, Unity Connection automatically detects when you move mailboxes from one version of Exchange to another, and automatically update Unity Connection user settings.
-
If you select a specific Exchange server, Unity Connection sometimes detects when you move mailboxes from one Exchange server to another, and automatically access the Exchange mailbox in new location. When Unity Connection cannot detect the new mailbox, you must manually update unified messaging services or unified messaging accounts:
-
If you moved all the Exchange mailboxes accessed by a unified messaging service: Update the unified messaging service to access a different Exchange server.
-
If you moved only some of the Exchange mailboxes accessed by a unified messaging service: Update unified messaging account settings to use a unified messaging service that accesses mailboxes in the new location.
-
Table 2 identifies when Unity Connection automatically detect mailbox moves between Exchange servers. For information on updating Unity Connection user settings when Unity Connection cannot detect mailbox moves, see the “Moving and Restoring Exchange Mailboxes” chapter.
If you select a specific |
Unity Connection can automatically detect mailbox moves between the following Exchange versions |
||||
2016 |
2019 |
2016 and 2016 | 2016 and 2019 | 2019 and 2019 | |
Exchange 2016 server |
Yes |
No |
Yes |
No |
No |
Exchange 2019 server |
Yes |
Yes |
Yes |
Yes |
Yes |
If Unity Connection is not configured to use DNS, you must select a specific Exchange server. If this does not allow you to access all the Exchange mailboxes in the organization as described earlier in this section, you must create more than one unified messaging service.
If you select a specific Exchange server and that server stops functioning, Unity Connection cannot access any Exchange mailboxes. If you select to allow Unity Connection to search for Exchange servers and if the Exchange server that Unity Connection is currently communicating with stops functioning, Unity Connection searches for another Exchange server and begins accessing mailboxes through that server.