While I call this post “tricks” for deleting a Windows Azure Virtual Machine it really is not a trick. It does require a little deeper understanding of how Windows Azure creates and hosts Virtual Machines in order to use the REST API to delete them.
Let us start with some background. When you use the Windows Azure Portal to create a new Virtual Machine, a hidden service is created for you that will host the virtual machine role. This will allow more than one Role (i.e. Virtual Machine) to be connected to this service to allow for the automatic round-robin of calls made to the exposed ports.
Below is a list of the Services in one of my Azure Account.
Using the REST API to list all Services, I see that not all of the services returned are shown on the screen in the portal. The service named Test0206D is not listed inside the portal.
<HostedService>
<Url>https://management.core.windows.net/<subscription-id>/services/hostedservices/Test0206D</Url>
<ServiceName>Test0206D</ServiceName>
<HostedServiceProperties>
<Description>Implicitly created hosted service2013-02-07 01:20</Description>
<Location>West US</Location>
<Label>VGVzdDAyMqZE</Label>
<Status>Created</Status>
<DateCreated>2013-02-07T01:20:58Z</DateCreated>
<DateLastModified>2013-02-07T01:21:32Z</DateLastModified>
<ExtendedProperties />
</HostedServiceProperties>
</HostedService>
.csharpcode, .csharpcode pre
{
font-size: small;
color: black;
font-family: consolas, “Courier New”, courier, monospace;
background-color: #ffffff;
/*white-space: pre;*/
}
.csharpcode pre { margin: 0em; }
.csharpcode .rem { color: #008000; }
.csharpcode .kwrd { color: #0000ff; }
.csharpcode .str { color: #006080; }
.csharpcode .op { color: #0000c0; }
.csharpcode .preproc { color: #cc6633; }
.csharpcode .asp { background-color: #ffff00; }
.csharpcode .html { color: #800000; }
.csharpcode .attr { color: #ff0000; }
.csharpcode .alt
{
background-color: #f4f4f4;
width: 100%;
margin: 0em;
}
.csharpcode .lnum { color: #606060; }
In this case the Description clearly tells us this was created for us and when. When we delete a Virtual Machine, the service will start to show up inside the portal. If you never want to deploy a new Virtual Machine to that service again, it can be deleted. Otherwise, keeping the service allows the DNS Name to be reserved and allows a new Virtual Machine Role to be added to this service at a later point.
In order to Add a new Role (i.e. Virtual Machine) to an existing service, use the From Gallery option to create the Virtual Machine. Then, on step 4, Virtual Machine mode, select the Connect To An Existing Virtual Machine option. You will get a drop down of available options.
This background leads to the reason it might be tricky to delete a Virtual Machine using the REST API.
To Delete a stand-alone Virtual Machine
In an earlier blog post I listed the way to delete a Virtual Machine was to do an HTTP DELETE to the following URL.
https://management.core.windows.net/<Subscription-ID>/services/hostedservices/<Service-Name>/deploymentslots/Production
.csharpcode, .csharpcode pre
{
font-size: small;
color: black;
font-family: consolas, “Courier New”, courier, monospace;
background-color: #ffffff;
/*white-space: pre;*/
}
.csharpcode pre { margin: 0em; }
.csharpcode .rem { color: #008000; }
.csharpcode .kwrd { color: #0000ff; }
.csharpcode .str { color: #006080; }
.csharpcode .op { color: #0000c0; }
.csharpcode .preproc { color: #cc6633; }
.csharpcode .asp { background-color: #ffff00; }
.csharpcode .html { color: #800000; }
.csharpcode .attr { color: #ff0000; }
.csharpcode .alt
{
background-color: #f4f4f4;
width: 100%;
margin: 0em;
}
.csharpcode .lnum { color: #606060; }
While this work, it only works in the case of a strand-alone Virtual Machine. If you do not know if the Virtual Machine is stand-along or attached, do an HTTP GET to the URL above. If you only have one <Role> element than it is a stand-alone Virtual Machine.
To Delete a Virtual Machine that is attached to another Virtual Machine
In order to Delete a Virtual Machine that is part of another service, you need to Remove the PersistentVMRole. This is done by an HTTP DELETE to the following URL.
https://management.core.windows.net/<subscription-id>/services/hostedservices/<service-name>/deployments/<deployment-name>/roles/<vm-name>
.csharpcode, .csharpcode pre
{
font-size: small;
color: black;
font-family: consolas, “Courier New”, courier, monospace;
background-color: #ffffff;
/*white-space: pre;*/
}
.csharpcode pre { margin: 0em; }
.csharpcode .rem { color: #008000; }
.csharpcode .kwrd { color: #0000ff; }
.csharpcode .str { color: #006080; }
.csharpcode .op { color: #0000c0; }
.csharpcode .preproc { color: #cc6633; }
.csharpcode .asp { background-color: #ffff00; }
.csharpcode .html { color: #800000; }
.csharpcode .attr { color: #ff0000; }
.csharpcode .alt
{
background-color: #f4f4f4;
width: 100%;
margin: 0em;
}
.csharpcode .lnum { color: #606060; }
The service name and virtual machine name are straight forward but the deployment name is tricky. The deployment name is usually the Service Name but it can also be the name of the first virtual machine you put into the service. To find out for sure, do an HTTP GET to the following URL to get the details of the service deployment.
https://management.core.windows.net/<subscription-id>/services/hostedservices/<service-name>/deploymentslots/Production
.csharpcode, .csharpcode pre
{
font-size: small;
color: black;
font-family: consolas, “Courier New”, courier, monospace;
background-color: #ffffff;
/*white-space: pre;*/
}
.csharpcode pre { margin: 0em; }
.csharpcode .rem { color: #008000; }
.csharpcode .kwrd { color: #0000ff; }
.csharpcode .str { color: #006080; }
.csharpcode .op { color: #0000c0; }
.csharpcode .preproc { color: #cc6633; }
.csharpcode .asp { background-color: #ffff00; }
.csharpcode .html { color: #800000; }
.csharpcode .attr { color: #ff0000; }
.csharpcode .alt
{
background-color: #f4f4f4;
width: 100%;
margin: 0em;
}
.csharpcode .lnum { color: #606060; }
This will return an XML response that looks like the following.
<Deployment xmlns="http://schemas.microsoft.com/windowsazure" xmlns:i="http://www.w3.org/2001/XMLSchema-instance">
<Name>Test0202A</Name>
<DeploymentSlot>Production</DeploymentSlot>
...removed...
</Deployment>
.csharpcode, .csharpcode pre
{
font-size: small;
color: black;
font-family: consolas, “Courier New”, courier, monospace;
background-color: #ffffff;
/*white-space: pre;*/
}
.csharpcode pre { margin: 0em; }
.csharpcode .rem { color: #008000; }
.csharpcode .kwrd { color: #0000ff; }
.csharpcode .str { color: #006080; }
.csharpcode .op { color: #0000c0; }
.csharpcode .preproc { color: #cc6633; }
.csharpcode .asp { background-color: #ffff00; }
.csharpcode .html { color: #800000; }
.csharpcode .attr { color: #ff0000; }
.csharpcode .alt
{
background-color: #f4f4f4;
width: 100%;
margin: 0em;
}
.csharpcode .lnum { color: #606060; }
The Name element is the name of the Deployment.
In summary, a single call can be made to delete a stand-alone Virtual Machine. For scenarios that join several Virtual Machines together inside a single service it takes a deeper understanding of that service’s properties in order to remove a Virtual Machine from that service.
Looking for a simple tool to work with the Windows Azure REST APIs? I have a free tool here that greatly simplifies making REST calls.