The resulting server will be suitable as a (shared, insecure) playground accessible via the internet. It is not a secure setup suitable for production usage. A technical operator setting up a production system would certainly approach things differently and possibly choose different Azure services.

This article shows the simplest and fastest way to get a Camunda BPM server running on Microsoft Azure without command line usage. Keeping things as simple as possible, we perform all steps in the browser. No technical knowledge of Azure or Camunda and no local tool installation are required.

At CamundaCon Live today, I was thrilled to unveil the next step on the Camunda Cloud roadmap - the Camunda Cloud Early Access Program. Now your team can get started on Camunda Cloud, running your clusters with more resources, a higher replication factor and a higher partition count.

In the last few years we’ve noticed many of our users are migrating from bare-metal infrastructures to cloud-based ones. While the cloud has overcome several limitations of the traditional infrastructure, other problems arise when deploying your microservices in environments that have the possibility to scale up and down dynamically based on workload.
When deploying Camunda BPM, the first problem that you will encounter will be, most probably, session management.While this is easily solvable in traditional environments by using sticky sessions, the same solution does not apply when you deal with cloud environments like, Kubernetes.