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/Tim Posey commented
Azure Front Door now solves the problem of needing IPv6 to work our PaaS services like App Service.
Thank you for your feedback. We’re considering this for a future release of Azure Search.
Azure Search Product Team
For any questions, please reach out to us at AskCosmosDB@microsoft.com
Work on this feature has started. Will update here when this becomes generally available.
Thank you for your suggestion and votes.
We have reviewed this and have elected to not include this on our road map for the time being. We may revisit this in the future so will leave as unplanned rather than declined or closed.
Thanks for your suggestion and comments.
We’re evaluating more compressed storage formats. Meanwhile, please consider using a client-side compression library for encoding fields/JSON fragments that are not used for querying.
Support for both public and private IP at the same time is available on both V1 and V2 SKU. Customers can host multiple sites behind the same IP and port using multi-site listener today.
Support for allowing same port on both public and private IP is in the roadmap.
Thanks for the feedback, service tag is called AzureCloud and it’s already available in all regions
Thank you for all the votes and feedback. We have started work on this and the capability will be supported soon. If you would like to get in touch with us to discuss your scenarios, please fill this form: https://aka.ms/ApplicationGatewayCohort
DNSSEC remains on our long term roadmap, however it is unlikely to be available in CY 2019. If DNSSEC is a critical and immediate requirement for your business we’d suggest that you consider evaluating 3rd party DNS hosting solutions that provide this feature.
This is on our long term roadmap.
Thanks for the suggestion. This item is on the longer term roadmap. We will investigate supporting P2S with AD authentication first, then consider AAD afterward.
Thanks for your feedback
We’ll review this feature to include it on our roadmap.
We have released the public preview for this feature! Learn more about how to use it here: https://docs.microsoft.com/azure/active-directory-b2c/active-directory-b2c-setup-oidc-azure-active-directory