Sorry to hear you’re having trouble. We’re working on enabling this for Support subscriptions. If you’re the user who purchased the Support subscription, please try downloading the invoice at https://account.windowsazure.com/subscriptions.
Our finance team keep missing support plan invoices as they are not emailed and find it frustrating to have to remember how to access. Also it can only be the Billing owner? So no option to delegate!
Thank you all for the feedback! This is something we are actively developing, and hope to rolling out in a preview in the first half of this year! Stay tuned for more information!
Program Manager, Azure Files
Waiting for this
Waiting for this!
109 votes3 comments · Networking » VPN Connectivity (Point-to-Site, Site-to-Site) · Flag idea as inappropriate… · Admin →
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.
Really love this idea. As an organisation (50 users) we would prefer to endpoint our remote worker VPN's into our Virtual Network in Azure so that we can rely less on our on premises infrastructure. Currently we are using an OpenVPN server on premises, connectivity to Azure resources are provided by the Site to Site VPN, so that part of the puzzle is in place anyway.
What I'd like to see is that each client uses the same certificate as the first form of auth and the second is username and password which authenticates against either a Domain Controller (AD) or Azure Active Directory. Managing Certificates on a per user basis is not scale-able for us so we can't use the Point to Site VPN service as is today.