Updated: May 7, 2015
The Register Subscription API must be called before you are allowed to create Scheduler resources such as job collections.
The Register Subscription request is specified as follows. Replace <subscription-id> with your subscription ID.
PUT https://management.core.windows.net:8443/<subscription-id>/services?service=scheduler.jobcollections&action=register HTTP/1.1
Required. Set to value “schedulerdf.jobcollection” for this operation
Required. Set to “register” for this operation
The following table describes required and optional request headers.
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.
The response includes an HTTP status code, a set of response headers, and a response body.
A successful operation returns status code 200 (OK).
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. See Tracking Asynchronous Service Management Requests for more information.
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
The following sample URI makes a request for fictional subscription named mysub:
PUT https://management.core.windows.net:8443/mysub/services?service=schedulerdf.jobcollections&action=register HTTP/1.1
The request is sent with the following headers:
x-ms-version: 2013-06-01 Accept: application/xml Content-Type: application/xml; charset=utf-8 Host: management.core.windows-int.net Content-Length: 0
The request is sent with the following XML body:
After the request has been sent, the following response is returned:
HTTP/1.1 200 OK Cache-Control: no-cache Content-Length: 0 Server: 1.0.6196.70 (rd_rdfe.131113-1631) Microsoft-HTTPAPI/2.0 x-ms-request-id: 693534c48ea231d597d700832d1a85b3 Date: Mon, 09 Dec 2013 04:42:34 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 (Scheduler API)
Get Resource Provider Properties
Create Cloud Service (Scheduler API)
Get Cloud Service (Scheduler API)
Get Cloud Services (Scheduler API)
Delete Cloud Service (Scheduler API)
Create Job (Scheduler API)
Update Job (Scheduler API)
Get Job (Scheduler API)
Delete Job (Scheduler API)
Check Name Availability (Scheduler API)
Create Job Collection (Scheduler API)
Update Job Collection (Scheduler API)
Get Job Collection (Scheduler API)
Delete Job Collection (Scheduler API)
Get All Jobs (Scheduler API)
Get Job History (Scheduler API)