I personally like using a wholly JS stack, with TypeORM + MySql/Postgres over MongoDb + Mongoose because TypeOrm's Typescript support is much stronger. After developing large projects with Typescript, there is no going back to regular javascript (typings help catch a LOT of errors / maintains data structure !)

Sticking with a javascript stack will allow you to share certain aspects of your application between front and backend. For example: one particularly common feature is to validate API call data and form entry data. Both of these are the same data shape typically (aside from pagination, metadata, etc), and can benefit from a single schema for validation. I use Yup to define this schema, then in the front and back end I can utilize this definition instead of rewriting the same logic in two different languages.

Same goes for certain utility functions such as data structure typings, decryption, encryption, sanitizing inputs, formatting of data, and other utilities. No point of writing these in two languages when both frontend and backend will use them. It will also help reduce developer work load, due to less tests / code to work with.

The only thing you must ensure in your import chain the frontend never imports any secret variables or sensitive logic used by the backend, as that will get bundled into your application. All shared imports should be individual modules

If you want to go one step further, next.js is basically create react app with server side rendering (SSR). This would allow you to skip the annoying step of configuring separate backend and frontend build tools. Might be worth exploring depending on your skill level.

You must have gone through multiple thoughts on how to handle the requirement, but the biggest problem that I am able to see here is a dependency on a certain platform for executing Powershell scripts. Next is being a developer will never suggest having Powershell or bash as a backend of your system until it is related to some IoT Stuff. In place of it, I would rather suggest you use Infrastructure as a Code that comes with terraform or Ansible or as your application is based on Azure so u can use Azure Resource Manager too.

Adding to it for making config or attaching a trigger to these infrastructure controllers, you can use lightweight stateful APIs with the help of flask or express or go-mux, to keep track on the progress of deployments.

Hi

I am new here . . . but for backend - I assume you implement it with NodeJS - maybe you could give try to FeathersJS Server? I have used it previously for my PHD project. It comes with support of dozens of databases. You do not need to worry about database scripts and connection routines, FeathersJS abstracts all of this for you. It implements connection with database using services. These services conform with CRUD philosophy which obviously you can customize based on your needs.

This server is well documented.

Also authors of this server claim that you will be able to deliver production grade app within days and from my experience I can say that this is true. This server should be good choice for beginner

Good luck!