We have several VMs which provide a service to our web roles. We use traffic manager to loadbalance between these VMs.

As the the only valid traffic to these VMs is from our webroles, our office or the TM probes, we use windows firewall on the VMs to restrict all other traffic.

The issue we have is that the traffic manager Probe IPs change on occasion.

If the list of Probe IPs was published, we could ensure that our FW rules are kept upto date ensuring that TM is doing it's supposed to be doing!

IPv6 has been a standard for years and ISPs are starting to roll out native IPv6 stacks to consumers. The time is now to support IPv6.

With Azure trying to attract more than just Windows devs, we need to be able to VPN using non-Windows platforms for point-to-site connections.

Need support for ICMP features like Ping in Azure Websites, Azure Mobile Services thru node.js, Web/Worker Roles/Cloud Services.

being restricted to only one VPN when using a static gateway is extremely limiting. This means that once a static VPN has been created between a VNet and a site (i.e. our office) we have no way of connecting the Azure Vnet to another VNet using a different VPN i.e. no multi-site VPN feature if a static gateway has to be used for ANY VPN. This stops any other connectivity into the VNet apart from enpoints and ACL's which is both less secure and messy to manage.

Enable Network Security Group logging capabilities to show dropped packets.

Please provide a way to log the dropped packets that are blocked by Network Security Groups and make the log accessible to us for auditing and security reasons.

There are two charges related to the Azure VPN service: the compute resource charge at $0.05/hour, and the egress data volume charge. Both are based on resource consumption, Unfortunately, even if the VPN tunnels are not connected, the gateway compute resource is still being consumed and will cost ~$38 monthly!
This is not really "Pay only for what you use".

Need functionality to “STOP” (and of course "START") a gateway if the customer is certain that the gateway will not be in use.

Today, I needed to change a virtual network to a existing Virtual Machine. I had to delete this VM, create a new one using attached disks from the old one and set the Virtual Network. It would be nice if we had another way to do that, using Portal for example.

Windows Azure should offer domain registrar services so users don't have to maintain our domain names with a separate company. This also has the potential to greatly streamline the process of setting up a website on Azure.

On the following link, we are able to get the list of the azure datacenter / endpoint IPs that are actually used.

https://www.microsoft.com/EN-US/DOWNLOAD/DETAILS.ASPX?ID=41653

Please add a source tag like INTERNET or VIRTUALNETWORK to use Azure IP addresses in NSG rules.

If I have a port range it is really a pain to add endpoints if I need to add a port range between 20000 and 20010 for TCP and UDP. In this case I have to create 20 endpoints.

Some things work, other things don't. I can setup an apex domain, but to get SSL working on an apex domain in hosted cloud service web role requires tweaking. Traffic manager doesn't work with apex domains.
Azure needs a DNS service like Amazon's Route 53. (http://aws.amazon.com/route53/)

If Azure DNS supported zone transfers, then if could be used both as a reliable secondary DNS service, or as an external proxy service for AD split-brain, or on-premise hosted DNS configurations.

Currently it is not possible to utilise a HTTPS (port 443) probe against a backend pool and as a result you must use either port 80 or a TCP probe which isn't the same as actually making a HTTPS request and testing the HTTP response code.

When the device is restarted, or internet connectivity is regained, the device automatically connects to the VPN again.

Add the ability to Monitor Site 2 Site VPN's and create alerts when they drop

We should be able to fully customize the VPN gateway parameters for phase 1 & 2 negotiations:

* Specify the pre-shared key
* Lifetime values
* Encryption
* Static IP address that won't change if the gateway is deleted and recreated
* etc.