Azure VM Runtime Team
Azure VM Runtime Team
Latest posts
Introducing Managed RunCommand Artifacts
As most of you may know from the current Managed RunCommand documentation there are multiple ways your script may be specified. However, what ...
Using Managed RunCommand in an ARM Template
Perhaps one of the largest differences between "Action RunCommand" (internally called RunCommand V1) and "Managed RunCommand" (internally called RunCommand V2) ...
When will CustomScript extension re-execute my script?
One of the lesser known differences between RunCommand and CustomScriptExtension is the fact that we do promise to not re-run your script in RunCommand, but no...
The treatFailureAsDeploymentFailure flag
In both VmApplications and RunCommand, we support a property called "treatFailureAsDeploymentFailure". Note that for Managed RunCommand it may not be visible ...
Working with VM Application Names
I admit that VM Application names can be a bit tricky, or at least non-intuitive. The basic issue is this, you have some binary - let's call it MyApp.exe - and ...
Working with unmanaged storage account quotas in VM Applications
While working with VM Applications, it's possible to receive the following error. Operation could not be completed as it results in exceeding approved ...
How to determine if your Runcommand script failed
Today, we're going to cover what can be a maddening issue in just determining whether your script failed. Let's start with a very simple operation. Open a ...
Long running RunCommands
Recently, there's been a bit of confusion involving long running RunCommands. For reference, the default wait time for RunCommand has been 90 minutes - the ...
RunCommand vs Custom Script Extension vs VM Applications
I'm sure that many of you would swear that Microsoft loves to confuse you. Currently, there are not three but four ways to run code on your machine...