OK, the first choice is how you want to package your applications, containers or not containers. Using containers may make development and deployment of your applications easier, but if you have no experience with containers then this is going to be a steep learning curve.
If you do decide to use containers then you essentially have 3 options in Azure:
- Azure Web Apps - the platform as a service hosting for web applications, this supports running containers
- Azure Container Instances - containers as a service where you can just request a container be created and run for you
- Azure Kubernetes Service - Kuberenetes clusters as a service
By the sounds of it you don't need the functions that Kubernetes provides, so I would avoid the extra complexity that brings. Azure Container Instances would work for you, but they are really designed for handling burst workloads, rather than 24/7 services, so the pricing may not be what you want. The simplest option may be to look at using Web Apps. You can run your containers without needing to worry about the underlying infrastructure and it does support multi container workloads - https://docs.microsoft.com/en-us/azure/app-service/containers/tutorial-multi-container-app
If you don't want to go down the container route then you are looking at the more traditional hosting services. This would limit you to:
1. Azure Web Apps (without containers)
2. Azure VM's
The Azure VM route would need to be configured and managed by yourself, so not ideal. Again, I would probably look at web apps.
I haven't mentioned databases, I would strongly recommend you look at Azures Database as a Service offerings, be this SQL, MYSQL, PostgreSQL etc. Running a DB in a container is not what I would advise.