Microsoft 365 Virtual Marathon - Microsoft365DSC, The next best thing since sliced bread

[kalmaronarok]

Hello there!
23:23 and somewhere around 26:00 you are saying that the recommended way to use it via DevOps because it's agentless.

1) I want to use it in Azure Automation directly as Runbook, so you mentioned that it requires a vm, while on DevOps don't. This is something I don't understand.
Running a runbook in Azure Automation and a Pipeline/Release in DevOps seems to be the same. Both during a runtime, take some host from AgentPool and execute "job" on that host.

When running it from DevOps, host from the AgentPool won't become an agent? How it works exactly?

2) Another thing that bothers me is: once configuration is applied (tiggered by a cmdlet on a host), that host became an agent and every 15 minutes (by default) that agent will verify the configuration. When host is stopped/killed/whatever, consistency check won't be executed anymore.
What happen if you trigger a release every 3 hours? Does it mean that every host will become an agent?

Ideally I would like to have:
- a scheduled job in Azure Automation that will apply the current configuration every 1h or something.
- an scheduled job in Azure Automation for monitoring part (just generate a report if there are diffs)

Can you help me to understand this better?

[jamesa]

This looks fascinating. Gonna check your github out, thank you:)