Microsoft Azure Reviews

We use this solution for IaaS, SaaS, PaaS security, identity, and Kubernetes.

I like everything, overall.

It's a cloud platform so it's alive.

There are many different components such as SaaS, PaaS, and API, so every month they are releasing a few hundred new features.

It is constantly updating. There are weekly releases, sometimes daily releases, and there should be fewer that are consolidated into one.

I have been using Microsoft Azure for six years.

We are using the latest version.

The stability is very good.

It's a very scalable solution. It is not really the number of users we have, but rather, it is more a case of service PCs. We have 70,000 or more.

My experience with technical support has been good. They are very supportive.

It's as complex as it wants to be. There's nothing initial about it.

It's an OPEX model, you pay as you go, or you can reserve funds.

Pricing can always be better.

It's a good product and I recommend it to others.

I would rate it a nine out of ten.

The availability of the humongous amount of features and solutions in Azure are most valuable to us.

The continuous improvement of Microsoft is amazing. The agility and speed at which Microsoft is doing all this is really amazing.

The improvements are more on the partner's part than on the product's part. It is difficult to keep up with the continuous improvements that Microsoft is doing.

Issues were seen in the size and unclear configuration settings. If the bandwidth is limited, it can be an issue when migrating from on-prem to off-prem.

We have implemented this for our customers since the very beginning.

This depends on the support contract which you subscribe to. The free support is bad, but the paid versions have better support, i.e., more you pay, the better the support.

The other solutions that we had used before were on-premise solutions. We saw a major shift of the resources towards Microsoft Azure.

The setup was straightforward; with the help of TechNet, if there were any issues then they were easily solvable.

In regards to the pricing and licensing, you need to be aware of what to do. If it fits in your current licensing contract, add it to that contract. If not, then depending on the company's size, ask the reseller with whom you are doing business (or ask me) for advice on this issue.

We did evaluate other solutions and, in some cases, we also advised for this product, as it is specific to certain workloads. AWS and Google are the other vendors that we looked at.

Have a vendor agnostic partner to look at your environment and discuss the vision you have on this.

Scalability, affordability and the flexibility of the product.

• You can off-site required services to help mitigate risk
• You can take advantage of the scalability to have short term high intensive processes be used by their services
• You can totally take away the need for any server hardware in your organisation

Probably the 2 main areas where things could be improved are getting direct console access to VM's and its Azure backup solution to add backup types (eg System State).

3 months

We went with the volume license of credits and still find it difficult to activate those credits as there is a particular website you have to go to.

There has been documented issues with stability, however we did not experience it.

No issues encountered.

Good, I can shoot email questions and get responses in a good amount of time.

I haven't had to raise a technical support for Azure though for Office 365 I have and I've found it excellent.

We looked at AWS, a locally based cloud provider and a datacentre.

It was a learning curve to get it up and running. If I had prior training I would have found it straight forward but the time lines for implementation meant I had to "dive in".

In-house

We are able to provide services to clients that allows us get a good ROI once we have deployed Azure to them.

• Setup cost with Azure is minimal for what they are supplying. Everything takes less than 10 minutes to deploy.
• Day to Day costs is what you use, we can now review those costs and look at the new features (Automation) to make those costs even more efficient.

We looked at AWS, a locally based cloud provider and a datacentre.

Get onboard with Microsoft and the Azure team and listen out to their partner training. They did a big Azure for IT Pros via their channel 9 msdn a few weeks ago. There is plenty of webinars and e-books which will teach you what you want to know.

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.

Azure is a big world with potential things that we have to check and learn. We have Azure as the data analytics, artificial intelligence, and much more. I work with technology like Microsoft, Symantec, and with Azure connectivity online, like SaaS.

We are integrators for AWS and Azure.

I don't know the exact number of users because we work with different customers. So one customer is only servicing one, another customer has probably 300, another customer has probably 500. We have different customers with a different number of users that use this technology.

With the Azure solution, you can get more value from your cloud investment no matter what your future goals are. It depends on your level of familiarity with the cloud you are using or with your computing. Azure helps you with every stage of the cloud. When you start using Azure, you don't even buy it. It's just a simple sign-in and a free account, and you get free services. It's a great way to get into that kind of technology. That's why I've been using this solution for almost eight years.

They have a feature from the network, the communication, so the firewall is the most communication that we can find when we try to work with the Azure platform. Perhaps it's our environment, and that not all the customers are familiar with how to work with cloud technologies. For that reason, it's the most communication that we can find. I am in the Azure service sales, and that is one of the features that can help you to stay informed and take any action in the area that you found a thing generated for.

It has a personalized dashboard for service issues. You can check the Azure service help, and you can find any issue that you have in your platform. It's a safe point to check when you have an issue, so you can manage the issue and learn how to track that issue, and you can more effectively execute plans that you have to scale or that you have to put in action using Azure bots.

They have free coursework that you can check on the website, and a free update that you can find for SQL server security. We are more familiar with Azure, so maybe we have to wait a couple of years to get more familiar with AWS.

Something that could be added to the solution is the use of deep learning, which is going to grow in the near future.

We are waiting for a new version, a new RFID for Azure Virtual Desktop AD 1, or Virtual Live Desktop AD 1. It really needs a whole new platform, because I think their platform has the best opportunity to offer features like HORIZONT.

I have been using this solution for eight years.

I would rate this solution 8 out of 10.

My advice is to just read and keep in touch. The technology is something that I have to read about every day, keep in touch with, study, take courses, and take certifications. So, currently, the best advice I can give to anyone is to keep updated.

Every time you check online you can find a new feature from Azure. The world of Azure is so big, so there is plenty of information that you can find, check, and test.

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.

I was testing the integration capabilities. I deployed a simple solution with a front and back end with an SQL database. For the server-less solution, it was just to interact with the database. That's what kind of the load that I was testing. The use case was to integrate with the directory, authenticate, and then consume some of the services there.

One of the services that I found to be great is the connector. For example, the other day, I was creating an application for internal research. With that connector, it was really easy to integrate some services to interact with the connectors. The credential allows you to authenticate with the active directory. Then, with that authentication, you can have the assurance that the people who are consuming the application are the right ones.

I know there have been a lot of improvements and a lot of new services lately. I'm really not aware of all of them.

One thing which is great is that they give users hub integration. That's a strong aspect, which would be good for many people and clients and developers so that they have that integration right away.

I haven't checked the console for some time, however, compared to the AWS console, the interaction console of the web part, the web services, it's not so easy. That will be a good area to improve, which is to make the console for interaction with services a little easier.

Another point to improve could maybe be the pricing model or maybe the interaction with information. When you look for information in AWS, it's more straightforward and clear. It's hard to find that information on Azure.

I used the solution for maybe one month at the beginning of maybe March of this year. I was doing some tests with Microsoft Azure. I was deploying some services.

The stability is good. There are no bugs or glitches. It doesn't crash or freeze. It's reliable. 

The scalability is fine. However, it may be another thing to improve. I haven't look looked at it in some time, however, I remember at the beginning, I tried to research for the price, for rates, and things. I didn't find it easy to locate, which made it hard to gauge the cost of scaling. 

From my side, I don't plan to increase usage. Right now, I'm working for other clients, and with the solutions of the clients. For research purposes, I will do maybe one or two instances, just for testing. It's not a big deal.

While I've never needed technical assistance, my understanding is that it's pretty good.

It was not very difficult to set up the solution. In the beginning, it's a bit difficult to just find the services and things like that. They need a kind of list or something, something more visible. That would help. 

Our implementation was not too big. It took maybe two days. Another deployment we did took maybe three. I'm not really a complete expert. It might have taken a bit longer for me due to my lack of experience.

I did not use consultants or resellers for deployment. I did it myself. There wasn't too much pressure. I was doing the deployment more for research purposes. 

The price of the solution is unclear. it's hard to find the costs. 

The company I am working for is a Microsoft partner.

I'd advise potential new users to try to get as much information as possible about licensing and about the products that they are going to use. That will be good to have a very clear understanding of. Beyond that, it's not a problem to get started and go.

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