issues relaying to 365 for one user

%3CLINGO-SUB%20id%3D%22lingo-sub-1527236%22%20slang%3D%22en-US%22%3Eissues%20relaying%20to%20365%20for%20one%20user%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1527236%22%20slang%3D%22en-US%22%3E%3CP%3Ehybrid%20setup%2C%20exchange%202013%2C%20and%20365.%3C%2FP%3E%3CP%3Eall%20users%20are%20on%20365%2C%20copiers%20and%20couple%20of%20servers%20send%20email%20to%20365%20via%20exchange%20relay.%3C%2FP%3E%3CP%3Ehaving%20an%20issue%20with%20single%20new%20user.%26nbsp%3B%20report%20emailed%20from%20server%2C%20goes%20to%20exchange%202013%20relay%20connector%2C%20then%20to%20365.%3C%2FP%3E%3CP%3Eemailed%20report%20has%203%20people%20copied%20on%20it%2C%20the%20two%20preexisting%20users%20received%20the%20email%2C%20the%20new%20user%20did%20not.%3C%2FP%3E%3CP%3EI%20ran%20PS%20commands%20on%20my%20exchange%20server%20for%20message%20trace%2C%20and%20it%20shows%20the%20email%20being%20sent%20out%20to%20all%203%20users.%3C%2FP%3E%3CP%3Enothing%20appears%20in%20quarantine%20on%20365.%3C%2FP%3E%3CP%3Emessage%20trace%20on%20365%20from%20the%20report%20email%20to%20the%20new%20user%20returns%20nothing%20though%2C%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3Ewhat%20am%20I%20missing%3F%26nbsp%3B%20its%20almost%20like%20365%20is%20saying%20%22nope%22%20for%20these%20emails%20to%20this%20one%20person%2C%20but%20no%20recording%20the%20nope%20anywhere.%3C%2FP%3E%3CP%3Eis%20there%20another%20place%20to%20look%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1527236%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1527975%22%20slang%3D%22en-US%22%3ERe%3A%20issues%20relaying%20to%20365%20for%20one%20user%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1527975%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F376608%22%20target%3D%22_blank%22%3E%40admiral_sulu%3C%2FA%3E%26nbsp%3B%3A%20You%20might%20have%20already%20checked%20this%20but%20just%20to%20confirm%2C%20this%20new%20user%20was%20provisioned%20on-premises%20and%20then%20migrated%20to%20office%20365%3F%20or%20a%20remote%20mailbox%20was%20created%20directly%20in%20office%20365.%20Check%20if%20remote%20routing%20address%20is%20properly%20stamped%20against%20the%20user.%20Another%20good%20test%20would%20be%20if%20you%20have%20any%20mailbox%20on-premises%20or%20you%20can%20create%20one%2C%20see%20if%20you%20are%20even%20able%20to%20send%20emails%20to%20the%20new%20user%20from%20your%20exchange%20server.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1532156%22%20slang%3D%22en-US%22%3ERe%3A%20issues%20relaying%20to%20365%20for%20one%20user%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1532156%22%20slang%3D%22en-US%22%3Eby%20remote%20routing%20address%2C%20do%20you%20mean%20the%20onmicrosoft.com%20email%20account%3F%3CBR%20%2F%3Ethat%20seems%20correct%3CBR%20%2F%3EI%20have%20created%20mailboxes%20since%20then%20and%20no%20problems%20have%20been%20reported.%3CBR%20%2F%3Ecreate%20the%20mailbox%20on%20exchange%2C%20then%20migrate%20to%20365.%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1534097%22%20slang%3D%22en-US%22%3ERe%3A%20issues%20relaying%20to%20365%20for%20one%20user%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1534097%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F376608%22%20target%3D%22_blank%22%3E%40admiral_sulu%3C%2FA%3E%26nbsp%3B%3A%20Yup%2C%20the%20remote%20routing%20address%20is%20of%20the%20format%3A%20%3CA%20href%3D%22mailto%3Auser%40mail.onmicrosoft.com%2C%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Euser%40mail.onmicrosoft.com%2C%3C%2FA%3E%26nbsp%3Byou%20should%20see%20that%20in%20your%20email%20address%20policy%2F%20proxy%20addresses%20of%20users%20you%20migrated.%3C%2FP%3E%3CP%3EGoing%20forth%2C%20you%20can%20either%20create%20the%20mailbox%20on%20exchange%20and%20migrate%20it%20or%20simply%20use%20the%20following%20command%20to%20create%20the%20mailbox%20directly%20in%20cloud%20%3A%3C%2FP%3E%3CP%3EEnable-RemoteMailbox%20%22Kim%20Akers%22%20-RemoteRoutingAddress%20%22kima%40contoso.mail.onmicrosoft.com%22%3C%2FP%3E%3CP%3EThis%20has%20same%20effect%20as%20migrated%20user.%3C%2FP%3E%3CP%3ERef%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fpowershell%2Fmodule%2Fexchange%2Fenable-remotemailbox%3Fview%3Dexchange-ps%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fpowershell%2Fmodule%2Fexchange%2Fenable-remotemailbox%3Fview%3Dexchange-ps%3C%2FA%3E%3C%2FP%3E%3CP%3EJust%20to%20confirm%2C%20the%20issue%20has%20been%20resolved%20and%20you%20dont%20need%20any%20further%20assistance%20on%20this%20one%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

hybrid setup, exchange 2013, and 365.

all users are on 365, copiers and couple of servers send email to 365 via exchange relay.

having an issue with single new user.  report emailed from server, goes to exchange 2013 relay connector, then to 365.

emailed report has 3 people copied on it, the two preexisting users received the email, the new user did not.

I ran PS commands on my exchange server for message trace, and it shows the email being sent out to all 3 users.

nothing appears in quarantine on 365.

message trace on 365 from the report email to the new user returns nothing though,  

what am I missing?  its almost like 365 is saying "nope" for these emails to this one person, but no recording the nope anywhere.

is there another place to look?

3 Replies
Highlighted

@admiral_sulu : You might have already checked this but just to confirm, this new user was provisioned on-premises and then migrated to office 365? or a remote mailbox was created directly in office 365. Check if remote routing address is properly stamped against the user. Another good test would be if you have any mailbox on-premises or you can create one, see if you are even able to send emails to the new user from your exchange server.

Highlighted
by remote routing address, do you mean the onmicrosoft.com email account?
that seems correct
I have created mailboxes since then and no problems have been reported.
create the mailbox on exchange, then migrate to 365.
Highlighted

@admiral_sulu : Yup, the remote routing address is of the format: user@mail.onmicrosoft.com, you should see that in your email address policy/ proxy addresses of users you migrated.

Going forth, you can either create the mailbox on exchange and migrate it or simply use the following command to create the mailbox directly in cloud :

Enable-RemoteMailbox "Kim Akers" -RemoteRoutingAddress "kima@contoso.mail.onmicrosoft.com"

This has same effect as migrated user.

Ref: https://docs.microsoft.com/en-us/powershell/module/exchange/enable-remotemailbox?view=exchange-ps

Just to confirm, the issue has been resolved and you dont need any further assistance on this one?