Try our new research platform with insights from 80,000+ expert users
reviewer1417791 - PeerSpot reviewer
Senior Regional IT Infrastructure Consultant at a manufacturing company with 10,001+ employees
Real User
A feature-rich and stable platform with good redundancy and scalability
Pros and Cons
  • "The redundancy across different regions is the most valuable. It provides a big value for cloud services, especially for Microsoft."
  • "The level of authorization or authorization cascading can be improved. We have the most powerful admins and then we have sub-admins, but the level of authorization is not that easy to handle or manage."

What is our primary use case?

Azure cloud is a platform for many things, such as hosting, file services, application or power apps, and data lake. All these things are a part of Microsoft Azure. We're using it as a full suite. We are a big tenant with all solutions for Microsoft. We are using the latest version of Microsoft Azure.

What is most valuable?

The redundancy across different regions is the most valuable. It provides a big value for cloud services, especially for Microsoft.

What needs improvement?

The level of authorization or authorization cascading can be improved. We have the most powerful admins and then we have sub-admins, but the level of authorization is not that easy to handle or manage.

For how long have I used the solution?

I have been using Microsoft Azure for three years. I am using this solution on a daily basis. It is the main platform that we have.

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

What do I think about the stability of the solution?

Its stability is good. It is very stable.

What do I think about the scalability of the solution?

It is very easy to scale. We have more than 7,000 users. 

How are customer service and support?

They are pretty sufficient. I would rate them an eight out of ten.

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

We also have different cloud vendors like Amazon and Salesforce, but they all are for different purposes, so it depends on the service.

How was the initial setup?

The initial setup was simple. It was done in stages. 

What about the implementation team?

We had the full support and dedication from Microsoft for its installation. Its maintenance is done by a vendor, and we also have some technical support from Microsoft when we are doing this stuff.

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

Microsoft always provides the entry-level solution with a cheap license. Once you start to like the product, then you have to pay for the full package, which is more expensive than the entry-level solution. Every feature comes with a license and a cost. Some licenses have multiple features, and some features require a specific license.

What other advice do I have?

I would advise starting directly with Microsoft and then asking the vendors to recommend the trusted partners to work on the implementation or migration, and not vice versa. First, talk with the architect of the design and see if they can recommend a trusted partner who can do the implementation.

I would rate Microsoft Azure a nine out of ten. It is a big product and platform. It covers many things in terms of features.

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: My company does not have a business relationship with this vendor other than being a customer.
PeerSpot user
IT Unit Manager at a financial services firm with 10,001+ employees
Real User
Kubernetes service and API management are the most valuable, and it has very good stability and scalability
Pros and Cons
  • "Kubernetes service and API management are the most valuable."
  • "It should have a better hybrid-cloud central analysis. Their support service also needs to be improved. Our main concern is support calls. Our issue is basically related to the technical functionality of the services that we use. It doesn't behave as expected, and support often fails to solve the problem."

What is our primary use case?

We use it to extend our own data centers and banking scenarios for banking solutions.

How has it helped my organization?

It provides us with access to technology that's not available in any other form. It only exists in the cloud. In order to keep our solutions modern, we have to do it through the public cloud.

What is most valuable?

Kubernetes service and API management are the most valuable.

What needs improvement?

It should have a better hybrid-cloud central analysis. Their support service also needs to be improved. Our main concern is support calls. Our issue is basically related to the technical functionality of the services that we use. It doesn't behave as expected, and support often fails to solve the problem.

For how long have I used the solution?

I have been using this solution for three years.

What do I think about the stability of the solution?

It is pretty stable. It has very good stability.

What do I think about the scalability of the solution?

It is scalable. There are no issues with scalability.

We have a maximum of 200 users. They include internal developers and other types of profiles.

How are customer service and technical support?

Their support service needs to be improved.

How was the initial setup?

It is complex because the solutions are complex. It depends on how you want to do the setup. For our business scenario, it is complex because there are a lot of security rules that are involved in it.

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

It is competitive with other public cloud providers, and its price is very close to different cloud providers. There is not a noticeable difference between different cloud providers. Otherwise, it would be a risk for them to have services that were much more expensive than their competition. They're pretty much neck to neck on pricing.

What other advice do I have?

I would advise others to go for the closest possible platform as a service. Do not go for infrastructure as a service; go for platform as a service.

I would rate Microsoft Azure a nine out of ten.

Disclosure: My company does not have a business relationship with this vendor other than being a customer.
PeerSpot user
Buyer's Guide
Microsoft Azure
August 2025
Learn what your peers think about Microsoft Azure. Get advice and tips from experienced pros sharing their opinions. Updated: August 2025.
867,497 professionals have used our research since 2012.
reviewer1454712 - PeerSpot reviewer
Executive Officer at a government with 201-500 employees
Real User
Hosts our whole data center and has a simple setup and very good support
Pros and Cons
  • "We've got multiple tools on Azure, which is a very good feature of Azure. Our Palo Alto firewall and other things are hosted in Azure. We're using Sentinel as well, which is a security tool that is being used by our SOC teams. I've also used AWS, and I find Azure to be more Windows-driven. Although Azure is newer as compared to AWS, it is growing fast. Microsoft is working towards the betterment of Azure."
  • "As compared to AWS, Azure can improve its functionality. In terms of the feature list, it is still lacking a bit as compared to AWS. AWS supports lots of types of operating systems, which Azure is still catching up with. Azure is mainly focused on the Windows system, and it is not yet there in terms of integration with other operating systems like Linux, Unix. Azure is slowly catching up."

What is our primary use case?

Our whole data center is on this basically. We are UK Export Finance, so we've got financial products there. All of our servers are hosted in Azure.

We are using an Azure subscription. We are on Azure Public Cloud, but we have got our own private subscription.

What is most valuable?

We've got multiple tools on Azure, which is a very good feature of Azure. Our Palo Alto firewall and other things are hosted in Azure. We're using Sentinel as well, which is a security tool that is being used by our SOC teams.

I've also used AWS, and I find Azure to be more Windows-driven. Although Azure is newer as compared to AWS, it is growing fast. Microsoft is working towards the betterment of Azure.

What needs improvement?

As compared to AWS, Azure can improve its functionality. In terms of the feature list, it is still lacking a bit as compared to AWS. AWS supports lots of types of operating systems, which Azure is still catching up with. Azure is mainly focused on the Windows system, and it is not yet there in terms of integration with other operating systems like Linux, Unix. Azure is slowly catching up.

For how long have I used the solution?

I've been working with Azure for the last five years.

What do I think about the stability of the solution?

Lots of glitches are still there. Microsoft is constantly working to resolve those. It is a new product as compared to AWS, so, obviously, it would have some glitches. Three years ago, it was full of bugs. It is much better and stable now.

What do I think about the scalability of the solution?

It is scalable. We've got around 450 users.

How are customer service and technical support?

Their technical support is very good. Their response is very good. At the end of the day, we're a business, and their business support is pretty good.

How was the initial setup?

The setup is quite straightforward. It is not at all hard.

We've got a third-party maintenance company that actually maintains our Azure space. 

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

It is not cheap. Its price could be a little bit less.

What other advice do I have?

It is a cloud solution at the end of the day. People can pick up any cloud solution, but Azure is renowned. Azure and AWS are the main competitors in the cloud market now. AWS comes first, and Azure comes after that. If your solution is predominantly in the Linux space, you should go for AWS. If you are primarily Windows-based, you should go for Azure.

I would rate Microsoft Azure an eight out of ten.

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: My company does not have a business relationship with this vendor other than being a customer.
PeerSpot user
Sr Solutions Architect at System Soft Technologies, LLC
Real User
Information protection is great as is the ability to provide temporary and secure access to vendors
Pros and Cons
  • "Good information protection feature."
  • "Could be more user friendly; initial setup is difficult to understand."

What is our primary use case?

The product is being used for document sharing and archiving. The company wants their customers to be able to pull certain documents that they put on file. The idea is that through active directory B2B, they will offer access to the different files and customers will be able to pull the files they need from the server. The company uses information protection to make sure that only the right people have access to the right files. We are integrators, mainly on the software side. We are partners with Microsoft Azure and I'm a senior solution architect. 

How has it helped my organization?

The company has different vendors that they bring in. This product has made it easier to onboard those individuals and to provide access to them when needed and then to basically cut them off when the time comes. The way they have it set up, documents can't be downloaded. They are only accessible online but can be accessed from anywhere so the company doesn't have to worry about setting up VPNs and the like. They provide a username, password, a two-factor authentication and that enables access.

What is most valuable?

Information protection is a good feature because you can label different documents and different files, and that allows them to put like NDA files in a specific bucket, as opposed to just regular, safe or confidential storage.

What needs improvement?

This solution is not user friendly to set up and it's difficult to understand, particularly with regard to information protection and the sort of licensing needed to utilize it. Simplification would go a long way. 

I'd like to see them improve on the watermarking. There's a feature that allows you to watermark documents that are checked out. Currently it watermarks a document with whoever publishes it. For example, if you wanted to watermark the email address, it doesn't watermark with the person checking out the file, but with the person publishing the document. It would be more valuable if the watermarking was related to the person checking out the document, in case it leaks out.

For how long have I used the solution?

I've been using this solution for several years and on my most recent project, for the past six months. 

What do I think about the stability of the solution?

The stability has been great. We haven't had any issues whatsoever with stability.

What do I think about the scalability of the solution?

As far as I know, scalability is fine. Our current customer isn't huge so I can't speak to enterprise size customers. It's not infinite scalability, but it is Azure Cloud. If you need more storage, you buy more storage. 

How was the initial setup?

The initial setup is fairly complex. There is a ton of documentation, but once you get through that it's really not difficult, it's just not intuitive. The product requires better documentation that explains things. I think a lot of it has to do with the licensing requirements. It's not obvious and so you can be following a step-by-step tutorial and still not get it right because the software requirements aren't right but it doesn't give you that in clear text. 

You can probably set this up within 30 minutes, realistically, as long as you know all the steps. Unfortunately, it took about four or five hours to troubleshoot the situation because we didn't understand what the license requirements were. We had to go and obtain those licenses and try it a second time. It'll be fine now because we understand it but there are certain things like having to be a security administrator within the roles and responsibility matrix, and that's not really outlined in the documentation.

What was our ROI?

The company wanted it to deploy rapidly. They didn't want to spend a lot on this project to buy storage, and clear that storage, ensuring that it was 100% secure. This was either going to be a very short-term project or it was going to blow up to something large and they weren't sure which direction it was going to go. Enabling them to use OPEX spend just to utilize what they need when they need it at a low cost, was super valuable to them.

What other advice do I have?

I would recommend anyone wanting to implement this solution to carry out background homework on active directory, on information access management (IAM), and then understand the licensing before you deploy. That aside, it's pretty straightforward. I've learned that setting up secure documents doesn't have to be difficult as long as you take into account those caveats of understanding your licensing and active directory.

I would rate this solution 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: My company does not have a business relationship with this vendor other than being a customer.
PeerSpot user
reviewer1242897 - PeerSpot reviewer
Principal Consultant at a computer software company with 10,001+ employees
Real User
This helps us meet multiple requirements other PaaS solutions do not but there is a lot of room for improvement
Pros and Cons
  • "It is a flexible solution that is straightforward to use."
  • "Stability can suffer in the context of a large architecture."

What is our primary use case?

I work with our enterprise architecture. In my network, there are almost 400 total applications. I have been working here for almost six months on a network migration and in those six months, I have been working with many of those applications that have been included with the involvement of Azure in the migration.   

We are migrating everything from the old network to a new architecture. There are multiple teams that I work with and people work with me throughout the organization. I review all the target architectures and the deployment and everything that comes along with the pieces of the migration that involve Azure. Any issues, large or small, I have to look into. These issues might be simple certificate issues or they may involve multiple interfaces that need to be used for a solution.  

Because we have a very complex system, it is not easy to complete the migration. The landscape also has a mixture of different technologies and platforms. If I have to customize, I just get a Terraform script or ARM template from a developer who is assigned to that task. I review all that stuff that they give to me.  

When we went to the version of Azure that we use now, there are certain solutions that we created. If we had trouble, we worked with Microsoft to create that solution for our organization and the problems that needed to be solved.  

We define our own solutions with Microsoft that are not available in the open market. Because of the way we have used Azure, we do not really have a very focused end-product. It is a highly customized product that we have built using many tools.  

Azure is now a mixture of solutions. There are certain applications, which are IaaS (Infrastructure as a Service) applications, where we just go and use them. Then there are certain applications that are a mixture of IaaS and PaaS (Platform as a Service). For certain parts, we use private clouds, public clouds, or hybrid clouds. We originally wanted to use more public clouds, but as we proceed, we are moving into more hybrid mechanisms. In the future, I don't know exactly what direction we will take because the technologies and the climate are changing so quickly.  

But right now, we are only using Azure with images being created from the existing architecture. For Azure, we use private cloud, public cloud, and mixed, or hybrid cloud as needed and all of these work together.  

In the future, we may go for some specific function-based services or even open-market APIs. We can use open APIs with Azure. API management is also possible. So there are a lot of permutations and combinations that go with each application based on sizing and NFR (Non-functional Requirements) validation.  

For Microsoft Azure, we use the product itself as a platform, I work mostly with their services. These can be PaaS services or DNS services, monitoring services, storage services — basically all the supporting services that are available to us with Azure. Anything that is not available, we try to build on PaaS. If the services we want are not available, I have to do a complete fabrication.  

So we use mostly PaaS services for most of the supporting services and then we work further in solution optimization, which is something we can accomplish through Azure. Ultimately all that depends on the budget. If a company is ready to spend on a cloud solution, an ROI (Return on Investment) model helps. The amount of customizations and the real need for a solution comes out of the realities of the ROI.  

Our contracts are based on supplying solutions for what the customer needs. If they have selected that a particular application will be available and make this a system mandate which we have to flow, then we have to keep those applications. Azure is one of the tools that we are using to help make these kinds of customizations and to meet their expectations after the migration.  

How has it helped my organization?

Azure gives us a different form of PaaS to work with during our migration and helps us to meet multiple requirements that current solutions do not provide in any one product. 

What is most valuable?

One of the most valuable things about Azure, I think, is that it is pretty straightforward. There are well-defined processes and it is not a bad product to work with. I only work on Azure right now most of the time. I cannot directly compare it with other solutions in the present situation because it is not always practical to consider every solution. Certain platforms on the market are very strong with other services. For example, Kubernetes on RedHat Openhift is better for working with AWS. But I have to ask from a usability, a complexity and a budget standpoint if that is really required.  

If I do my work and my applications are sorted out well in advance, I do not have any issues. From a user perspective — not from a cloud architect or enterprise architect perspective — my requirements are being met. As long as these requirements are met, I do not see anything as a showstopper. If there is a showstopper which I think I absolutely can not solve with Azure and I think another solution would handle, then possibly we may go into a multi-cloud scenario.  

That is also a limitation for our organization. The goal is never to seek complexity. Personally, I think there is no direct comparison between what solution is better and what solution is worse. There are only solutions that work or are capable of doing something and those solutions which can not do it, or were not designed to do it, or do not want their product to do it, et cetera.  

Part of my place in working with these solutions as part of my process is working with products I am comfortable with. So the more that I use Azure, the more comfortable I get with what it can do as a solution, and the more comfortable I am using it. If I started using AWS more, I would get more comfortable with AWS and maybe incorporate that more heavily in the solutions.  

What needs improvement?

There are some small things that could be done to improve Azure. I think they should actually do more to implement function as a service. It is a completely separate capability that they currently do not address. Function as a service can be a completely different scheme altogether than PaaS or IaaS which it does quite well.  

For an example of a FaaS, I think the Azure product can be stronger in terms of storage. I would like to see it have better management systems as a service specifically for managing documents. Right now they are handled as a more generalized object.  

Say Azure came out with Microsoft Document Management and it was very strong as a service. It would not have to be deployed as a complete infrastructure. I would be able to use that as a service inside my organization and it is a product that any organization can use.  

The question is what is the separate USP (Unique Selling Point) that Microsoft will provide to the user that would fit a unique need when making FaaS solutions available. Document management systems have already been proven to be very popular by Google. Microsoft Office uses OneDrive storage. There may be a better way to promote document management in a more general PaaS. Sometimes it is very useful to virtualize a platform or an infrastructure, but in the same way, it is sometimes valuable to virtualize a function. Applications may be a collection of functions.  

It is this type of branching out of services that Azure can do within the structure they already have.  

They are targeting Azure into specific domains and not working as much with open-source as they could. That would be helpful. I think eventually this approach will just drive the competition away. If I have a product that is very good for manufacturing as a function — something like is being done with Edge — it might be beneficial for Azure to be able to tie in this FaaS and let manufacturing clients start working with the solution without having to reach outside of Azure. Right now that I do not see that happening and it is an opportunity that Microsoft is missing with Azure.  

For how long have I used the solution?

I am responsible for designing our migration, so I have to work with Azure to define the parts of that solution. I had previously been using AWS mostly for personal services so I was familiar with PaaS platforms, but I have now also been using Azure exclusively for the last six months to supplement the functionality we require.  

What do I think about the stability of the solution?

The product is stable. There are a few qualifications attached to that.  

I think the stability of Azure varies depending on the workloads. It is more stable from the perspective of how it behaves in a mid-size deployment. For a very, very large implementation, I have yet to see that same kind of inherent stability. I believe it is because of the complexity of the client's system or architecture.  

You may be able to say that if it is more of a Microsoft product landscape, then possibly it is more stable in general. The more that there is a mixture of technologies, then it will tend to be less stable. No application can be stable in every circumstance.  

As the project I am engaged in is very large, we have experienced some episodes of instability. We solve the stability problems as we go along to a great extent. But I think there are a lot of situations that have to be dealt with in real-time. Though we have direct contact with a Microsoft team architect, it is difficult for them at times to just jump in and solve an issue. You can not usually solve a problem instantly looking down at it from 55,000 feet when the situation on the ground is very, very complex.  

At first, they only have generalized solutions to your problem. I think they need an extension of the existing team. This would be like a core team to work with client organizations to do case studies to define patterns in what is causing instabilities.  

Because Azure is cloud technology and cloud comes with its own problems, these bleed over into Azure stability. All these patterns that contribute to instability have to come out in order to be solved. As Microsoft collects more case studies and more knowledge of where these problems tend to occur, this should enable them to stabilize the product against those issues.  

Overall, I would say Microsoft Azure is a stable solution, but even as a stable solution, it usually has some bugs or glitches.  

What do I think about the scalability of the solution?

As of today, we have almost 1,000 people using the solution. We have a very big migration project that will last for the next four to five years before it is completed. They have many applications and many users for those applications. If the volume of users or applications were to scale, that should not be a problem.  

How are customer service and technical support?

I do not really have much direct contact with the Azure or Microsoft support teams. We have a separate team for that. I have a great architect that I work with here (Sweeden). But if an issue comes up, the application team goes to work on it to support the resolution. It is their option to contact Azure to raise that issue or resolve it themselves.  

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

I was using AWS before Azure, but I was using it mostly for my own personal needs. I was deploying my own applications. I used it for about two years but not from a company perspective. I deployed my own applications in the public cloud and loaded them there for use at a personal level.  

In the company right now, I am only using Microsoft Azure. The company itself is using everything, really. At this point, my experience in the company is specialization as the person who is helping to utilize Azure.  

How was the initial setup?

The initial setup was simple and it is simple for a simple application. If I want to build with a simple application, I simply go do that. But if I have a very heavy interface-based application, then the choices become more difficult and involved.  

If I have a WebSphere application, that is easy. A complex platform or a complex interface dependence becomes difficult to implement because of restrictions. If I can not simply go and deploy as it is, obviously it is more complex to deploy in the system.  

For a small company with a typical landscape of Microsoft technology, it becomes very easy to work with Azure. It is possible to go through that setup by yourself and test your servers and the entire functionality. 

After deployment, you will require maintenance. We can not simply have a production list and push everything out. You need pre-production, testing, and then deployment. All that has to be done on Azure.  

There are a lot of things you will have to work out with security certificates. Meanwhile, things keep on changing in the product itself. New upgrades keep on rolling out. If the old version does not support the new upgrade, then you will need to get involved with patching and other upgrades to take care of the issues that are introduced.  

We have a dedicated team for maintenance. We know we need to do testing and that is why we created tasks for that. But, generally, I think complexities in the setup depend upon what applications you are building. Simple applications and simple systems make for simple deployment.  

What about the implementation team?

We are working with the vendor directly. We also have contacts with Microsoft. Microsoft directly provides us all the tools and information we need for implementations.  

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

The pricing of Azure depends on the build of what you prepare. You can optimize everything, and with Azure, you can optimize your utility and costs. For example, say you create a subscription and you want to do more backups and you want a private cloud for that. This will affect your cost differently than if you do not add the backups with Azure or if you add the services with a public or hybrid cloud.  

We have very good, large contracts with big organizations. We do very high-level analytics and modeling to predict outcomes. For example, we may show that a certain solution that we implement with Azure will be likely to reduce a company's cost from the current level to 50% over the next five years. That, to me, is important when considering the cost of a subscription. It is not just the cost perspective that is important, but the ROI as well.  

What other advice do I have?

I would definitely recommend Azure as a solution because it is a popular product by a major brand and it is very easy to use. I think those people I would recommend it to should normally be those who understand the cloud and the advantages and disadvantages. I use it for a lot of things and I do not see any problems. I love it now as a solution so I would recommend it. But if I have a different experience with another very large migration project using a different product, I would have to compare Azure with that. I may get more comfortable with the other product for reasons I have not discovered yet.  

On a scale from one to ten where one is the worst and ten is the best, I would rate Microsoft Azure as a seven-out-of-ten. It is a good product and I love using it but it could do even more and has a lot of possibilities to grow as part of a relatively new technology. The future is more open than closed to the possibilities.  

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. Partner
PeerSpot user
Solutions Architect at a comms service provider with 10,001+ employees
Real User
A customizable solution with a good interface and helpful support
Pros and Cons
  • "The most valuable features are the interface and customizability."
  • "Dashboards and reporting could be improved."

What is our primary use case?

We are a solution provider and Microsoft Azure is one of the technologies that we help our clients to implement. For example, when one of our customers wants to migrate from on-premises to the cloud, we assist them with the process. Once they decide on technology, we build the solution.

Our clients implement Azure to use as Infrastructure as a Service.

What is most valuable?

The most valuable features are the interface and customizability.

The approach used for cloud migration is something that I like.

Documentation and community support are good.

What needs improvement?

Dashboards and reporting could be improved.

For how long have I used the solution?

I have been working with Azure for three years.

What do I think about the stability of the solution?

Azure is a stable system.

What do I think about the scalability of the solution?

There are no issues with scalability. We have a range of customers that vary in size from small to medium-sized businesses, as well as enterprise-level organizations.

How are customer service and technical support?

I am happy with the good support that we are getting. I have not been in contact with them directly but some of my colleagues have dealt with them.

How was the initial setup?

The installation and initial setup are easy. We implemented over the course of a few days. 

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

Reducing the price would be of benefit to our customers.

What other advice do I have?

My advice for anybody who is considering this solution is to do a proof of concept first. This is what I suggest to all of our customers, especially before migrating to the cloud. It will ensure that it meets the requirements.

I would rate this solution a ten out of ten.

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: My company has a business relationship with this vendor other than being a customer. Partner
PeerSpot user
reviewer2349756 - PeerSpot reviewer
Senior DevSecOps Engineer at a tech vendor with 1,001-5,000 employees
Real User
Top 5
Comes with account management feature but interface needs to be made similar to AWS
Pros and Cons
  • "The tool's most valuable aspect is the account management side. This involves tasks such as assigning credentials to different individuals, managing user accounts, and implementing Privileged Access Management."
  • "The tool should add an interface that is similar to AWS."

What is our primary use case?

In my department, we primarily use AWS. However, for single sign-on, we use Azure Directory. It helps with integration when logging into various systems. The IT operations team utilizes Microsoft Defender for tasks such as tracking various endpoints and conducting business reviews.

What is most valuable?

The tool's most valuable aspect is the account management side. This involves tasks such as assigning credentials to different individuals, managing user accounts, and implementing Privileged Access Management. 

What needs improvement?

The tool should add an interface that is similar to AWS. 

What do I think about the stability of the solution?

Microsoft Azure is stable. 

What do I think about the scalability of the solution?

My company has around five to ten users for Microsoft Azure. It is scalable. 

How was the initial setup?

The tool's deployment is easy. 

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

Microsoft Azure is expensive. 

What other advice do I have?

The tool is a great product to use, and very intuitive. It is beneficial for users and enterprises. I rate it an eight out of ten. The product is easy to learn, but it may become difficult depending on your technical ability.

Disclosure: My company does not have a business relationship with this vendor other than being a customer.
PeerSpot user
Technical support engineer at 64 Network security pvt ltd
Real User
An exceptionally stable and easy-to-access solution for file storage and file backup
Pros and Cons
  • "Feature-wise, I like its stability. Also, it is easy to access the solution and its options."
  • "The security feature in the solution is an area that needs to be improved."

What is our primary use case?

We were using Microsoft Azure for file storage and file backup. So, it was one of our backup resources. Internally, NAS is there in our company. So, we go from NAS to Veeam and Veeam to Azure.

What is most valuable?

Feature-wise, I like its stability. Also, it is easy to access the solution and its options. Also, the backup solutions can take anything, so we can easily find out any option.


What needs improvement?

The security feature in the solution is an area that needs to be improved.

For how long have I used the solution?

I have experience with Microsoft Azure until six months ago. Also, I was using the solution's latest version.


What do I think about the stability of the solution?

It is a stable product.

What do I think about the scalability of the solution?

It is a scalable product. There are more than 100 users using the solution. I am just involved in the maintenance of the servers and infrastructures.

How are customer service and support?

We need to purchase Microsoft Azure for our clients, including cloud backup and any Azure solutions. So, So that time, we need to contact technical support. I expect more technical support from Azure.

How was the initial setup?

The solution's initial setup is straightforward. When you need to create multiple tasks, the solution can get complex. I am not involved in the deployment process.

What other advice do I have?

I can recommend it to other people who want to start using it. So, our company provides a lot of solutions to our clients, including backup solutions like NAS storage, cloud storage, and servers. Parallely, we provide support to users.

I rate the overall solution a nine out of ten.

Disclosure: My company does not have a business relationship with this vendor other than being a customer.
PeerSpot user
Buyer's Guide
Download our free Microsoft Azure Report and get advice and tips from experienced pros sharing their opinions.
Updated: August 2025
Buyer's Guide
Download our free Microsoft Azure Report and get advice and tips from experienced pros sharing their opinions.