Microsoft Azure Reviews

We have some services that are customer-facing that was put on a public cloud. We also have some of the applications that we use in-house, and we put that in our private environment.

Currently, because we have migrated our infrastructure to the cloud, we boosted some of our core applications in the Windows virtual environment. We also make use of it for our call center solution.

I like a lot of features. For example, the Windows virtual solution has helped in such a way that our client-based application was converted into a web-based version through the use of the Windows Virtual Desktop. It makes life very easy for our users when working remotely from anywhere. Because of Azure, the work from home policy makes our work feel seamless. We make use of SharePoint, and collaboration has been very smooth and wonderful. We also make use of Microsoft Teams. It's been wonderful. It's been very awesome.

With Microsoft, our only concern is exchange rates because we're paying in dollars. It's very expensive for us because of the exchange rates. It would help if they partnered with someone locally so we can pay in our local currency. That's the only major area that we wanted them to look into. At least for exchange rate purposes, they should try to do something.

We have just migrated our infrastructure. I have been using Microsoft Azure for a couple of months.

I can guarantee that it's 100% reliable.

It's very easy, and we don't regret this step at all. It's very scalable, and sometimes if we don't need the VM that we set up, we can quickly decommission it. Then if you wanted it back up again, we could bring it up quickly. It's very scalable. We have an average of 50 users at the moment.

Technical support is very good. I like that they have local partners and local support in our own country and not someone in another geographical region. When we wanted to do the setup with the Microsoft partner, we had some issues, and we reported it to them. They were very responsive. 

The initial setup is very straightforward.

The implementation was straightforward because Microsoft had some partners here. To be a good Microsoft partner, you would have done a lot of training with all this stuff, making our deployment and migrations very seamless.

We're paying in dollars, and it's very expensive for us because of the exchange rates. We have all kinds of agreements with the partner, and we'll be paying quarterly. But it depends on how you want to pay. It depends on the option that's flexible for you.

We would recommend this solution to potential users. I would advise them to analyze the infrastructure and what they want to achieve. After that, they should be able to get across to a good partner. 

That will help them a lot because they would need a good supportive partner. Migration can be very miserable, so they should consider a good partner. They should also have their own internal strategy on what they want to achieve. This will help the partners help them. 

We wanted to do a whole lot of things that cost us even more. But because we were able to get a reliable partner, they were able to guide us very well, and we were able to get some significant cost savings.

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

We are vendors. We are neutral from the technologies. We provide solutions to our clients as well as implement the customer needs with the different technologies.

We have a multi-channel mobile app solution that we implement, and we have an API deployed on Azure cloud. We use API management in the Azure cloud.

The most valuable feature of this solution is the ease of use.

The Azure APIs is monetization. Its support, monetization for prepaid and postpaid are good features that we look for.

I would like to see this solution support integration.

We have been selling Microsoft Azure for a couple of years.

We are implementing the latest version.

Microsoft Azure is stable.

It's a scalable solution. We have approximately 1,000 users who are using this solution.

Technical support is awesome! It's very good.

We have installed many competitive products, such as Appigee and IBM, but Microsoft Azure is the easiest one to install.

While I was not a part of the deployment, I know it took them less than a week.

We have a team of 10 to 15 for the deployment, customization, and implementation of this solution.

For anyone who is interested in using this solution, I would recommend it.

I would rate Microsoft Azure a nine out of ten.

We use it to extend our own data centers and banking scenarios for banking solutions.

It provides us with access to technology that's not available in any other form. It only exists in the cloud. In order to keep our solutions modern, we have to do it through the public cloud.

Kubernetes service and API management are the most valuable.

It should have a better hybrid-cloud central analysis. Their support service also needs to be improved. Our main concern is support calls. Our issue is basically related to the technical functionality of the services that we use. It doesn't behave as expected, and support often fails to solve the problem.

I have been using this solution for three years.

It is pretty stable. It has very good stability.

It is scalable. There are no issues with scalability.

We have a maximum of 200 users. They include internal developers and other types of profiles.

Their support service needs to be improved.

It is complex because the solutions are complex. It depends on how you want to do the setup. For our business scenario, it is complex because there are a lot of security rules that are involved in it.

It is competitive with other public cloud providers, and its price is very close to different cloud providers. There is not a noticeable difference between different cloud providers. Otherwise, it would be a risk for them to have services that were much more expensive than their competition. They're pretty much neck to neck on pricing.

I would advise others to go for the closest possible platform as a service. Do not go for infrastructure as a service; go for platform as a service.

I would rate Microsoft Azure a nine out of ten.

Currently we are hosting custom web applications, boxed applications, Azure VMs, Azure files for shared company files, Azure blob storage, Azure Active Directory with Active Directory sync, Single Sign On, and development and testing purposes.

Creating VMs for development has been huge since we ran out of resources locally. Creating Hybrid solutions provides us with greater confidence in higher availability. Storage has made remote access to files much more painless and easy. Using SSO has also been great reducing the number of passwords and locations required to use them.

Customized Dashboard, Site-to-site and point-to-Site VPN, Virtual Machines, Web Apps, SQL, SharePoint, Storage, Test/Dev environments.

Pricing is very difficult to guesstimate. With so many a la carte options and individual pricing it can be a hassle to understand. I constantly need to go over the report to find out where I can save money and what is eating up the monthly costs.

No issues with stability. Has been rock solid.

Scalability is Microsofts big advantage. At anytime you can scale up or down your servers or services growing them or shrinking them to your needs. You can even automate this process. I personally do not get into Enterprise solutions but they continue to add larger solutions frequently.  

Customer Service:

First response is 2-4 hours. Staff is knowledgeable but can often be difficult to understand and slow. Although I do not call about routine issues and bring very complex problems there way. With that said I will say every issue does get resolved.

Technical Support:

I rate technical support 7/10. First response is 2-4 hours. Staff is knowledgeable but can often be difficult to understand. I have also found that a few of them try to e-mail you despite your request for a call. This causes much miscommunication and additional time your problem is not getting resolved.

I only give them an 7 because I have struggled a time or two with understanding their English or getting the ball rolling resolving my issue. This all really depends on the department you need.

I will say that they always get the issue resolved regardless of the complexity of the problem.

No I have not, but we chose Azure simply simply because we are Microsoft partners and get free Azure credits to work with.  Microsoft is also a power player in cloud solution and a trusted name.  

Huge learning curve for me. I found just diving in was incredibly difficult. Much lab time required to understand how things work together. Once you get going however it all makes sense.

I also find the GUI to be more intuitive then AWS and feels better.

They are constantly changing the GUI while they continue migrating the ASM model to the ARM model. Since this is a living platform it can change from one day to the next adding features. 

I implemented all the solutions myself with a little research.

Microsoft does have special pricing for Development purposes. This does help reduce the monthly costs for our team.

As our local resources reach their end of life, we have moved servers and services to Azure.  It becomes more of an operation expense as apposed to a capitol expense. 

We are MS partners. Depending on your partnership you may or may not get Visual Studio Enterprises licenses. Each license allows you to get a $150 Azure credit per month.

This has been great for our developers and I to put in to practice some Azure solutions.

There are many other free credits available as well.  Do some searching.

If you need to purchase Azure they do have a pricing calculator that may help you determine costs.  https://azure.microsoft.com/en...

I know AWS is another great solution, but have not tackled it yet. I do have plans to experiment with Amazons solution to determine for my own the differences. 

The biggest advantage to using Azure over any other cloud solution is the ability to move your domain into the cloud and be completely server free and still have domain services.

I have also found that site-to-site vpn with domain services rack up a good percentage of our monthly costs. These are the fundamentals to move your network into Azure.

We were using Microsoft Azure for file storage and file backup. So, it was one of our backup resources. Internally, NAS is there in our company. So, we go from NAS to Veeam and Veeam to Azure.

Feature-wise, I like its stability. Also, it is easy to access the solution and its options. Also, the backup solutions can take anything, so we can easily find out any option.

The security feature in the solution is an area that needs to be improved.

I have experience with Microsoft Azure until six months ago. Also, I was using the solution's latest version.

It is a stable product.

It is a scalable product. There are more than 100 users using the solution. I am just involved in the maintenance of the servers and infrastructures.

We need to purchase Microsoft Azure for our clients, including cloud backup and any Azure solutions. So, So that time, we need to contact technical support. I expect more technical support from Azure.

The solution's initial setup is straightforward. When you need to create multiple tasks, the solution can get complex. I am not involved in the deployment process.

I can recommend it to other people who want to start using it. So, our company provides a lot of solutions to our clients, including backup solutions like NAS storage, cloud storage, and servers. Parallely, we provide support to users.

I rate the overall solution a nine out of ten.

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.

As the solution is cloud-based, we always use the latest solution. 

We make use of the solution in the cloud for specific internal applications.

Use of the solution could be easier. It is too complex.

The solution is not sufficiently informative and there is a need to wade through much information. 

Moreover, we find it lacking when it comes to active dashboards. This is problematic when looking to Teams, as it does not allow one to know what is transpiring in real time, such as when there are concurrent conferences. This information only becomes available the following day. 

I have been using Microsoft Azure Review for three years.

The solution is stable. 

The solution is scalable. 

Microsoft's technical support is good. There is no room for improvement. 

We looked at web user before going with the solution. 

As the solution is cloud-based there is no installation involved. 

The license is on a monthly basis.

There are approximately 100 users utilizing the solution in our organization.

I would definitely recommend it to others.

I rate Microsoft Azure as a seven out of ten. 

Our use cases are basically cost agility and efficiency.

Microsoft Azure really enforces the automation capabilities of our workforce. It drives us towards a new operating model in terms of delivering services more quickly and more automatically.

I think Azure's level of automation to achieve efficiency or agility is valuable. I also like the change capability cadence, the showback capabilities, and understanding what our costs are. We don't have that in our on-premise environment. That whole showback capability is very interesting for us. It helps to hold the stakeholders accountable for our spending. 

Talking about improvement is like a double-edged sword. We like that they have the new capabilities, but sometimes they're deprecating capabilities faster than we can handle. If we had to improve it, we would want to stay on some of these older capabilities a bit longer. It's a brilliant platform for our staff to be more agile and more efficient but probably doesn't match with us in terms of maturity.

For example, they offer this tagging capability, but they keep introducing new platforms without it. We've become heavily reliant on tagging, but in the case of NetApp, they introduced it into the environment, and now we're not able to get the showback off of that. 

If they introduce new capabilities, they have to have all the features and functions on that new capability. They're not very good at that. If they introduce new capabilities, all the feature sets on these new capabilities should be available immediately. From my perspective, that's where they need to improve.

We have been using Microsoft Azure for about a year.

Stability is very good.

Microsoft Azure is very scalable. Our data center staff are using the solution, and then the application teams are engaging the data center staff to use that solution. We've just had a few use cases in there, and now we're just gaining experience.

Like with any new technology, we're currently re-skilling staff. It's the way we're approaching it on a six to 12-month journey before we start to get to the product and the benefits.

Technical support is average.

The initial setup isn't straightforward. You need to bring in an experienced system integrator to help you with the knowledge transfer. That's the approach we took.

We brought in an experienced system integrator that helped us build the environment and did the knowledge transfer into our workforce. I think that's a requirement. We had a very positive experience with our system integrator. The setup, we call it the Azure landing zone, and it's the data center. To set up the foundational build was a three-month engagement.

The system integrator is the intermediary between Microsoft and us. That's the value proposition of a system integrator. The system integrator helps cut through some of that. Microsoft is a big organization, and it's sometimes very hard to get to the right resources with the right knowledge. The challenge with Microsoft is that they have multiple solutions, and it's up to you to pick the right solution path. That's very hard for most organizations to do.

It's a metered environment, and it's pay-as-you-go. That's the big challenge with a metered environment. The challenge is optimizing how you use that to reduce your meter costs. It's like your children have to be good at not leaving the lights on in their bedroom to save on the power bill. That's a cultural change. 

You have to change your consumption patterns, and that's hard to do. You can get a very big bill because your consumption patterns aren't very good. We're no different than any other organization that's gone to a public cloud. You get these surprise bills, and then you've got to figure out how to manage them down appropriately.

For us, the additional cost is connectivity to the Azure data center. They said that we had to set up an Equinix data center to get from our location here in Regina, Saskatchewan, to Toronto down East. Those are some big new communication charges that we didn't have before.

That adds a significant cost to that. Private internet connectivity to a cloud is a big expense. That can be a very big cost, especially for remote businesses that are co-located to cloud data centers.

Microsoft Azure was a strategic choice. We wanted to go with a multi-cloud model, but we felt like we didn't know enough about clouds. We just kind of thought Microsoft was one of our strategic partners and decided to go with them and learn before we took the multi-cloud approach.

The advice I would give potential users would be to focus on their cost management skills and metering skills. It's all about managing your consumption. You've got to understand your consumption patterns and then learn how to manage consumption patterns going forward.

It's a really good product. In terms of leading hyperscalers, they offer very competitive features, functions, and rates compared to AWS and Google. They continue to advance their technical capabilities as rapidly or more rapidly than the other two hyperscalers. So, I would rate Microsoft Azure very high.

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