Start Role
The Start Role operation starts the specified Virtual Machine.
Request
The Start Role request may be specified as follows. Replace <subscription-id> with the subscription ID, <service-name> with the name of the cloud service, <deployment-name> with the name of the deployment, and <role-name> with the name of the Virtual Machine.
Method |
Request URI |
|---|---|
POST |
https://management.core.windows.net/<subscription-id>/services/hostedservices/<service-name>/deployments/<deployment-name>/roleinstances/<role-name>/Operations |
URI Parameters
None.
Request Headers
The following table describes the 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 2012-03-01 or higher. |
Request Body
The format of the request body is as follows:
<StartRoleOperation xmlns="https://schemas.microsoft.com/windowsazure" xmlns:i="http://www.w3.org/2001/XMLSchema-instance">
<OperationType>StartRoleOperation</OperationType>
</StartRoleOperation>
The following table describes the elements of the request body.
Element name |
Description |
|---|---|
OperationType |
Required. Specifies the operation to be performed. The value must be set to StartRoleOperation. |
Response
The response includes an HTTP status code and a set of response headers.
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.
Response Header |
Description |
|---|---|
x-ms-request-id |
A value that uniquely identifies a request made against the management service. |
Response Body
Unused reserved IP addresses incur a slight charge. If you are starting a Virtual Machine in a deployment that is associated with an unused reserved IP address, it might not continue to incur charges depending on the number of reserved IP addresses that you are using in your subscription.