Nicolas Chabrier - PeerSpot reviewer
Cloud Strategy B2B leader at Sunrise UPC
Real User
Promotes clear, logical structures preventing impractical configurations and offers seamless integration
Pros and Cons
  • "The customer service and support are very good. When we raise a ticket, we quickly get feedback or someone assigned to help us identify the problem, which, 90% of the time, was on our end. I'm very happy with the support they provide."
  • "The only thing is regarding the management of multi-cloud environments. That's not really possible."

What is our primary use case?

My experience primarily revolves around modernization, IT transformation, and infrastructure as a service in the cloud, along with managed services, cloud service provider strategies, designing cloud services, and monetization strategies.

So, I'm mainly focused on consulting for customers. However, I also use it personally. 

How has it helped my organization?

My customers integrate Microsoft Azure into their existing IT infrastructure. They adopt a hybrid approach, and they tend to move as much as possible to the cloud. It's a transition to fully cloud-based solutions, dealing with legacy systems through temporary hybrid solutions until everything can be migrated.

Projects often leverage Azure for data handling, using Microsoft's data platform, Power BI, and Azure Synapse Analytics. Innovations with Azure are increasingly driven by integrations with OpenAI and tools like ChatGPT, enabling rapid project initiation and delivering substantial results in artificial intelligence applications.

It's very exhaustive and very comprehensive. Regarding the security features, the security stack of Microsoft has made a lot of improvements in the last two years. We really appreciate the offerings, particularly what they have done with Microsoft Sentinel, a platform that helps manage what is happening within your organization, which is very good. 

An improvement could be a version that is more adapted for small companies. Microsoft Sentinel is great for large companies but less so for smaller ones. I also appreciate what they have done with Microsoft Purview. The cybersecurity stack of Microsoft is very good.

What is most valuable?

Microsoft Azure promotes clear, logical structures preventing impractical configurations. So, compared to the older platform I know, the advantage of Microsoft Azure is it's very coherent. You can't really build something totally stupid. 

With other platforms, it's possible to build something technically possible but practically very stupid. So, it's very coherent on the Microsoft platform, and it's also consistent with what Microsoft has done on-premise. 

If we have a customer with a strong Microsoft footprint, it's pretty obvious that we should move to Microsoft Azure. On the opposite side, if we have a customer that's super Linux-oriented, they have a lot of Linux services and stuff like that for those types of customers. It's easier, maybe, to move to AWS.

Another area of improvement is Microsoft Sentinel. It is great for large companies but less so for smaller ones. An improvement could be a version that is more adapted for small companies.

What needs improvement?

The only thing is regarding the management of multi-cloud environments. That's not really possible. 

So basically, it's wonderful if you manage Microsoft clearly and if you manage Microsoft Azure, but if you need to consume external services and have a global overview of all your consumption, it's not the case. 

Google, for instance, has tools that help you manage multiple environments, which makes sense because Google is really the cloud provider. So that's why they need to be compliant with the others. 

But for sure, Microsoft's approach is different, and it's wonderful when you're one hundred percent on Azure. But if you'd like to have something more of a multi-cloud strategy, that's a bit of a gap where they could improve.

Buyer's Guide
Microsoft Azure
March 2024
Learn what your peers think about Microsoft Azure. Get advice and tips from experienced pros sharing their opinions. Updated: March 2024.
763,955 professionals have used our research since 2012.

For how long have I used the solution?

I have been using this solution for more than ten years now. 

What do I think about the stability of the solution?

It is a very stable solution. I would rate the stability a ten, but I never give it ten, so I would rate it a nine out of ten. 

What do I think about the scalability of the solution?

I would rate the scalability a nine out of ten because no one is perfect. Azure's scalability features are fundamental. They allow our applications to grow with our customers. 

For instance, when a customer enters new markets, it's easy to deploy an environment in a new data center or provide a CDN for closer distribution. We encourage customers to adopt modern applications based on microservices, which are natively scalable and elastic, allowing the IT infrastructure to grow with their market demands and expectations.

In Switzerland, where I'm based, the majority of people use Azure. AWS entered the market a bit later. The problem is they're working more with Microsoft products like Microsoft 365 than with Azure as an infrastructure platform, which is still pretty new here. We're at an early stage in Switzerland for full cloud adoption.

Our customers are medium enterprises mostly because they are the most prominent customers we see in my business. Large customers already use Azure extensively, like the top 50 big companies, including Zalando, Nestle, Kraya, and Philip Morris for PMI. They're using Azure a lot, but not always AWS. If you're very big, you'll have at least two cloud providers. 

The medium market is more Microsoft-oriented than AWS. Small companies, however, don't know much about the cloud or are not interested in it; they are interested in solutions that may be hosted in the cloud, but that's not their focus.

How are customer service and support?

The customer service and support are very good. When we have an issue in an Azure environment, it's usually our fault, not Microsoft's. Maybe it is an issue with the design we made.

However, when we raise a ticket, we quickly get feedback or someone assigned to help us identify the problem, which, 90% of the time, was on our end. I'm very happy with the support they provide.

How would you rate customer service and support?

Positive

Which solution did I use previously and why did I switch?

I've worked with many solutions as I'm involved in cloud strategy, focusing on cloud technology.

I have substantial knowledge of the AWS platform and Microsoft Azure, particularly in infrastructure as a service, management, cloud platforms, FinOps, containers, and microservices. 

I have a good overview of the offerings from AWS, Microsoft, and Google, and they're very close. They observe each other and are very similar. For me, Microsoft Azure is a very good platform with a lot of utility. 

AWS is probably the most exhaustive platform, allowing for a wide range of technologies. However, this means you can create monster systems that don't make sense, though it might be useful for a very niche market. 

Google tries to think out of the box, offering alternatives that can comply with other platforms, and having a more data-driven approach. But AWS and Microsoft are very close.

How was the initial setup?

I would rate my experience with the initial setup a five out of ten, with ten being easy to set up. 

It's not difficult because you are well-guided, but it requires an understanding of the philosophy and knowledge. It's definitely easier than AWS, which is more complex and designed by engineers for engineers. Managing AWS is definitely a bit more complex than Azure.

What about the implementation team?

The time it takes to deploy Microsoft Azure varies. You can create an environment in five minutes, but setting up a whole organization can take longer. It depends on what you mean by "deploy." 

In Azure, the environment size matters; whether you have one server or three thousand, it's not the same thing, and it also includes factors like replication. Now, everything is scripted, so the deployment time also depends on your maturity and experience. It's faster to deploy a cloud environment than a physical one.

First, we identify what needs to be achieved and make the architecture. Then we deploy in a test environment, perform integration and acceptance tests, move to a pre-production environment for real-life assessment with limited users, and based on success, move to production. 

There's a sandbox or dev environment, a test environment for testing, a pre-prod for limited user testing, and then production for a dedicated market or group if successful.

What's my experience with pricing, setup cost, and licensing?

I would rate the pricing a seven out of ten, where one is cheap and ten is expensive.

It's not about licensing but subscription. For an SME, spending roughly 5,000 euros per month becomes interesting, indicating a significant infrastructure setup in the cloud. 

For those just starting their cloud journey or using only Office 365 and similar services, it's much cheaper, about 1,000 to 2,000 euros per month.

Customers pay Microsoft to get the environment up and running, but they may also need to pay external providers or suppliers for managed services. This is where we see an opportunity to provide an integrated offer that includes both the Microsoft suite and management on top. 

It's crucial, especially for companies that may not know how to fully leverage the product, to have this guidance and support. 

This is where Microsoft partners come in, adding value on top of Microsoft's offerings. 

For an SME, depending on their IT infrastructure, having managed services is important, as they may not have a large IT department. The cost of managing the environment might be similar to the expense for Microsoft services, potentially around 5,000 euros a month to manage the environment.

What other advice do I have?

I would advise that migrating to the cloud is an amazing opportunity. However, it's crucial to understand the drivers of the cloud, what changes it brings, and to reconsider the organization and skills within the organization. 

If you expect to move to the cloud without changing the structure, processes, personnel, or without providing training, it won't work. You might end up disappointed, wanting a direct copy of what you had in a cloud environment in the past, which could be more expensive.

Moving to Azure requires training your IT teams, but also providing basic cloud training for everyone, including the CFO, CIO, and even the CEO. Everyone needs to understand the concept of the cloud and what can be achieved with it.

Creating a cloud center of excellence is also critical to reshaping the company with cloud capabilities. This can lead to significant changes and transformation, increasing elasticity, reactivity, and potentially huge savings.

Overall, I would rate the solution a nine out of ten. 

Which deployment model are you using for this solution?

Hybrid Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer: consultant
Flag as inappropriate
PeerSpot user
Managing director at antarymain solutions
Real User
Top 5
A scalable and stable tool that provides various valuable features under one roof
Pros and Cons
  • "I get all the features under one roof."
  • "The subscriptions are complicated."

What is our primary use case?

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

What is most valuable?

I get all the features under one roof.

What needs improvement?

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

For how long have I used the solution?

I have been using the solution for almost one year.

What do I think about the stability of the solution?

The tool’s stability is good.

What do I think about the scalability of the solution?

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.

How was the initial setup?

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.

What was our ROI?

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

What's my experience with pricing, setup cost, and licensing?

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.

What other advice do I have?

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.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
PeerSpot user
Buyer's Guide
Microsoft Azure
March 2024
Learn what your peers think about Microsoft Azure. Get advice and tips from experienced pros sharing their opinions. Updated: March 2024.
763,955 professionals have used our research since 2012.
AbasoJadhav - PeerSpot reviewer
Team Lead at Tech Mahindra Limited
Real User
Top 10
Feature rich, simple deployment, and good support
Pros and Cons
  • "The most valuable feature of Microsoft Azure is the Area feature. Additionally, the SQL Server DB as a serverless pool is useful, storage-wide external tables are helpful, and PolyBase is very good at reading external data. The capacity of Synapse to analyze in analytics is very good and it supports a range of data."
  • "The scalability could improve."

What is our primary use case?

We are using Microsoft Azure for many purposes in our project. We have a cloud-based SQL Server and we are bringing data to Azure DB through the Area feature. We are using SQL Server as a database, and from there we are using the data for analysis. We are doing forecasting using all the data. 

What is most valuable?

The most valuable feature of Microsoft Azure is the Area feature. Additionally, the SQL Server DB as a serverless pool is useful, storage-wide external tables are helpful, and PolyBase is very good at reading external data. The capacity of Synapse to analyze in analytics is very good and it supports a range of data.

For how long have I used the solution?

I have been using Microsoft Azure for approximately one year.

What do I think about the scalability of the solution?

The scalability could improve.

We have many teams that are using this solution in different projects.

I rate the scalability of Microsoft Azure a four out of five.

How are customer service and support?

We did not contact the support from Microsoft Azure often.

I rate the support from Microsoft Azure a four out of five.

How would you rate customer service and support?

Positive

Which solution did I use previously and why did I switch?

I did not use another solution prior to Microsoft Azure.

How was the initial setup?

The deployment of Microsoft Azure is easy because it is cloud-based.

What about the implementation team?

We have one person that can deploy Microsoft Azure when they have proper access rights. If the project is small it can be seamless. For example, I'm handling a 10 to 12 person team, and for deployment, one person that has all access writes can deploy Microsoft Azure seamlessly.

What other advice do I have?

I would recommend this solution to others.

I rate Microsoft Parallel Data Warehouse an eight out of ten.

Which deployment model are you using for this solution?

Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Strategic Sourcing Manager at a financial services firm with 1,001-5,000 employees
Real User
An absolutely stable solution that allows us to scale up and down as needed
Pros and Cons
  • "The ability to scale down is a big thing."
  • "It can be improved in terms of ease of billing or monitoring of the billing. That gets to be a little difficult."

What is our primary use case?

We have our data lake on it. In terms of deployment, I believe we have a hybrid deployment.

How has it helped my organization?

We can temporarily build out an environment for different scenarios, such as testing, and when testing is done, we can shut that environment down. So, we do not have an overhead in our own data center.

What is most valuable?

The ability to scale down is a big thing.

What needs improvement?

It can be improved in terms of ease of billing or monitoring of the billing. That gets to be a little difficult.

For how long have I used the solution?

I have been using this solution for four years.

What do I think about the stability of the solution?

It is absolutely stable. Microsoft doesn't want to sell something that isn't.

What do I think about the scalability of the solution?

Its scalability is excellent. You just turn something on, and it is there. We have not made any reservations on it. We can scale up and scale down as needed. There is nothing that we have that is a commitment.

We probably have about 500 users, and they are administrators, developers, BI folks who actually manipulate it and create reports, and then we have end-users for the data. They are the people that use those reports.

In terms of the plans to increase its usage, right now, we're going through a merger, which will impact the data a little bit. So, we are in a holding pattern in terms of scaling up anything until that merger gets completed.

How are customer service and support?

We go through a third party for that, and their support is really good.

Which solution did I use previously and why did I switch?

We were fully on-premise with some SaaS platforms, and we then moved to Azure for a part of that.

How was the initial setup?

It was complex, and that was mostly because of the security needs. We had to understand how things fit together.

The original deployment, just for testing, took about half a day, but to really get it going and to be able to allow access to people, other than the administrators, took more time. We're a financial institution, so we had to have everything monitored and secure. It probably took about four months to get it functional on the production side.

What about the implementation team?

We used a consultant. They were excellent. They knew exactly what they were talking about. They were able to give us not only what was needed presently for our deployment but also the things to think about as we let the environment grow in the future.

For its deployment and maintenance, I've got security folks who watch what's going on. They make sure that only the right people are getting the right data, and it is not being allowed to folks who shouldn't have access. I have nothing public-facing on it. I've got administrators. I've probably got three people in security and five people in the administration. We're a 24/7 business, so it is split across all of that time.

What was our ROI?

Originally, when we implemented it, it was basically in a like-for-like way, which is not the way the platform is designed. So, once we were able to really get in there and figure things out, we figured out that we could use a much smaller footprint. That helped us out quite a bit in terms of a return on investment. We are seeing probably about 75% of the regular data center cost in Azure, so there were 25% savings, but we could see that go down as testing was being eliminated over different platforms.

What's my experience with pricing, setup cost, and licensing?

Currently, we do not have anything reserved. There are no reservations that we have built into the Azure environment, so all of our licensing is on a consumption basis. As things spin up, those licenses spin up.

In terms of the additional costs incurred beyond the standard licensing fee, such as for operations, it's kind of tough for me to judge because I already had a fully-staffed operations team in a fully on-premise platform environment. So, we didn't spin up anybody extra for that. It just changed what they were doing.

Which other solutions did I evaluate?

We evaluated other options. We decided to go with Azure because we understood the licensing and VMs and how all of that worked together. Prior to the merger, we were looking at bringing the platform onto AWS. It wasn't that we were necessarily exclusive; we just felt that this was our best first step.

What other advice do I have?

I would advise understanding what data you're going to be putting out there, and what your security requirements are for that. You should be ready to have a workshop so that everyone involved knows what's going on. Get a good understanding from the accounts payable team about how the payments are coming in and how to monitor them.

I love the product. From a procurement standpoint, I don't have a lot of control over it. Unless we've got some contracting of what we plan on doing, I don't have a lot of control over licenses, etc. An administrator can just go out, do it, and put the licensing in place, and then it is like you've got to pay for it. It doesn't function well in a P2P type of environment.

I would rate it an eight out of 10.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
IT Technical Manager
Real User
Technical simplicity in terms of implementation; flexible and scalable
Pros and Cons
  • "Provides a high level of availability and 99% uptime."
  • "Lacks flexibility in terms of storage or resource allocation."

What is our primary use case?

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

What is most valuable?

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.

What needs improvement?

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.

For how long have I used the solution?

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

What do I think about the stability of the solution?

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. 

What do I think about the scalability of the solution?

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. 

How are customer service and technical support?

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. 

How was the initial setup?

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

What's my experience with pricing, setup cost, and licensing?

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.

What other advice do I have?

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. 

Which deployment model are you using for this solution?

Hybrid Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Works at a real estate/law firm with 10,001+ employees
Real User
Good security, excellent scalability, and very stable
Pros and Cons
  • "Technical support, from what I understand, is quite helpful and we speak with them regularly."
  • "The installation process is complex."

What is our primary use case?

We don't use DevOps; we just use the Azure Cloud platform. The solution is primarily used for PaaS and FaaS.

What is most valuable?

The solution has been very stable.

We find the product to be scalable. 

The security network inside of the information on the network is very good.

Technical support, from what I understand, is quite helpful and we speak with them regularly.

What needs improvement?

There aren't really any issues with the product itself. For us, the problems are organizational and the processes inside the company, which uses Azure, aren't as clear. They need to define a good process and a good implementation strategy going forward. We only really have issues with what they want to do, and not the technology itself. Basically, the technology is not the problem. It is just the way we want to use it.

It would always be nice to have even more integration capabilities.

A company needs to have strong finance managers. It could cost a lot if you haven't got a finance function inside each company.

The installation process is complex. 

The pricing could always be better and a bit more standardized.

For how long have I used the solution?

I've been using the solution for five years at this point. It's been a while. 

What do I think about the stability of the solution?

The solution is very stable and reliable. The performance is good. It's not buggy. there aren't glitches. It doesn't crash or freeze.

What do I think about the scalability of the solution?

The product has been very scalable. If a company needs to expand it, it can do so.

At this time, I'm not sure exactly how many people are directly using the solution.

How are customer service and technical support?

While I haven't personally used technical support, our company does have a technical account manager on the Azure side and we are coordinating each week to identify all the topics we need to address - including our disaster recovery plan, which is important to the company right now. 

Which solution did I use previously and why did I switch?

We did not previously use a different solution before we chose to work with Azure. 

How was the initial setup?

The installation process is not very straightforward. 

When you want to install with a higher level of security inside the infrastructure, nothing communicates. Therefore, engineering security and network engineers need to understand what they have to do exactly, and what the problem is. With Aure, there's a learning curve for installation. You need to work with it for at least one year before you get comfortable enough and are able to troubleshoot and configure everything relatively well.

What's my experience with pricing, setup cost, and licensing?

The solution has the potential to be expensive if you as a company are not careful as to how you use it. 

What other advice do I have?

I'm a customer and an end-user.

I'd rate the solution at a ten out of ten. For me, it's a perfect product and I enjoy its capabilities. 

I would recommend this solution to other users and organizations. 

Which deployment model are you using for this solution?

Public Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Microsoft Azure
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
IT Engineer at United Nations
Real User
Top 20
Responsive technical support, scales applications well, and reliable
Pros and Cons
  • "One of the features I have found to be valuable is the scale set feature."
  • "There needs to be better data security. There are organizations that do not want their data to be submitted to Microsoft, they should have strong encryption."

What is our primary use case?

We use the solution for multi-factor authentification while sorting out the identities. We want to use this solution for as many applications for the authentification process.

What is most valuable?

One of the features I have found to be valuable is the scale set feature. We have been able to get good results scaling up and down our applications. Additionally, the dashboard is fuctional.

What needs improvement?

There needs to be better data security. There are organizations that do not want their data to be submitted to Microsoft, they should have strong encryption.

In the future, Microsoft should increase its data center percentage in Africa.

For how long have I used the solution?

I have been using the solution for two years.

What do I think about the stability of the solution?

The solution has been stable.

What do I think about the scalability of the solution?

We have found the scalability of the solution to be good. We have approximately 4,000 people using the solution in my organization.

How are customer service and technical support?

If we are having a hard time finding a solution to an issue the technical support has been very quick to respond.

How was the initial setup?

The initial setup is straightforward for me since I have done it before, for people new to installing it could experience some difficulty.

What's my experience with pricing, setup cost, and licensing?

The solution does not offer very many free services which can become expensive. We are on an annual license.

What other advice do I have?

I would recommend this solution to others.

I rate Microsoft Azure an eight out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Associate Director at a financial services firm with 10,001+ employees
Real User
Great for configuring on a variety of machines; very stable and scalable
Pros and Cons
  • "It's a reasonably priced solution."
  • "Could be more user friendly; security features should be improved."

What is our primary use case?

In our company, this solution is mainly used for configuring devices and enabling them to be used by multiple users. I'm a developer. 

What is most valuable?

The product is valuable if you don't want to spend a lot of money configuring your own devices on different machines. I like that if I only want to use limited features, I don't have to pay for it. 

What needs improvement?

The solution is not particularly user friendly so that could be improved. With Microsoft Azure it's quite difficult to do anything freely or try my hand at something new. I think the solution is also lacking in security. I'd like to see the option of a free account for carrying out a POC and the ability to play around with the solution without any restrictions. 

For how long have I used the solution?

We've been using this solution for a year. 

What do I think about the stability of the solution?

This is a stable solution.

What do I think about the scalability of the solution?

We have the server on cloud so it's scalable according to demand. All of our staff use it, and we have 15,000 users.

Which solution did I use previously and why did I switch?

I previously used AWS. In comparison, Azure is a little restricted because of the security features and, as a developer, I'm not comfortable with that. AWS is more user friendly and in general, people find it easier to use. AWS is easier to install and to experiment and play around with to get a feel for the product.

How was the initial setup?

There is no setup as such, it's on a server and it's a matter of configuring on the cloud. If you need, you can spawn 3,000 machines with a single execution and 10,000 or so test scripts within minutes.

What other advice do I have?

I would definitely recommend this solution. 

I rate it an eight out of 10. 

Which deployment model are you using for this solution?

Public Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Microsoft Azure
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Buyer's Guide
Download our free Microsoft Azure Report and get advice and tips from experienced pros sharing their opinions.
Updated: March 2024
Buyer's Guide
Download our free Microsoft Azure Report and get advice and tips from experienced pros sharing their opinions.