Microsoft 365, AD and Windows · #29
Online AD and Microsoft 365 Username Generator
Generates collision-free UPN and sAMAccountName candidates from a list of names; converts Turkish and German characters correctly.
- Data is processed in your browser and not sent to a server
- Export: CSV
Tool
What does this tool do?
In bulk onboarding the most frequent errors are badly converted characters (İ → i̇, ı → ?), collisions with existing accounts missed because of letter case, and two people with the same name silently getting the same account. The tool converts names safely to ASCII, compares case-insensitively with the existing list and its own candidates, and numbers collisions.
How to use it
- Enter staff as
First;Lastper line (tab or comma also work). Only the first word of the first name is used. - Paste existing UPNs or sAMAccountNames into the second field (e.g.
Get-ADUser -Filter * | select -expand SamAccountName). - Choose domain and templates, press Calculate and download the CSV.
Fields
- Staff list
- First;Last per line. Data does not leave your browser.
- Existing user names (optional)
- UPN or sAMAccountName, one per line.
- UPN domain
- UPN template
- {first} first name, {last} last name, {f}/{l} initial.
- sAMAccountName template
- At most 20 characters; long names are truncated.
- German characters
- ü → u or ü → ue
Worked example
| Input | Value |
|---|---|
| Staff list | |
| Existing user names (optional) | |
| UPN domain | contoso.com |
| UPN template | first.last |
| sAMAccountName template | flast |
| German characters | Plain (ü → u, ö → o, ä → a) |
Expected result: cagri.isik, ali.yilmaz2 and ali.yilmaz3 (ali.yilmaz exists), sukru.ozturk, jurgen.muller; sAM: cisik, ayilmaz2 …
[email protected] in the existing list counts as a collision despite the upper case. The two Ali Yılmaz do not get the same name; numbers are given in order. Numbered accounts are marked in the CSV; confirm their email address with the user.
Method and assumptions
Conversion: Turkish ç ğ ı İ ö ş ü → c g i i o s u (İ and I are lower-cased with Turkish rules). German ä ö ü ß become a o u ss or ae oe ue ss depending on the option. Other accents are stripped; anything but letters and digits is removed.
Comparison is case-insensitive, and the part before @ of the UPN and the sAMAccountName share one pool. Collisions get 2, 3… appended. sAMAccountName is limited to 20 characters.
Using the result and troubleshooting
Import the userPrincipalName and sAMAccountName columns into New-ADUser or the Microsoft 365 bulk add template. Refresh the existing list right before bulk creation.
For users whose name changes, use the UPN and SMTP Address Change Planner.
Limits and common mistakes
- It does not connect to AD or Entra; it only compares with the list you enter.
- Collisions with proxyAddresses or deleted objects (recycle bin) are not visible.
Frequently asked questions
Why does 'İ' sometimes become 'i̇'?
With non-Turkish lower-casing, İ becomes i plus a combining dot. The tool lower-cases with the Turkish locale and reduces the result to ASCII letters.
Related tools and service
- UPN and SMTP Address Change PlannerBuilds the proxyAddresses value for users' new UPN and primary address, keeps the old address as an alias and shows conflicts.
- AD Distinguished Name ParserSplits one or more DNs into CN, OU path, domain and canonical name.
Related service: Server and Cloud Management