Microsoft Azure pros and cons

Microsoft Azure is an optimized solution when we compare it to any other particular cloud solution.

In terms of scalability, it is perfect.

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.

The scalability is the most unique feature. Whenever our user count is high, and utilization of our application results in high use of resources, Microsoft Azure automatically scales our application so that users can access it without any issues or errors. Microsoft Azure gives you the flexibility to scale your applications up and down at any moment. It is quite easy and impressive.

The ability to scale down is a big thing.

In Azure, everything is pretty straightforward. Once you know it, the platform is very easy to use.

The application services are the most valuable in Microsoft Azure. I'm not using them directly but I am using the function and the web applications. I don't need to pay a lot for the maintenance. I do not need to have a DevOps employee.

The most valuable feature of Microsoft Azure is it has everything together in one place. It is one large tool with lots of small tools that are updated often.

Microsoft Azure has hundred of services that they offer on the platform.

I know there have been a lot of improvements and a lot of new services lately. I'm really not aware of all of them.

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.

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.

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.

Customer services and support should be improved. If a user faces challenges in accessing Microsoft Azure, the support team takes time—it could be 24 to 48 hours—to resolve them. We need solutions in four to five hours. And there are business-critical issues where we need an immediate resolution.

It can be improved in terms of ease of billing or monitoring of the billing. That gets to be a little difficult.

It would be helpful if Azure provided more information on the various add-ons to give people an understanding of what they are used for, and how they're applied by other companies or businesses.

The documentation can be outdated and is not as clear in Microsoft Azure as it is in AWS or Google.

There is a need to be better on-premise solutions that are more helpful. However, I don't think that is the goal of Microsoft Azure. They want the solution to be secure cloud solutions with cloud applications. This is their main goal at the moment.

There are times when using a service in Microsoft Azure can be confusing because you have four or five options that do similar operations. It would be helpful if there was a clear decision tree around those features. Microsoft does provide a lot of decision trees around a lot of their services, but it's not for everything.

I haven't checked the console for some time, however, compared to the AWS console, the interaction console of the web part, the web services, it's not so easy.