There is currently no indication as to which regions have low or high capacity.
This makes reacting to regional capacity problems almost impossible. Its not possible for me to migrate my workloads via ASR into a new region as I'm not certain the new region has the capacity for my VMs.

Allow for a Red, Yellow and Green traffic light system to allow customers to see which regions have available capacity.

If node reboot/crash or VM has to automatically moved to a different and physical node to avoid further impact . A notification should be sent to end users which VM running on this node. Our customer complaint that they didn't receive any emails or alerts when VM reboot was caused by physical node unhealthy.

This should be a future of Azure China notifications

Please update this roadmap page to reflect that Availability Zones are now GA in a few regions and in preview in a couple of other regions. Please also give an indication of when Availability Zones are expected to go GA/preview in other regions (especially North Europe).

In storage account, firewall and virtual networks, the firewall part. It says "Add IP ranges to allow access from the internet or your on-premises networks. ". However, there's a limitation here that only public IP can be set here.

Can we have a feature that allow setting a firewall over intranet IP or CIDR so that we can connect to the storage accounts over our Azure Connections from our On Premise sites?

Thanks!

With the IP restriction function, the HTTP status page is only 403.
Just like web.config, it is good to have a function that can be customized by Azure portal.

                 <ipSecurity allowUnlisted="false" denyAction="AbortRequest">

                        <add allowed="true" ipAddress="192.168.0.101" />

                        <add allowed="true" ipAddress="172.16.0.0" subnetMask="255.255.255.240" />

                 </ipSecurity>

When a guest OS is crashing (eg. kernel panic), Azure doesn't automatically register this VM as failed. Although an alert can be triggered via Azure Monitor for virtual machines, there should be an option to automatically restart a VM with a failing heartbeat.

The sign-in logs for Enterprise Applications do not include any logging information if the SSO method is password based.

Azure performs some processing behind the scenes (checking the user account has permissions, etc), so this information should be available through the sign in logs.

I have an important suggestion: Dear Microsoft Azure team, provide and make plans for new coverage and host locations in Saudi Arabia and United Arab Emirates. Thank you so much.

Hi, currently media services aren't available in the UK datacentres meaning storage accounts have to be hosted elsewhere. Ideally for us (and I can imagine a growing number of businesses going forwards) we would need this data stored in the UK to ensure UK data protection laws are adhered to!

First of all, All Azure public IP must be removed from Hotmail blacklist, and Azure should stop changing public IP address whenever you reboot , let1s say you have a smart host, When you reboot your VM, the IP will change, we have to change in many places, or you have a DNS server god forbid!!!! More dangerous

As the only non-China-based cloud platform with Datacenter in Hong Kong, AKS is the first choice for Hong Kong companies. Please include more services like Kubernetes in Hong Kong region. Thank you.

Some customization I am looking for are not in the documentation so I am wondering if we can customize the following items:
- Text on the web page of user registration.
- Text in the email of confirmation
- Text in the email (secure code by email)
- Redirect to an external webpage after user registration.
- Host a link (forgot password) on user's PC login windows (i.e. Windows 7 or Windows 10).

Two points that can be added as enhancement :

1. Currently we don't have a time as of when we can schedule the Cost management extracts . So it would be good to have one .


2. If we get the extract on more granular level i.e. Hourly basis .

AKS should add new nodes to the clcuster when existing nodes crash/get deleted

Azure doesn’t have that level of granularity in Azure Monitoring to identify and alert at WebApp instance level. Otherwise, this could also help us to identify the cause of that culprit instance stuck issue (high thread / CPU /Memory and so) along with WebApp name. It can also help us to minimize the downtime in initial diagnosis to find the culprit WebApp and corresponding instance identification.

VNet Global Peering connectivity is needed for Azure Dedicated HSM because:
1. Need to connect from dozens of subscriptions to HSMs across regions for HA/DR
2. VNet to VNet connections are limited to 30 tunnels per VPN gateway
3. Virtual WAN is not explicitly supported by Dedicated HSM