Share via

Special characters in on premise OU

Ask Always 41 Reputation points
2020-07-24T14:27:18.107+00:00

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 #?

Microsoft Security | Microsoft Entra | Microsoft Entra ID
0 comments
Accepted answer
  1. VipulSparsh-MSFT 16,311 Reputation points Microsoft Employee
    2020-07-27T09:07:57.987+00:00

    @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.

    1 person found this answer helpful.

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Leon Laude 86,026 Reputation points
    2020-07-24T16:11:49.597+00:00

    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

    2 people found this answer helpful.

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.