This is why when I built our systems, I did most of them using a combination of public/private keys and TOTP 2fa. Also severely isolating those systems so that the list of people who need access is as small as possible.
It's orders of magnitude less of a pain in the ass than password cycling.
It's not just Microsoft, I believe NIST has the same guidelines now.
Forcing people to constantly change passwords just means they either iterate a number or write them down. It also means they start to resent the tech and people who make them do it. It helps no one.
That’s real slick. Royalty free Lofi is 90% of my music consumption anymore since the RIAA decided they don’t want their artists to be relevant to anyone who is big on streaming.
I have found 2 use cases, one of which I've never actually seen in the wild.
The most common use case is, "I need to store data where the schema is unknown or can change without notice, and have my shit not break." This is what we used Mongo for.
The other use case I could see (and this is pretty much only with Dynamo) is, "I want to build an application that's cross-region native. Most of my data is relatively static, so I accept eventual consistency on changes. I will have a separate data store for transactional data and data that cannot be eventually consistent." I want to build this project, but it will never happen because it's too easy to RDBMS in a single region to start.
The author calling pfsense, "overpriced," has never actually purchased business grade network equipment. Netgate devices are remarkably affordable for what you pay for them in comparison to most of their competitors.
It's orders of magnitude less of a pain in the ass than password cycling.