RunCommands and Custom Script Extension failing across the subscription

Question

Im having issues executing run commands across the subscription. They hang even in new Virtual Machines 90% of time similar to deploying Custom Script Extensions.

I've tried to run the same commands by deploying the same template in another subscription and they all worked immediately. Is there a limit or throttle in place that I need to remove?

Answer 1

Hi Leonardo Santos,

Thank you for your patience while we worked on this request.

Issue Summary: You reported that RunCommand, Custom Script Extension, and other VM extension–based operations were not executing and were remaining in a stuck or updating state across multiple VMs and VMSS instances within the affected subscription, while the same deployment functioned correctly in another subscription.

Findings from Engineering Review: After analysis, this behavior was not attributed to a single platform-side failure. Instead, it was determined to be a combination of the following factors:

RunCommand timeout scenarios where operations did not complete within the expected execution window.

Resource constraints (memory pressure) on certain VMs, which can prevent extensions from starting or completing successfully and may lead to errors such as OutOfMemoryException.

A concurrent execution condition on some VMSS instances (RunCommand triggered alongside other extension operations), which resulted in failures in a limited set of cases. This was identified and tracked internally.

A few extension failures were categorized as transient/client-side execution issues (for example, file download or retry-related failures), which typically resolve after re-execution once system resources are stable.

Current Status: As you confirmed, all operations are now working as expected, indicating that the issue has been mitigated.

If issue is resolved. Could you please accept the answer and upvote it.