Specify Profile Path Attribute for AAD Joined Windows 10
Administrator should be able to choose which attribute from AAD should be used for local profile path creating for Windows 10 Azure AD Joined workstations in C:\Users. Current DisplayName attribute is not flexible, because it create different paths with special characters.
Stanisław Bugalski commented
Yeah, AAD Connect product group should consider that case.
Now we have to remember to change user First and Last name before first logon.
This is such a triavial issue I'm amazed how it hasn't been addressed for years now.
Here's the problem in more details:
When a Windows 10 device is joined to Azure Active Directory, the logon process creates the user's folder in this location: c:\users (as might be expected, this becomes the %USERPROFILE% path). The folder name appears to be constructed based on the user's First name and Last name, as entered in the Azure Active Directory.
However, when the user's first name or last name in the Azure Active Directory includes non-ASCII international characters (for ex. šđčćž), these will be included in the folder name. Although that's not a problem by itself, it generates a range of problems for a huge number of applications typically relying on %APPDATA% to store important settings. The applications having problems include Microsoft Office, Outlook, Google Drive, MS Teams, Skype and so on and they typically fail during either installation or startup.
The workaround is to change the First and Last name fields in Azure AD (prior to first time logon) so they contain only ASCII characters, or alternatively change the %USERPROFILE% folder name in the registry, but that's only a workaround to a bug.