Kick back and have a drink while Azure Automation does your dirty work
Rating: 8 out of 10
IncentivizedUse Cases and Deployment Scope
We are currently using Azure Automation to manage aspects of Microsoft 365 and Sharepoint that cannot otherwise be automated. Specifically, we are using it to generate failed login alerts from Microsoft 365 and to perform synchronization of employee information between Azure AD and Sharepoint for an internal business directory. With the use of Azure Automation, we have both of these tasks scheduled to run periodically each day.
Pros
- Scheduled automation of Microsoft 365 and Azure tasks
- Scheduled automation of scripting (e.g. Powershell)
- Perform periodic maintenance
Cons
- 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.
Likelihood to Recommend
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.
