Special characters in on premise OU

Question

Hi,
We have some OUs that begin either with # or have # in the OU name. Would this pose any issues for some tools in Azure like dsrevoke or with synchronization?

Online documentation says "/" will cause issues. But will #?

Answer 1

@AskAlways-3728 Thanks for reaching out. Having a special character like "/" or "#" will not have any effect on synchronization to azure AD. In both scenarios the OU will sync just fine with no issues. I just tested that in my lab as well and both OU's with "/" and "#" synced just fine.
Also I was not able to find anything with Dsrevoke with respect to "#" but will keep on checking, If I find something useful , I will post it here.

---

If the suggested response helped you resolve your issue, do click on "Mark as Answer" and "Up-Vote" for the answer that helped you for benefit of the community.

Answer 2

Hi,

All characters are allowed, even extended characters. However, although Active Directory Users and Computers lets you name an OU with extended characters, it is recommended that you use names that describe the purpose of the OU and that are short enough to easily manage.

For more information, see the best practices over here:

Naming conventions in Active Directory for computers, domains, sites, and OUs
https://support.microsoft.com/en-us/help/909264/naming-conventions-in-active-directory-for-computers-domains-sites-and

Best regards,
Leon