In my case Microsoft licensing and the cost that comes with it
And for internal applications where users already have per-user Windows CALs, Windows Server is already licensed and deployed, IIS is effectively free.
With that said, it's not obviously better or worse than open source alternatives in general, just different — though, at least from an admin perspective, not necessarily any more different than, say, Apache and Nginx.
My own personal bias tends towards deploying on a given application's "native" platform where possible, so I'd generally only consider IIS as an application server for a Windows-native application or application developed using a primarily Microsoft stack.
And, for reasons of license cost alone, I'd certainly look elsewhere for any non-revenue-generating personal applications.
But in these cases at least, modern IIS releases are, in my experience, stable, reliable, extensible, securable, and as easy to deploy and configure as anything else I've used (mostly Apache and Nginx).
I can't comment on scalability because I've never personally had to scale it beyond a few tens of thousands of (total, not concurrent) users.
Plenty of dumpster-fire applications are implemented on top of IIS, of course, but that's true of any popular Web application server.
I last used it full time in 2015 (about 20% of my career was spent in .net stuff and the frameworks and languages were excellent.) Back then I could do single click deploys out of the box from visual studio straight to IIS in ways much more elegant than anything I had seen in the ruby world.
All this was before asp.net core, and all their Linux stuff.
It must be even easier now.