Microsoft Azure Reviews

We use the email accounts and SharePoint. We want to use the AI and OCR services, but we do not have many use cases.

I get all the features under one roof.

The subscriptions are complicated. The process is not user-friendly.

I have been using the solution for almost one year.

The tool’s stability is good.

The tool is scalable. Around 30 people use the solution in our organization. We are trying to get projects from Europe and North America. Once we get more projects, we will be scaling up.

The initial setup is straightforward. It took me around one week to set up the product. I did the deployment myself since I am into IT.

The return on investment is good because everything is in the cloud. We save a lot on infrastructure costs and server costs.

I pay a yearly subscription fee for the solution. The pricing is normal compared to other service providers. I can increase or decrease my subscription based on my organization's needs.

We are into data management. We do a lot of data consumption and data validation. We need a lot of virtual solutions and storage solutions to process data. I would recommend the solution to others. Overall, I rate the tool a nine out of ten.

We use the solution for hosting business applications and the test environment.

The compliance is really good. It provides visibility of our top risks and recommendations on how to close them. Sentinel is really good from a security standpoint. The product provides a host of security tools. We deploy and configure everything ourselves. So far, we have not had any issues related to Azure.

The solution must improve its pricing.

I have been using the solution for a couple of years.

I rate the stability of the tool a nine and a half out of ten.

The tool is highly scalable, depending on the design. I've not had any issues. We have to factor in cost and design. About 2000 people use the solution in our organization. It is extensively used in our organization. Based on business growth, we might increase the number of users.

We had some technical issues. The support team was ready to support us once we raised a ticket. They responded in a reasonable time and escalated the issue when necessary.

The initial setup is pretty straightforward. The information is readily available, and there are many local partners who are extremely supportive. Deployment is just a matter of getting the login set up. It was pretty fast.

Our in-house team had been trained to deploy the tool, so they knew what to do. We have a few trained cloud admins who can manage the product. There are a lot of automation options, so they don't need a big crowd to work with it.

The product has a good ROI. It depends on how we handle the cost based on resource creation and the data we build based on our setup.

We have a licensing option from our partner in which the solution is bundled up with a whole host of other services. There are no additional costs associated with the product.

It is one of the best tools in the market. It's a very good cloud service. It has a lot of good security options. The reporting options are also good. The on-premise AD is fantastic. The tool gives us flexibility in deployment. If we get the design wrong, that's not Azure’s problem. It's our problem. Overall, I rate the solution a nine out of ten.

We use Microsoft Azure for database service and advanced analytics.

We have a process where we collect a large amount of data from different sources. By using a database, we can analyze and present it in business intelligence (BI). Oh, here's another example. Some months ago, we started using Power BI embedded, which helped optimize the number of licenses for our company. Additionally, with this development, we improved the centralization of tables. 

I believe the personalization model and the cost optimization are the most valuable features. With the model, you pay for what you use. For instance, in this development, we utilized Power BI embedded and deployed the entire web page using Azure resources. By leveraging Azure, we can easily control and adjust the platform as needed, resulting in cost optimization.

For additional features, I believe our team is interested in exploring SmartOps on Azure.

We are also exploring the power platform and have a keen interest in leveraging premium features. It would be beneficial if Microsoft could enhance the free version to allow for more exploration and development. That's my only suggestion regarding Azure.

I have been using this solution for over a year. 

I would rate it a five out of ten.

I would rate the scalability of Azure an eight out of ten. 

We had some issues with Microsoft's support team. In a project where we had to scale with Azure, it involved multiple people and sessions, and it took several weeks to resolve the issue. It was very difficult to get a resolution.

Negative

The initial setup was easy. It's a good platform for deployment.

There is a return on investment. It's worth considering.

I'm currently comparing it with AWS, and we don't have full knowledge of all the features and their inclusion in the price. AWS seems to have a slight advantage in terms of price. So, Microsoft Azure is slightly expensive.

I would recommend the suite. In our company, we use the Microsoft suite, which includes Outlook, SharePoint, and OneDrive. I believe that Microsoft offers a very good product.

Overall, I would rate the solution an eight 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.

Our primary use case for Azure is for workload, database, and service migrations. I use Azure to migrate services to serverless Azure services. Some of the services I utilize within Azure are Azure SQL database, managed database, Cosmos, virtual machines, service accounts, and infrastructure as a code for migration.

I'd like to see improvements with the price calculator tool. I would like to get a forward-looking view of the services I want to cost. For example, if I want a bigger machine with two CPU's and eight gigabytes of RAM, maybe the calculator can allow me to input my recipe, the tool can then give me a list of virtual machines that have that specification, and it will be easier for me to choose the virtual machine I want. 

There are no additional features at this time I can suggest for future releases.

I have worked with Microsoft Azure for 7 years.

Microsoft Azure is very stable, it has a SLA of 99.9%.

The Azure services are very scalable.

Microsoft have varying types of support levels. Depending on what level of support you have , this determines the response time from them.

We implement in-house.

All services in the cloud are easy to set up, the services are ready to use from the outset. For example, it would take me 5 minutes to deploy one virtual machine in Azure, or a Sharepoint cluster may take me 4 hours. The cloud deployments are normally automatic once you start.

Regarding licensing, always look to optimize costs with the use of Azure Advisor.

We use Microsoft Azure and AWS, depending on what the client wants. Some clients like to compare prices between the two, it depends on the workload that my client would like to migrate also.

Microsoft Azure is for customers who want to move to cloud-based solutions, take advantage of licensing e.g. hardware or software licensing benefits, and other cloud-related benefits, e.g. Azure container benefits, making their applications more scalable, etc.

This solution shows good performance. There were learning hiccups initially, but now it's okay.

More integration with other platforms is what I would like included in the next release for this solution.

We've been implementing Microsoft Azure for our customers for four years.

Microsoft Azure is a stable solution.

I found Microsoft Azure to be scalable.

We don't directly interact with technical support because the licenses are bought by our customers, so it's our customers who interact with them, but we didn't see any major issues with Microsoft Azure, on the ground.

As Microsoft Azure is a cloud-based solution, installation was easy.

Our team implemented this solution. The technical team, particularly those with knowledge about Microsoft Azure should be able to implement it well. We used our engineers to implement it.

We've been using different Microsoft solutions. Microsoft has solutions. It starts from Azure data sending, data storage, and other Azure related solutions. other Microsoft solutions that everybody uses include Office, Outlook, C#, .Net, etc., from the technical side.

It is our customers who use Microsoft Azure. They wanted to move to Microsoft Azure, so we moved them. We just maintain it for them, and also do the development and the support for their applications.

For people who want to start using this solution, if they are currently using the Microsoft Stack on-premises, moving to Microsoft Azure will be good.

'm giving Microsoft Azure a score of eight out of ten.

We use Azure for a variety of services and we are in the process of configuring everything. We use GoDaddy to host our domain, and then we provision from GoDaddy for services such as email. This is one of the things that I just recently configured.

Right now, we're in the process of setting up the firewall. This provides us with security for the website. Firewalls are something that I have a lot of experience with because, in my previous organization, I dealt with audits and other similar tasks that depend on security.

The most valuable feature of Azure is the flexibility to pick and choose what you need, on the spot, and then be able to manage it yourself.

In Azure, everything is pretty straightforward. Once you know it, the platform is very easy to use.

The training material that they have is very good, and it's easy to understand.

Most of the problems that we've had are related to the DNS and the SSL certificate. Those two things have been a real pain. Sometimes, it happens because of GoDaddy and sometimes it happens because of Azure. Either we make a change in GoDaddy and the configuration is lost, or our developers make a change to the website and from there it gets lost.

It would be helpful if Azure provided more information on the various add-ons to give people an understanding of what they are used for, and how they're applied by other companies or businesses. One downside is that I find myself signing up and paying for things that I don't really need, and I have to call them to find out exactly what it is that I'm paying for. For example, I recently added the Azure Data Studio and I don't know what I need it for. I see that it can create a connection and run a query but I don't know if I'm going to be using it. That said, I will probably need it in the future.

My current organization has been using Microsoft Azure for the past two months. I have extensive past experience with it.

Stability-wise, it has been fine.

Azure is a scalable platform.

I have not been in contact with technical support myself. In fact, we have not had to reach out to them very often. We generally figure out things on our own but we also have an IT contract with personnel to work to resolve issues when they occur. Technical issues are something that you always want to try to resolve yourself.

Although we haven't had any problems that we couldn't resolve, we know that if we have to call technical support then we're going to be on hold for a while. This is something we don't want and can avoid by having our own IT support contract.

In my previous job, I worked for large telecom and we used a variety of products. These included AWS, as well as Azure, and we also had our own cloud that we leased to third parties.

I received training and certification on both Azure and AWS. However, I did not have much opportunity to use AWS.

In my current company, we migrated the business from AWS to Azure within the last two months.

The initial setup for me was easy because I have experience with Azure, as well as AWS, and a private cloud in my previous organization. I was in the internal network group, and I had all of the operational responsibilities for that area.

We were able to set it up and get it working in a day.

Migrating to Azure from AWS was not a big deal.

The price of this solution is one of the things that attracted us to it.

We considered both Azure and AWS for my current company. When we began, the company already had an existing website running with AWS, but I had more experience with Azure. We did extensive research to compare the two and we found that Azure was definitely the way to go.

We were already using several other Microsoft products, which means that our environment is more compatible using Azure.

My advice for anybody who is implementing Azure is to look at the training materials that they have available. They are very easy to understand and I recommend running through the ones that pertain to your use cases. A lot of the time, it will have the additional information that is needed to understand the problem and help you to find the relevant information in other sources. For example, it contained information about GoDaddy that was relevant to our environment.

The biggest thing is that the information is all there and a lot of people don't like to look, but I suggest using the help and the instructional videos before calling somebody else. Everything is available.

I would rate this solution a nine out of ten.