Lucky Michael on Thu, 29 Sep 2016 21:12:32
I just created a new Azure Windows 7 Enterprise VM.
The public IP v4 is 188.8.131.52
I am not able to use the IPv6 Address.
The VM has been created in the West Europe Region, which supports IPv6:
IPv6 for Azure VMs available in most regions
Monday, September 26, 2016
At Ignite 2016, we announced general availability of IPv6 for Azure virtual machines.
Most public Azure regions can now host dual-stack (IPv4+IPv6) VMs:
- Brazil South
- Canada Central
- Canada East
- Central India
- Central US
- East Asia
- East US
- East US 2
- Japan East
- Japan West
- North Europe
- North Central US
- South India
- South Central US
- Southeast Asia
- UK North
- UK South 2
- West Central US
- West Europe
- West India
- West US
- West US 2
The following regions cannot presently host dual-stack (IPv4+IPv6) VMs:
- Australia East, Australia Southeast
- UK West, UK South
- Germany Central, Germany Northeast
- USGov Central, USGov East
- China North, China East
Can you please help me to resolve the issue?
Regards, Latchezar Michaylov
Loydon Mendonca on Fri, 30 Sep 2016 09:44:42
Hello Latchezar Michaylov,
Thank you for posting on the Azure forums.
Below are certain limitations listed for a dual Stack setup on Azure VMs. Please go through and let me know if you have any further questions.
1- You may not upgrade existing VMs to use IPv6 addresses. You must deploy new VMs.
2- A single IPv6 address can be assigned to a single network interface in each VM.
3- The public IPv6 addresses cannot be assigned to a VM. They can only be assigned to a load balancer.
4- The VMs with the IPv6 addresses cannot be members of an Azure Cloud Service. They can be connected to an Azure Virtual Network (VNet) and communicate with each other over their IPv4 addresses.
5- Private IPv6 addresses can be deployed on individual VMs in a resource group but cannot be deployed into a resource group via Scale Sets.
6- Azure VMs cannot connect over IPv6 to other VMs, other Azure services, or on-premises devices. They can only communicate with the Azure load balancer over IPv6. However, they can communicate with these other resources using IPv4.
7- Network Security Group (NSG) protection for IPv4 is supported in dual-stack (IPv4+IPv6) deployments. NSGs do not apply to the IPv6 endpoints.
8- The IPv6 endpoint on the VM is not exposed directly to the internet. It is behind a load balancer. Only the ports specified in the load balancer rules are accessible over IPv6.
For more details refer to Overview of IPv6 for Azure Load Balancer.