SOLVED

Invalid characters in UPN and email address

%3CLINGO-SUB%20id%3D%22lingo-sub-957340%22%20slang%3D%22en-US%22%3EInvalid%20characters%20in%20UPN%20and%20email%20address%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-957340%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EQuite%20a%20large%20number%20of%20mailboxes%20are%20not%20sync%20to%20Cloud%20because%20special%20characters%20are%20not%20supported%20in%20Office%20365.%3C%2FP%3E%3CP%3EIs%20invalid%20character%20support%20in%3A%3C%2FP%3E%3CP%3E-%20public%20folders%20where%20email%20address%20has%20special%20character%3F%3C%2FP%3E%3CP%3E-%20distribution%20list%3F%3C%2FP%3E%3CP%3E-%20mail%20contact%3F%3C%2FP%3E%3CP%3EThank%20you%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-957340%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3E2010%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%20Online%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%20Server%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EHybrid%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-957572%22%20slang%3D%22en-US%22%3ERe%3A%20Invalid%20characters%20in%20UPN%20and%20email%20address%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-957572%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F396472%22%20target%3D%22_blank%22%3E%40NodorinaMing%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYou'll%20need%20to%20clean%20that%20up%20or%20prevent%20the%20sync%20of%20those%20objects%20by%20filtering%20in%20AADConnect%3C%2FP%3E%3CP%3Ehere%20is%20some%20info%20on%20what%20is%20allowed%3A%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Foffice365%2Fenterprise%2Fprepare-for-directory-synchronization%3FredirectSourcePath%3D%25252fen-us%25252farticle%25252fPrepare-to-provision-users-through-directory-synchronization-to-Office-365-01920974-9e6f-4331-a370-13aea4e82b3e%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Foffice365%2Fenterprise%2Fprepare-for-directory-synchronization%3FredirectSourcePath%3D%25252fen-us%25252farticle%25252fPrepare-to-provision-users-through-directory-synchronization-to-Office-365-01920974-9e6f-4331-a370-13aea4e82b3e%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eand%20the%20tool%20that%20can%20help%20identify%20and%20fix%20these%3A%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Foffice365%2Fenterprise%2Fprepare-directory-attributes-for-synch-with-idfix%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Foffice365%2Fenterprise%2Fprepare-directory-attributes-for-synch-with-idfix%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-957574%22%20slang%3D%22en-US%22%3ERe%3A%20Invalid%20characters%20in%20UPN%20and%20email%20address%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-957574%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F396472%22%20target%3D%22_blank%22%3E%40NodorinaMing%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EYou'll%20need%20to%20clean%20that%20up%20or%20prevent%20the%20sync%20of%20those%20objects%20by%20filtering%20in%20AADConnect%3C%2FP%3E%0A%3CP%3Ehere%20is%20some%20info%20on%20what%20is%20allowed%3A%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Foffice365%2Fenterprise%2Fprepare-for-directory-synchronization%3FredirectSourcePath%3D%25252fen-us%25252farticle%25252fPrepare-to-provision-users-through-directory-synchronization-to-Office-365-01920974-9e6f-4331-a370-13aea4e82b3e%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Foffice365%2Fenterprise%2Fprepare-for-directory-synchronization%3Fredirect...%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3Eand%20the%20tool%20that%20can%20help%20identify%20and%20fix%20these%3A%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Foffice365%2Fenterprise%2Fprepare-directory-attributes-for-synch-with-idfix%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Foffice365%2Fenterprise%2Fprepare-directory-attributes-for-synch-with-id...%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-965125%22%20slang%3D%22en-US%22%3ERe%3A%20Invalid%20characters%20in%20UPN%20and%20email%20address%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-965125%22%20slang%3D%22en-US%22%3E%3CP%3EI%20did%20quite%20a%20bit%20of%20testing%20on%20this%2C%20there%20are%20some%20nuances%20and%20you%20can%20add%20back%20addresses%20with%20special%20characters%20as%20a%20secondary%20alias%20and%20that%20will%20work.%20See%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fcloudrun.co.uk%2Fexchange-online%2Fspecial-characters-in-upn-and-email-addresses-in-office-365-migrations%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fcloudrun.co.uk%2Fexchange-online%2Fspecial-characters-in-upn-and-email-addresses-in-office-365-migrations%2F%3C%2FA%3E%26nbsp%3Bfor%20more%20info.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1019326%22%20slang%3D%22en-US%22%3ERe%3A%20Invalid%20characters%20in%20UPN%20and%20email%20address%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1019326%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3CBR%20%2F%3E%3CBR%20%2F%3EREF%20to%20%3CA%20href%3D%22https%3A%2F%2Fcloudrun.co.uk%2Fexchange-online%2Fspecial-characters-in-upn-and-email-addresses-in-office-365-migrations%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fcloudrun.co.uk%2Fexchange-online%2Fspecial-characters-in-upn-and-email-addresses-in-office-365-migrations%2F%3C%2FA%3E%3C%2FP%3E%3CP%3EI%20have%20removed%20invalid%20characters%20from%20all%20email%20addresses%20(not%20display%20name).%20However%20the%20mailbox%20is%20still%20not%20sync%20to%20Office%20365.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EGetting%20NDR%3A%3C%2FP%3E%3CTABLE%3E%3CTBODY%3E%3CTR%3E%3CTD%3E%3CTABLE%3E%3CTBODY%3E%3CTR%3E%3CTD%3E%3CP%3EReported%20error%3A%3C%2FP%3E%3C%2FTD%3E%3CTD%3E%3CP%3E%3CEM%3E550%205.1.10%20RESOLVER.ADR.RecipientNotFound%3B%20Recipient%26nbsp%3B%20avc.dec%40companny.xxx%26nbsp%3Bnot%20found%20by%20SMTP%20address%20lookup%3C%2FEM%3E%3C%2FP%3E%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3E%3CP%3EDSN%20generated%20by%3A%3C%2FP%3E%3C%2FTD%3E%3CTD%3E%3CP%3EME2Pxxxxxxx98.ausprd01.prod.outlook.com%3C%2FP%3E%3C%2FTD%3E%3C%2FTR%3E%3C%2FTBODY%3E%3C%2FTABLE%3E%3C%2FTD%3E%3C%2FTR%3E%3C%2FTBODY%3E%3C%2FTABLE%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

Hi,

 

Quite a large number of mailboxes are not sync to Cloud because special characters are not supported in Office 365.

Is invalid character support in:

- public folders where email address has special character?

- distribution list?

- mail contact?

Thank you

3 Replies
Highlighted
Best Response confirmed by NodorinaMing (Occasional Contributor)
Solution

@NodorinaMing 

You'll need to clean that up or prevent the sync of those objects by filtering in AADConnect

here is some info on what is allowed:

https://docs.microsoft.com/en-us/office365/enterprise/prepare-for-directory-synchronization?redirect...

 

and the tool that can help identify and fix these:

https://docs.microsoft.com/en-us/office365/enterprise/prepare-directory-attributes-for-synch-with-id...

Highlighted

I did quite a bit of testing on this, there are some nuances and you can add back addresses with special characters as a secondary alias and that will work. See https://cloudrun.co.uk/exchange-online/special-characters-in-upn-and-email-addresses-in-office-365-m... for more info.

Highlighted

Hi,

REF to https://cloudrun.co.uk/exchange-online/special-characters-in-upn-and-email-addresses-in-office-365-m...

I have removed invalid characters from all email addresses (not display name). However the mailbox is still not sync to Office 365.

 

Getting NDR:

Reported error:

550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient  avc.dec@companny.xxx not found by SMTP address lookup

DSN generated by:

ME2Pxxxxxxx98.ausprd01.prod.outlook.com