They are probably just trying to keep consistency between an AD instance and Exchange or something like that. Or just laziness.

When we generate new user accounts we run a script that generates an email (so we don’t have to manually do it). It gets generated with the username of the individual which in our case would be first initial, last name. Then another alias gets generates to first.last@x.whatever and is set as primary. While the username@x.whatever is left as an alias, but would still technically work if you emailed it.

If a username already exists we will use the first and second letter of the first name and then the last name, etc.

In the above I mentioned consistency and laziness, but there is also another side, and that is your user base. If you are servicing hundreds of thousands of people or just a ton in general, consistency is very much preferred. Try having to explain to an end user that their login is simply “username” for their computer, but their email is “first.last@x.whatever” oh and let’s go ahead and loop in Azure SSO so now their software license login and login for all these other portals is “username@x.whatever”.

You end up with a mass of confusion. Sometimes simplicity is best when it’s possible.

Sure, please do!

FML lol. I’m still recovering from the flu.

https://www.timbers.com/competitions/mls-regular-season/2025/matches/porvsatx-03-01-2025/

Will update title shortly.

Thank you for pointing that out.

That is a much better though than I had.

I was over here like, wtf, did you just defile that grub by shoving a bullet in it’s butt, uhhh head? I know nothing about grubs lol.

Glad to know it’s not that.