Microsoft Azure Reviews

We use the solution to manage and secure my users' email for the Active Directory.

The solution’s initial setup is a bit complex.

I have been using Microsoft Azure for seven months.

I rate the solution’s stability an eight out of ten.

Only two users are currently using the solution.

I rate the solution’s scalability an eight out of ten.

We pay a monthly licensing fee for the solution, which could be cheaper.

We are currently evaluating how to maximize the use of services to back up our database. Microsoft Azure is a cloud-based solution. I would recommend Microsoft Azure to other users because it has many services that will benefit companies.

Overall, I rate the solution a seven out of ten.

We use the solution as part of the scrum agile methodology. 

We use Azure DevOps' full hierarchy to manage our data workloads. From product management to development and QA stages, Azure DevOps provides tools. Additionally, we're implementing automation testing and integrating it with our CI/CD pipelines using Azure DevOps. This platform helps us manage all our processes. 

The main advantage of using it is that it supports a smooth workflow from development to QA, following the Scrum Agile methodology. It manages the sequence of tasks and sprints. The tool's integration capabilities are good. 

Microsoft Azure needs to improve its customization capabilities. Each organization has unique tasks and fields that it wants to use. Additionally, the search functionality could be more flexible. 

I have been working with the product for five years. 

I rate the product's stability an eight out of ten. 

I rate the solution's scalability a seven out of ten. 

I haven't contacted technical support yet. 

I rate Microsoft Azure's deployment ease as five out of ten. It takes around a month and a half to complete, while our sprints take two weeks. Moreover, we conduct three rounds of testing and development. 

The product is expensive. 

I rate the overall solution an eight out of ten. 

We had a cloud migration project from on-premise to the cloud. We used various components like Azure’s cost calculator to provide the ongoing running costs.

SQL Server has been most beneficial for our client’s workload.

Everything needs improvement. The tool must constantly improve to provide a better experience. The security must be improved. The scalability could also be improved.

I have been using the solution for five years.

I rate the tool’s stability an eight out of ten.

I rate the tool’s scalability a nine out of ten. Our clients are medium to large businesses.

I rate the ease of setup a five out of ten. The product is deployed on the cloud. The deployment took a few hours.

I rate the pricing an eight out of ten. All cloud services are expensive.

I rate the solution’s ability to support our client’s business growth a seven out of ten. We don't get direct support from Microsoft. I rate Azure's integration capabilities a seven out of ten. I will recommend the tool to others. Overall, I rate the product a nine out of ten.

The solution has high stability.

We have reported some bugs we encountered, and it would be good if those bugs were resolved more quickly.

I have been using Microsoft Azure for more than one year.

I rate the solution a nine out of ten for stability.

Currently, we are happy with how the solution scales. Around 60 users use the solution in our organization on a daily basis.

I rate the solution an eight out of ten for scalability.

The solution's initial setup was quite easy, and you can get support to help you with the installation.

On a scale from one to ten, where one is cheap and ten is expensive, I rate the solution's pricing an eight out of ten.

We use management tools for APIs. A few people were involved in the solution’s deployment and maintenance. I would recommend the solution to other users.

Overall, I rate Microsoft Azure a nine out of ten.

We use Microsoft Azure for migration purposes.

The portal makes it easier to work with the solution.

The solution's initial setup was a bit complex in the beginning. We had to go through a major learning curve before we got hands-on familiarity with it.

I have been using Microsoft Azure for one year.

I rate Microsoft Azure a seven out of ten for stability.

Microsoft Azure is a scalable solution. Less than 20 users in our organization use Microsoft Azure.

I rate Microsoft Azure an eight out of ten for scalability.

I rate Microsoft Azure a five to six out of ten for the ease of its initial setup.

The solution's deployment time depends purely on the size of the application. On average, the solution's deployment would take us anywhere from two weeks and longer. Depending on our testing, it would take us about a month to design and deploy the solution.

Microsoft Azure is deployed on the cloud.

I would recommend Microsoft Azure to other users, but they should have a strong system integrator or someone working with Microsoft to assist. The strength would lie with the organization deploying the solution; they have to be on par to understand better what is happening.

Overall, I rate Microsoft Azure a seven out of ten.

We use Microsoft Azure in two places. The first use case involves the Chatbot framework, and we've been using that for 18 months. This is what we predominately use it for.

Our second use involves hosting some of our critical applications. It allows us to address some of our human resource use cases in the area of policy queries, as well as some backend actions.

The automated connectors to some of our critical enterprise systems are an important feature. These are very large, critical, global HCM systems.

The library of predefined use cases is very helpful and we found the HR use case that we needed within it.

There are improvements needed from a roadmap standpoint. Some of the roadmap items that they typically publish don't move at the same pace.

The predominant area in need of improvement is support.

Microsoft needs to continue working on out-of-the-box connectors to contemporary products in the market, specific to different verticals such as finance and HR. Investing in this would be helpful because it means deploying solutions faster. We've had challenges in terms of having to custom-build some of it and at the same time, the roadmap contains more connectors.

We have been using Microsoft Azure for the past 18 months.

This is definitely a stable platform. I haven't seen issues in that respect.

Azure is a scalable platform. We have more than 10,000 people in the organization that use it from an application standpoint. The end-users could be managers or other employees in a variety of roles.

Our in-house administration team has fewer than 40 people that work with it.

At the moment, we have no plans to increase our usage.

The primary support needs to be improved. I would rate them as moderate because from a technical and service guarantee perspective, they are pretty good. However, when it comes to new roadmap items or handling requests, or adding new activities, they are moderate.

This is the first such solution that we put into place.

The initial setup is pretty much straightforward.

Our initial deployment took between six and eight weeks. This period had more to do with our setup being compliant with some of the features on Azure. 

We worked with the Microsoft consulting team during the deployment.

The team was knowledgeable but there were some areas that they could have done better. For example, we had issues with our enrollment and some of our IT requirements at the organizational level. We could have perhaps used some architecting skills.

For permanent maintenance, so we have a hybrid model when it comes to maintenance. We've outsourced some of it, and that really comes from a fixed contract so we don't control the number of people that work on it.

Internally, we have two people; one who manages the services, and the other one is more of an administrator.

My advice for anybody who is implementing Microsoft Azure is to first, very clearly agree on the terms of deployment. Second, get the initial design and prototypes for your specific implementation vetted and signed off at an early stage because this will help with security clearances and data privacy clearances. These were the two major learning points for us.

In summary, this is a good platform but there are several areas for improvement.

I would rate this solution a seven out of ten.

The solution does not have a specific version. We are talking more about a resource group. Whichever is the latest version is the one we use. 

The solution is used across the industry. Currently, I am working on something involving the education industry. My previous assignment focused more on clinical trials or medical data. These are two of the most recent and largest projects I have undertaken. 

The solution has given us more agility, scalability and opportunity to optimize the cost.

The solution should have better interface capabilities. 

There should be be better support for microservices and containers.

I have been using Microsoft Azure since 2010. I have used it within the past 12 months. 

The solution is stable. 

The solution gives our organization scalability. 

We have plans to increase its usage. 

Microsoft Azure's technical support is good.

We did not use another solution prior to Microsoft Azure. 

The initial setup is straightforward.

The deployment does not take long. In fact, the deployment time is not really applicable. When it comes to Azure, we are talking more about a platform than a proper product. I'm more into migration. 

In our case, it is we who are the consultants. As such, we are mostly into deployment at the moment and not maintenance. There are other providers who handle the latter. 

I am not in a position to comment on whether we have seen a return on our investment.

The licensing is pay per usage, so it can be both monthly and yearly. It supports all.

There are no additional costs beyond the standard licensing fees. There are various licensing programs, so the customer may choose the one which aligns with his needs. 

The solution provides platform as a service and infrastructure service, both of which are good.

Since Microsoft Azure supports close to 200 or 300 products, we are not talking about a single product or solution and this makes it difficult for me to provide advice. Being a platform, there may be thousands of users who are making use of it. However, in my organization, we are talking about nearly 200. 

I don't have specific advice to give. This product lends good support when it comes to Microsoft tech. If the organization is a part of the overall Microsoft ecosystem, employing things such as O365 or M365, then Microsoft Azure does a better job than the competition. 

I rate Microsoft Azure as a nine out of ten. 

We are customers of Microsoft and I'm the IT technical manager. 

The most valuable feature for me is the high level of availability and the 99% uptime of the system. I also appreciate the technical simplicity of the system in terms of implementation.

I'm currently based in the Philippines and the availability of services locally could be improved. Technically speaking, I'd like to see more flexibility in terms of storage or resource allocation. Resourcing is currently quite fixed so that if you want to move between level two and level three resources, or customize resources, you can't do that. The discrepancy in terms of costing is around $200. If they improved flexibility for selecting resources it would be easier for us to get the costing approved.

I've been using this solution for around two years. 

The solution is stable, one of the most reliable in the Philippines. The downside is that currently all the services are outside the country. Singapore and Hong Kong provide the closest service but we have laws that prohibit certain amounts of data residing in other countries. None of that affects stability. 

One of the key takes from using cloud services is scalability and flexibility. If a company hits some roadblocks financially, they can reduce infrastructure and also reduce what they use in the cloud lowering the cost. 

I've had several outages or major issues and I've had good experience with technical support. They resolved the problems in less than a day. The only downside is that in the Philippines you're dealing with the vendor and not Microsoft direct. I have two steps of support; if the vendor can't provide the support, then they escalate to Microsoft. 

The initial setup is quite simple. We currently have 20 users on the infrastructure side in addition to 20+ developers.

We have difficulty in getting the costing approved. We pay for a virtual machine and the resources currently implemented there, then we need a license from Microsoft Windows OS and the database itself. In our latest license purchase, the manager approved a monthly fee of around $2,000 for the resources we use. If you're going to the cloud, that's currently included in the cost and will be less if you have the software assurance from Microsoft; on-prem is more expensive.

The big takeaway on this product is the high availability of the system on cloud and reduction of on-prem costing. There are no concerns about the electrical doing some redundancy in between, cooling, purchasing, procurement of IT equipment. Instead of budgeting based on CAPEX, we're doing it from an OPEX point of view. One of the key takes for moving to the cloud is the cost. You can leverage with the cloud and let go of some things required to maintain a system on-prem, the kinds of things that alleviate some complexity in doing maintenance of the system. The solution is suitable for any size company. 

I highly recommend Microsoft Azure. Everyone knows Microsoft so the learning curve is easier. I rate the solution nine out of 10.