Microsoft Azure Reviews

We are resellers. We use Microsoft to provide a service to our customers.

We offer SaaS software for the marketplace. 

We offer SaaS software for the B2B marketplace and provide solutions to our customers through public cloud infrastructure.

We have yet to explore this solution and what it has to offer because we are still in the transformation phase from Amazon to Azure.

It could be more open to external solutions.

Integration with other ecosystems would be beneficial. During this transitional period, this is our primary concern. For example, when we offer solutions to our customers, we must connect to their IT ecosystem, which we are unable to do in some cases.

A good strategy would be to include a feature for integrating with external ecosystems.

We would also like to improve the security.

We switched from Amazon to Azure six months ago.

In the short time that we have been using this solution, it appears to be stable enough for our needs.

We work with 50 companies that use this solution on a daily basis.

We have no issues with the technical support. It's fine.

We needed to find someone who could help us. It depends on the support contract you have with Microsoft. 

The standard level of support was obviously insufficient for us, and we had to resort to a more advanced level of support for partners who had complex technical questions. This meant that there would be some additional support costs, but everything would be fine once you made that decision.

We use Auth0, which is an IAM-based solution.

We are using an identification solution provided by a cloud provider. We are based on Azure. We work with a Microsoft Azure infrastructure, and we use the solution provided by Microsoft to authenticate the users.

It is easy to install.

It took us a few months to deploy. I did not take a lot of time to move to Azure but moving to another infrastructure using microservice takes longer.

We are coming from a moderate approach to installation and going for a modular one that is based on microservices.

To be able to manage the microservices, we made some modifications.

The length of time it took to complete the implementation was primarily due to changes we made to the infrastructure that was required for our customers.

We have a dedicated team of ten people who will deploy and manage the infrastructure.

We have a separate Dev team for the application itself.

Customers pay for our software and use our solution as a service through monthly payments. They don't pay the licensing fee directly to Microsoft.

We provide a solution as a service to our customers. They pay us for our services, which are based on Microsoft.

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

I would rate Microsoft Azure an eight out of ten.

We're using Azure Premium P1 and it hosts our website and most of the applications we use. We are an airline company and for some of our enterprise apps, it enables things like single sign-on and hosts most of our virtual machines, as well as some of our web servers for the on-prem application. Our customer mobile app for purchasing tickets is for that purpose but we also use it for enterprise apps. I use Minecraft for my email security, but I integrate it with Azure to incorporate the single sign-on, as well as for multifactor authentication in my Office 365 environment, and the productive Parti app. I'm an IT security specialist and we are customers of Azure.

The feature I appreciate is that everything is basically shift forward from a security standpoint. Most of our systems are integrated with Azure for authentication purposes. Given that I'm a security specialist I use it for that purpose. The rest of the team uses it more for things like application deployment. I also use it to determine sign-ons, and things like compliance to devices. 

Microsoft allows you, via Azure, to have different authentication methods. You can use the Microsoft Authenticator app, text or voice, or something called a FIDO, which is like a USB security key. Unfortunately, the authentication method only allows me to have up to 90 users, and there are 2,300 people in the company. When I have to push multifactor authentication, I cannot specify certain users for the authenticator app. It forces me to lock it down and say conditional access only allowed.

Another issue I have is that Microsoft notifies me retroactively about certain things. For example, when a user sends an email with over 200 recipients, it can take half an hour for me to get a notification but sometimes it can take 24 hours. I have the same issue when it comes to things like phishing attempts. It's a problem. 

I've been using Azure for three years. 

The solution is stable, although I'd like some advance warning when they make changes. It can sometimes take hours to update so that if I have a user using multifactor authentication and I take them off, it can take up to an hour for it to take effect.

Technical support is very good. 

I can only speak from my own experience and I have many Microsoft certificates, including as a Microsoft solution architect expert in Azure, so it might be easier for me than it is for others. I tend to do a lot of things on the app and I use it on a daily basis. Even if I don't know where something is, the documentation on techniques, everything is there. I wasn't involved in the deployment at this company but in my previous position, it took a couple of days, not very long. Microsoft provided support. It's just a matter of configuring the tenant.

I would recommend Azure because there's a lot of documentation available and a lot of user guides, it has everything. 

I rate the solution eight out of 10. 

I am a manager of a team and we will have approximately 18 applications that will be cloud-based using this solution.

One of the most valuable features of Microsoft Azure is the compatibility with all of our Windows applications and other Microsoft technologies.

I have been using Microsoft Azure for approximately one year.

The solution could improve the stability. However, this could be a configuration issue that we are not been trained.

There is good community support available.

I have previously used AWS and GCP.

Microsoft Azure is more expensive than other solutions, such as GCP. We have found that GCP offers more utilities at a very reasonable price. I think the reason we are having a discount is because of the bank contract we have.

I would recommend this solution.

I rate Microsoft Azure a seven out of ten.

We buy licenses in order to provide an ecosystem on Microsoft, using Azure for documents and also for accessing Office 365 and for corporate messaging and so on.

We use Azure for everything. For example, we use Microsoft Teams on Azure for our conference calls and we also use scrum tools and project management tools as well. we use it on endpoints to work in remote places. Our CRM and procurement platforms sit on Azure. There's also antivirus features on it.

The solution is good for enterprise control and managing various systems.

The solution is quite stable.

The scalability has been good.

We haven't seen any security gaps as of yet. It feels very safe.

The initial setup is very easy.

Technical support has been extremely helpful.

We need more security to be available on our smartphones and mobile devices. They need to improve the protections available in that area in particular. We're actually currently looking for solutions that will protect devices of this nature so that they can safely access the corporate network. 

We began to use this solution last year, in 2020, when we begin to have to do remote work.

The stability of the solution is excellent. There are no bugs or glitches. It doesn't crash or freeze. the performance has been good. 

The scalability of Azure is very good. If a company wants to expand it, it can do so with relative ease.

We have about 300 endpoints in our organization that use Microsoft Azure. 

The technical support on offer is very good. If we ever need help or extra assistance, they are happy to jump in. We're quite satisfied with the level of service on offer.

The installation was mostly straightforward, although we did run into a few small issues. We had the local Microsoft team assist us, however. For the most part, everything ran smoothly.

It typically takes two to four hours to install everything.

We have a technical team of 15 people that can handle deployment and maintenance as necessary. They are IT and help desk personnel as well as two managers. We also have a team that focuses on cybersecurity and information protection.

Our local Microsoft team helped with the installation.

We're on a three-year standard license. We do have to pay for licensing.

We haven't looked at other solutions. We prefer sticking with Azure.

We're customers and end-users.

We use both the cloud and on-premises. 

We're using the latest version of the solution.

I'd rate the solution at a seven out of ten. It's very good, however, it has room to grow.

I'd highly recommend the solution to other individuals and organizations.

We use this solution for single sign-on authentication.

We like that you sign in only once and that grants access to all of the Microsft applications, as well as others such as ServiceNow and SAP Concur.

Ease of use could be improved. You wouldn't just be able to use this solution without being trained on it.

We have Microsoft Azure for approximately five years.

We are always updating Microsoft.

It's been pretty stable. There have only been one or two instances where Microsoft went down. One time, it was the building's main operations center that was struck by lightning and caught on fire.

We have 20,000 users in our organization who are using this solution.

As we acquire other companies, we will increase the usage.

Technical support needs improvement. If you are able to get a rep then it's great. If not, you are left hanging.

Previously, we used Okta.

We switched over because we got the Enterprise package with Microsoft Suite.

The initial setup was completed by our internal Microsoft team.

Microsoft Azure definitely provides us with a return on investment.

Licensing costs for Enterprise are on an annual basis. In addition, we pay to have Gartner help us negotiate.

It is best to have a dedicated team because it is not easy to use and get set up or to get acclimatized in the amount of training that you need to become familiar with the solution.

I would rate Microsoft Azure a nine out of ten.

We use the solution for multi-factor authentification while sorting out the identities. We want to use this solution for as many applications for the authentification process.

One of the features I have found to be valuable is the scale set feature. We have been able to get good results scaling up and down our applications. Additionally, the dashboard is fuctional.

There needs to be better data security. There are organizations that do not want their data to be submitted to Microsoft, they should have strong encryption.

In the future, Microsoft should increase its data center percentage in Africa.

I have been using the solution for two years.

The solution has been stable.

We have found the scalability of the solution to be good. We have approximately 4,000 people using the solution in my organization.

If we are having a hard time finding a solution to an issue the technical support has been very quick to respond.

The initial setup is straightforward for me since I have done it before, for people new to installing it could experience some difficulty.

The solution does not offer very many free services which can become expensive. We are on an annual license.

I would recommend this solution to others.

I rate Microsoft Azure an eight out of ten.

We have a complete Microsoft ecosystem. Azure comes with a variety of parts such as infrastructure as a service and platform as a service or SaaS. We are using it for infrastructure as a service and software as a service as well, so both SaaS and IaaS are being used.

All of our solutions are being deployed on the Azure server. We use the Azure authentication functionality across our organization, which is a single sign-on functionality, so it is Azure-based. We also are incorporating the DevOps framework, which, again, is being integrated to Azure. Our complete backbone is being moved to Azure, and most of our systems are moving to the cloud version.

I think the single sign-on functionality and the ease with which you can deposit things on the cloud have been valuable.

Azure has very robust security functionalities and authentication features, which come with mobility, along with backup and credential checks.

Scalability is also very robust because you can deploy the solutions on the go, and along with that, it provides you an ecosystem to integrate with the existing Microsoft products. For example, we have Power BI, and it's very nicely integrated with the Azure cloud version.

The interface is quite user friendly and intuitive. The reporting is perfect as well.

Integration with other services could be much better.

We have been using Microsoft Azure for over two years now.

The stability is very good. As it is a Microsoft product, the reliability is very good.

Because it's a cloud-based solution, scalability is not an issue at all. We currently have over 200 development team members using Microsoft Azure.

Technical support staff have been responsive, and the support was good.

The initial setup was a bit complex. It was getting ruled out sometimes, but it was at a Pan-India level. So, it was expected to take some time; it took about 8 to 12 months. Overall, it was good.

I believe that we have a three-year license, and I'm happy with the pricing.

I think Azure works best when you have the complete Microsoft ecosystem. Then, you get the real value out of it. In my firm, we have the complete enterprise licensing model. So, we have an integrated ecosystem, which provides a very collaborative way of working, along with the ease of creating.

If I were to rate Microsoft Azure on a scale from one to ten, I would rate it at nine.

I primarily used the solution for hypothetical cases. I used the solution to look at the 2019 active directory environment, some remote SQL storage, and storage access from on-premises to the cloud.

There's a feature for automated tasks. As an administrator, handling administrative-type tasks, it's quite useful. For example, I was spending lots of money when I would spin things up. I'd spin up a SQL server. I'd spin up different types of things. They cost a lot of money. I would get distracted, walk away, and go to bed. I'd get up in the morning, and I'd see I'd have a bill. Therefore, I spun up an automated task and wrote a PowerShell script, put it in an automated task, and it would run at seven o'clock every night, and delete all my resources. It saved me money.

You can build an environment in minutes. It's very good in terms of being an infrastructure as a service, and I found that really fascinating.

All the devices they have up there that replace existing devices in the real world like load balancers or F5 are helpful. I'm not sure how they relate or how they form compared to F5, or the firewalls compare to the ones that are in data centers, however, they looked all right to me.

The solution is mostly stable.

The product scales extremely well.

It's a bit of a mystery how the storage is going to perform. For example, when you've got a storage device like Hitachi or NetApp, you can run reports on that storage and you can do all this good stuff. I'm not sure if that's the case with Azure. A lot of the stuff is kind of proprietary, at the moment.

The cost is quite high.

You can't control the data as much as you would like to. When it's theirs, it's theirs. With Hitachi, Hitachi has its own policies. You can move data around based on how much it's used into lower-cost discs and whatnot. You might be able to do that with Azure. However, I can't verify that.

The initial setup is complex.

They need to make storage easy and offer more interconnectivity between solutions.

I've used the solution for about a year or so. Maybe a year and a half at most. It hasn't been that long.

In terms of stability, I've seen it go down twice now. They've had two problems with the active directory. That said, I would describe it as stable. They have different sites, regions, and whatnot, where you can move your data around in case you lose a data center or you lose a region. However, if you lose the active directory, that can take everything down.

It's not any more stable than an enterprise environment, to be honest. Maybe a little bit, however, if you lose a network connection to it, that's not stable.

I worked in a bank, a huge 50,000 employee enterprise. I saw their infrastructure go up and down about the same, once or twice a year. That's about the same as Azure, therefore, it's not anything different than an enterprise. You can make an enterprise resilient if you have lots of domain controllers and you do lots of redundant paths. 

The solution is very scalable. It's one of its great selling points. If a company needs to scale, it can do so with ease.

I've never been in touch with technical support. I can't speak to how helpful or responsive they are.

For a layperson or someone who is not trained, it wasn't an easy initial setup. It had some complexities.

I've personally gotten used to the process. The deployment, for example, wouldn't take that long now. While in the beginning, a deployment might take a month, now that I am more comfortable with the solution and more familiar, I can likely do it in a few days. 

That said, it depends on a company's plans and its own unique environment and complexities. It can vary. Most people seem to struggle with all of the connections they had before.

The number of people you need to deploy or maintain the solution really depends on the size of the environment. After implementation, you could probably scale back your employees from 10% to 50% with Azure.

I can handle an implementation myself. I'm getting better and faster at it.

I've found the cost to be a bit high. You also get dinged for extra things along the way.

The charges are also unpredictable. Even if you think something is a relatively static item, they'll charge you for it and it will change your expectation of the cost.

I've looked at other solutions, such as Hitachi and Netapp.

The biggest struggle a person would have these days, as an architect, is to determine what the cost-benefit of going to Azure would be rather than going to a storage device such as a Hitachi or a NetApp. Which has better value? What's going to be better in the next couple of years? You can really get screwed if you're going to be pulling data down from the cloud. If you pull a lot of data from the cloud, it's going to cost you. You don't get charged for putting it up. You get charged for pulling it down.

I basically used the solution to study.

I used a few different deployment models. I made an on-prem environment, Hyper-V environment, on my laptop and I connected it to the cloud.

I'd advise those considering the solution to not put all of their eggs in one basket. By that, I mean, it's a good idea to go hybrid and not full cloud. Going hybrid covers that network loss that you could suffer if you lose the network. If you lost a data center or a region, you could still have your on-prem server running an image of the cloud onsite.

I'd give the solution an eight out of ten. I haven't had a chance to study AWS or Google, however, I like this solution very much.

We have a private cloud, but we are interested in having a hybrid cloud that includes Microsoft Azure. This use of it as an Infrastructure as a Service will help us to expand our scale using our hardware.

Primarily, we use Azure to test services and solutions that we want to use on the public cloud. Nothing in production is being used on Azure yet because of latency.

Azure is helpful when you want to set up a server, such as a Linux test server. For example, we can transfer our code to the test server and do a comparison.

This solution is easy to use. It has quite a good interface for things like provisioning a server.

Provisioning a server is fast, taking only one or two minutes before it is ready. In our private cloud, this process still takes longer.

At this point, the latency is too high to use Azure in our production environment.

I would like to see support for data streaming in the future because I understand that currently, data streaming is not there. It would work like Kafka does, in Microsoft Azure. If they can provide the Platform as a Service and Infrastructure as a Service, it will be better.

For example, if want to use Kafka, I should be able to purchase Microsoft Azure and then use my Kafka license. This would also give me support. Right now, using it requires first getting a server through Infrastructure as a Service, then getting a Kafka license, then installing the server in the cloud.

We started using Microsoft Azure last year.

Azure is a scalable product. We are not using it extensively yet because we just started exploring it for use as a testing server. However, if we are satisfied with the security and issues with latency then we are going to set up performance tests.

We have not had any issues with support. The interface is quite user-friendly, so we have not needed to contact them. I think that they do have assistance available for onboarding, or creating a server.

We did evaluate other solutions but that is the job of another team in the company. I was only told that we also tried Google Cloud.

The initial setup is straightforward. Microsoft Azure provides an easy interface to log in and create a server.

The pricing is flexible. Our company engaged in negotiations to get a better price, which resulted in a two-year contract.

It seems that the cost of using the service in the short term is definitely good. However, in the long-term it is different. The long-term cost is higher than if you set up the servers on-premises, which is something that could be improved through more competitive pricing.

Our usage is rather limited right now but for what we use it for, the product is quite good and we are satisfied with the services. This is a product that I can recommend for anybody who does not want to invest a lot of money in their own hardware.

I would rate this solution a nine out of ten.

The existing infrastructure of our customers is on-prem. We will be migrating or moving from on-prem to Microsoft Azure cloud.

We don't have to spend money to purchase the hardware, set up a data center, get people to work on it, and maintain security. We don't have to spend any money on these things. It is ready to use, and resources are available for us. We just create an account on Azure and start using the services. 

The time to market is very fast. We just supply the resources, virtual machines, and databases, and our applications are up and running. This helps our customers and us to be more future-ready and cloud-ready.

Its scalability is valuable. Depending on our requirements, we can add as many virtual machines as we want. We are able to get high availability for services. Services are always available, and they have the maximum uptime. If there is any issue with one of the services, another service is always available. 

It is pay-as-you-go. You don't have to spend any money upfront. You use the service and pay after one month or a couple of hours of use.

For deploying multiple resources in a big number, such as in hundreds, we need a streamlined process and more user-friendly scrips. The scripts have to be more user-friendly, and they should also supply some standard templates to deploy multiple resources at a time. Currently, it is very easy to deploy a couple of resources, but if you want to deploy multiple resources, it becomes complex.

The material that they provide for integration with an existing on-prem data center is complex. They have to make them user-friendly. The scripts related to resource management need to be simplified.

I have been using this solution for one year. In our company, we have been using it for four to five years.

It has a very high uptime for services. They are able to provide as per Service Level Agreement (SLA). We are not seeing any downtime for our applications. Our users have not reported any issues. 

They have their internal redundancy for hardware and software. If there is an issue with any hardware, another hardware is ready to take the load.

It is very scalable. We can add as many virtual machines as we want. We have 400 to 500 people who are using this solution.

I have not worked with support. We work in a design team where we have a dedicated Microsoft account partner to provide support. That support is fine. If there is an issue with running virtual machines or there are any infrastructure issues, another team takes care of that. I've not got any complaints from them that their support is not working.

Previously, we had the regular on-prem solution with our own data center. We had to deploy physical servers, networks, databases, and everything else. We needed flexibility and scalability for our customers and applications, and that's why we moved to the cloud.

The initial setup was easy. 

It is operational expenditure (OPEX). There is no cost upfront. When you start using it, you have to pay the charges. Initially, the cost is less, but after you start using it more and more, the cost will go higher. It is a little bit costly, but that is okay because you get better resources. You also get better support in terms of how you create the resources. Documentation is available, and the SLAs are met. 

Companies are now starting to switch over to Azure, and before doing any kind of migration, they need to plan each and everything from scratch. They should have a Microsoft consultant or somebody from Microsoft so that they can plan well before using Azure. Otherwise, they will not be aware of where they are spending and how they can reduce the spending. They would also not know whether their security compliances are being met and whether their network is being fully utilized or having some issues. Proper planning has to be done before using Azure. 

I would rate Microsoft Azure an eight out of ten.