Forum Discussion
Solved
Unified GAL with AADConnect
Hi,
My customer wants to merge bikes.com" into cars.com's existing hybrid-configured and federated tenant by adding bikes.com email domain to the existing tenant and create a unified GAL as cars.com users need to lookup bikes.com user in the GAL and vice versa.
- "Cars.com" is configured as an AD/Exchange hybrid forest
- "Bikes.com" is currently an autonomous on-premises AD/Exchange forest but users need Office 365/Teams
Q1: Will the configuration be sufficient to provide a unified GAL in both Exchange Orgs?
Q2: If Yes, how will the users from each forest appear in the GAL in the other forest? Contacts? Users?
Q3: What would be the easiest way to enable free/busy calendar sharing between cars.com and bikes.com users? Exchange Availability service?
Thanks in advance,
Douglas
- They will not, as they'll be getting the on-premises GAL.
6 Replies
- The only way to end up with "unified GAL" in this scenario is to move all users to a single O365 tenant. Alternatively, you can use third-party "galsync" tools, as AAD Connect only synchronizes from on-prem to Azure AD.
As for free/busy sharing, org relationships are the way to go: https://docs.microsoft.com/en-us/exchange/sharing/sharingVasilMichev, thanks for your reply.
Could you please clarify "move users to a single tenant"?
The suggested solution is a single O365 tenant with two domains (cars.com and bikes.com) as bikes.com will keep its domain. Cars.com is already configured as an Exchange hybrid and now they want to merge bikes.com into the already existing tenant.
To get a unified GAL, will an AADConnect write-back sync suffice or does bikes.com also need to be an Exchange hybrid?
Thanks, Douglas- Writeback doesnt cover recipient objects, so objects created directly in O365 will not be visible on-premises. The only way to see all recipients across both domains will be when using an O365 account and only if both domains are in a single tenant. Or you can use third-part "galsync" products to create matching entries on-premises. PowerShell is also an option, if you feel up to it.
