AWS Systems Manager vs. Azure Automation

When you have a process running in aws that needs to copy files to group of instances as part of the process Installing software on a group of machines Adding Cloudwatch agent to instance.

Incentivized

We have found Azure Automation to be well-suited for tasks that must be performed on a scheduled basis. No matter how simple or tedious tasks are to perform manually, if they run on a scheduled basis, it makes sense to have them automated. If the tasks at hand are only performed once or infrequently, then it may be best to continue performing them manually.

Incentivized

• Copy files to a group of instance with particular tag
• Enable CW agent and push metrics to CW
• Easy to install software in a group of instances.

Incentivized

• Scheduled automation of Microsoft 365 and Azure tasks
• Scheduled automation of scripting (e.g. Powershell)
• Perform periodic maintenance

Incentivized

• I would like to see the Search feature improved a bit more.
• UI is little bit confusing initially

Incentivized

• An automation template library would be nice
• Clear estimation of costs - this goes for the entire Azure Automation platform
• It can be daunting at first due to all the settings and menu levels, but it is not difficult once you get started.

Incentivized

We did not evaluate any other automation products since we are already using Microsoft 365 and the Azure platform. Additionally, Azure Automation allows for a reasonable number of tasks to be performed each month at no cost, which is especially nice when testing the platform. We found Azure Automate's integration of Powershell invaluable when working directly with Microsoft 365, Sharepoint, Azure AD, and other systems via API.

Incentivized

• Reduced team's time spent on EC2 management
• Patch management
• Remote access

Incentivized

• Ensures tasks are not forgotten
• Saves times - routine tasks no longer have to be performed manually
• Complicated tasks are no longer an issue

Incentivized