My team is attempting to come up with a new naming standard for our Active Directory groups within SQL Server to help manage permissions.
However, before implementing this convention we decided to look up character limitations of both active directory and SQL Server Logins and while the character limit itself doesn't appear to be a direct issue, we did stumble upon this article from 2014: Max Length of AD Names for Security
My team and I used one of our dev servers to attempt to recreate this potential issue, but realized that it was very difficult to test as the permissions on AD groups sometimes don't propagate for hours even if you restart the server (tested this last night and proved it). I am wondering if anybody knows if this issue has been resolved on SQL Server 2016/2017. Is it safe to use the naming convention I posted at the very top where the first 20 characters are the same or do we have to come up with a way of abbreviating all of our objects so that the first 20 characters of a login are NEVER the same.