Congrats, you handled every technical issue by the book ! Now, according to Martin Fowler's definition, this is not microservices (cf. https://martinfowler.com/articles/microservices.html#ProductsNotProjects).

Likewise, your conclusion is confusing "Microservices architecture has great features such as high availability, scalability, automation, autonomous teams". If you don't start from autonomous teams, then you have already wasted the company's money.

I have to admit that every microservice talk/post handles the technical side, but not the organizational side. Everybody seems to have forgotten Conway's law?!

Microservices are an organizational solution to an organizational problem (the development team grows too much). If you can split your monolith into microservices but keep your legacy organization, you're wasting your money, your time and your sanity. But of course, you'll be able to write it down on your resume.