Microsoft Azure Reviews

Microsoft Azure assists in lowering the cost of on-premises infrastructure as well as improving performance.

The most valuable aspect of this solution is its ease of use.

It is quite easy to configure, including the resources.

We don't have any expectations. We have recently stabilized our application in terms of moving to the Cloud. We are still exploring the features available in Microsoft Azure, so determining what could be improved is difficult.

More integration may be required in the future, but I don't believe it is necessary for us at this time. We would be working with a hybrid platform more than anything else.

From a security perspective, there is always something that can be improved as we serve our customers.

I have been using Microsoft Azure for approximately one year.

Microsoft Azure is a stable solution.

Microsoft Azure is a scalable product.

In our organization, we have more than 5,000 employees who use this solution. The organization itself has moved onto the Microsoft Azure Platform.

At this time we will not be increasing our usage.

I have not contacted technical support, but perhaps the infrastructure team has.

All of our applications are developed using Microsoft.NET Technologies. We prefer to use the Microsoft Platform.

Salesforce CRM is a tool that we use internally, as well as Symantec.

For virtual meetings we use Teams.

I was not involved with the initial setup. We have a team of two members to deploy and maintain the infrastructure.

There are no licensing fees.

I would recommend this solution to anyone thinking about using it.

In my opinion, everything is fine, I would rate Microsoft Azure a ten out of ten.

The most valuable aspect of the solution is the limitless possibilities of the infrastructure. 

The documentation is out of date. It needs to be improved and modernized. 

Technical support needs improvement. 

I would like to see more flexibility surrounding what framework you can use for machine learning model creation.

I've been using the solution for three years. 

The solution is very stable. There are no bugs or glitches. it's reliable and the performance is good. It doesn't crash or freeze. 

The solution scales well. A company can expand it as necessary.

We have around 100 consultants using the solution. 

They do not seem to have enough technical support staff. Sometimes you have to contact them using email. You get the answer maybe three weeks after that email. It's available, however, it's not enough, and it's not very fast.

In terms of the initial implementation, how difficult or easy it is depends on the services. The most common deployments are pretty clear and it's pretty simple, however, in some cases, it's very difficult.

The deployments can be fast. For the simplest ones, five minutes is enough. However, sometimes when you are trying to use a specific service, for example, the cloud solution, it could take days or weeks just to get it available.

We have had a partner support us with the implementation. 

We pay a licensing fee on a yearly basis. I don't have details in terms of the exact costs. Sometimes there are extra costs here and there. 

We're a partner.

Inside the cloud, I have experience using different kinds of products like databases products virtual machines, etc.

I'd advise new users to prepare for certification. The most basic one is fine. Companies should preview the solution before they start any project.

I would rate the solution at an eight out of ten.

Microsoft Azure is entirely our current cloud computing product in which the team is engaged. We are using the stack for development and application logs, and audit perception from the application. We are using the log services.

The main benefit of Microsoft Azure is that it is cloud-based. We are using Microsoft Visual Studio for our code and it is tightly integrated with Microsoft Azure. Additionally, the solution is user-friendly.

The dashboard of Microsoft Azure could be better.

I have been using Microsoft Azure for approximately two years.

Microsoft Azure is very stable.

I have found the scalability of Microsoft Azure very good.

We have approximately 60 users using this solution, we have plans to increase usage to 100 users.

I have not contacted the support from Microsoft directly. However, we have a consultant from Microsoft providing us support when needed.

We have a six-person DevOps team that does the maintenance and support of Microsoft Azure.

The price of  Microsoft Azure is reasonable.

I would highly recommend this solution to others. There are still unexplored areas of this solution.

I rate Microsoft Azure an eight out of ten.

We are using Microsoft Azure for various databases, file storing, backup, disaster recovery. It's a very useful service.

Microsoft Azure has thousands of services and products.

Microsoft Azure could improve by having the availability be 100%. Which is difficult, but not impossible.

In the future, there should be more automation.

I have been using Microsoft Azure for approximately four years.

The solution is stable.

Microsoft Azure is highly scalable.

Our customers that are using the solutions can have from 100 to several thousand that are using the solution.

We have plans to extend the usage of this solution.

The technical support is very good.

My projects are normally complex. However, the implementation of Microsoft Azure is very simple.

The length of time the full deployment can take depends on the complexity of the project. It can vary from one month to half a year. It depends on the goal of the project.

I would rate the initial setup of Microsoft Azure a four out of five.

My advice to others is you need to be technically aware of Azure services, which are always in some kind of improvement. It is helpful to be aware of the possibility and functionality of your projects and the financial cost for Azure services in the project plan.

I rate Microsoft Azure a nine out of ten.

We primarily use the solution for backups and ASO.

The ASO is great.

We enjoy the disaster recovery aspect of the solution, which is very interesting, as we pay when it is on. When it's off we don't pay. 

There is no effort investment. We just pay what is being replicated, that's all.

There is the potential to scale.

The stability is good.

We've found the technical support to be responsive. 

In a month, there is a plan to increase pricing, which is something we are not looking forward to.

We've worked with the solution since it was first released. We've used it for a while.

The product is very stable compared to if you are going to employ it in-house. There are no bugs or glitches. It doesn't crash or freeze. t's reliable. 

The scalability is good. If you need to expand it, you can.

We are in Mauritius. Mauritius is a very small country. We have about 1.2 million inhabitants. We are not that big of a country. I have about 25 clients using it.

We are an indirect reseller. We do have the CSP, the cloud service provider, in Mauritius, with whom we purchase. When we have an issue, we deal with them. They do have engineers that provide support as well.

That said, if there are any big troubles then we contact Microsoft directly. So far, our experience has been very positive. The callback is within 20 minutes. It's fine.

The initial setup is not simple. You need to be trained. It's not like it's just ready to be implemented - you need to be trained in what you are doing.

The deployment is quick and only takes about one day.

We do get an ROI from the disaster recovery aspect of the solution. 

The pricing is great, as we only pay for what we use. 

That said, the prices are about to increase in the next month.

We do have some clients in South Africa and some clients in Germany, however, we've noticed that the pricing for Germany is less expensive than South Africa. South Africa has a new data center, which is likely why the price is a bit high.

We implement the solution. We are silver resellers. 

We are using the latest version of the solution.

I'd rate the solution at a nine out of ten.

We primarily use the solution for our infrastructure. It's specific to server regulation and desktop regulation.

We used it for our customers in the pandemic. In terms of expansion on-premise, they were not able to do so due to the chip shortage. Therefore, we are moving everything to cloud and we are capacity-building - a temporary requirement. We are shifting them to the cloud.

As a partner, I like that they have a good benefit on margin.

The stability has been excellent. Multi-regions can leverage their capabilities easily.

The product is scalable.

We find the initial setup to be very simple. 

There are worldwide issues on Microsoft Azure, however, it is happening to Google also and as well as AWS. The problems we have are nothing new.

Technical support needs to be better.

I've been dealing with the solution for three years now.

The stability of the product has been great. There are no bugs or glitches. It doesn't crash or freeze. 

The product is scalable. If a company wants to expand it, it can do so.

We have 30 customers on the solution right now.

Technical support isn't so good. We'd like them to be more helpful and responsive. We'd like them to be faster.

The communication and those aspects are pretty good, however, the resolution could be faster and better.

As a cloud-based solution, the initial setup is very simple, very straightforward. 

We were able to deploy the solution in one day for a few clients. 

We have 20 team members that are technical (Azure system admins) and can handle the deployment and maintenance. We offer 24/7 coverage.

We offer this solution to our clients and can implement it for them.

The licensing is based on usage. Typically, it's a monthly fee that is paid to Microsoft.

We are a Microsoft Gold partner where we provide that, also we are users.

I'd rate the solution at a nine out of ten.

Customers who are on more Office 360 should leverage Azure. From a compliance perspective, these things are much more user-friendly compared to other clouds. Otherwise, there are a lot of compliance issues if we go with the other clouds where the mobility license is required. On Azure, for Microsoft users, those things are straightforward.

The advantage of Microsoft Azure is its simplicity. It's easy to launch a project. However, the problem with this kind of solution is the reliability for the customers. You have to be sure to stay with Microsoft.

It's not always simple to manage the team who use it. Sometimes customers abuse the capacity and it's not always easy to bill the department for the usage.

Microsoft Azure is not always a user-friendly solution. There are too many people who develop this solution. For the end-users, sometimes it's not really fun to use or simple to use. It could be improved.

It's difficult to stop the solution when you have started, you need to use it for the long term. You have to make a good choice when you start the project with Microsoft or with Amazon too. You will have the same problem, once you choose one you have to commit.

When a feature doesn't exist in Microsoft Azure, generally we can use other software that does the job very well, such as backups or supervision. Any products to help the customers and engineers to do a good job, such as managing large infrastructure. There is a lot of solution to make it work well.

I have been using Microsoft Azure for approximately three years.

The stability of the solution was good we have not had a problem.

The scalability is good, there are nearly no limits, and simple to do. However, it is difficult to see the limit.

My engineers sometimes have used the support, I don't have any feedback about troubles with the support. I think the support is good. I don't have bad feedback.

The deployment of the solution is quick and easy.

My advice to others is to be sure if they choose the cloud it is the right choice for them. A customer can be in a hybrid solution, or cloud, or on-premise solution. I prefer the hybrid solution, in the same project. It's a choice they need to make for the long term.

I rate Microsoft Azure an eight out of ten.

I use Microsoft Azure for different clients. I have different workloads or different architecture in Azure.

The most common use case is for migrations from on-premise to cloud. The principal solution is for a virtual machine, storage, and networking. 

The principal features that I use include computing, networking, and storage.

The elasticity within the cloud is great for clients to complete their pre-determined goals.

The cost is pretty good. They have a pay-per-use way of dealing with licensing that is very attractive. Migrating to the cloud becomes very attractive due to this.

The solution can scale.

Stability has been good.

Maybe Microsoft could improve its monitoring around the networking.

Clarity on the cost of the things could be better in some cases. For example, it's difficult to do a report with the cost of the things in Azure. Their calculator to estimate the cost needs to improve in terms of the estimation they provide.

I have five years of experience with this product.

There are some products that have good stability and virtual machines - depending on your setup and configuration - are very good. With Microsoft Azure, it's very rare that I even have a problem with it. In any solution, there's always some form of issue, however, with this, it's less common.

I've found the scalability to be quite good. 

I have worked with clients that have 300 users or more, however, sometimes with a smaller client they will have maybe 60 or 100 users.

Technical support is very good, however, it depends on the problem. There are some problems that originate with the client itself that Microsoft, naturally, couldn't necessarily resolve due to the origin of the problem. However, in general, I haven't had any problems with the support with Microsoft. They are helpful and responsive. 

Whether the initial setup is straightforward or complex depends on the client. There are some products that are more complex to set up. However, for me, it's easy to deploy different features or different products. It's easier compared to on-premise deployments.

Deployments can be two to three months for an enterprise.

For maintenance, you need a good team with good skills in Microsoft Azure, especially in the cloud due to the fact that it's a bit different. Things are different in the cloud compared with on-premise. 

I am able to deploy the solution for clients. 

I work with a team in my company. When, for example, we need help or support from Microsoft, we have a contact with the architect of this provider to resolve some issue or some problem that we have in the cloud.

The pricing is quite good, and it is designed as pay-per-use.

We are partners with Microsoft.

I am an architect, cloud architect, and I work in design solutions and implementing solutions in the cloud.

I'd rate the product at an eight out of ten.