Microsoft Azure Reviews

Right now we're designing our desktop solutions. I need, for example, to use a virtual desktop and I need to use infrastructure as a service. I am looking for other infrastructure as a service solutions as well,

We really like the infrastructure as a service and the data center as a service solution functionality. 

The backup data center and the business compute solutions for Azure are good. There are a lot of good hybrid solutions with onsite and cloud solutions.

The solution is very easy to set up.

The solution is very stable for Windows setups.

The technical support on offer has been very good.

The pricing needs to be a bit lower. It's an expensive solution right now.

In future releases, I would like to see Microsoft offer personal desktop environments in a virtual solution. Citrix, for example, now offers this as an option.

I only have some limited experience with the product. I've only been using it for about six months or so. It hasn't been that long.

For the most part, the solution is stable. It's great with the Windows solution, however, with Linux and other operating systems, I hope that it's okay. I don't know for certain. I've never tried it with others. For Windows, it is very good. When the customer has all-Windows solutions everything is okay. There are no bugs or glitches and it doesn't crash or freeze.

The companies we usually sell to are typically medium-sized. When it comes to scaling, the cloud solution is an elastic solution. I can scale it well. The customer can go up however high they want to go. The solution allows for that flexibility. It's easy to expand with the solution.

I've reached out to technical support in the past. I understand that if I need them I can easily reach them. They are available and responsive. I'd say we are satisfied with our solution.

The initial setup is not difficult or complex. It's pretty straightforward. It's easy. A company shouldn't have any issue with the process.

We sell the solution to our clients and it takes six months to one year to deploy it.

We would like to see Microsoft lower its prices a bit for their customers. It's a costly solution.

I'm a Microsoft reseller.

I'm not sure which version of the solution we're using.

While we are currently using the on-premises deployment model, we are considering moving to the cloud.

I'd recommend the solution to other users and organizations. I'm already recommending it to various clients as a potential solution for them.

I'd rate the solution at a nine out of ten. We're quite satisfied with the solution.

I'm currently trying to build a new product for my company using Microsoft Azure. Prior to that, I was using Microsoft Azure on the cloud to deploy microservices using specific Azure services to host the microservices. But the most common Azure services that we're using is the App Service and relational databases. In terms of the application, the first one was just the Microsoft Azure application and the second one was an integration with Elastic Stack. I'm a software architect.

The user interface offers a good experience, it's better than Azure itself. The portal is great. Microsoft Azure has very good documentation for any kind of technical person.

Sometimes the Azure Calculator doesn't have a good way to do a higher estimate, because for any organization there are sometimes issues with the application sites, but I know that the logs are not the real time and there are issues with login synchronization. It cam sometimes take more than five minutes for that information to reach the Azure application side. I'd like to see integration with other lifecycle managing rules because with Azure DevOps, it's straightforward, but the system is painful sometimes. 

I've been using this solution for nearly five years, the last 12 months in this new company. 

In general, stability is good, but in the past month I had some issues with the connection to Azure resources, not just Microsoft Azure, but with Azure in general. Microsoft has an issue with its authentication system which has proved painful, because my applications were up and running, but I can't log in to make changes or see metrics. It's a lot better now, we've had the application down three or four times but it hasn't been critical. 

Scalability is good, I haven't had any issues with their configuration. I think we have around 600 concurrent users. 

I haven't used Azure support. They have good documentation, although I sometimes think that the examples on GitHub aren't updated. On the whole, documentation is good. 

We previously used AWS but we knew there was already a lot of experience with Microsoft Azure and their technologies and we wanted to use all the features for each service. Given that this is with government and the integration is with Microsoft Azure, we can use all the features and benefits of each service. Another issue is that they were using AWS with infrastructure as a service, but they redesigned this application to use software as a service and platform as a service. We dropped the use of infrastructure as a service and using the platform as a service, and it was estimated that it would cost less than with AWS.

I think the initial setup is straightforward. I have around 20 microservices, so deployment took probably two weeks. It took longer than a previous implementation which took several hours.

We did a quick check with cloud computing, but we didn't find anything really efficient outside of the Google Kubernetes Engine that was better than the Azure Kubernetes Service or the Kubernetes service in AWS. But it was just a quick check and it was documented.

I can sometimes see that Microsoft has poor training, but to be honest the whole training thing isn't good at a technical level. They are designed to be the entrance point and show the way you can create a web portal and database. But if they could offer an in-depth technical solution of Azure services that would be good. It's possible that Google has something about it and they can offer better learning than Microsoft sometimes does. Reading through their documentation can take some time. 

I rate this solution a nine out of 10. 

It's primarily used for access to the cloud or the virtual machines and to have a cloud-based solution that can handle tasks such as data processing, or for having data storage, and all types of other things.

The product is very flexible.

The performance overall is great.

It's a great advantage for a company to be on the cloud. It gives a company nice advantages.

The solution has proven to be quite stable so far.

The solution has been scalable.

There are no new releases per se; the solution simply adds on more services over time. 

The solution needs to offer more data analysis services. It would be extremely helpful to Azure's clients if they had more of this.

I've been using the solution for about a year or so. I believe it's been around 12 months. It hasn't been that long.

The stability of the solution has been very good. There are no bugs or glitches. It doesn't crash or freeze. It's reliable.

So far, we've found the scalability to be pretty good. If a company needs to expand, it can do so with ease.

We have about five people working directly on the solution currently.

We haven't really dealt with technical support. I can't speak to how helpful or responsive they are. I've never had any direct interactions with them personally.

There isn't really an initial setup. It's on the cloud. You don't really have to deploy anything or set anything up.

Our customers don't have to pay any licensing fees in order to use Azure.

As we are on the cloud deployment model, we're always on the latest version of the solution. It is always automatically updated for us.

Overall, I'd rate the solution at an eight out of ten. We've been pretty happy with its capabilities so far.

In general, I would recommend the solution to other organizations.

We use Microsoft Azure for blob storage and for a lot of the components that they have inside the cloud.

The integration with Databricks is the most valuable aspect of the solution. It's easy to use and to put on the pipeline. Data Factory and Databricks together build a pipeline. They really integrate very well.

The stability is very good.

The solution is comparable to AWS in terms of pricing.

The design of the platform is not so easy to navigate. It's not very user-friendly.

Some services are more difficult to use in AWS and GCP. I have projects on the three clouds, and some things are easier to do on AWS. On the other hand, using Databricks on Azure is easy, as they are integrated well. However, some products are more difficult to use than other products. 

The stability has been good. There are no bugs or glitches. It doesn't crash or freeze. It's reliable in terms of performance.

We have about 30 people using the solution.

I don't really deal with technical support. I'm the data scientist manager. The engineering team would be the ones that would reach out for help if they needed support.

In terms of deployment, each product requires a number of staff to deploy the model of machine learning or to build the stature to consume the data. It really depends.

I don't handle the licensing or payments aspect of the solution. I can't speak to the costs involved or what the license looks like. 

In AWS, our monthly cost was something around $10,000 or something close to that. We had to pay around $120,000 a year. It's most likely something close to that.

We are a customer and end-user. We don't have a business relationship with Microsoft.

We deployed the solution in multiple ways. We've used the solution both on-premises and on the cloud.

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

We are customers of Microsoft and I'm an IT architect.

The solution reduces work for our IT teams. They don't have to keep things up to date, and we can concentrate on our mission. The best feature for us is the help we get from Microsoft to migrate applications to the latest release and support efforts. It saves us a lot of time. 

The cost is a big issue, it can quickly go up if you don't control things. We've set up a system that shuts down machines regularly so we don't run up costs. Sometimes our development teams start up machines and forget to shut them down, and we see our costs go up quite rapidly with monthly surcharges. It would be helpful if Microsoft didn't change the control panels quite so often. It means we need to retrain personnel whenever things change and that seems to have an impact on our IT teams.

We've been using this solution for nearly four years. 

Stability is good and the solution is easy to maintain. 

Scalability is really awesome. We don't have to worry about it at all, we're really impressed. Everyone in the company uses Azure. 

Tech support is great. I find that we get answers quickly. It's just the first line of support that I criticize sometimes because it seems that whenever we open a ticket, they give us a run around with certain questions that basically we've answered. But as soon as we get into the next level of support, it's more advanced and questions are answered quite rapidly. Our tech guys know how to open a ticket and basically provide all the available information that they need. We sometimes have to get through that initial loop, and answer the same questions again and again, until they push us to another level of support.

Four years ago the initial setup was quite complex but lately I find it's becoming increasingly easier, and the set up rules for securities are a lot simpler. These are things that are improving all the time. 

Licensing is on an annual basis. 

If a company wants to concentrate more on their mission and less on supporting infrastructure, they should give Azure a go. I find that it saves us a lot of time.

I would rate this solution an eight out of 10. 

We primarily use Azure for Office 365.

My experience with technical support so far is very good.

If the price were reduced then it would be an improvement.

I have been using Microsoft Azure for one year.

For me and many other people, the general view is that Azure is very stable. We definitely plan to continue using it in the future.

This is a scalable solution and we have thousands of users in our organization.

I have had to contact Microsoft support about a problem that I was having with my virtual machine, where it could not find my VM. When I called them, they solved the problem quite fast.

Prior to Azure, we used all of our Microsoft products on-premises.

The initial setup was easy because we didn't do anything.

We hired an IT consultant who is experienced in setting up cloud solutions. We did not do any of the setup ourselves.

The licensing fees depend on the number of users that we have.

Overall, this product is very good and I can recommend it. It would be difficult to improve.

I would rate this solution a nine out of ten.

Working Azure Kubernetes Service (AKS) to create a Kubernetes cluster. 

We are maintaining two environments of Kubernetes cluster on Azure using Azure Kubernetes Service (AKS).

We have used other managed PaaS services like ACS, Database, and monitoring, integrated with Jenkins for continuous integration and continuous deployment. 

We are running our product which is deployed on Azure AKS cluster. This really helps us to drive more business from customers.

• It's very easy to create a Kubernetes cluster with the Azure Console 
• Able to connect to the cluster using Azure PowerShell
• Able to connect to the cluster using kubectl
• Very good help from Microsoft Knowledge Base and also from the community
• Very good support from the Microsoft team
• Easy to manage as the core part is handled by Microsoft
• Easy to add/scale up the cluster with more nodes by using the Azure console window or through scripting
• Can integrate plugins with Jenkins for auto deployment
• Integrated with a lot of open source tools for easy deployments and other functionalities like logging, monitoring, etc.

Better logging part when deployments are crashed, even when the entire cluster is crashed.

Should always go with recommendations provided by Microsoft during the creation of new clusters. Otherwise, stability is an issue.

Scalability is very good.

Technical support is excellent. Recently, we have encountered a few issues however, the customer support team helped us very quickly to come out of it.

We did not previously use a different solution. Kubernetes is the one we are using for container orchestration through Azure-managed Kubernetes service.

The initial setup is very easy; straightforward.