How to automate disparate technology process in Azure

To answer your question, yes, sure, there's ways to automate the process using Azure. I would choose Logic Apps because Business Process Automation is one of it's primary use cases. But...that's the easy part!

The hard part for you is making these disparate apps accessible to outside services. Running within Windows VM's, they don't have natural endpoints like native Azure Services.

There's lot's of ways to do this, depending on you ability to modify the VMs and programming skills.

Continued: Since all the VM are in the same domain and network connected, the first thing would look at is a bit old school (new and shiny isn't always the best), Windows Tasks. At least for 2-4.

Meaning, a Schedule Task on #2 can check for the email, then run its SQL, then start a Task on #3.

#3 can run it's jobs then start a task on #4 that runs the c# program. Then #4 can trigger the Python script. Your big gap then is how to trigger the Python script. That could be as simple as FTP'ing a trigger file for task on #5 to see.

The Windows scripting can be done in PowerShell. Not very elegant, but neither is your environment.

Finally, and almost the most important, you can use Azure Monitor and a custom log format to track the process.

To answer your question, yes, sure, there's ways to automate the process using Azure. I would choose Logic Apps because Business Process Automation is one of it's primary use cases. But...that's the easy part!

The hard part for you is making these disparate apps accessible to outside services. Running within Windows VM's, they don't have natural endpoints like native Azure Services.

There's lot's of ways to do this, depending on you ability to modify the VMs and programming skills.

Continued: Since all the VM are in the same domain and network connected, the first thing would look at is a bit old school (new and shiny isn't always the best), Windows Tasks. At least for 2-4.

Meaning, a Schedule Task on #2 can check for the email, then run its SQL, then start a Task on #3.

#3 can run it's jobs then start a task on #4 that runs the c# program. Then #4 can trigger the Python script. Your big gap then is how to trigger the Python script. That could be as simple as FTP'ing a trigger file for task on #5 to see.

The Windows scripting can be done in PowerShell. Not very elegant, but neither is your environment.

Finally, and almost the most important, you can use Azure Monitor and a custom log format to track the process.