Uhmm, what about the opposite?

Instead of making the software development to mimic your organization communication structure, why not change your organization to mimic the software development needs?

In the Agile Manifesto principles, we can read about this: «The best architectures, requirements, and designs emerge from self-organizing teams.»

Why hindrance software development to accommodate a certain government structure, when the software itself could make that structure obsolete?

I understand that there is a lot of resistance, specially as you start climbing the organization structure, to accept changes (or in other words, to be agile), and because of it, things like SAFe ends being very popular because it allows to fool yourself that you are more agile. But given that a good software enable new levels of productivity in a company, it also looks like that it can disrupt how it works, therefore, change its structure.

Refusing that change will certainly diminish its productivity.

BTW: about microservices, according to the original guidelines, is one microservice per domain, or in other words, per team, so each team can be independent of the others.