Are you sure there is no ticket? Some systems let you make tickets that the end user is not notified for. Also, depending on the size/ levels of automation your call may have populated all your info on the agents end.

Depending on the help desk they probably knew it was you. Did you call from a phone HR knows about? If it was a walk up, did they make the ticket before or after resetting your MFA?

Aka sso.tax

Wiki for anyone who does not feel like searching: https://en.m.wikipedia.org/wiki/Ninja_rocks

I should point out that when Wikipedia of all places has a legal status section you should take real care with how/when/where you have them.

As someone who manages a Google workspace instance currently, God I wish I had exchange for my email service.

Let's take this one step further. I should be able to get the core ideas in your code by comments and cs 101 level coding (eg basic data structures, loops, and if/then).

We've got it rigged up for aws sso. Each department can make any number of permissions sets (and link to any number of groups). The config for that is all stored in git (with code owners configured so you can only mess up your own stuff).

So I'm using it with Python. For me it's able to do some stuff that terrafom never would be able to (Ive got a spot where resources are generated for each file/object on disk).