I have a problem with SharePoint on-prem 2016 people picker: Our client dont want to open any unsecure ports like 389. Is there any way to configure people picker work only with port 636?

Adding users to sites is very difficult without possibility to resolve users with people picker.


  • Thank you Trevor. It seems to be hard to add users even manually without people picker thats resolving accounts. Only way so far is to ask users login site once, but problems for creating personal sites and some other functions still exists. Wish I could convince importance of tcp/389, even that security is of course important.
    – Antti
    Jan 30, 2019 at 6:41

2 Answers 2


This is not possible. Usage of tcp/389 is baked into the SharePoint code for the People Picker.


I had a project with a similar issue. We ended up writing our own ClaimsProvider.

Our case didn't match exactly your problem. We had to use UserProfileService as user base, as we were not allowed to communicate with ActiveDirectory in any way.

We started digging into the problem with this article:
Fixing People Picker for SAML Claims Users Using LDAP

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.