Thanks for all the feedback folks. Unfortunately this is taking longer than we’d like.
We will reach back out when we are closer to a preview.
We would like to see SQL DB support the "VNet Join" scenario where the service endpoint uses a private IP within the VNET/Subnet. This will facilitate access scenarios where non-Azure resources should access SQL DB using private networking.
Transitive network flow between peered vnets is on our roadmap but we have no dates to share at this time.
The use of private IP also improves the connectivity and routing options when using a complex network topology that involves non-Azure resources.
Allowing SQL DB to use a VNET based IP address would significantly improve the manageability, security and accessibility in a high security corporate environment.
Soon we’re going to start working on a first class experience in the Azure Portal that allows for a user invited to an Azure AD tenant via the “B2B Collaboration” feature to become a Member (vs their default Guest) and thus be able to be assigned as Azure AD Global Admins or Azure Subscription Co-Admins
The old portal allowed the addition of an account "from another Azure AD tenant which I manage". These accounts are set to "member" but show the "#EXT#" UPN for external user.
It does not appear possible to add external accounts as "member" in the new portal.
Looking for a clear definition between Guest and (#EXT#) Member to understand if/when/where this will be an issue.