Delete Cloud Service

Article
09/29/2016

The Delete Cloud Service request deletes the specified cloud service and all child resources.

Request

The Delete Cloud Service request is specified as follows. Replace <subscription-id> with your subscription ID and <cloud-service-id> with your cloud service ID.

Method	Request URI
DELETE	https://management.core.windows.net/<subscription-id>/cloudServices/<cloud-service-id>

URI Parameters

None.

Request Headers

The following table describes required and optional request headers.

Request Header	Description
x-ms-version	Required. Specifies the version of the operation to use for this request. This header should be set to 2013-06-01 or a later version.

Request Body

Empty.

Response

The response includes an HTTP status code, a set of response headers, and a response body.

Status Code

A successful operation returns status code 202 (Accepted).

Response Headers

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.

Response Header	Description
x-ms-request-id	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. See Tracking Asynchronous Service Management Requests for more information.

Response Body

None.

Authorization

Any management certificate associated with the subscription specified by <Subscription-Id> can be used to authenticate this operation. For additional details, see Authenticating Service Management Requests

Sample Request and Response

The following sample URI makes a request for fictional subscription named mysub and fictional cloud service mycs:

DELETE https://management.core.windows.net/mysub/cloudServices/mycs

The request is sent with the following headers:

x-ms-version: 2013-06-01
Host: management.core.windows.net
Accept: application/xml

The request is sent with the following body:

None.

After the request has been sent, the following response is returned:


HTTP/1.1 202 Accepted
Cache-Control: no-cache
Content-Length: 0
x-ms-servedbyregion: ussouth
x-ms-request-id: 8a8b61334f522aa299f3b6aabaf59fc6
Date: Sat, 26 Oct 2013 05:16:46 GMT

What is Scheduler?
Get Started Using Scheduler in the Management Portal
Scheduler Concepts, Terminology, and Entity Hierarchy
How to Build Complex Schedules and Advanced Recurrence with Azure Scheduler
Scheduler PowerShell Cmdlets Reference
Scheduler High-Availability and Reliability
Scheduler Outbound Authentication
Scheduler Limits, Defaults, and Error Codes
Plans and Billing in Azure Scheduler
Azure Scheduler Pricing
Azure Scheduler Videos
Register Subscription
Get Resource Provider Properties
Create Cloud Service2
Get Cloud Service1
Get Cloud Services2
Delete Cloud Service (Scheduler API)
Create Job1
Update Job1
Get Job1
Delete Job2
Check Name Availability1
Create Job Collection
Update Job Collection
Get Job Collection
Delete Job Collection
Get All Jobs
Get Job History1

Share via