Before running any of Coexistence Manager for GroupWise’s F/B Connector subcomponents, you must synchronize GroupWise users as Office 365 contacts, and Exchange users to GroupWise. Coexistence Manager for GroupWise’s Directory Connector does not support directory synchronizations directly between GroupWise and Office 365. In this non-hybrid O365 scenario, however, you can configure Microsoft’s Azure AD Sync synchronization tool to synchronize a local AD with Office 365. See Microsoft’s Azure AD Sync tool documentation for instructions and guidance in configuring the Azure AD Sync tool for this purpose.
NOTE: GroupWise sometimes mistakenly generates F/B queries for addresses in the form email@example.com (instead of firstname.lastname@example.org). Queries to such addresses will fail if AD does not recognize the address, so be sure to add that address form as an alias in AD for each Exchange user.
Configure and verify the link from Office 365 to the domains/subdomains supported by the GroupWise server. This procedure tests whether the certificate on the Coexistence Manager for GroupWise Web Server is trusted by O365.
For FBC coexistence with Office 365, run Enable-OrganizationCustomization, and then create the availability address space by opening a PowerShell session and using the following commands:
You can use Network Load Balancing to permit multiple web servers to handle Autodiscover requests. This is optional, not required to deploy Coexistence Manager for GroupWise. For more information, see .
Configure DNS to point autodiscover.<smtpdomain.com> to the computer where Coexistence Manager for GroupWise’s Autodiscover service is installed. For each domain, Exchange connects to predefined Autodiscover URLs using DNS host entries.
For Exchange to get free/busy information from the domain supported by a GroupWise server, through the Coexistence Manager for GroupWise Free/Busy Connector, you must make the Coexistence Manager for GroupWise Autodiscover Web Service resolvable to this URL: