Developing Angular And Serving Though Back-end Pros and Cons?

I’ve been breaking down a tool at work into micro-services.

We use Angular, store production build code in a static folder in Pyramid.

If a Service has no need for a pyramid back-end, should I strip way the Pyramid back-end and use ng serve and the angular HTTP API instead?

Do all Micro-services need to have some type of same configuration in regards to tools used?

Or is it best to only take what you need with you when abstracting out a service from a monolith?

I plan on doing auto generation boiler plate code for services later, so I thought of standardizing tools for each service.

Originally I was serving compiled index.html file from Pyramid routes for each service that required front end.
Lately, I ran into a bug that will not allow angular to wait on HTTP responses from pyramid back-end.

Thus, I have decided to look into limiting the tools to what is only needed. But I am not sure if it the correct move.

Are their any pros regarding security for serving and routing angular apps through back-end’s such as pyramid?

What are your opinions and advice if any. Thank you!