Avatar of Joergen Lind
Joergen Lind
Flag for Denmark asked on

On-Prem and Office 365 GALs are different

Hi everyone.

We're in a hybrid setup with Exchange 2013 and Ofice 365.

Our issue is that some users with a mailbox in Office 365 cannot send to some users with mailbox on the on-prem Exchange 2013.
I've narrowed it down to the GALs, where the primarysmtp fields are different for the same user.

On-prem GAL entry:
smtp:user.name@company.com
smtp:user.name@company.dk
SMTP:user.name@dept-company.com
smtp:initials@company.dk
smtp:initals@dept-company.com
x500:/0=ExchangeLabns/.... etc

Office 365 GAL entry:
SIP:intials@company.com
SMTP.initials@company.com
SPO:SPO_436334 etc
x500:/o=COMPANY/ou=Exchange Administrative Group [FYDI.... etc
smtp:user.name@company.copm
smtp:initials@company.onmicrosoft.com

The MAIN culprit here is of course that the user's Primary SMTP address, listed in the Office 365 GAL, does not exist on the user's mail account at all.

But why are those two GAL's different? Is that by design? Links and/or helpful answers are much appreciated.

Thanks,

Bjorn Dirchsen
ExchangeMicrosoft 365* global address list

Avatar of undefined
Last Comment
Joergen Lind

8/22/2022 - Mon
Vasil Michev (MVP)

If you have made changes directly in O365, those are in general not written back to AD. This is indeed by design, there are very few attributes that are written back to on-premises and only in specific situations. ProxyAddresses is one of those attributes (if you have the "Hybrid" option in AAD Connect enabled), so I'm not sure what went wrong in your case. But it's always required to make any changes in AD, then rely on dirsync to replicate them in O365.

In this specific scenario, you can just add the additional alias on-prem and be done with it.
Shreedhar Ette

Is domain dept-company.com is added to Office 365 Domains?
Joergen Lind

ASKER
@Vasil Michev. We ONLY make changes to users from the on-prem AD/Exchange since only few changes are written back from Office 365.  SO we can rule this out. Ok, I can add the nescessary attributes, but since these users are test-users i would like this to work before I migrate the remaining 100 users :)

Thanks, Bjorn
I started with Experts Exchange in 2004 and it's been a mainstay of my professional computing life since. It helped me launch a career as a programmer / Oracle data analyst
William Peck
Joergen Lind

ASKER
@Shreedhar Ette. No, dept-company.com is not added to the Office 365 domains. Could that be the reason?
ASKER CERTIFIED SOLUTION
Shreedhar Ette

Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
Sign up - Free for 7 days
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question
Vasil Michev (MVP)

Oh, good catch Shreedhar, I totally missed that. And it seems I also misinterpreted the addresses, assuming the O365 ones are the on-premises ones... Guess I should drink some more coffee :)

So yeah, Bjorn, you need to add/verify any domains you have associated with email addresses and any other attributes. Otherwise they will either be replaced with the @tenant.onmicrosoft.com domain or dropped altogether.
Joergen Lind

ASKER
Cool. I'll jump to it right away and update with my findings.

Thanks a lot guys!

Br, Bjorn
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.
Joergen Lind

ASKER
It worked! Adding dept-company.com to the list of Domains (and waiting for the GAL to be updated at 5am)  solved it.

The attributes of the user in the O365 GAL are now:

Office 365 GAL entry:
SIP:intials@company.com
SMTP:user.name@dept-company.com   <-- New!
SPO:SPO_436334 etc
x500:/o=COMPANY/ou=Exchange Administrative Group [FYDI.... etc
smtp:user.name@company.com
smtp:initials@dept-company.com   <--- New!
smtp:initials@company.onmicrosoft.com

Thanks to Shreedhar for spotting the culprit right away!