VM Started Automatically to Create/Update/Delete Virtual Machine Extension by SQLVMResourceProviderAuth

Thanks for posting your question in the Microsoft Q&A forum.

Azure may automatically start a stopped VM when extensions (like the SQL IaaS Agent) need to be created, updated, or deleted. These operations require the VM to be running so scripts/agents inside the OS can execute. The actions show up under SQLVMResourceProviderAuth because they’re triggered by the SQL VM Resource Provider, not by a user.

Afterward, Azure does not stop the VM again, you need to shut it down manually if you don’t want it left running. This is expected behavior.

Please don't forget to close up the thread here by upvoting and accept it as an answer if it is helpful

Hi tonypinter ,
Welcome to the Microsoft Q&A Platform.

why it happened

• azure started the vm under SQLVMResourceProviderAuth to run the vm agent and install/update/remove the SQL IaaS Agent extension
• you’ll see “create/update” and sometimes “delete” for the extension
• after that the vm stays running; it isn’t auto-stopped

common triggers

• an azure policy like “deploy SQL IaaS Agent extension for SQL server vms” ran a remediation
• you registered the vm as a sql vm or changed ahb/licensing, backup, or auto-patching
• automatic upgrade or migration of the sql iaas extension

how to confirm (quick checks)

• vm > activity log: filter for start virtual machine and virtual machine extension; caller = SQLVMResourceProviderAuth
• azure policy > compliance: look for sql vm extension policies and any remediation tasks
• vm > extensions: find SqlIaaSExtension and check its recent timestamp/version
• sql virtual machines (resource): review auto-patching, backup, and ahb settings

this is expected platform behavior, not user activity