Microsoft Azure Reviews

Microsoft Azure is essentially an IaaS solution, we use the DMs and everything in that.

Microsoft Azure is primarily an Infrastructure as a Service product.

We are satisfied with this solution.

We have not had any issues with the performance, or the stability.

It's more user-friendly than AWS.

I have only been using it for a month, so I'm still learning about the various options that are available. They have a lot of options, but I won't be able to comment unless I use it or explore it properly. Everything is fine, but I'm still learning.

The license price could be lower. If there is anything else, I will not know unless I explore.

I have just started working with Microsoft Azure. I have been working with it for one month. I got my trial subscription and started working with it.

Microsoft Azure is a stable solution.

Microsoft Azure is a scalable product.

I use it for my own personal use.

I contacted technical support a while ago. They were also helpful. I only had one question about the file quarantine and file locking options, and they were very helpful. They have a support team that responds fairly well.

For remote work, we have been using Microsoft Teams.

We are also using McAfee Proxy, as well as Box.

We are also using Amazon AWS. 

I've only recently begun working with AWS. I started but then stopped because I didn't like the user interface. 

AWS is used and preferred by a large number of customers, but I am more comfortable working on Azure rather than AWS. This is a personal preference.

The initial configuration is straightforward. We only need an email ID and we can sign up in a matter of minutes.

We can complete the installation on our own.

Pricing is determined by how much you can use and how much you want to use it.

It's not on a per-user basis; it's on a per subscription basis. It is dependent on how much you use. It has a metering system. If you use a service, you will have to pay for it. You do not have to pay if you do not use any of the services. That's how it works.

The licensing fees could be cheaper.

I would definitely recommend this solution to others who are considering using it.

I would rate Microsoft Azure a ten out of ten.

Its main use case is data center migration. We are doing data center migration to Microsoft Azure.

Azure is a set of different services, and the version depends on the service that you choose, but normally, we work with the latest version.

There are a lot of things that we like about it. It is very easy to provision and configure. It is flexible and scalable.

We have faced some issues on the pricing side, but it has improved lately. We are trying to adjust to the new pricing methods that they are using now. It should be better from now on.

In terms of features, it is constantly improving. We receive improvements from the site daily.

I have been using this solution for about 10 years.

It is stable.

It is scalable. We have a team of 15 engineers who are continually working with our customers to provide support for the solution.

Their support is good.

Its setup is easy.

I would advise others to start moving everything to the cloud because it is cheaper, flexible, and scalable.

I would rate it a 10 out of 10.

I generally, use Microsoft Azure for storage and to have applications running, such as the Microsoft Suite without having to have a physical desktop or hardware. I could use it wherever I want. I could use it from a tablet, instead of having all that files on a tablet, you can have it stored, saved, everything right there in Azure.

The best feature in Microsoft Azure is that I don't have to change computers. I don't have to upgrade or if something breaks or a hard drive crashes. The lack of a physical aspect is the major feature for me.

I have been using Microsoft Azure for approximately two years.

Microsoft Azure is stable.

I do not have to worry about scalability because I do not have users other than myself. However, it is scalable.

I have not had the need to contact the support, I have not any issues.

The installation was easy.

By using Microsoft Azure you can save money from not having to purchase or maintain infrastructure.

The price of the solution could be reduced. There should be a loyalty cost reduction model. If customers have been using the service year after year they should receive a discount.

I would advise those thinking about using Microsoft Azure to try it out, especially for businesses. If you know that your office might be moving, instead of having all the cost of physical hardware to either get rid of or repurchase, the cost of the subscription is going to be a lot less than moving all your physical servers, storage devices, and computers. You won't have any maintenance, the need to worry about hardware breaking, hardware crashing, or people breaking any of the hardware. The workstations and connectivity are all they would need to worry about if they decided to move from one spot to the other.

I rate Microsoft Azure an eight out of ten.

We use Azure for the Active Directory and integration with Exchange Online. Our customers need it to manage, connect, and administrate the permissions from Cloudbase. Here in Egypt, we are not using or connecting with the cloud-based application, but in the last two years, we have supplied the solution for our customers. In total, we have between 10 and 20 customers using Azure.

I've been working with Microsoft Azure for about two years.

It's a cloud-based application, so installation is straightforward and doesn't take much time.

The price of the Azure license could be cheaper.

I rate Azure nine out of 10. It's a perfect application, and I would recommend it to others.

We primarily use it for infrastructure and for some of its containers. It's very similar to AWS.

We moved to it as part of the initiative for the country to start using Azure services.

The solution offers many of the same features and has similar functionality to AWS.

The performance is good.

It's easy to use.

We find that it's stable. 

The solution scales quite well.

The solution is less mature than AWS. That said, it is catching up quickly.

The solution could always be cheaper. That way, it would be less expensive than AWS.

I've been dealing with the solution since 2016. It's been about five years or so. I've had some time to work with it a bit. 

The stability is very good. It's a reliable solution. There are no bugs and glitches. It doesn't crash or freeze. 

We have found the scalability to be very good. If a company needs to expand, it can do so with ease. It's not a problem at all.

Technical support has been great. They are helpful and responsive. We are pleased with the level of attention we get if we need assistance. 

We have also used AWS. We use both of them right now and like them both. They are very similar tools. 

There isn't really an initial setup. it's on the cloud and subscription-based. 

The pricing is more or less the same as AWS. They are very competitive with each other. There isn't too much of a difference, price-wise. 

In our case, the solution doesn't have a license. It's subscription-only. However, you can buy your own license separately and install it on whatever system application you're using on Azure. This is the same in the case of AWS.

I'd rate the solution at an eight out of ten. It's a good solution with a lot of potential and we've been happy with its capabilities so far. 

Whether or not I would recommend it to other companies depends on the use case. If you have a specific use case for using the cloud in general, then likely it makes sense to go with Azure.

We have developed for our customers a website where they do onsite inspections of heavy moving equipment. They have the ability to build reports that are all web-based now and by clicking a button it goes out to their customers. This company is now starting to roll it out. They started in Zimbabwe, Zambia, and South Africa. They are currently expanding the system to Brazil and Australia. We had to move from on-premise solutions to a cloud-based system and this what we are using Azure for.

We have found the most valuable feature to be the pricing calculator.

The solution could be easier to use. However, when comparing it to AWS it is a bit easier.

In an upcoming release, the interface could improve.

I have been using this solution for approximately two months.

Azure is reliable. I am doing other work for another company where I do not host it in Azure myself, but they have a U-systems running on Azure and it is operating all over the world. There are times when it can slow down a little but most of the time, it runs very smoothly.

We have two people using this solution in my organization.

I have one experience calling the technical support for Azure and the response was almost immediate, they are very good.

I have used AWS previously. Although AWS might be cheaper in some instances, I found it has an even worse configuration. You have to configure every detail, whereas with Azure it easier.

The installation was straightforward. Once you have a Microsoft ID everything else just falls into place.

I am currently on a pay-as-you-go subscription and my customers are going to be on a three-year contract. For what is offered in the three-year package it is quite reasonably priced. However, if I was to run it in my office from my own service it would be cheaper but the risk is too high. Here in South Africa, we have something called load shedding where the electricity is turned off for periods of time to regulate to load of the electricity being used. It can go off for five to six hours causing the batteries in the cell towers and fiber exchanges to start dropping and then the customers are offline.

This is why I have to move to a cloud platform that has generators, redundancy on fiber connections, and other mechanisms in place. It creates a lot of challenges for us.

Microsoft has two data centers in South Africa, one in Johannesburg and one in Cape Town. We will most likely be balancing between South Africa, Europe, and maybe even have a service in Australia.

I would advise others to do their research before they purchase any platform service. Everything could look fine on the surface but if you do not understand things, such as DPUs and flexible databases, you can run into some difficulties.

I rate Microsoft Azure an eight out of ten.

We use Microsoft Azure to host our software development solutions and solutions for reproduction.

We have many solutions running alongside Microsoft Azure that are mainly for the financial sector.

We use Microsoft Azure to host and develop.

It's great! It's very useful.

It has a separate environment for developers and developers' solutions. We have environments for PaaS and quality assurance, and we also have an environment where we can lend our solutions to our customers.

We like the Azure DevOps.

If you have large traffic amounts, Microsoft Azure will continue to provide our customers with the best storage experience.

It's very secure.

Microsoft Azure has incredible customization.

It's not user-friendly because it is made for developers. A normal user can't use it, but for a developer, it is a very friendly solution.

The initial setup can be improved. It should be simplified and made easier for developers to set it up.

I would like to see the use of Microsoft DevOps simplified. It's automation to develop and deploy software that is very difficult to use. It is so complicated and we need extra time to learn it. It is not easy. 

I have been working with Microsoft Azure since 2016.

We use the standard S3 applications.

Microsoft Azure is very reliable. It's a highly stable solution.

Microsoft Azure offers huge scalability. We can manage scalability automatically or manually. It is very fast and very reliable.

We have approximately 30 users in our organization who use Microsoft Azure.

The service is very good. They are highly technical and provide answers to things that are not easy to apply. Before the pandemic, at least, the support was good and very fast. 

We had some issues with support after the pandemic, where the replies took a very long time. Technical support could improve their response time. They should respond faster.

We use many Microsoft tools, such as Microsoft Teams, also Skype, and Google Meet.

The initials setup is difficult. It requires specialists. 

Similar to Google Cloud and Amazon Web Services, it is complex.

It can take six to twelve months to deploy this solution.

We had help from specialists to help with the complex setup. It is not easy for everyone.

I would suggest calling a specialist who is certified to help with the setup and the deployment, don't do it yourself. The specialists are reliable and can deploy the solution faster.

I would rate Microsoft Azure a ten out of ten.

I'm currently trying to build a new product for my company using Microsoft Azure. Prior to that, I was using Microsoft Azure on the cloud to deploy microservices using specific Azure services to host the microservices. But the most common Azure services that we're using is the App Service and relational databases. In terms of the application, the first one was just the Microsoft Azure application and the second one was an integration with Elastic Stack. I'm a software architect.

The user interface offers a good experience, it's better than Azure itself. The portal is great. Microsoft Azure has very good documentation for any kind of technical person.

Sometimes the Azure Calculator doesn't have a good way to do a higher estimate, because for any organization there are sometimes issues with the application sites, but I know that the logs are not the real time and there are issues with login synchronization. It cam sometimes take more than five minutes for that information to reach the Azure application side. I'd like to see integration with other lifecycle managing rules because with Azure DevOps, it's straightforward, but the system is painful sometimes. 

I've been using this solution for nearly five years, the last 12 months in this new company. 

In general, stability is good, but in the past month I had some issues with the connection to Azure resources, not just Microsoft Azure, but with Azure in general. Microsoft has an issue with its authentication system which has proved painful, because my applications were up and running, but I can't log in to make changes or see metrics. It's a lot better now, we've had the application down three or four times but it hasn't been critical. 

Scalability is good, I haven't had any issues with their configuration. I think we have around 600 concurrent users. 

I haven't used Azure support. They have good documentation, although I sometimes think that the examples on GitHub aren't updated. On the whole, documentation is good. 

We previously used AWS but we knew there was already a lot of experience with Microsoft Azure and their technologies and we wanted to use all the features for each service. Given that this is with government and the integration is with Microsoft Azure, we can use all the features and benefits of each service. Another issue is that they were using AWS with infrastructure as a service, but they redesigned this application to use software as a service and platform as a service. We dropped the use of infrastructure as a service and using the platform as a service, and it was estimated that it would cost less than with AWS.

I think the initial setup is straightforward. I have around 20 microservices, so deployment took probably two weeks. It took longer than a previous implementation which took several hours.

We did a quick check with cloud computing, but we didn't find anything really efficient outside of the Google Kubernetes Engine that was better than the Azure Kubernetes Service or the Kubernetes service in AWS. But it was just a quick check and it was documented.

I can sometimes see that Microsoft has poor training, but to be honest the whole training thing isn't good at a technical level. They are designed to be the entrance point and show the way you can create a web portal and database. But if they could offer an in-depth technical solution of Azure services that would be good. It's possible that Google has something about it and they can offer better learning than Microsoft sometimes does. Reading through their documentation can take some time. 

I rate this solution a nine out of 10.