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.
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/IPv6ForAzureVNETdoc
A sample JSON template is posted in the quickstart repository: https://azure.microsoft.com/en-us/resources/templates/ipv6-in-vnet/
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 addressHenrique commented
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.
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