The customer service and support are very good. When we raise a ticket, we quickly get feedback or someone assigned to help us identify the problem, which, 90% of the time, was on our end. I'm very happy with the support they provide.
The valuable features of Microsoft Azure are that it is cloud-based and has good storage. The storage is completely managed by Azure. We do not need to do any patching of security because it is handled by Azure which is a benefit. The solution is fully compatible with the Microsoft technology stack and is very scalable.
There are multiple DevOps solutions and tools available in Microsoft Azure, but most of the time they are either in the build mode, meaning you don't get complete support for them because they are either making changes, or changing the names of the particular services. Sometimes, services vanish from the portal. We are not able to see that. I think they actually change the names of the services.
One key area for improvement is the Azure load balancer. Currently, it only supports virtual machines (VMs) running in the same virtual network (vNet) on the backend.
They should definitely support machines or IPs running on-premises (prem) or in other Azure VNets. GCP and AWS already support that. So, Azure Load Balancer should support that as well
Business Development Executive, Managing Partner at a tech services company with 1-10 employees
Jan 4, 2022
Microsoft Azure is so complicated inside. If you should do something internally, if you have to configure something, the opinion about Azure is that it is a little complicated inside. That's why the end users and clients are looking for help and why we help them configure and do anything inside of Azure. That is why we offer other tools to optimize the Azure environment.
I don't understand why we spend so much time and money on Azure when Microsoft relies on third-party companies for support in the CSP model. I don't know how the support model works within Microsoft, but giving it to poor-performing third-party companies is not ideal.
The solution should improve the shared cache. For the shared cache, Microsoft uses RADIUS third-party services. We have a lot of trouble with RADIUS and I suppose that is due to the fact that is not owned completely by Microsoft.