5 Common AWS support Issues & How to Resolve Them

Share on facebook
Share on twitter
Share on linkedin

How to Deploy Neo4j on Microsoft Azure, a Step-by-Step Guide [Azure Series,  Part II]

As a growing number of businesses adopt Azure as their cloud platform of choice, they are inevitably going to run into some common support issues. While Azure is a very reliable and robust platform, there are still some pain points that users need to be aware of. In this blog post, we will troubleshoot 5 of the most common AWS support issues.


1. VM Creation Fails or Takes too Long

If you’re trying to create a new VM in Azure and the process is taking too long or failing altogether, the first thing you should check is your subscription quota. Each Azure subscription has certain limits on the number of resources that can be created. If you have reached your limit, you will need to increase your quota before you can continue. You can do this by opening a support ticket with Microsoft Azure.


2. Cannot Connect to VM After Creation

If you are able to create a VM but cannot connect to it, the most likely cause is a network security group (NSG) rule blocking port 3389, which is the port used for RDP connections. To resolve this issue, open the NSG for the VM in question and add an inbound rule allowing traffic on port 3389 from your IP address.


3. Resource Deployment Fails in ARM Template

If you’re deploying resources via an ARM template and the deployment fails, the first thing you should do is check the deployment logs in Azure Portal. These logs will often contain helpful information about what went wrong and how to fix it.


4. Slow Network Performance

If you’re noticing slow network performance when connecting to an Azure VM, one possible explanation is that your VM is located in a different region than your client’s computer. Try connecting to a different region and see if that improves performance. If not, try creating a point-to-site VPN connection directly to your VM. This will route all traffic through the VPN gateway, which may improve performance depending on your network configuration.


5. App Service Worker Role Stuck in Stopping State

If you have an App Service worker role that’s stuck in the “stopping” state, it could be due to website files still being in use by IIS worker processes. To resolve this issue, recycle the App Service app pool from within Azure Portal. This will kill all existing IIS worker processes and allow the worker role to stop successfully.


Overall, the key to troubleshooting AWS support issues is to gather as much information as possible and then follow a systematic approach to finding a resolution. And don’t forget that Microsoft offers 24/7 technical support for Azure, so if you are unable to resolve the issue on your own, reach out to their support team for assistance.



While Microsoft Azure is a very reliable cloud platform, there are still some common support issues that users need to be aware of. In this blog post, we have troubleshot 5 of the most common issues: VM creation failures or taking too long, inability to connect to VM after creation, resource deployment failures in ARM template, slow network performance, and App Service worker role stuck in stopping state. By following the steps outlined above, you should be able to resolve these issues quickly and get back up and running without any major downtime!

Related Posts