Hi @Israel, Sahar ,
Thank you for reaching out to Microsoft Q&A Forum ,
We would strongly suggest you the following on this case:
--> If you don't want these extensions enabled , Please do go ahead and uninstall it from portal/CLI .
--> If you want to add them back , please use either of portal/CLI as well , Detailed steps as follows :
1) Using Azure Portal: (Easy way)
-> Browse to the VM Blade
-> Go to Diagnostics Settings Under Monitoring Section
-> Select Diagnostics Storage Account (if exists or create a new storage account to store diagnostics data)
-> Click on Enable Guest-Level Monitoring
2) Using Azure CLI command
az vm extension set \
--resource-group myResourceGroup \
--vm-name myVM \
--name IaaSDiagnostics \
--publisher Microsoft.Azure.Diagnostics \
--version 1.9.0.0 --protected-settings protected-settings.json \
--settings public-settings.json
Please note to create protected-settings.json & public-settings.json files.
Source: https://learn.microsoft.com/en-us/azure/virtual-machines/windows/extensions-diagnostics
Why is it not suggested to have running extensions disabled with the VM using tweaks ?
When ever an azure VM boots up , It will try to look into all the available extensions and would wait for all of them to start before proper VM start.
Hence if we have an extension which is not in running state or have a scenario where an extension is running but it is somehow disabled from OS , The VM start/stop operation could timeout or fail .
to avoid such issues on the VM we would suggest you to follow the above approach .
Hope this gives you more clarity on extensions and its importance on VM provisioning , Please do accept the answer if this help .
Thanks & Regards,
Pradeep