Updated: June 29, 2015
The Delete Deployment asynchronous operation deletes the specified deployment.
The Delete Deployment request may be specified as follows. Replace <subscription-id> with your subscription ID, <cloudservice-name> with the name of the service, <deployment-slot> with staging or production, or <deployment-name> with the name of the deployment.
You must make sure that the request that is made to the management service is secure. For additional details, see Authenticating Service Management Requests.
Optional. Specifies that the operating system disk, attached data disks, and the source blobs for the disks should also be deleted from storage.
The comp=media parameter is only available using version 2013-08-01 and higher.
The following table describes the request headers.
Required. Specifies the version of the operation to use for this request. This header should be set to 2009-10-01 or higher. For more information about versioning headers, see Service Management Versioning.
The response includes an HTTP status code and a set of response headers.
A successful operation returns status code 200 (OK). For information about status codes, see Service Management Status and Error Codes.
The response for this operation includes the following headers. The response may also include additional standard HTTP headers. All standard headers conform to the HTTP/1.1 protocol specification.
A value that uniquely identifies a request made against the management service. For an asynchronous operation, you can call Get Operation Status with the value of the header to determine whether the operation is complete, has failed, or is still in progress.
If the deployment that is being deleted is using a reserved IP address, the address continues to be reserved for your subscription. The unused reserved IP address continues to incur charges. For more information, see Reserved IP Pricing. To delete the reserved IP address if you don’t need it anymore, use Delete Reserved IP Address.