Still no news to share, just to add that we are investigating options on modifications for the App Service multi-tenant offering with enhanced capabilities.
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/
This issue is not really a good brand image for Azure. How is it possible IPV6 in not yet supported (May 2016) ?
We’ll look into this one. For the time being, please have subscription owners setup tag policies and be on the lookout for more governance improvements coming soon.
Today, it is a real mess to have to move Azure services from one subscription to another to optimize cost according to the complexity and limitations.
This problem could lies into a too big dependency between the technical subscription concept and the billing subscription concept.
My many cases, there is in fact no need at all to change of technical subscription, but only to optimize cost.
Azure could become smart and agile in this area.
On direct move into that direction would be to have consolidated Azure credits and apply them only on the last step of a consolidated invoice when due amount is calculated for the given month.
In "usage and billing" portal, each customer would have a tool to manage "Cost Centers" according to their internal cost structure.
In the Azure portal, I think what is important to define, is the region/datacenter and the option to specify a cost center but no more a direct link to subscription.
By default a new subscription would be associated to a cost center (an existing one or a new one to create).
Next according to the monthly usage report of each service and the cost center associated with, the billing process will optimize consomption to reduce the final bill according to set of subscriptions per customers (available per cost center).
Azure has this capability already with EA & CSP. We would like to offer this for Web direct customers as well.
-Matt (Azure Billing)
Great, in this process Azure Credits should also be consolidated and apply only on the last step for the final amount to be payed. This would avoid a lot of mess trying to optimize cost by moving services from one subscription to another (with all problems and limitations we know).
We are looking into the requirements. Can you please elaborate the scenarios?
That’s what we strive towards: a consistent experience! What would you say are the services you are most anxious to see come on-premises first?
Thank you for the feedback! We will look into the possibility of bringing this on-premise.
Due to increased interest in BYOIP to Azure, we are reviewing design options however we do not yet have timelines to share. Thank you for your interest in BYOIP- your comments here help us make the case.
And what's about LISP and http://opencontrail.org/about/ support ?
This is something we are working to change, it is indeed an unnecessary email.
Let us look at improving this UI.