Windows Azure cloud Services and virtual machine reserved IP addresses will be officially released

What is reserved IP address? When do I need to reserve an IP address?   With the recent PowerShell release, Microsoft Azure allows users to reserve public IPV4 addresses in Azure subscriptions. You can keep an IP address at any time in your subscription, or you can associate it with a cloud service deployment that is in the area where the IP address is reserved. This new bulletin is specifically for IP addresses that are targeted to the public Internet. The Azure platform already supports reserved internal IP, as described here.   need to reserve IP addresses for a variety of reasons   A-record DNS is simpler: Because the same public IP is maintained after the VM is deleted and shut down, it is not necessary to reset DNS or other applications to the newly specified IP based on IP at reboot. Internal connection security: Now you can access the Azure service from the corporate network by using the public IP and through internal proxy/firewall access control and by including the IP in the list of allowed access. You don't have to worry about resizing every time you start or stop a VM. The following illustration shows how IP reservations for VIPs (reserved IP) work. Azure provides reserved IP in a regional scope, that is, a reserved IP can be used to associate a cloud service that uses the size of any role instance.   How do I reserve an IP address in Microsoft Azure?   From this week, you can use the Azure PowerShell cmdlet or REST API to create reserved IP addresses in Azure subscriptions. You can reserve IP addresses in any area other than the following areas. We will provide support to these areas as soon as possible.   Brazil (preview) east China North China Note that the platform does not support creating reserved IP addresses through the admin portal. The following is an example of creating a reserved IP address using the PowerShell cmdlet:   New-azurereservedip–reservedipname "Mywebsiteip" –label "Websiteip" – Location "Japan West"   platform does not support reserving IP addresses for existing cloud services or virtual machines. We hope to announce this support in the near future.   How do I use reserved IP addresses for virtual machines?   When you create a reservation IP in a subscription, you can use reserved IP to create a virtual machine deployment. The following is an example of reserving IP for NEW-AZUREVM PowerShell cmdlet.   NeW-azurevmconfig-name "Webappvm"-instancesize small-imagename $images [130]. imagename | Add-azureprovisioningconfig-windows-adminusername $username-password $password | New-azurevm-servicename "Maheshwebapp"-reservedipname "Mywebsiteip"-location "Japan West"   There are two key scenarios to emphasize   shutdown VM-Previously, when all virtual machine instances turned off, the public IP was released, and the virtual machine instance was assigned a new public IP when it started. However, as this feature is published, if the VM uses reserved IP, the reserved IP can be used when the VM is redeployed. Remove VM-Remove all virtual machines that previously reserved IP, and reserved IP will remain in the subscription for future VM deployments in this area. You can refer to the virtual machine REST API documentation here.   How do I use reserved IP addresses for cloud services (Web role/worker role)?   We also announced support for the use of reserved IP for cloud Services (Web/worker) deployments. To use reserved IP for cloud services, you need to download the SDK version 2.3 (released in April 2014). The following is an example of referencing a reserved IP in your service configuration schema (CSCFG).   <?xml version= "1.0" encoding= "Utf-8"?>   <serviceconfiguration servicename= "Reservedipsample" xmlns= "Http://schemas.microsoft.com/ServiceHosting/2008/10/ServiceConfiguration" osfamily= "4" osversion= "*" schemaversion= "2014-01.2.3" >   <role name= "WebRole1" >   <instances count= "1"/>   < Configurationsettings>   <setting name= "Microsoft.WindowsAzure.Plugins.Diagnostics.ConnectionString" value= " Usedevelopmentstorage=true "/>   </ConfigurationSettings>    </Role>    < networkconfiguration>    <AddressAssignments>    <ReservedIPs>    < ReservedIP name= "Mywebsiteip"/>    </ReservedIPs>    </AddressAssignments>    </NetworkConfiguration>   </ServiceConfiguration>   Note that when you delete the Web role/worker role deployment, The reserved IP associated with the deployment is still present in the subscription and can be used for future deployments in the same area.   How do I release reserved IP addresses from subscriptions?   Note that a reserved IP address that is not associated with the deployment, including the VM and cloud services, generates billing costs, so it is recommended that you release unwanted IP addresses. For more information about reserving IP billing, click here. The following PowerShell cmdlet shows how to free a reserved IP from a subscription.   Remove-azurereservedip-reservedipname "Mywebsiteip"-force   reserved IP address and virtual network based on association group   Currently, Microsoft Azure It is also not supported to deploy cloud services or virtual machines that are associated with reserved IP to virtual networks based on association groups. The following fragment shows an example of an error message that will be received when you try to deploy a virtual machine with reserved IP to a virtual network that is based on the Association group.   New-azurevm:badrequest:the DEPLOyment contains virtualnetwork demovnet that belongs the Affinity Group and ReservedIP that belongs to a region. This combination isn't even.   Reserved IP address and Zone virtual network   in this release, we will also publish support for regional (location-based) virtual networks. For more information, click here to visit the appropriate blog. Microsoft Azure supports deploying cloud services or virtual machines that are associated with reserved IP to a location-based virtual network.   Reserved IP address pricing   IPV4 addresses are very scarce resources, so Microsoft Azure can, in some cases, have a symbolic charge for IP addresses. For more information about reserving IP pricing and Billing FAQs, click here. Note that the cloud service should run at least one web/worker or virtual machine instance.   In the bill, you will see two hours of reserved IP-related entities   reserved IP addresses-when you subscribe to a reserved IP in one of the following situations the total number of hours sustained is not associated with a deployment (VM or cloud service) with a running instance (or) using an additional reserved IP address in the subscription. Reserve IP Remapping – each time an IP address is associated with a new cloud service, it is considered a remap. For more information about remapping pricing in the Reserve IP pricing page, click here. Reserving an IP address subscription restricts all Azure subscriptions to 5 reserved IPs. However, you can click here to submit a support request to increase the reserved IP limit for your subscription.