Service Management Versioning
Mis à jour: juin 2011
Operations provided by the Service Management API may have multiple versions. You must specify which version of an operation you want to use by setting the x-ms-version request header. Requests without an x-ms-version header will be rejected and return a (400) Bad Request response. If your service calls an older version of an operation, you can choose to continue calling the older version, or modify your code to call a newer version. Any differences in functionality between versions are outlined in the documentation.
The x-ms-version request header value must be specified in the format YYYY-MM-DD. For example:
Request Headers: x-ms-version: 2011-02-25
The following table shows which versions of the Service Management API that are currently available:
| Version | Description |
|---|---|
|
2011-06-01 |
The 2011-06-01 version added the following operations:
Get Deployment adds the following properties:
|
|
2011-02-25 |
The 2011-02-25 version added the following operations:
|
|
2010-10-28 |
The 2010-10-28 version updated the following operations:
The 2010-10-28 version added the following operations:
|
|
2010-04-01 |
The 2010-04-01 version updated the following operations:
The 2010-04-01 version added the following operations:
|
|
2009-10-01 |
The 2009-10-01 version was the first version of the Service Management API. It included the following operations:
|
Voir aussi
Concepts
About the Service Management APIAutres ressources
Windows Azure Service Management REST API Reference