Share via

Create Cloud Service


The Create Cloud Service request creates a new cloud service. When job collections are created, they are hosted within a cloud service. A cloud service groups job collections together in a given region. Once a cloud service has been created, job collections can then be created and contained within it.


A cloud service is created by submitting an HTTP PUT operation to the CloudServices OData collection of the Service Management API Tenant.Replace <subscription-id> with your subscription ID and <cloud-service-id> with your cloud service ID.


Request URI


URI Parameters


Request Headers

The following table describes required and optional request headers.

Request Header



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

The format of the request body is as follows:

<CloudService xmlns:i="" xmlns="">
  <Description>My Cloud Service for app3</Description>
  <GeoRegion>South Central US</GeoRegion>




Specifies the location of the data center where the service is hosted.


The name of the cloud service.


The description of the cloud service.


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



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



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:


The request is sent with the following headers:

x-ms-version: 2013-06-01
Content-Type: application/xml; charset=utf-8
Content-Length: 239

The request is sent with the following XML body:

<CloudService xmlns:i="" xmlns="">
      <Description>My Cloud Service for app</Description>

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

HTTP/1.1 202 Accepted
Cache-Control: no-cache
Content-Length: 0
ETag: 90c10ee5-3e21-40c1-aa97-d0474d79d450
x-ms-servedbyregion: ussouth
x-ms-request-id: a1b5026673f5220ea27d6ff9a3973963
Date: Sat, 26 Oct 2013 04:49:22 GMT

See Also

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 Service (Scheduler API)
Get Cloud Service1
Get Cloud Services2
Delete Cloud Service2
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