Problem with Active Directory 2016

Summary

First of all sorry for my English abilities. I'm a freshman yet.
AD 2016 doesn't implements RFC 822 for field userPrincipalName (username@domain)

Actual Behavior

The default searchFilter is:
(&(objectClass=user)(userPrincipalName={0}))
but AD 2016 has no data in userPrincipalName... then I send my "own" search filter instead of default with:
(sAMAccountName={0})

When you defines the AuthenticationProvider with a domain and an URL, It always use the method "createBindPrincipal" for the username and "{0}" will be (username@domain) and It is different to the "sAMAccountName".

If you send a "null" domain "createBindPrincipal" will return (username) as expected, although the "contextFactory" will throws an exception in "createContext" method.

Expected Behavior

Actually I don't know the best solution for this, but I expected configuring my domain, my URL and an account wich those executes "doAuthentication" succesfully.

Configuration

I have a Java config. I don't know if I might put my code here. But my code words under previous versions of active directory like this link:
https://msdn.microsoft.com/en-us/library/ms680857(v=vs.85).aspx

Version

Gradle Var:
springSecurityLdapVersion = "4.2.3.RELEASE"

Start by tracing AuthenticationProvider through createBindPrincipal and the contextFactory/createContext path, comparing the configured domain and URL with the custom searchFilter. Check how doAuthentication receives the username and whether the sAMAccountName filter is usable with the generated principal. Done means a Java-configured AD 2016 provider authenticates successfully with the documented account settings.