Many people use the Windows Task Scheduler to run PowerShell scripts. The Task Scheduler works, but it creates a dependency on a specific workstation and isn't as secure as you might like. Running Microsoft 365 PowerShell scripts in Azure Automation is a much better idea. It's time to dump the Task Scheduler!
Microsoft 365 PowerShell is not a single entity. Rather, it spans a mixture of workload-specific modules and the Microsoft Graph PowerShell SDK. When the time comes to write a new script, what should a developer choose to use?