Henrique
My feedback
-
99 votesHenrique
supported this idea
·
-
446 votesHenrique
supported this idea
·
-
223 votesHenrique
supported this idea
·
-
182 votesHenrique
shared this idea
·
-
127 votes
Thanks for the suggestion – this will require the new Azure VPN gateway SKUs to add IKEv1 support. It’s under review but will be in the longer term roadmap. For the short term, please leverage virtual appliances from Azure Marketplace to facilitate this connectivity.
Thanks,
Yushun [MSFT]Henrique
shared this idea
·
-
2 votesHenrique
supported this idea
·
-
6 votesHenrique
supported this idea
·
-
1,588 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/
Henrique
supported this idea
·
-
302 votes
Apologies. There was apparently a misunderstanding and the status has been corrected.
This specific feedback item is for NAT from private IP space to private IP address
Henrique
supported this idea
·
-
249 votes
We don’t have plans to provide this in the near term. there’s a potential workaround by using VM’s with multiple interfaces. I’ve added documenting this scenario to our doc backlog.
— ChristianHenrique
supported this idea
·
-
14 votes
Could you help us understand how this differs from hit highlighting? This sounds like exactly what you want.
Take a look at the highlight query parameter on the Azure Search REST API: https://docs.microsoft.com/en-us/rest/api/searchservice/search-documents
+1
Any updates?