I don't know that I've ever face palmed harder from a user response than today

Got it,
Username: eauditor
Password: I emailed you
- Weird. It's just showing up as ******** for me
  
  hunter2 for me

The skill of removing as much ambiguity as possible is valuable. This includes ambiguity derived from loopy brain. Prepare to still be amazed by wild interpretations, but minimize what you can. One tip is to reduce message complexity and clearly separate concepts (in this case, the greeting and the actual instructions).
- I get that, and I've had a reminder of an old failing at explicit communication to end users on my desk for 5+ years to help keep me grounded, but come on... In what interpretation other than Yoda giving instructions would an English as their first language user think 'hey hey!' was the username I was providing? It's out of frame, but the previous three sets of IMs I've sent this user started with hey hey! hey hey! and hello hello! so it's not like this was even a one off weird greeting for them (I should probably mix it up a bit more but what can you do)
  
  That's another useful tip: never underestimate user stupidity.
  
  It is almost as if OP was expecting their customer to have attended elementary school or something.

An auditor with this level of scrutiny and attention to detail? Say it ain't so.
- Sadly this was an internal coworker who requested the auditor’s access…
  
  Oof, i can relate to that.
  What's really sad here, though, is that it was so easy and effortless to assume it was the auditor himself lmao

Ah yes, email, the most secure channel possible
- Super fair, but it’s at least across two channels for a 3 day login with very limited permissions, not something I’m worried about in this situation.
  
  Actually it is not. 1:1 and group chats in Teams are stored in each participants mailbox. Ignore this if you're using exchange server or other onprem or cloud solution for email than exchange online :^)
  https://learn.microsoft.com/en-us/purview/ediscovery-teams-workflow#where-teams-content-is-stored
  Also both are stored in clear text due to compliance reasons.
  While SMS is rather insecure protocol, it's still generally the best way of delivering a new password to users as long as the username is delivered in a different way. This is mainly because it's one of the only methods generally available that is completely separate from your other communication methods besides calling (but try delivering password via call haha)
  Also the SMS should not contain any context to which system it is meant for, this info should be delivered together with the username. It's sometimes rather easy to guess a username (such as first.lastname or shortened) but gets harder when you need to guess the system as well.
  Of course even better way would be to not deliver password at all and let the user reset their passed themselves if there's a system in place for it. SSPR if you're in m365. https://learn.microsoft.com/en-us/azure/active-directory/authentication/concept-sspr-howitworks
  Edit: not sorry for rant these are very interesting topics I love to talk about.
  Edit2: formatting + more rant about sms
- Microsoft Teams 😂

Every day, I grow more convinced that the average person should never be anywhere near a computer.
- I am in the middle of a CRM migration and I feel like I'm having the "emails are IN the computer?!?!" conversation every hour