Microsoft Azure Reviews

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.

I'm the technical manager of our company and we are customers of Microsoft. 

We're able to provide our customers with what they want and very quickly.

This solution is quick, fluent and elastic. It's very easy to build a new service and get it into production. 

The solution is too expensive.

I've been using this solution for five years. 

The solution is stable. 

The solution is scalable, it's one of the main advantages. 

Customer service is pretty good for what I need. 

The initial setup is not very complex. It's quite straightforward to get a new platform and be in production. We carried out the implementation ourselves. We have 350 employees and everybody uses Azure. We have four IT professionals dealing with maintenance.

We spend around $10,000 per month on licensing and that's just for Azure. In addition, there is a per user charge for using Office 365.

The policy of the company is to use Microsoft products. We took a look at Google and AWS, but very quickly decided to go with Azure. It's a well-known solution and the decision was taken by the finance department.

Stability and simplicity of use play an important role, so I rate this solution eight out of 10. 

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. 

The use case for Azure is maintenance. Azure maintains the infrastructure so we don't have to, and that's the best use case for any cloud-based application.

Azure is very flexible.

Any time you use a cloud service, there are increased security risks. If you want more security, you have to have private hosting.

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

In general, I think Microsoft support is strong.

Azure could be cheaper. Of course, if you ask anyone, they'll always say it could be cheaper. We are paying monthly.

I rate Azure nine out of 10. I would recommend it to others.

We are primarily using the solution for One Drive on Microsoft, as well as Office 365 and Microsoft Teams.

The solution is easy to use.

It's great for ready-to-use services. 

It's set up to handle any cloud requirement.

The solution is stable. 

The scalability is great.

Microsoft needs to simplify its licensing, which is hard to understand currently.

The security of the solution could always be much better. 

We've been using the solution for three to four years. It's been a while.

The solution is very stable. There are no bugs or glitches. It doesn't crash or freeze. It's reliable. 

The scalability of the product is great. Due to the fact that it is a cloud deployment, it scales well. 

I've used technical support in the past. They are okay. We've been satisfied with them. 

We are also using AWS. 

We have a team that handles the implementation. 

Depending on the situation, you don't need too many people to maintain it. We always start with one resource and go from there. 

The licensing is always confusing with Microsoft. It's very hard to understand. 

Due to the fact that we're using the cloud deployment of the solution, we're always on the latest version. 

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

I would recommend the solution to other users and organizations. Azure is the first ones to come onto the market. They have a very good solution.