'alias@domain.local' synched to the cloud with DirSync.

I have hybrid Exchange 2010SP3, Office 365. DirSync no ADFS.
User primary address and UPN is 'alias@domain.com' but they do have 'alias@domain.Local' email address.
When user got synched to the cloud some recipient have 'alias@domain.local' and some don't. All attributes of the users are identical and not using any filtering on DirSync related to '.local' domain.

I think either all should have alias@domain.local or none. What could be the reason?
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Vasil Michev (MVP)Commented:
Just to clarify what you mean by alias@domain.local? The actual, literal .local domain, or the 'redacted' one, with @tenant.onmicrosoft.com. The first one should only be possible when syncing mail users/contacts.

The aliases provisioning flow is proxyaddresses -> mail -> UPN alias.
RHAuthor Commented:
company has DN=Domain.local, to build hybrid we added domain.com' and assigned user routable UPNs.

AD user have UPN; "username@domain.com"
proxyaddresses: primary STMP; "username@domain.com", "username@domain.local"

Synched all the users to the cloud using DirSync.

At this point we are in hybrid mode, users have mailboxes in the cloud and also on premise . User's whose mailbox still on premise shows as contact in the cloud.

Some synched user have proxyaddress '"username@domain.local" and  some of them don't.  On premise exchange all of them have this proxyaddress "username@domain.local".

I need to remove the "username@domain.local" proxy address before I move remaining mailboxes to the cloud.  

I 'm wondering why all of them don't have proxy address "username@domain.local" in cloud.
Vasil Michev (MVP)Commented:
"username@domain.local" can only be assigned to MEU or contacts. If the user is synced as any other type of recipient to EO, it can only have aliases from domains verified in O365. Try to compare the recipient type for one user that shows the alias, and one that doesnt:

Get-MsolUser -UserPrincipalName user@domain.com | fl cloud*,proxy*

Open in new window

Or directly check the recipient type:

Get-Recipient user@domain.com | fl RecipientType*

Open in new window

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

RHAuthor Commented:
Both users show as: Managed, Mailuser

Only difference I see when compare attributes of both synched cloud user:

Capabilities  : {BPOS_S_Standard, MasteredOnPremise}      (doesn't have @domain.local proxyaddress)
Capabilities : {MasteredOnPremise} (have @domain.local proxyaddress)
Vasil Michev (MVP)Commented:
You have applied a license to the first one?
RHAuthor Commented:
Yes, found that Exchange Online license was assigned to the first one (even the mailbox was still on premise), so assigned Exchange online license to another users (mailbox still on premise) and "@domain.local' got removed from cloud.

So if we assign Exchange online license to the user (even mailbox on cloud) 'username@domain.local' would be removed from users attribute in the cloud.

It means we don't have to remove 'username@domain.local' alias from on premise users?
Vasil Michev (MVP)Commented:
When you assign a license to any user, it will strip all aliases that are associated with non-verified (accepted) domains. This of course includes any of the non-routable ones too.
RHAuthor Commented:
Perfect, Thanks.
There is a flip side to it, if synched user doesn't have mailbox on premise, assigning  license would create mailbox in cloud. If licenses assigned before building hybrid it would create mailbox in cloud and after building hybrid wouldn't be able to move the mailbox to the cloud. Thanks again.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Office 365

From novice to tech pro — start learning today.