Microsoft Azure Reviews

I am a business development director who helps my clients by providing solutions during their digital transformation journey. I am a reseller of Microsoft Azure. My clients use this solution to host their data on the cloud and to have a secure database.

This is a very stable product.

I would like to see more automation and AI with the cloud to help the clients understand more about their clients, their data history, and their predictive analytics. This would help them better manage their clients.

I have been using this solution for almost four years.

The solution is stable.

The solution is scalable. Some of my clients have thirty users while others have more than two hundred users.

We have received very good support from Azure here in Jordan.

The initial setup is quite complex and took about six months.

Azure may seem intimidating but you will get use to the product the more time that you spend working in it.

I would rate this product a nine out of ten.

Microsoft Azure assists in lowering the cost of on-premises infrastructure as well as improving performance.

The most valuable aspect of this solution is its ease of use.

It is quite easy to configure, including the resources.

We don't have any expectations. We have recently stabilized our application in terms of moving to the Cloud. We are still exploring the features available in Microsoft Azure, so determining what could be improved is difficult.

More integration may be required in the future, but I don't believe it is necessary for us at this time. We would be working with a hybrid platform more than anything else.

From a security perspective, there is always something that can be improved as we serve our customers.

I have been using Microsoft Azure for approximately one year.

Microsoft Azure is a stable solution.

Microsoft Azure is a scalable product.

In our organization, we have more than 5,000 employees who use this solution. The organization itself has moved onto the Microsoft Azure Platform.

At this time we will not be increasing our usage.

I have not contacted technical support, but perhaps the infrastructure team has.

All of our applications are developed using Microsoft.NET Technologies. We prefer to use the Microsoft Platform.

Salesforce CRM is a tool that we use internally, as well as Symantec.

For virtual meetings we use Teams.

I was not involved with the initial setup. We have a team of two members to deploy and maintain the infrastructure.

There are no licensing fees.

I would recommend this solution to anyone thinking about using it.

In my opinion, everything is fine, I would rate Microsoft Azure a ten out of ten.

Azure virtual machines are stand-out.

Their backup strategy is a little complex which racks up the VM to other sole storage areas. This should be improved.

I have been using this solution for close to three years.

Microsoft Azure is very stable.

The solution is scalable.

Customer service was very good.

Initial setup was straightforward and flawless.

This was implemented via in-house team.

The pricing is fair and it was actually just reduced. My organization is paying approximately $100,000 annually with close to one thousand users. There are no additional fees.

Azure is user-friendly which is great for those with no code experience, though this limits flexibility.

This is a very simple solution. Their integration with Office 365 is very easy. And for those who are enterprise customers already using Office 365, their role-based access control communicating with Azure is much simpler and easier which allows for full control.

I would rate this a nine out of ten.

Our primary use case for Azure is for workload, database, and service migrations. I use Azure to migrate services to serverless Azure services. Some of the services I utilize within Azure are Azure SQL database, managed database, Cosmos, virtual machines, service accounts, and infrastructure as a code for migration.

I'd like to see improvements with the price calculator tool. I would like to get a forward-looking view of the services I want to cost. For example, if I want a bigger machine with two CPU's and eight gigabytes of RAM, maybe the calculator can allow me to input my recipe, the tool can then give me a list of virtual machines that have that specification, and it will be easier for me to choose the virtual machine I want. 

There are no additional features at this time I can suggest for future releases.

I have worked with Microsoft Azure for 7 years.

Microsoft Azure is very stable, it has a SLA of 99.9%.

The Azure services are very scalable.

Microsoft have varying types of support levels. Depending on what level of support you have , this determines the response time from them.

We implement in-house.

All services in the cloud are easy to set up, the services are ready to use from the outset. For example, it would take me 5 minutes to deploy one virtual machine in Azure, or a Sharepoint cluster may take me 4 hours. The cloud deployments are normally automatic once you start.

Regarding licensing, always look to optimize costs with the use of Azure Advisor.

We use Microsoft Azure and AWS, depending on what the client wants. Some clients like to compare prices between the two, it depends on the workload that my client would like to migrate also.

We are using Microsoft Azure for various databases, file storing, backup, disaster recovery. It's a very useful service.

Microsoft Azure has thousands of services and products.

Microsoft Azure could improve by having the availability be 100%. Which is difficult, but not impossible.

In the future, there should be more automation.

I have been using Microsoft Azure for approximately four years.

The solution is stable.

Microsoft Azure is highly scalable.

Our customers that are using the solutions can have from 100 to several thousand that are using the solution.

We have plans to extend the usage of this solution.

The technical support is very good.

My projects are normally complex. However, the implementation of Microsoft Azure is very simple.

The length of time the full deployment can take depends on the complexity of the project. It can vary from one month to half a year. It depends on the goal of the project.

I would rate the initial setup of Microsoft Azure a four out of five.

My advice to others is you need to be technically aware of Azure services, which are always in some kind of improvement. It is helpful to be aware of the possibility and functionality of your projects and the financial cost for Azure services in the project plan.

I rate Microsoft Azure a nine out of ten.

We primarily use the solution for backups and ASO.

The ASO is great.

We enjoy the disaster recovery aspect of the solution, which is very interesting, as we pay when it is on. When it's off we don't pay. 

There is no effort investment. We just pay what is being replicated, that's all.

There is the potential to scale.

The stability is good.

We've found the technical support to be responsive. 

In a month, there is a plan to increase pricing, which is something we are not looking forward to.

We've worked with the solution since it was first released. We've used it for a while.

The product is very stable compared to if you are going to employ it in-house. There are no bugs or glitches. It doesn't crash or freeze. t's reliable. 

The scalability is good. If you need to expand it, you can.

We are in Mauritius. Mauritius is a very small country. We have about 1.2 million inhabitants. We are not that big of a country. I have about 25 clients using it.

We are an indirect reseller. We do have the CSP, the cloud service provider, in Mauritius, with whom we purchase. When we have an issue, we deal with them. They do have engineers that provide support as well.

That said, if there are any big troubles then we contact Microsoft directly. So far, our experience has been very positive. The callback is within 20 minutes. It's fine.

The initial setup is not simple. You need to be trained. It's not like it's just ready to be implemented - you need to be trained in what you are doing.

The deployment is quick and only takes about one day.

We do get an ROI from the disaster recovery aspect of the solution. 

The pricing is great, as we only pay for what we use. 

That said, the prices are about to increase in the next month.

We do have some clients in South Africa and some clients in Germany, however, we've noticed that the pricing for Germany is less expensive than South Africa. South Africa has a new data center, which is likely why the price is a bit high.

We implement the solution. We are silver resellers. 

We are using the latest version of the solution.

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

We use Azure for a variety of services and we are in the process of configuring everything. We use GoDaddy to host our domain, and then we provision from GoDaddy for services such as email. This is one of the things that I just recently configured.

Right now, we're in the process of setting up the firewall. This provides us with security for the website. Firewalls are something that I have a lot of experience with because, in my previous organization, I dealt with audits and other similar tasks that depend on security.

The most valuable feature of Azure is the flexibility to pick and choose what you need, on the spot, and then be able to manage it yourself.

In Azure, everything is pretty straightforward. Once you know it, the platform is very easy to use.

The training material that they have is very good, and it's easy to understand.

Most of the problems that we've had are related to the DNS and the SSL certificate. Those two things have been a real pain. Sometimes, it happens because of GoDaddy and sometimes it happens because of Azure. Either we make a change in GoDaddy and the configuration is lost, or our developers make a change to the website and from there it gets lost.

It would be helpful if Azure provided more information on the various add-ons to give people an understanding of what they are used for, and how they're applied by other companies or businesses. One downside is that I find myself signing up and paying for things that I don't really need, and I have to call them to find out exactly what it is that I'm paying for. For example, I recently added the Azure Data Studio and I don't know what I need it for. I see that it can create a connection and run a query but I don't know if I'm going to be using it. That said, I will probably need it in the future.

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

Stability-wise, it has been fine.

Azure is a scalable platform.

I have not been in contact with technical support myself. In fact, we have not had to reach out to them very often. We generally figure out things on our own but we also have an IT contract with personnel to work to resolve issues when they occur. Technical issues are something that you always want to try to resolve yourself.

Although we haven't had any problems that we couldn't resolve, we know that if we have to call technical support then we're going to be on hold for a while. This is something we don't want and can avoid by having our own IT support contract.

In my previous job, I worked for large telecom and we used a variety of products. These included AWS, as well as Azure, and we also had our own cloud that we leased to third parties.

I received training and certification on both Azure and AWS. However, I did not have much opportunity to use AWS.

In my current company, we migrated the business from AWS to Azure within the last two months.

The initial setup for me was easy because I have experience with Azure, as well as AWS, and a private cloud in my previous organization. I was in the internal network group, and I had all of the operational responsibilities for that area.

We were able to set it up and get it working in a day.

Migrating to Azure from AWS was not a big deal.

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

We considered both Azure and AWS for my current company. When we began, the company already had an existing website running with AWS, but I had more experience with Azure. We did extensive research to compare the two and we found that Azure was definitely the way to go.

We were already using several other Microsoft products, which means that our environment is more compatible using Azure.

My advice for anybody who is implementing Azure is to look at the training materials that they have available. They are very easy to understand and I recommend running through the ones that pertain to your use cases. A lot of the time, it will have the additional information that is needed to understand the problem and help you to find the relevant information in other sources. For example, it contained information about GoDaddy that was relevant to our environment.

The biggest thing is that the information is all there and a lot of people don't like to look, but I suggest using the help and the instructional videos before calling somebody else. Everything is available.

I would rate this solution a nine out of ten.

I 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.

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.

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.

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.

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.

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.

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.

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.

We primarily use the solution for our infrastructure. It's specific to server regulation and desktop regulation.

We used it for our customers in the pandemic. In terms of expansion on-premise, they were not able to do so due to the chip shortage. Therefore, we are moving everything to cloud and we are capacity-building - a temporary requirement. We are shifting them to the cloud.

As a partner, I like that they have a good benefit on margin.

The stability has been excellent. Multi-regions can leverage their capabilities easily.

The product is scalable.

We find the initial setup to be very simple. 

There are worldwide issues on Microsoft Azure, however, it is happening to Google also and as well as AWS. The problems we have are nothing new.

Technical support needs to be better.

I've been dealing with the solution for three years now.

The stability of the product has been great. There are no bugs or glitches. It doesn't crash or freeze. 

The product is scalable. If a company wants to expand it, it can do so.

We have 30 customers on the solution right now.

Technical support isn't so good. We'd like them to be more helpful and responsive. We'd like them to be faster.

The communication and those aspects are pretty good, however, the resolution could be faster and better.

As a cloud-based solution, the initial setup is very simple, very straightforward. 

We were able to deploy the solution in one day for a few clients. 

We have 20 team members that are technical (Azure system admins) and can handle the deployment and maintenance. We offer 24/7 coverage.

We offer this solution to our clients and can implement it for them.

The licensing is based on usage. Typically, it's a monthly fee that is paid to Microsoft.

We are a Microsoft Gold partner where we provide that, also we are users.

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

Customers who are on more Office 360 should leverage Azure. From a compliance perspective, these things are much more user-friendly compared to other clouds. Otherwise, there are a lot of compliance issues if we go with the other clouds where the mobility license is required. On Azure, for Microsoft users, those things are straightforward.

I use Microsoft Azure for different clients. I have different workloads or different architecture in Azure.

The most common use case is for migrations from on-premise to cloud. The principal solution is for a virtual machine, storage, and networking. 

The principal features that I use include computing, networking, and storage.

The elasticity within the cloud is great for clients to complete their pre-determined goals.

The cost is pretty good. They have a pay-per-use way of dealing with licensing that is very attractive. Migrating to the cloud becomes very attractive due to this.

The solution can scale.

Stability has been good.

Maybe Microsoft could improve its monitoring around the networking.

Clarity on the cost of the things could be better in some cases. For example, it's difficult to do a report with the cost of the things in Azure. Their calculator to estimate the cost needs to improve in terms of the estimation they provide.

I have five years of experience with this product.

There are some products that have good stability and virtual machines - depending on your setup and configuration - are very good. With Microsoft Azure, it's very rare that I even have a problem with it. In any solution, there's always some form of issue, however, with this, it's less common.

I've found the scalability to be quite good. 

I have worked with clients that have 300 users or more, however, sometimes with a smaller client they will have maybe 60 or 100 users.

Technical support is very good, however, it depends on the problem. There are some problems that originate with the client itself that Microsoft, naturally, couldn't necessarily resolve due to the origin of the problem. However, in general, I haven't had any problems with the support with Microsoft. They are helpful and responsive. 

Whether the initial setup is straightforward or complex depends on the client. There are some products that are more complex to set up. However, for me, it's easy to deploy different features or different products. It's easier compared to on-premise deployments.

Deployments can be two to three months for an enterprise.

For maintenance, you need a good team with good skills in Microsoft Azure, especially in the cloud due to the fact that it's a bit different. Things are different in the cloud compared with on-premise. 

I am able to deploy the solution for clients. 

I work with a team in my company. When, for example, we need help or support from Microsoft, we have a contact with the architect of this provider to resolve some issue or some problem that we have in the cloud.

The pricing is quite good, and it is designed as pay-per-use.

We are partners with Microsoft.

I am an architect, cloud architect, and I work in design solutions and implementing solutions in the cloud.

I'd rate the product at an eight out of ten.