Microsoft Azure Reviews

In general, we use Azure for financial services.

Azure helps us take a few things to the market predictably and robustly. It gives us the speed and predictability to build something in a short time. The cost can sometimes be clumsier, but I believe it is similar to other cloud providers. These are the main advantages, but the price is one factor that has really bothered our clients.

Azure's Data Lake services are decent. I like AKS, and API Management is relatively straightforward to use. The security and SIEM options Azure offers are good. All the infrastructure services are easy to use and set up. 

In terms of adoption, one issue we face is providing training for users who are new to Azure and want to try some features out. There are some methods by which the organization has to allot some budget to them, but it has to be apart from the developer endpoints. It's difficult for them to try out something new. It would be nice if Azure had an evaluation period of 30, 60, or 90 days, so people could try out a few things and learn.

That is one challenging area, but this is a problem with all cloud providers, not just Azure. Some free subscriptions are available, but they are for the cloud platform as a whole rather than just a single service. For example, say I don't have a trial subscription, but I want to try something new like Azure AKS for 30 days to learn and to try out. 

It's hard to say what Azure could add. There are a few specific requirements that clients raise based on business needs. In general, I don't think there is any particular feature I can recommend.

I've been using Azure for about four or five years.

Azure has had some issues on and off, but that was a couple of years back, and now it seems okay. Sometimes the performance of the cloud degrades, but there are workarounds. 

We mainly use AKS, which is pretty scalable, so I don't see any issue there. Azure's scalability is relative, so it depends on the client and the solution. Most of our clients are B2B, so they don't have many users. However, we provide a retail banking solution that involves hundreds of transactions per hour. Azure can handle up to a hundred transactions per second can be supported, so I think it's okay.

We talk to Microsoft support often.

Azure setup is pretty straightforward and we mostly handle it in-house. However, it depends upon the complexity of the use case, how we are deploying, and the kind of application we are building. The build and deployment times depend on how we structure our packaging. 

Azure is expensive, but that depends upon who you ask. It probably wouldn't be considered a significant expense for a large corporation, but it's costly for smaller enterprises or startups.

Pricing is one area where Azure has room for improvement. There should be some due consideration. Azure has solved some issues with pricing from the development team's standpoint, but it is still quite costly. They should also offer a trial period for the individual platform solutions. I think that would be pretty handy for the developers.

I rate Azure eight out of 10. I would recommend it. I don't see any challenges from a technology standpoint.

I know Azure. We have the tools for optimized Azure infrastructure. As a partner, as an active integrator, I am looking only for plays to make the deal. I am not an end user, prospector or client. I use it in my projects but I am not buying any solution from Microsoft for ourselves. I am the seller.

When I talk about the Infrastructure as a Service from the Microsoft, I am referring to a hybrid infrastructure. We are talking about the moving of virtual machines and workload from on-premise system to the Cloud. This is my main topic when we are talking with the client. My technical team worries about the details of how we do this. I am not so good in the technical details.

In terms of our customers' use cases, in our last project, the customers migrated the SAP system from on-premise to the Azure with SQL as a database. We helped the customer to compare on-premise infrastructures and Infrastructure as a Service in Azure, and to help them migrate the machines, the tech, and the servers from on-premise to the Cloud and to have the tools from the Quest to help them optimize because they did not want to pay so much. They only wanted to pay by use. We are looking for the perfect tier from Azure to finish the project. This was our job. That's why I like the Azure.

There is not too much perfect information out there about how to optimize the infrastructure. Microsoft is looking for the bills where the sky is the limit but the customer is looking for the real cost. We help the customer and we have the answers regarding which tier or which configuration in Azure is proper for them.

Microsoft Azure is so complicated inside. If you should do something internally, if you have to configure something, the opinion about Azure is that it is a little complicated inside. That's why the end users and clients are looking for help and why we help them configure and do anything inside of Azure. That is why we offer other tools to optimize the Azure environment.

Microsoft makes the space for such tools because it is a little complicated and end users know it. That's why we sell these tools to optimize the Azure. I think the Microsoft team knows this and they create the space for other third party partners.

I know all the points about how the Cloud is so beautiful but if somebody starts to do something inside the Azure, it is a little hard to understand. Many services are so complicated to configure out. That's why sometimes clients are obviously confused inside the Azure. That's why they are looking for help with it and why they are looking for a Microsoft partner with the knowledge of how to connect this software into one solution. From my perspective, I like Azure because it makes me money from the end user clients. But for the customers, their opinion is, "Oh, my god. The AWS is easy."

It is well-known that Microsoft is not so easy for the end users. Maybe it's because there is a note of everything changing. They add new features and new functionalities. Azure is growing. From my point of view it's okay. From the customers, it's also ok, but they are looking for someone who understands how to configure it.

From the beginning, the first move to Azure as a solution, it's a long journey with many, many services to find the final configuration for the customer. But it's okay for me.

In terms of scalability, it is perfect. If you are a rich partner or a rich company and you have a lot of money on your credit card, the scalability and the possibility of using Azure is a perfect play. If you want two servers, if you want 200 servers, it's one click. From the marketing point of view, it's the perfect place to spend the money. I think the customers are really worried about the cost. If you request a lot of machines, it's only one click in the setup but the bill for that is so huge. They ultimately worry about how to prepare their production environment just for us. Not for the sky is the limit but for our requirements to help. We have tools for monitoring consumption of the Azure and we can switch virtual machines off when at the end of the day. Customers are happy that we offer that because they are a little worried.

For example, if you buy one huge service for your on-premise project, you pay for that one service. But if you put a development team on the project and they request a lot of virtual machines because it's so easy to deploy, someone should pay for that. This is literally one big worry from the client side.

The calculator from Microsoft for Azure is very basic. This tool only shows what you consumed and what you will pay. There is no answer if you want to know how big a credit card you need to run the project. We make money answering exactly how much you really need for your project. We save the budget for the customer. We find opportunities for Microsoft but when the customer is worried, we help them. It's also good for Microsoft because they run the project.

We have support but Microsoft is trying to cover only Azure as an infrastructure.

They are not interested in talking about current applications or current systems from a customer perspective. This is the job for the partner. Microsoft covers only the chief environment. The job for the partner is caring about the customer's real needs. That's our job.

We only have experience with AWS because for us it doesn't matter whether we run virtual machines on AWS or Azure. If the client is only looking for power servers, then the machine they are looking for is AWS. If they are not only looking for IaaS, Infrastructure as a Service, but are also looking for the DaaS or Database as a Service, they are looking for Azure. It is exactly the same way for customers that are using SQL Server. The first choice is Azure.

If you are looking for Oracle, they're thinking about AWS. Of course, if we are talking about the containerization, about the Kubernetes, AWS is also the first choice for our clients.

The initial setup depends on the project. Because we are the Microsoft partner and we have some money for our internal tests we do the setup part. We use Azure infrastructure for our demo when we show our virtual demo machine. For my colleagues, it's not so complicated but we are using only a very small part of Azure.

When we talk about the real project, it is not so easy. We are using a very basic functionality, but I know from the other projects that it is not so easy to implement, run, test, et cetera because it's always a little complicated. Maybe it's okay. It depends on the current customer's needs.

ROI is a very tough topic because with the first step, every customer is trying to compare what they pay on the infrastructure and what they will pay in Azure. This is never the same number.

The challenge is to show to customers the added value because Azure is not only a different type of data center, but is also a place where you can make the innovations and add some new services. It is much easier than on-premise. We have a lot of ready-to-use functionalities on Azure, but the magic is how to use it.

Sometimes, the customer does not have the knowledge to create new value for the business using the ready-to-use functionality on Azure from the Microsoft offer. This is the challenge.

Moving the one virtual machine is easy but knowing how to run your business application for the customer, this is the main challenge.

My advice to anyone considering Azure is if they want to make jumping to the Azure or to the Cloud easier, they should focus on and discuss what the steps are. When you are on premise, figure out the development and how to configure it to the Azure. I have had so many marketing presentations from Microsoft saying, "Oh, it's easy. You have the Advisor. Blah, blah, blah." This is pure marketing. The clients know it is only a commercial about Azure. If Microsoft wants to really get customers, they should help them step by step by showing them how it is easy and how to control every step of the project. They should care more about the customers during this type of project. If you did 10 project delegations, the next one is much easier, but the first is really not so easy. That's why customers are afraid about migrating to the Azure. "What about the bills? What about how to administrate? How long to build the infrastructure?" There are a lot of questions from the customer side.

On a scale of one to ten, I would give Microsoft Azure a seven. That is because there is always space for improvement. For me it's okay. It's reliable and it really works.

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.

Azure cloud is a platform for many things, such as hosting, file services, application or power apps, and data lake. All these things are a part of Microsoft Azure. We're using it as a full suite. We are a big tenant with all solutions for Microsoft. We are using the latest version of Microsoft Azure.

The redundancy across different regions is the most valuable. It provides a big value for cloud services, especially for Microsoft.

The level of authorization or authorization cascading can be improved. We have the most powerful admins and then we have sub-admins, but the level of authorization is not that easy to handle or manage.

I have been using Microsoft Azure for three years. I am using this solution on a daily basis. It is the main platform that we have.

Its stability is good. It is very stable.

It is very easy to scale. We have more than 7,000 users. 

They are pretty sufficient. I would rate them an eight out of ten.

We also have different cloud vendors like Amazon and Salesforce, but they all are for different purposes, so it depends on the service.

The initial setup was simple. It was done in stages. 

We had the full support and dedication from Microsoft for its installation. Its maintenance is done by a vendor, and we also have some technical support from Microsoft when we are doing this stuff.

Microsoft always provides the entry-level solution with a cheap license. Once you start to like the product, then you have to pay for the full package, which is more expensive than the entry-level solution. Every feature comes with a license and a cost. Some licenses have multiple features, and some features require a specific license.

I would advise starting directly with Microsoft and then asking the vendors to recommend the trusted partners to work on the implementation or migration, and not vice versa. First, talk with the architect of the design and see if they can recommend a trusted partner who can do the implementation.

I would rate Microsoft Azure a nine out of ten. It is a big product and platform. It covers many things in terms of features.

We use the product for Exchange, Microsoft Intune, SharePoint, and OneDrive.

The solution is secure and easy to use. It meets the security guidelines. It is approved by the state and the shareholders. MFA is a good feature. The reporting features are also good. The management and the logging of incidents are good. It’s a good solution for our use cases. I don't have any negative opinions about it.

Sometimes, I need better support. Microsoft must acknowledge support cases for the product. There have been some data leak issues lately. The support team is not responding to my emails. I had a call with an engineer on a weekend, and he told me he would follow up on Monday, but he hasn’t shown up yet.

I have been using the solution for one and a half years.

The tool is 99.99% stable.

The tool is scalable. We have 50 to 100 employees. We're a startup, but we are growing.

Overall, the support team is good.

Neutral

The tool was easy to install. The maintenance is fairly easy. When I have issues, I contact Microsoft, and the team helps me.

The tool is cheap.

We are not allowed to store data in Azure. Our data is encrypted via third-party software. Overall, I rate the product a nine out of ten.

Microsoft Azure is our principal could environment.

We use Microsoft Azure for Hosting Apps, Sites, and Blogs.

Advantages of Azure over On-Premises: Improved Performance and Cost Benefits.

It is easy to deploy.

The technical support is good.

The price is good.

I would like to see Internet content filtering included.

I have been working with Microsoft Azure for two years.

I am working with the latest version.

I would rate the stability a ten out of ten.

I would rate the scalability a nine out of ten.

I have plans to increase my usage in the future.

Technical support is good.

I would rate them a ten out of ten.

The initial setup is straightforward.

It is easy to deploy.

We have seen a return on investment.

The pricing is reasonable.

I Conducted Evaluations of Google Cloud (GCP), Oracle Cloud (OCP), and Amazon Web Services (AWS).

We opted for Azure based on familiarity and expertise as a Microsoft-driven organization.

It's a good product and the correct choice.

I would rate Microsoft Azure a nine out of ten.

We use Microsoft Azure for many different services. For example, we use the Azure Boards for work and issue tracking. The Azure Repos is a place we store code, it is similar to a Git repository for us. Microsoft Azure has pipelines for the deployment of your applications across environments. There are different cloud services for different use cases in Microsoft Azure that I interact with on a daily basis.

Microsoft Azure has benefited our organization mostly because we moved all our infrastructure to the cloud. That has helped with cost optimization. We don't have to worry about operational maintenance for things such as patching or updates for any of the servers because everything is handled by the cloud itself. We are always using the latest version.

Microsoft Azure has hundred of services that they offer on the platform.

The Microsoft Azure platform in itself is very good. The documentation that is available I find very handy and the community behind it is helpful. If you have any problems or anything, you can easily reach Microsoft's community, and then there would be someone who would be willing to help. That's a very good plus point for Microsoft Azure.

There are times when using a service in Microsoft Azure can be confusing because you have four or five options that do similar operations. It would be helpful if there was a clear decision tree around those features. Microsoft does provide a lot of decision trees around a lot of their services, but it's not for everything.

This would be helpful for the users because sometimes it gets confusing what to use, what not to use. Then you start with something, and then after two months, you think you should have used something else. There are approximately 200 services and I have found this issue with approximately 10 of them.

I have been using Microsoft Azure for approximately seven years.

Microsoft Azure is stable, I did not encounter any issues or anything in the platform. The uptime is very good. 

When you design your solution, you can make sure that everything is accounted for in your design, such as all the options are there. Microsoft Azure in itself is rarely down. If there is a complete blackout it can happen, but normally no. It's very reliable.

The scalability of Microsoft Azure is unlimited. You never have to be concerned with scalability. You only have to pay for it and then the scaling is available for you.

I have approximately 50 to 100 people using this solution in my organization. I use the solution on a daily basis.

I have not needed to contact the technical to Microsoft in my current experience. In the past, I have contacted Microsoft once or twice, but the process is straightforward. You raise a ticket, and then Microsoft's people reach out to you.

The initial setup of Microsoft Azure is very straightforward. You don't have to do any setup. You only have to sign up on the Microsoft Portal, and then you can start using it.

I did the implementation of Microsoft Azure myself.

There is not any maintenance required for this solution. If we build any solution on top of Microsoft Azure, then that's something that we have to take care of and maintain. The Microsoft Azure platform in itself does not need any maintenance from us.

Microsoft Azure is not expensive. You pay for what you use. If you are using it everything could be expensive.

We choose Microsoft Azure after doing the proper comparisons and proof of concepts. We did a complete pros and cons list for our vendor selection process.

I would highly recommend Microsoft Azure to others.

I would advise others that one of the most important points to make is to make sure that the security and governance of the platform have been thought of before you start building everything around it. Make sure you build your security framework and the governance framework around the platform that suits your company. Every company is different. Everyone will have different security and governance rules.

I rate Microsoft Azure a nine out of ten.

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.