Microsoft Azure OverviewUNIXBusinessApplication

Microsoft Azure is the #1 ranked solution in top Infrastructure as a Service Clouds and PaaS Services. PeerSpot users give Microsoft Azure an average rating of 8.4 out of 10. Microsoft Azure is most commonly compared to Oracle Cloud Platform: Microsoft Azure vs Oracle Cloud Platform. Microsoft Azure is popular among the large enterprise segment, accounting for 59% of users researching this solution on PeerSpot. The top industry researching this solution are professionals from a educational organization, accounting for 20% of all views.
Microsoft Azure Buyer's Guide

Download the Microsoft Azure Buyer's Guide including reviews and more. Updated: May 2023

What is Microsoft Azure?

Windows Azure is Microsoft's cloud platform, where developers can create, deploy, and maintain their apps. This cloud application platform allows developers to concentrate on the actual applications, while it takes care of all the elements behind the apps.

Windows Azure works across multiple frameworks and languages. It is fully scalable, localized in that it is hosted globally in many datacenters, and has widespread capabilities with elements of application development, deployment, and management.

Azure is comprised of several different service modules, including Infrastructure; Web; Mobile; Dev & Test; Big Data; Media;Storage, Backup & Recovery; and Identity & Access Management.

Microsoft Azure works as a:

  1. Platform as a service (PaaS)
  2. Software as a service (SaaS)
  3. Infrastructure as a service (IaaS)

Microsoft Azure is available:

  • On-premises
  • Hybrid
  • Multi-cloud
  • At the edge

Compared to its competitors, Microsoft Azure:

  • Has more affordable features
  • Has easier migration for organizations already using other Microsoft tools
  • Has several educational resources available
  • Provides robust support
  • Is ideal for small and large businesses

Microsoft Azure Features:

  • Scalability
  • Stability
  • Flexibility
  • Azure Site Recovery
  • Active Directory
  • Monitoring features
  • Cloud-based
  • Automated tasks
  • Change capability cadence
  • Showback capabilities
  • Information protection
  • Azure Data Lake
  • Excellent portal
  • Intuitive user interface
  • Remote desktop
  • Fast provisioning
  • Data security
  • Data resiliency
  • Speed of service
  • Integrated delivery pipeline
  • Disaster recovery
  • Robust templates
  • Flexible coding languages
  • Virtual systems testing

Benefits of Microsoft Azure:

  • Infrastructure as a Service (IaaS): Because Microsoft Azure is an IaaS, organizations can deploy as well as manage applications easily and quickly. Azure also provides you with the ability to customize the cloud software to meet your specific business needs.
  • Seamless integration: Microsoft Azure is built to seamlessly integrate with existing IT departments via hybrid databases, secure private connections, and storage solutions.
  • Cost-effective: Because Azure can harmoniously exist in your business environment with your data center, it is a very cost-effective solution.
  • Analytics support: Azure is designed with built-in support that is used to analyze data and provide key insights. Azure offers Cortana Analytics, Stream Analytics, Machine Learning, and SQL services.
  • Unique storage system: Compared to other cloud services, Microsoft Azure has more data centers and delivery points, which helps create an optimal user experience and also helps deliver content faster. In addition, Microsoft Azure makes it possible for organizations to exchange content across several virtual machines.
  • Enhanced flexibility: Azure provides extreme flexibility by allowing you to choose any level of functionality you require. It also supports many of the same technologies IT teams and developers usually depend on, making it easier for them to manage.
  • Easy implementation: Microsoft Azure is easy and quick to deploy. If necessary, you can change web apps to Azure with almost zero downtime.

Reviews from Real Users:

"It is a flexible solution that is straightforward to use," says the principal consultant at a computer software company.

OmarJ., future datacenter consultant: Microsoft Azure Cloud at a tech company, adds that "The user interface is very nice and makes everything easy to use."

You can build an environment in minutes. It's very good in terms of being an infrastructure as a service, and I found that really fascinating,” says an information technology consultant at a computer software company.

"I think Azure's level of automation to achieve efficiency or agility is valuable. I also like the change capability cadence, the showback capabilities, and understanding what our costs are," says an enterprise architect at an energy/utilities company.

Marco C., Ing. at Wolters Kluwer, says "The valuable features of Microsoft Azure are that it is cloud-based and has good storage. The storage is completely managed by Azure. We do not need to do any patching of security because it is handled by Azure which is a benefit. The solution is fully compatible with the Microsoft technology stack and is very scalable."

"The most valuable feature of Microsoft Azure is it has everything together in one place. It is one large tool with lots of small tools that are updated often," says the owner of a media company.



Microsoft Azure was previously known as Windows Azure, Azure, MS Azure.

Microsoft Azure Customers

BMW, Toyota, easyJet, NBC Sports, HarperCollins, Aviva, TalkTalk Business, Avanade, and Telenor.

Microsoft Azure Video

Microsoft Azure Pricing Advice

What users are saying about Microsoft Azure pricing:
  • "The cost of Microsoft Azure depends on the services that are used and there can be a discount at a corporate level from Microsoft."
  • "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."
  • "The price of this solution is one of the things that attracted us to it."
  • "With every cloud solution, you have to know what you need and the cost can be fine. The price can be a little bit high depending on how you manage your costs, but overall it's still a bit cheaper than an on-premise solution but with the advantage of flexibility. You're always up to date with the software, you only need to use it. You no longer have to be concerned with the on-premise physical security. We do not need to create a data center, it's more convenient for us."
  • Microsoft Azure Reviews

    Filter by:
    Filter Reviews
    Industry
    Loading...
    Filter Unavailable
    Company Size
    Loading...
    Filter Unavailable
    Job Level
    Loading...
    Filter Unavailable
    Rating
    Loading...
    Filter Unavailable
    Considered
    Loading...
    Filter Unavailable
    Order by:
    Loading...
    • Date
    • Highest Rating
    • Lowest Rating
    • Review Length
    Search:
    Showingreviews based on the current filters. Reset all filters
    Assistant Manager at a computer software company with 10,001+ employees
    Real User
    Optimized cloud solution with reliable recovery and fail services
    Pros and Cons
    • "Microsoft Azure is an optimized solution when we compare it to any other particular cloud solution."
    • "There are multiple DevOps solutions and tools available in Microsoft Azure, but most of the time they are either in the build mode, meaning you don't get complete support for them because they are either making changes, or changing the names of the particular services. Sometimes, services vanish from the portal. We are not able to see that. I think they actually change the names of the services."

    What is our primary use case?

    I am a technology consultant and pre-sales cloud solution architect.

    What is most valuable?

    These are the features I have found most valuable with Azure. For any particular cloud world, when we talk about the cloud computing model, it is all about agility, availability, how you are trying to scale up your environment, how you're providing high availability, your disaster recovery mechanism, and what is the service availability matrix that you're following? We then talk about the workloads which are being supported on the Microsoft platform. Then we come to the commercial side of those workloads. For example, if we are trying to migrate the Windows workload, then Microsoft Azure offers a lot of benefits for Windows and SQL licenses. We can include that in the picture while we are trying to draw a comparison between different providers. Because AWS does not provide that DAM facility, though there is something that they provide, but you need to put it on the installs, not on RDS. Make it easy to install.

    The second thing about Azure is that if we talk about Gartner, IDC and Forrester, although AWS is leading the chart in the leader's quadrant, when we look at the recent growth and what companies are acquiring and how much business they are pulling in year to year, there is a greater spike in the Microsoft Azure growth as compared to AWS.

    I have worked as a cloud solution architect in India and Microsoft Azure works on data centers. They have three different geographical locations where they put the data centers. So as per the ISO 27001 BSI compliance for DR, disaster recovery mechanism, you need to make sure that the primary and secondary data centers are separated by a geographical zone - which Microsoft Azure adheres to. That definitely makes it a good choice for the client who wants the data to be in India and to also follow the BSI compliance.

    Other factors include the Azure Site Recovery. The ASR one-stop DR solution provides RPO and RTO. It also gives you failover and failback scenarios. AWS did not have that kind of platform earlier. They had DM, DMS and SMS for small scale and medium scale app and database migration, but they didn't have a one-stop DR solution. They recently acquired cloud in their platform. Microsoft Azure also recently acquired cloud. They have built that particular platform into their Azure Migrate, which is their cloud feasibilities function provider. If we need to do a feasibility assessment or dependency mapping, we can use that particular tool or the Azure Migrate. It's a very good tool. I use that tool for multiple things.

    I am trying to draw a comparison between the two leading cloud providers.

    When we try to do backup scenarios, Azure Site Recovery is supported with all kinds of platforms. But it is not capable when you are trying to do recovery of a database or a recovery of an application server which are already on HA, high availability. HA would mean that you have only done the clustering. If there was clustering there, then definitely the ASR does not support it. But if you don't have HA, if you don't have the clustering done, then definitely ASR would be supported in that particular scenario. You can also do big database migrations with the Azure Site Recovery if there is a single database. Otherwise, you can use native database solutions to migrate them to cloud. For example, SQL Enterprises uses the Always On, where you introduce a new machine into the clustering. Then you try to put that as a secondary, and then you migrate.

    Otherwise, if you have SQL Standard, then you can use a log sheet mechanism, which can be used to migrate the data. For SAP HANA, you can use HSR, HANA Service Replication, and for Oracle you can use the Data Guard, the negative solutions supported, but definitely Azure is doing that, as well. When we talk about a typical DR scenario, the cost that you are giving within Microsoft Azure would be storage, then the Azure Site Recovery cost, and then the network readiness. Microsoft Azure is an optimized solution when we compare it to any other particular cloud solution.

    What needs improvement?

    In terms of what could be improved with Azure, I would like to see something like what Google has created with their cross-platform solution, Anthos. I would like to see some features like Anthos has. Secondly, there are multiple DevOps solutions and tools available in Microsoft Azure, but most of the time they are either in the build mode, meaning you don't get complete support for them because they are either making changes, or changing the names of the particular services. Sometimes, services vanish from the portal. We are not able to see that. I think they actually change the names of the services.

    For example, they had advanced data analytics in Office 365. They actually removed it and they now include all those features in Windows Defender. 

    One more thing that I would like to say is that AWS works on availability zones. You have multiple availability zones in a particular region, which means that in that particular region you have more than one data center. If any of their single data centers fail, they can do a failover to the next immediate data center, which is in the same region. But in the case of Azure, if the data center fails for one particular region, they need to do a failover to different region altogether, which is separated by a geographical distance. That will be a kind of DR scenario.

    Microsoft should focus on the higher availability of data centers where they can have more than one data center in a single region. I think they have implemented that kind of solution in the USA. They are going to do it soon in Europe and other countries as well, but it still is an upcoming feature. It's not completely built. They need to build that. 

    The second thing which I feel regarding Microsoft Azure in India, is that they have less case studies when we talk about SAP on Azure as compared to SAP on AWS. There are fewer numbers of case studies on the portal. You can't find any. Whereas when you go into the India section for AWS, you will find plenty in terms of SAP and cloud.

    Case studies are not there. If you have case studies, good case studies of large banks or any kind of government sectors, those case studies would definitely help to build customer trust on that particular platform.

    There is one more thing which I would like to talk about in terms of costing. When you talk about AWS, they have three different types of costing models - partial upfront, no upfront, and all upfront. Azure has two models, all up front and no upfront. But also in these costing models, AWS has multiple other payment modes in terms of one-year or three-year. Azure does not have that. It lacks that particular costing mechanism, which it needs so there are more costing models. There is a lack of pricing flexibility, and I would like to see more costing models and licensing.

    The third thing I would like to say, is that Azure was pretty bad in terms of the recent service off-time for Microsoft Azure and AWS. They didn't complete 99.99% of service they provide to the customers as compared to AWS. AWS data centers have also gone out recently, I think, four or five service interruptions, but definitely Azure should be keeping that in mind. I think with the help of clustering data centers in a single region, they can achieve that.

    I do not want to take any credit away from Azure or AWS, but definitely Anthos is a big plus point for DCP. Azure should also build that kind of platform. Secondly, they can work on creating more data centers to build the regional availability,  which AWS already has across geography. The third thing they can work on is their costing models and the RI models - make them a bit more flexible for the client.

    For how long have I used the solution?

    I have been working on Azure for the past seven years.

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

    What do I think about the stability of the solution?

    Regarding stability, Azure is doing well in terms of IES portfolio. They need to progress on the implementation of more data centers in a single region, which would increase their service level agreement by a little. They definitely need to work on their DevOps services. AWS' DevOps services are pretty good. If you go into ratings, the leading raters or the leading magazines, Forrester or Gartner or IDC, rate AWS services much higher compared to Azure. So, they need to increase on their service.

    The third thing on the stability factor is that they publish more cases on the core infrastructure migration, the mission critical applications like SAP migration or Apple migrations. Putting the case studies on the portal would alleviate the doubt that Azure is stable. Azure is stable, but the case studies have to be there to support that.

    What do I think about the scalability of the solution?

    When we talk about scale and scale out mechanisms, this works pretty seamlessly in Azure. For example, if I need to use the spot instances that AWS has (spot instances are those instances which are actually created at times when you need a high memory or a high CPU for some time) you can configure a spot instance and the spot instance occurs, and it does the load checkpoint. Azure does the same thing with scaling out. However, one thing regarding RI is that AWS does not support that, but when I am in a particular RI, for example my family is the DS series, I am in DS3 or DS4, if I want to scale up, I can scale up with the same RI, but if I need to scale down, I cannot scale down unless I remove that RI and create a new one. I cannot scale into a different family altogether.

    Cross-family scaling is not there. Cross-family scaling would help because sometimes being on cloud machines which are in RI, those machines have been used for one year and are currently a very small application host or they are hosting applications or IA services, etc... Now, that particular application has been, or is getting decommissioned, and the company wants to leave the same RI machines for a different application altogether for which they want that particular application to perform on a higher computer issue. For that particular thing I need to cancel that RI and with the remaining my budget, and with the call deduction that Microsoft does, I need to purchase a new RI. If the cross-family RI is there, then it is definitely smoother, and the priority won't be there. So, it will not be an economic blow for the company.

    How are customer service and support?

    When you open a normal case, Azure has a response matrix. They don't have a resolution matrix - at what particular time that will be resolved. The maximum resolution matrix is not there. But when we talk about the premium support, then Azure has a response matrix and a resolution matrix, and they also have the escalation matrix.

    When I was working in Progressive Infotech, we had the advanced support subscription with Microsoft Azure Support. We were given multiple hours of advanced support. We were also provided with other things. I felt then that when you're opening a support ticket, and the support ticket priority is less or if the ticket that you opened is not in the premium bracket, the resolution will be late and the support matrix won't follow the time. They have a response. I think the response matrix is there for basic support and for advanced support. Premium support has the resolution matrix, as well. But the support center needs to have a service level agreement, which has the response matrix, the resolution matrix, and escalation matrix. That will build more trust from the partners in the OEM. AWS actually does not have that, but their response and resolution are pretty good because all the cases that you open in AWS are paid.

    How was the initial setup?

    Azure materials are pretty good compared to AWS, or any other platform materials. Azure has multiple platforms, and MS Learn is where you can learn about the platforms and the services. Then you have Docs.Microsoft.com, which you can use as a troubleshoot document or understanding of how to implement that solution. With the help of Microsoft Azure, the Microsoft platform, you have multiple types of cases which you can open in the Microsoft Portal. The premium cases are there. Then you have support cases, as well. Azure is pretty good there. Their support matrix is pretty good. The materials are there, the support matrix is there. So, that is pretty good.

    What other advice do I have?

    Microsoft Azure has multiple levels that an organization can take. Once they had the silver, bronze and the gold partnerships, and in terms of the productivity there is the Office 365 suite or the Azure suite, and they have specialty certifications, as well. You have the premium certifications. If you are also providing support to the client, then as a manager you can join Microsoft as an expert MSP. I think there are 50 or 55 in the country. It started at 15, and it grew to 55. Because many companies who are putting out tenders or an RFP or RFQ, mention in the PQ criteria that the partner should be MSP certified.

    It would definitely help. It would act as a USP for you because there are multiple companies in India, more than hundreds and hundreds of companies in India and outside India. The customer would know the first company which is an expert MSP and the Microsoft partners would also give the lead to those export MSPs. Currently, you can also elevate the level by being on a fast track team, which is a one-stop team for Microsoft implementation and support for the Office 365 platform. The fast track team can be a very good asset because you can get a faster certification and then you сan be on the fast track board. You can actually make money when you do a successful implementation or support for a particular client. So the value is there.

    On a scale of one to ten, I would give Microsoft Azure an eight.

    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

    Microsoft Azure is the #1 ranked solution in top Infrastructure as a Service Clouds and PaaS Services. I like it ,its easy to use.

    See all 13 comments
    Business Development Executive, Managing Partner at a tech services company with 1-10 employees
    Real User
    Very reliable IaaS and DaaS, but quite complicated inside.
    Pros and Cons
    • "In terms of scalability, it is perfect."
    • "Microsoft Azure is so complicated inside. If you should do something internally, if you have to configure something, the opinion about Azure is that it is a little complicated inside. That's why the end users and clients are looking for help and why we help them configure and do anything inside of Azure. That is why we offer other tools to optimize the Azure environment."

    What is our primary use case?

    I know Azure. We have the tools for optimized Azure infrastructure. As a partner, as an active integrator, I am looking only for plays to make the deal. I am not an end user, prospector or client. I use it in my projects but I am not buying any solution from Microsoft for ourselves. I am the seller.

    When I talk about the Infrastructure as a Service from the Microsoft, I am referring to a hybrid infrastructure. We are talking about the moving of virtual machines and workload from on-premise system to the Cloud. This is my main topic when we are talking with the client. My technical team worries about the details of how we do this. I am not so good in the technical details.

    In terms of our customers' use cases, in our last project, the customers migrated the SAP system from on-premise to the Azure with SQL as a database. We helped the customer to compare on-premise infrastructures and Infrastructure as a Service in Azure, and to help them migrate the machines, the tech, and the servers from on-premise to the Cloud and to have the tools from the Quest to help them optimize because they did not want to pay so much. They only wanted to pay by use. We are looking for the perfect tier from Azure to finish the project. This was our job. That's why I like the Azure.

    There is not too much perfect information out there about how to optimize the infrastructure. Microsoft is looking for the bills where the sky is the limit but the customer is looking for the real cost. We help the customer and we have the answers regarding which tier or which configuration in Azure is proper for them.

    What needs improvement?

    Microsoft Azure is so complicated inside. If you should do something internally, if you have to configure something, the opinion about Azure is that it is a little complicated inside. That's why the end users and clients are looking for help and why we help them configure and do anything inside of Azure. That is why we offer other tools to optimize the Azure environment.

    Microsoft makes the space for such tools because it is a little complicated and end users know it. That's why we sell these tools to optimize the Azure. I think the Microsoft team knows this and they create the space for other third party partners.

    I know all the points about how the Cloud is so beautiful but if somebody starts to do something inside the Azure, it is a little hard to understand. Many services are so complicated to configure out. That's why sometimes clients are obviously confused inside the Azure. That's why they are looking for help with it and why they are looking for a Microsoft partner with the knowledge of how to connect this software into one solution. From my perspective, I like Azure because it makes me money from the end user clients. But for the customers, their opinion is, "Oh, my god. The AWS is easy."

    It is well-known that Microsoft is not so easy for the end users. Maybe it's because there is a note of everything changing. They add new features and new functionalities. Azure is growing. From my point of view it's okay. From the customers, it's also ok, but they are looking for someone who understands how to configure it.

    From the beginning, the first move to Azure as a solution, it's a long journey with many, many services to find the final configuration for the customer. But it's okay for me.

    What do I think about the scalability of the solution?

    In terms of scalability, it is perfect. If you are a rich partner or a rich company and you have a lot of money on your credit card, the scalability and the possibility of using Azure is a perfect play. If you want two servers, if you want 200 servers, it's one click. From the marketing point of view, it's the perfect place to spend the money. I think the customers are really worried about the cost. If you request a lot of machines, it's only one click in the setup but the bill for that is so huge. They ultimately worry about how to prepare their production environment just for us. Not for the sky is the limit but for our requirements to help. We have tools for monitoring consumption of the Azure and we can switch virtual machines off when at the end of the day. Customers are happy that we offer that because they are a little worried.

    For example, if you buy one huge service for your on-premise project, you pay for that one service. But if you put a development team on the project and they request a lot of virtual machines because it's so easy to deploy, someone should pay for that. This is literally one big worry from the client side.

    The calculator from Microsoft for Azure is very basic. This tool only shows what you consumed and what you will pay. There is no answer if you want to know how big a credit card you need to run the project. We make money answering exactly how much you really need for your project. We save the budget for the customer. We find opportunities for Microsoft but when the customer is worried, we help them. It's also good for Microsoft because they run the project.

    How are customer service and support?

    We have support but Microsoft is trying to cover only Azure as an infrastructure.

    They are not interested in talking about current applications or current systems from a customer perspective. This is the job for the partner. Microsoft covers only the chief environment. The job for the partner is caring about the customer's real needs. That's our job.

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

    We only have experience with AWS because for us it doesn't matter whether we run virtual machines on AWS or Azure. If the client is only looking for power servers, then the machine they are looking for is AWS. If they are not only looking for IaaS, Infrastructure as a Service, but are also looking for the DaaS or Database as a Service, they are looking for Azure. It is exactly the same way for customers that are using SQL Server. The first choice is Azure.

    If you are looking for Oracle, they're thinking about AWS. Of course, if we are talking about the containerization, about the Kubernetes, AWS is also the first choice for our clients.

    How was the initial setup?

    The initial setup depends on the project. Because we are the Microsoft partner and we have some money for our internal tests we do the setup part. We use Azure infrastructure for our demo when we show our virtual demo machine. For my colleagues, it's not so complicated but we are using only a very small part of Azure.

    When we talk about the real project, it is not so easy. We are using a very basic functionality, but I know from the other projects that it is not so easy to implement, run, test, et cetera because it's always a little complicated. Maybe it's okay. It depends on the current customer's needs.

    What was our ROI?

    ROI is a very tough topic because with the first step, every customer is trying to compare what they pay on the infrastructure and what they will pay in Azure. This is never the same number.

    The challenge is to show to customers the added value because Azure is not only a different type of data center, but is also a place where you can make the innovations and add some new services. It is much easier than on-premise. We have a lot of ready-to-use functionalities on Azure, but the magic is how to use it.

    Sometimes, the customer does not have the knowledge to create new value for the business using the ready-to-use functionality on Azure from the Microsoft offer. This is the challenge.

    Moving the one virtual machine is easy but knowing how to run your business application for the customer, this is the main challenge.

    What other advice do I have?

    My advice to anyone considering Azure is if they want to make jumping to the Azure or to the Cloud easier, they should focus on and discuss what the steps are. When you are on premise, figure out the development and how to configure it to the Azure. I have had so many marketing presentations from Microsoft saying, "Oh, it's easy. You have the Advisor. Blah, blah, blah." This is pure marketing. The clients know it is only a commercial about Azure. If Microsoft wants to really get customers, they should help them step by step by showing them how it is easy and how to control every step of the project. They should care more about the customers during this type of project. If you did 10 project delegations, the next one is much easier, but the first is really not so easy. That's why customers are afraid about migrating to the Azure. "What about the bills? What about how to administrate? How long to build the infrastructure?" There are a lot of questions from the customer side.

    On a scale of one to ten, I would give Microsoft Azure a seven. That is because there is always space for improvement. For me it's okay. It's reliable and it really works.

    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

    Windows Azure is Microsoft's cloud platform, where developers can create, deploy, and maintain their apps. Very useful and helpful app. You all can go for it.

    See all 3 comments
    Buyer's Guide
    Microsoft Azure
    May 2023
    Learn what your peers think about Microsoft Azure. Get advice and tips from experienced pros sharing their opinions. Updated: May 2023.
    710,326 professionals have used our research since 2012.
    Ing. at Wolters Kluwer
    Real User
    Top 20
    Limited maintenance, good interface, helpful support
    Pros and Cons
    • "The valuable features of Microsoft Azure are that it is cloud-based and has good storage. The storage is completely managed by Azure. We do not need to do any patching of security because it is handled by Azure which is a benefit. The solution is fully compatible with the Microsoft technology stack and is very scalable."
    • "The solution should improve the shared cache. For the shared cache, Microsoft uses RADIUS third-party services. We have a lot of trouble with RADIUS and I suppose that is due to the fact that is not owned completely by Microsoft."

    What is our primary use case?

    Our target markets are advisors and all the staff they need to manage for their customers, such as regulatory information, accounting tax, tax income, tax regulation, accounting, balance sheets. We have also targeted different niche countries. It's a very regulated market and these are our principal customer.

    At the corporate level, we have another division. That does not produce or sell software, but content, normative content, educational content.

    For the software division, we work with advisors and payroll consultants.

    How has it helped my organization?

    Microsoft Azure has helped organizations because they no longer need to do a lot of server maintenance.

    What is most valuable?

    The valuable features of Microsoft Azure are that it is cloud-based and has good storage. The storage is completely managed by Azure. We do not need to do any patching of security because it is handled by Azure which is a benefit. The solution is fully compatible with the Microsoft technology stack and is very scalable.

    All the Microsoft Azure's interface for managing the portal is very good and responsive.

    What needs improvement?

    The solution should improve the shared cache. For the shared cache, Microsoft uses RADIUS third-party services. We have a lot of trouble with RADIUS and I suppose that is due to the fact that is not owned completely by Microsoft.

    For how long have I used the solution?

    I have been using Microsoft Azure for approximately five years.

    What do I think about the stability of the solution?

    Microsoft Azure is highly stable.

    What do I think about the scalability of the solution?

    Microsoft Azure is scalable in my experience.

    We have approximately 400 customers with many terabytes of data. We have some customers that are using this solution that has 400,000 customers.

    At the moment our product is intensively being used by the advisors that are onboarded because our software is the primary tool for the advisors.

    How are customer service and support?

    If we have a problem with Microsoft Azure we open a ticket with Microsoft and they respond very quickly and are very helpful.

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

    I have previously used other solutions but nothing comparable to the Microsoft Azure cloud solution.

    We chose Microsoft Azure because it's tied to Microsoft technologies. We are already working with Visual Studio and other Microsoft technologies, such as .NET, and other on-premise products. The migration path is all shorter and our corporation suggested using Microsoft Azure.

    How was the initial setup?

    The initial setup is difficult because when you move into a fully managed cloud environment with a lot of services, you change your mind completely about how you operate and in the first month we had to learn a lot of tasks.

    Looking back to the past the difficulty was not the interface of the solution, there was a lot of information to know and to have knowledge about concepts for cloud service that took time. There was a lot of documentation and finding the correct one can be difficult sometimes. When I used Google to find something, I can find a lot of information but the problem is to find the current information or the most effective information.

    There is a lot of different elements you need to set up or configure, such as the environment, monitoring, deployment of applications, preparing the dashboard for monitoring, and the continuous development integration by clients.

    We have two kinds of deployment, a continuous integration deployment when we don't change the database schema. This is fully unattended and can be done online with no problem for the users. It takes approximately 30 minutes but the time can vary.

    Once a month, or less, there is a major release. In this case, often we modify the database schema. This requires stopping all the applications, no user can have access while the modification to the database is taking place. The operation takes from half an hour to an hour and a half depending on the database schema and the types of modification required. When we change the structure of tables we have hundreds of thousands of records that can take a lot of time.

    We are moving to a more continuous development strategy. We are trying to have more applications because at the moment we have approximately seven web apps and a lot of services, but they are too tightly bound to the database. They're trying to divide them for more flexibility and to have continuous deployment. We had no continuous deployment. Normally we deployed some minor releases once or two a week, and there is a major release once a month. We are moving to have more continuous deployment.

    We are working this year on test automation from unit test integration. They're investing a lot in this because we managed numbers for the tax declaration. Regulation can be problematic.

    What about the implementation team?

    We are producing, maintaining, and are selling solutions for our customers, such as Microsoft Azure. We do not use an integrator.

    We have a two-person team that does the implementation and maintenance of the solution. Once you prepare the infrastructure, sometimes we have to improve by changing some things. Recently we had to prepare for the disaster recovery from Europe to Europe, and we had to invest time in the pipelines and deployment.

    What was our ROI?

    When you have on-premise solutions you have to manage lots of aspects, such as security, patching, large expense, and acquiring hardware and servers. With Microsoft Azure, you have the ability to activate a lot of processing power and then dismiss it when you do not need it. It saves you a lot of money not have to have the infrastructure or the maintenance. 

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

    The cost of Microsoft Azure depends on the services that are used and there can be a discount at a corporate level from Microsoft.

    What other advice do I have?

    In the next release of Microsoft Azure, they will be addressing the problem of the continuous  ETL workload to continually extract the data and ingest it in a docker analysis database. This will be released in the next version released in 2022. Microsoft Azure is continuously improving the solution for the market.

    It is important to know that cloud services work differently than on-premise solutions.

    I was talking with our colleague in the internal department to let me test the scalability of his system because we have a process from our application to the online shop. They are having a problem with the scalability test because of their hardware. They have hardware that they can't scale the testing environment. Using Microsoft Azure we do not have these issues because it is on the cloud.

    I rate Microsoft Azure a nine 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

    Great, an amazing organization to work with. You did a great job guys very very good.

    See all 2 comments
    Technical Program Manager at a university with 201-500 employees
    Real User
    Top 5Leaderboard
    Dynamically scales our enterprise application up and down, and security features give our users confidence
    Pros and Cons
    • "The scalability is the most unique feature. Whenever our user count is high, and utilization of our application results in high use of resources, Microsoft Azure automatically scales our application so that users can access it without any issues or errors. Microsoft Azure gives you the flexibility to scale your applications up and down at any moment. It is quite easy and impressive."
    • "Customer services and support should be improved. If a user faces challenges in accessing Microsoft Azure, the support team takes time—it could be 24 to 48 hours—to resolve them. We need solutions in four to five hours. And there are business-critical issues where we need an immediate resolution."

    What is our primary use case?

    We have deployed our enterprise application on Microsoft Azure and we are using it for our day-to-day operations and management of that application. The application has millions of users, mainly from the EMEA region, and serves our clients as well as our internal users.

    How has it helped my organization?

    Previously, we had legacy applications hosted on-premises, and that setup was very limiting for our users. When we migrated our application to Microsoft Azure, users gained the flexibility to access the application from anywhere and at any time.

    The benefit from the business perspective is that with a large user base, the users are very happy. The feedback from our end-users is that there are no issues in accessing the application. It can be opened anywhere. Also, the timely updates and the security features make it very effective in protecting against vulnerabilities, security threats, and any third-party attacks. Users feel very secure when using our application.

    What is most valuable?

    The solution is very 

    • reliable
    • scalable
    • secure.

    The scalability is the most unique feature. Whenever our user count is high, and utilization of our application results in high use of resources, Microsoft Azure automatically scales our application so that users can access it without any issues or errors. Microsoft Azure gives you the flexibility to scale your applications up and down at any moment. It is quite easy and impressive.

    Additional features that we have found to be very useful are the data security and capacity management.

    Azure also provides features such as storage, computing, and networking in the cloud. It offers a wide range of services, such as financial analytics, Azure Data Factory, and Azure Firewalls, and these help our application to run smoothly.

    The built-in Microsoft Firewall secures our application in a very unique way.

    For how long have I used the solution?

    We have been using Microsoft Azure for more than three years.

    What do I think about the stability of the solution?

    The stability is perfect. We have found no issues yet when using Microsoft Azure.

    What do I think about the scalability of the solution?

    Our concurrent user count is more than 1,000. Our users include product owners and project managers, as well as our consulting and marketing teams. It is used 24/7.

    We plan to increase our usage of the Microsoft Azure platform. Our project requirements are quite large as we are now moving to data analytics and big-data analytics. We need to procure services from Microsoft like financial analytics and Power BI.

    How are customer service and support?

    Customer services and support should be improved. If a user faces challenges in accessing Microsoft Azure, the support team takes time—it could be 24 to 48 hours—to resolve them. We need solutions in four to five hours. And there are business-critical issues where we need an immediate resolution.

    Otherwise, the technical support is good. They are understandable and they are familiar with the product.

    How would you rate customer service and support?

    Positive

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

    We did not have a previous cloud-based solution. We had legacy applications on-premises.

    How was the initial setup?

    The initial setup is quite easy. Azure's consulting and business team is very effective and helpful. They helped us understand the product's features. They provided us with a clear roadmap for migrating our application to Microsoft Azure, for the services they offer, and for how the business could be run successfully.

    The deployment took about three months. Our implementation strategy was simply to work with the vendor.

    We initially assigned five to six people for the end-to-end deployment. After the initial implementation, when the Microsoft team left, we needed some resources who could handle the management of the Microsoft Azure platform. Those resources are in place in case our application goes down or there are issues that require them to directly contact the Microsoft team. But all the support and security updates are managed by Microsoft.

    What about the implementation team?

    Microsoft has its own solution architects and consulting team to help you. That makes it easy as it doesn't involve third-party integrators and saves us the money we would be charged for third-party services.

    What was our ROI?

    We have definitely seen a return on investment because our previous, on-premises, legacy application was very limited for our users and clients. Since migrating to Azure, we have clear visibility into our application and users can use it from any location. Our return on investment has been very positive.

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

    The pricing and licensing are quite good. We had no issues with them because they were clear about the pricing, subscription, the number of users, and how much the charges would be per month. 

    Pricing depends on the services you are using from Microsoft Azure. Also, some services are only deployed in the U.S. region, while others are available in the Asia-Pacific region.

    Which other solutions did I evaluate?

    We evaluated AWS and GCP, but Azure's features and services matched our requirements better.

    AWS had similar options, but their prices were higher, and they didn't have the same regional availability. The bandwidth and the data-processing charges were quite high with AWS, compared to Azure.

    What other advice do I have?

    I highly recommend this solution to any prospective buyer. If you are using other Microsoft applications like Microsoft 365, Power BI, Data Factory, or Azure Migrate, you will definitely find it useful. Azure is fully integrated with other Microsoft applications, as well, including Microsoft Office, Microsoft Project, and Microsoft SQL Server. Microsoft Azure is an all-in-one solution.

    We are feeling very secure hosting our application on Microsoft Azure because Microsoft is a global giant and provides excellent solutions and services.

    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    PeerSpot user

    The scalability is the most unique feature. Whenever our user count is high, and utilization of our application results in high use of resources, Microsoft Azure automatically scales our application so that users can access it without any issues or errors. Microsoft Azure gives you the flexibility to scale your applications up and down at any moment. It is quite easy and impressive.

    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
    Deborah Gamelin - PeerSpot reviewer
    Vice President at Asset Track for Cloud, LLC
    Real User
    Top 5
    Flexible, easy to manage, and good training material is available
    Pros and Cons
    • "In Azure, everything is pretty straightforward. Once you know it, the platform is very easy to use."
    • "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."

    What is our primary use case?

    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.

    What is most valuable?

    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.

    What needs improvement?

    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.

    For how long have I used the solution?

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

    What do I think about the stability of the solution?

    Stability-wise, it has been fine.

    What do I think about the scalability of the solution?

    Azure is a scalable platform.

    How are customer service and support?

    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.

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

    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.

    How was the initial setup?

    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.

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

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

    Which other solutions did I evaluate?

    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.

    What other advice do I have?

    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.

    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    PeerSpot user
    AlanGulle - PeerSpot reviewer
    Data SME at Sparta Global
    Real User
    Top 5
    Highly secure, fully integrated, and helpful support
    Pros and Cons
    • "The application services are the most valuable in Microsoft Azure. I'm not using them directly but I am using the function and the web applications. I don't need to pay a lot for the maintenance. I do not need to have a DevOps employee."
    • "The documentation can be outdated and is not as clear in Microsoft Azure as it is in AWS or Google."

    What is our primary use case?

    We deploy all of our projects in Microsoft Azure. We are a startup company. We have been since the beginning deploying our code in Azure cloud. We are actively using the full capabilities of two cloud services.

    What is most valuable?

    The application services are the most valuable in Microsoft Azure. I'm not using them directly but I am using the function and the web applications. I don't need to pay a lot for the maintenance. I do not need to have a DevOps employee. 

    I am familiar with Google, and everything I was doing was in Google. I had to control my back proxies and do my own configuration files. With Microsoft Azure, it is all easy.

    What needs improvement?

    The documentation can be outdated and is not as clear in Microsoft Azure as it is in AWS or Google.

    For how long have I used the solution?

    I have been using Microsoft Azure for approximately four years.

    What do I think about the stability of the solution?

    The solution is stable. 

    It's easy to monitor, there's no problem with the code in their development. We had some stability issues, it was not the fault of Microsoft Azure, but it was the mistakes of the developers. It was easy to monitor it in Azure.

    What do I think about the scalability of the solution?

    Microsoft Azure is highly scalable.

    On only one web application I created with one service plan I can connect 10  projects. Imagine one machine can run 10 projects at the same time because whatever the project has more requests or demands, it will scale its machines and auto-scale down. This is why it makes it affordable. I can control which project is demanding more computing power or storage power.

    We have approximately 50 people using this solution in my organization. It is mainly back and front developers.

    We are drastically increasing our usage because last year we were running 13 projects, and now 19 projects. In 2022 we are trying to double our team.

    How are customer service and support?

    The support could improve. For example, Python is needed for Microsoft Azure,  and the lack of documentation for the community is a problem. If you are a Python developer Microsoft Azure released an update to Python at the end of May 2021. Theoretically, I can use it with Python, but if I have a problem I need to call a Microsoft engineer to solve it. It takes some time. However, I did receive very good support from the Microsoft engineers to make my system production-ready, but language support for Python and other languages is coming late.

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

    I have used other solutions, such as Google and AWS.

    When comparing these solutions to Microsoft Azure, AWS has better documentation, Google's cognitive services, and predictions give better results, and Microsoft Azure has the best UI. If you want to reach the database of Google, there is no such SQL manager UI. Microsoft Azure UI is easy to use and has great tools.

    How was the initial setup?

    The deployment's easy and the pipelines are easy from the Azure DevOps, everything is integrated and it has good security. The overall setup is extremely easy.

    What about the implementation team?

    We have a team in London that is maintaining the solution. We have 450 backend developers at this site and approximately five people are looking after all the maintenance and admin roles. We have database and developers administrators that are giving access to the people for the production maintenance. 

    What other advice do I have?

    I am very happy with the solution.

    Thanks to the training I have received from Microsoft Azure, which cost £60,000, I'm up-skilling all my team for the certification, databases, and machine learning tool. Every month I'm receiving approximately £1,000 from the training credit for the up-skilling.

    It is simple to start with Microsoft Azure if you know the application life cycle. You can try so many things without any cost because of the serverless system. You will not be charged for any request at the beginning. For example, you are creating a function application in Azure the first 10,000 requests are free. It is great because you can anyone a developer to test anything.

    They're not using very heavy machine learning systems, the system is generally cheap. For example, they are giving a free month trial and a developer can't finish it personally if they do not use a large computing machine.

    At the moment they are adding new features faster than I expected. For example, they have Python support but five years ago there wasn't any Python support. They were slow at the beginning but now it updates very quickly. For example, the community services for the low code, no code power platforms, and the power platforms.

    I spoke to my developers, machine learning engineer, data engineer, and data scientists and told them please use the auto ML or the community services better. As a London business user site team, we can create all the virtual agents and AI builders with the no code platform for the machine learning models for the power applications. The auto ML is very powerful and you don't need to be an expert in machine learning.

    I rate Microsoft Azure a nine out of ten.

    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    PeerSpot user
    Owner at a media company with 1-10 employees
    Real User
    Multiple tools available, updated often, and performs well
    Pros and Cons
    • "The most valuable feature of Microsoft Azure is it has everything together in one place. It is one large tool with lots of small tools that are updated often."
    • "There is a need to be better on-premise solutions that are more helpful. However, I don't think that is the goal of Microsoft Azure. They want the solution to be secure cloud solutions with cloud applications. This is their main goal at the moment."

    What is our primary use case?

    We are using Microsoft Azure mainly for our test environment. Addiotanlly, we use it for our enterprise resource management as we have installed a SaaS solution.

    What is most valuable?

    The most valuable feature of Microsoft Azure is it has everything together in one place. It is one large tool with lots of small tools that are updated often.

    What needs improvement?

    I have found that if you not working with Microsoft Azure's GUI every day, it's not very user-friendly. It changes very often and fast. They are implementing new functionality. If you're not working with it every day, it always takes you additional time to get acquainted with the GUI. You always have to know all the tools because it's one software solution where you work with different kinds of tools to achieve results by implementing policies and other parameters. It would be better if they had everything in one place so that it is clear what type of operations we are doing, such as DLP. However, that's is how it is with all of the tools of Microsoft Azure at the moment.

    There is a need to be better on-premise solutions that are more helpful. However, I don't think that is the goal of Microsoft Azure. They want the solution to be secure cloud solutions with cloud applications. This is their main goal at the moment.

    For how long have I used the solution?

    I have been using Microsoft Azure for approximately five years.

    What do I think about the stability of the solution?

    The performance of Microsoft Azure depends on whether you have good bandwidth for your data connection, if the connection is strong then the performance is good. If you have a very poor connection, then it's can be a little slow, but has been okay.

    What do I think about the scalability of the solution?

    We have one administrator and one system engineer that are using the solution. They are doing the administration for our solution. We're not a big company, we have 19 employees.

    We haven't tried to scale Microsoft Azure. It's not necessary for us to scale it at the moment. We have started out with one issue where we needed it and for very sensible documentation, now we are using it in different kinds of projects. For example, for many types of data classifications.

    If it's necessary we will increase usage. Otherwise, we will keep the same amount of usage.

    How are customer service and support?

    The technical support of Microsoft Azure was helpful. They were very good because they spoke the same language as we did. We both spoke German. It worked very well, we have no complaints.

    How was the initial setup?

    Some of the aspects of the implementation of the solution are very easy if you know which tool you have to use. It's not too complicated if you know which tool you will be using but to find the right tool to do the necessary functions sometimes takes some time. I'm not doing the setup every day. I have one engineer that it is his job. But nevertheless, I also want to do the setup to know how it's working.

    I am not sure how long the implementation took for our DLP project, once we started the implementation we started to use other tools and eventually returned to the main project.

    What about the implementation team?

    We did the implementation internally.

    We have one engineer that is administrating and supporting Microsoft Azure.

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

    With every cloud solution, you have to know what you need and the cost can be fine. The price can be a little bit high depending on how you manage your costs, but overall it's still a bit cheaper than an on-premise solution but with the advantage of flexibility. You're always up to date with the software, you only need to use it. You no longer have to be concerned with the on-premise physical security. We do not need to create a data center, it's more convenient for us.

    Which other solutions did I evaluate?

    Some of our customers are looking for on-premise solutions other than Microsoft Azure which is cloud-based. We help them find the solutions they need.

    What other advice do I have?

    My advice to others thinking about using this solution is to try it out. There are features which are very good and some other features where you should watch out but that's for every solution, you have pros and cons. When you're a small company, try everything out that is offered by Microsoft because they're one of the best. Microsoft is still the market leader in a lot of fields. I would suggest using Microsoft tools if they fit the relevant use case. If the solution does not fit the use case, or you need more security or other aspects, then you can look around for other tools. additionally, on the marketplace, Microsoft provides enough other tools you could use.

    I rate Microsoft Azure an eight out of ten.

    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: May 2023
    Buyer's Guide
    Download our free Microsoft Azure Report and get advice and tips from experienced pros sharing their opinions.