spocino Totally respect where you are coming from. Preference of one shell over another for daily driving is something very subjective. But I can tell you from experience that is a great sysadmin tool on any platform, and only getting better.
One of the best examples of where it is excels is the ability to work in a shell with an object-oriented language. This has many benefits, one being that It takes a lot of the trouble of parsing data from command output. While using sed, tr, and the like to parse and manipulate data is definitely doable, it is cumbersome. The ability PowerShell gives me to just assign the output to a variable and call the property I want like "$var.property" is pretty great. (Or just surround the command in parenthesis and dot call the property directly from the output like "(Get-Process).name", if you're feeling frisky.)
Even when you have to work with string output directly, a String is a class in PowerShell (since it's all .Net core), and has all the String methods you'd expect from a full programming language. So you can very easily and intuitively do splits, replaces, trims, joins, and more.
That all said, in a lot of ways I think of PowerShell as more of a threat to Python for IT automation, tooling and systems orchestration, than a threat to Bash (and the others) as a shell. If you work in a Linux only environment, or you're just a home user of Linux, it probably doesn't make sense for you. Doubly so if your bash-fu is already strong, and you're Python savvy. But in mixed OS environments, it is an invaluable tool to have as an admin, especially at the enterprise level.