Microsoft Azure Reviews

We've been using Microsoft Azure for federal government installations, and it has been really useful. Azure works well with the servers and equipment that we use. We've been deploying a hybrid environment, so this has been a great tool for our clients. For example, we've been upgrading systems for a secure health institution in Mexico City, so we deployed an Azure-based management system for the entire institution. However, things weren't so easy for some of our other clients. In one case, we used Azure to manage all the mortgages, connectivity, and databases for a huge mortgage provider. We managed all that information in Microsoft Azure. 

One of the best features is the last package security of upgrades to Microsoft Azure. Also, we like Azure's compatibility with other operating systems. 

We use Microsoft Server 2019 and 2016. And I didn't like the 2019 client, so we had to downgrade back to 2016. The main issue there was its monitoring system. Our client needed an alternative, and if they were using more Windows products, they also needed to make that downgrade.

I started working with Microsoft Azure around 10 years ago.

I would rate Microsoft Azure 10 out of 10. We like how accessible it is to the end-user, not just the engineers or developers.

I have developed a platform on Azure for the semiconductor industry. Azure is an excellent choice for enterprises in sectors like semiconductors, biochemistry, etc.

To me, the most valuable Azure features are AKS, Cloud SQL, security, and account management.

I've been using Microsoft Azure for a couple of years.

Azure is as stable as most cloud providers like AWS and Google Cloud.

Azure is stable but not as scalable as I'd like. In terms of scalability, AWS is better than Azure. In my organization, we have 500 or so employees.

Azure installation is complicated. When we first deployed Azure, it was challenging. By contrast, AWS is easy to install and maintain. Azure is tough. It takes from one to two weeks to fully deploy. Our technical team responsible for deploying and managing Azure has 30 people.

I rate Azure eight out of 10. Azure is difficult to deploy at first, but we have the money to develop, maintain, and support it.

We are using SharePoint through Azure.

The solution has helped our company by having zero maintenance.

The user interface is very good for administrators.

Microsoft should have one package for all their solutions in one place to be found. 

I have been using Microsoft Azure for one year.

Microsoft Azure is stable.

I have found Microsoft Azure scalable.

I have satisfied with the technical support from Microsoft.

The initial setup was easy.

I did the implementation of the solution.

The price of the solution could be less expensive and the pricing model could be less confusing.

My advice to those wanting to implement the solution is to have training. It is important to train the internal employees.

I rate Microsoft Azure a nine 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.

I have been using Microsoft Azure for Infrastructure as a Service in the cloud. We're using it to get the devices registered and be Azure Ready at home or the office.

The most important thing is we don't have to maintain any physical infrastructure. With typical conventional on-premise solutions, we have to maintain many things like the hardware, clusters, etc. With this cloud platform, you don't have to worry about all those things. We have the service always available, and this is the main advantage.

I like that we use everything on our standard Active Directory on on-premises on Azure. The key advantage is that you can have the sole indication based on the cloud. This isn't possible with an on-premise Active Directory. This enables work from home and at the office because it's on the cloud.

It could be more flexible. If you look at all Mircosoft products, they are not up to the mark. For example, Azure Ready doesn't provide the same kind of access a domain administrator has and the kind of flexibility that they have when using Active Directory. 

Microsoft support could be better. Their service could also be better. For example, specific policies for templates suddenly become unavailable. When I checked, they said that certain things might be withdrawn based on customer feedback. This happened once or twice, and it wasn't available at all for five days, it just went down.

I have been using Microsoft Azure for about ten months.

Microsoft Azure is a stable solution.

Microsoft Azure is a scalable solution. We have close to 1,200 people using this solution at our organization.

I have used Microsoft support before. I would give them a six out of ten. This is because we had certain glitches happen that could have been avoided. For example, they say that this is because it's a new product or the new architecture. They say things like, "it will be more stable after some time, maybe a year or two." 

The initial setup and deployment were straightforward. 

Our in-house team implemented this solution. We have about 15 to 20 people to install and maintain this solution.

We pay yearly for the license. 

I would recommend this cloud computing service to new users.

On a scale from one to ten, I would give Microsoft Azure a nine.

Microsoft Azure can be used for everything, including development, hosting and storage. Since it offers active directory as relates to the cloud, it can be used for directory management and logins.

We work with Azure, which is okay, but very clunky and complex. It lacks fluidity and is not intuitive. This can be problematic and require one to work with external consultants. Things can depend on the client. Not everything can be known in advance and there may be a need to make changes to the interface. Changes which are made to the functionality are not always intuitive. As such, while the solution offers very good functionality, its intuitiveness, in respect of user experience and configuration, is not the best. I should note that these are minor issues and I do not work with Azure very much, there being only a couple environments in which we employ it. 

We see the same issue with Microsoft, which is not an intuitive platform. The ways in which the various components are placed seems to be illogical. There are different screens and end-configurations. In my familiary with Microsoft, a decision was reached to do things this way and there is no way to alter this. 

As such, the solution could definitely be more intuitive. 

The solution is reasonably stable.

The solution is completely scalable. 

I have encountered no issues with Microsoft tech support. 

The setup of everything is very quick, although the real issue revolves around the speed at which the changes get synchronized. While this may take 24 hours, there are occasionally issues which arise, such as problems with the DNS or general networking issues. This requires one to involve Microsoft tech support.

The technical team required for deployment and maintenance can vary. One of the clients with whom I work is an external provider who does all the configuration in Azure. Another has a back-end of Microsoft 365 and I manage this on my own.

Everything involves an annual commitment with a monthly charge.

The solution is also cloud-based.

At present, two of my clients are using the solution. 

I would not recommend the solution to someone who does not require it, instead referring the person to AWS. Like Microsoft Azure, AWS is also not sufficiently intuitive, although it is a more robust solution in my experience. 

I rate Microsoft Azure as a six out of ten. 

We use Microsoft Azure for different use cases. For example, we are hosting our corporate website on Azure. We are a software development company and we have hundreds of development and testing environments in Azure. Additionally, we use different Microsoft services, such as Office 365 and Azure Active Directory. A lot of our services are based on these technologies.

We are using Microsoft Azure because our organization uses a lot of Microsoft solutions. We have used Microsoft technology for a long time and we have internal engineers with great capability that understand the technology. This is why Azure is the best for us.

The quality of some components of Microsoft Azure is not that great. For example, Microsoft has not fixed issues in Microsoft Teams for many years. There are well-known issues that are submitted by customers two years ago and they still are not fixed.

I have been using Microsoft Azure for approximately four years.

Microsoft Azure is stable.

The solution is scalable.

We have hundreds of users using this solution in my organization.

The technical support has been great.

We use Google GCP and AWS by Amazon.

The initial setup is not a problem it is similar to competitors, such as AWS.

The pricing of Microsoft Azure is not very flexible.

I would recommend this solution to others.

I rate Microsoft Azure an eight out of ten.

We use Microsoft Azure for our IDB. That is our primary use, but we also have a certain degree of MDM through Microsoft.

It does what it is supposed to do, and what we expected of it. That's the key benefit. Being cloud-based saves the provisioning aspect of an on-premises solution.

The support subscription models need improvement.

I have been using Microsoft Azure for a couple of years.

We are using the latest version.

Microsoft Azure is a stable solution.

As far as we have expanded it, it is scalable. It's a startup company, we haven't scaled it to a significant number of people yet.

We have between 100 and 150 people in our organization who use Microsoft Azure.

I don't think that we will expand our usage at the moment.

I have contacted technical support on one occasion. My biggest issue with the technical support of Microsoft is when we had an issue that was product-related and it was difficult to get support on the subscription level we were on. In order to try to get support, we were told that we needed to upgrade. It was quite frustrating that an issue with their product required an upgrade to get serviced when it was a failure that they were responsible for.

It's not a question of knowledge, the knowledge was there. Access to that knowledge and the subscription model they were trying to put in place was the issue.

I used to work for Oracle. My previous experience was with Oracle Enterprise Manager.

I wasn't present or involved at the time of installation. I came along later. I started with the company after that.

Licensing fees are paid monthly.

We are currently in the process of deploying Zabbix to cover our monitoring needs. We have used other monitoring products which come with certain components.

From my point of view, it would depend on the type of solution and everything they were trying to encompass. In our case, it made sense to go with Azure. I think that for other companies, I would recommend that it's a good solution, but that depends on what problem you are trying to solve. It also depends on what infrastructure is already in place, and whether you want to have a lot of disparate systems communicating, or whether you want to consolidate that to a specific vendor. But for the purposes of what we needed Azure to do, it does the job. However, we don't use all of the MS Apps functionality.

It does the job, but it doesn't wow me. I am pretty happy with it. I don't get overly excited about it, but I am not disappointed with it. I would rate Microsoft Azure a six out of ten.