Offering IPv6 support across Networking is a high priority for us and we are actively working to deliver this.Satya Tanwar commented
IPV6 support on EventHub is a critical requirement for us.
Quick update: We reduced the entry point to partitioned collections by 75% to make it more cost effective for applications that need high storage but low throughput.
Please see https://azure.microsoft.com/en-us/blog/azure-documentdb-entry-point-for-partitioned-collections-now-75-cheaper/ for details, and email us at firstname.lastname@example.org for any questions.Satya Tanwar commented
Completely agree with @Jon McGuire.
We definitely recognize the popularity of this feature, and we discuss it constantly during the planning phases. However there are certain technical limitations in the system that add a large amount of development cost. Because of the cost and the fact that there is a workaround available, other features get prioritized over this one.
That being said, please keep voting for it. The popularity of the feature does help bring it up and makes us reconsider every time.
Apologies for the delay.
We’re doing some research both on the specifics of this ask as well as what it would take to support this.
Is the ask here to do the same thing that regular Azure AD does (see: https://blogs.technet.microsoft.com/enterprisemobility/2014/12/18/azure-active-directory-now-with-group-claims-and-application-roles/) or is are there different requirements around this for Azure AD B2C?