Repository navigation
Specifying VM Extensions supported? #46
Description
Activity
Generally we don't want Azure extensions embedded into the good image as they can have issues post sysprep/name change (we primarily work with windows systems). You can use Azure policy to force the extensions into the image being created but this can cause all kinds of problems so we try to explicitly AIB from Azure policy where possible.
We generally deploy extensions on 're-hydration' either as part of the ARM/bicep deployment and/or via Azure policy if images are being deployed manually
I'm new to this Azure VM Builder. We have been using Packers for multi-cloud for ages.
Just out of curiosity, how do organisation slipstream all the required Azure agents/third party agents into an image? As an example, AMA agent for Linux which can only be delivered through VM Extension config.
Can we have the config embedded to the image to automatically onboard those essential VM Extensions when Virtual Machine is provisioned for anyone who are running an IT Operations to view logs, management or etc tasks?