Disassociate Reserved IP Address
Updated: July 10, 2015
The Disassociate Reserved IP operation disassociates an existing reservedIP from the given deployment.
The Disassociate Reserved IP request is specified as follows. Replace <subscription-id> with your subscription ID and <reservedIpName> with the name of reservedIP that need to be disassociated.
Method | Request URI |
|---|---|
POST | https://management.core.windows.net/<subscriptionId>/services/networking/reservedips/<reservedIpName>/operations/disassociate |
None.
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. The value of this header must be set to 2015-02-01 or higher. |
< ReservedIPAssociation xmlns="http://schemas.microsoft.com/windowsazure" xmlns:i="http://www.w3.org/2001/XMLSchema-instance"> < ServiceName >service-name</ ServiceName > < DeploymentName >deployment-name</ DeploymentName > < VirtualIPName >virtualIP-name</ VirtualIPName > </ ReservedIPAssociation >
Element name | Description |
|---|---|
ServiceName | Required. Name of the hosted service. |
DeploymentName | Required. Name of the deployment. |
VirtualIPName | Optional. Name of the VirtualIP in case of multi Vip tenant. If this value is not specified default virtualIP is used for this operation. |
The response includes an HTTP status code, a set of response headers, and a response body.
A successful operation returns status code 202 (Accepted).
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. |
None.