Share via

Create Job Collection


The Create Job Collection request creates a new job collection.


The Create Job Collection request is specified as follows. Replace <subscription-id> with your subscription ID, <cloud-service-id> with your cloud service ID, and <job-collection-id> with the ID of the job collection you’d like to create. There are no “default” pre-existing job collections; every job collection must be manually created.


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. The InstrincSettings element is optional, but allows you to specify quotas and settings at the job collection level, as shown below. Plan may be Free or Standard. MaxJobCount and MaxRecurrence control the maximum job count in the collection and the maximum recurrence of the collection respectively.

<Resource xmlns:i="" xmlns="">


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:

PUT /cloudServices/mycs/resources/scheduler/jobCollections/JC1 

The request is sent with the following headers:

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

The request is sent with the following XML body:

<Resource xmlns:i="" xmlns=""></Resource>

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

HTTP/1.1 202 Accepted
Cache-Control: no-cache
Content-Length: 0
ETag: 09fc72f3-4d1b-4a28-a4bd-ed1edf8845fa
Server: 1.0.6198.18 (rd_rdfe_stable.131024-2205) Microsoft-HTTPAPI/2.0
x-ms-servedbyregion: ussouth
x-ms-request-id: 7c448bbc2aab2191b356e570ccf8d2d6
Date: Wed, 30 Oct 2013 02:05:47 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 Service2
Get Cloud Service1
Get Cloud Services2
Delete Cloud Service2
Create Job1
Update Job1
Get Job1
Delete Job2
Check Name Availability1
Create Job Collection (Scheduler API)
Update Job Collection
Get Job Collection
Delete Job Collection
Get All Jobs
Get Job History1