Perhaps the early microservices evangelizers such as Netflix have created this environment - after all, who cares whether Netflix is a monolith or a swarm of microservices as long as billing works and users get content when they want?
There's another strong driver for microservices however, which is customer choice, particularly in SaaS settings.
In our industry (HR software), there is no one right answer, or one business problem - customers demand choice, every customer has slightly different needs, and microservices are indicated because they allow customers to pick and choose. The same is true for most SaaS areas I would say.
As an example, one tiny sub-area of HR software, employee engagement improves when we offer employees meaningful benefits. It turns out that many employees love their pets, and offering pet insurance could be a great perk (the HR space is so big that just this niche within a niche could be a multi-million dollar opportunity for someone with a good offering).
Yet would anyone seriously consider altering a monolithic HR application to add pet insurance management? Never. The only viable solution is a microservice, that does just this, and does it well, and plugs into the rest of the stack via APIs.
tl;dr: in the SaaS world, microservices are sometimes indicated not for architectural reasons, but to support customer choice, which is far more important.