Utilizing Azure Custom Script Extensions to maintain a custom PowerShell module across multiple servers

Question

I'm trying to automate some tasks at work and someone gave me an idea that we could utilize Azure Custom Script Extensions to maintain a custom PowerShell module across multiple servers.

The script is located on our Azure DevOps, but I assume I could create a Pipeline that moves it to storage account after a pull request is completed.

However, my question is - how does Custom Script Extension work in the first place and would it be suitable for my needs, which are having an up-to-date PowerShell module available on multiple servers?

question from:https://stackoverflow.com/questions/65846844/utilizing-azure-custom-script-extensions-to-maintain-a-custom-powershell-module

Answer 1

Waitting for answers