Stefan de Kooter
My feedback
-
49 votesStefan de Kooter
supported this idea
·
-
1,754 votes
We’ve moved this ask to the backlog due to technical challenges in reserving Public IP addresses during stop state.
Stefan de Kooter
supported this idea
·
-
1,573 votes
IPv6 in Azure VNET is currently previewing globally- in ALL Azure Public cloud regions.
Announcement (Service Update): https://azure.microsoft.com/en-us/updates/public-preview-microsoft-adds-full-ipv6-support-for-azure-vnets/
Links to Documentation & Samples
Full documentation including sample scripts is available here: https://aka.ms/IPv6ForAzureVNETdocA sample JSON template is posted in the quickstart repository: https://azure.microsoft.com/en-us/resources/templates/ipv6-in-vnet/
Stefan de Kooter
supported this idea
·
Gateway run hours should not be a separate cost besides the data transfer/connected hours. Since a GW can be deployed multi-tenant there shouldn't be a tenant -specific cost. When running a normal VM we don't pay separately for a hypervisor as well but only for the usage of the resource.
So make the GW a shared resource, come up with a data transfer rate that covers the cost and scale that thing! offcourse the same goes for P2S VPNs. VPNaaS, not GW-VM-aaS.