Microsoft Azure Reviews

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.

The advantage of Microsoft Azure is its simplicity. It's easy to launch a project. However, the problem with this kind of solution is the reliability for the customers. You have to be sure to stay with Microsoft.

It's not always simple to manage the team who use it. Sometimes customers abuse the capacity and it's not always easy to bill the department for the usage.

Microsoft Azure is not always a user-friendly solution. There are too many people who develop this solution. For the end-users, sometimes it's not really fun to use or simple to use. It could be improved.

It's difficult to stop the solution when you have started, you need to use it for the long term. You have to make a good choice when you start the project with Microsoft or with Amazon too. You will have the same problem, once you choose one you have to commit.

When a feature doesn't exist in Microsoft Azure, generally we can use other software that does the job very well, such as backups or supervision. Any products to help the customers and engineers to do a good job, such as managing large infrastructure. There is a lot of solution to make it work well.

I have been using Microsoft Azure for approximately three years.

The stability of the solution was good we have not had a problem.

The scalability is good, there are nearly no limits, and simple to do. However, it is difficult to see the limit.

My engineers sometimes have used the support, I don't have any feedback about troubles with the support. I think the support is good. I don't have bad feedback.

The deployment of the solution is quick and easy.

My advice to others is to be sure if they choose the cloud it is the right choice for them. A customer can be in a hybrid solution, or cloud, or on-premise solution. I prefer the hybrid solution, in the same project. It's a choice they need to make for the long term.

I rate Microsoft Azure an eight out of ten.

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.

I was testing the integration capabilities. I deployed a simple solution with a front and back end with an SQL database. For the server-less solution, it was just to interact with the database. That's what kind of the load that I was testing. The use case was to integrate with the directory, authenticate, and then consume some of the services there.

One of the services that I found to be great is the connector. For example, the other day, I was creating an application for internal research. With that connector, it was really easy to integrate some services to interact with the connectors. The credential allows you to authenticate with the active directory. Then, with that authentication, you can have the assurance that the people who are consuming the application are the right ones.

I know there have been a lot of improvements and a lot of new services lately. I'm really not aware of all of them.

One thing which is great is that they give users hub integration. That's a strong aspect, which would be good for many people and clients and developers so that they have that integration right away.

I haven't checked the console for some time, however, compared to the AWS console, the interaction console of the web part, the web services, it's not so easy. That will be a good area to improve, which is to make the console for interaction with services a little easier.

Another point to improve could maybe be the pricing model or maybe the interaction with information. When you look for information in AWS, it's more straightforward and clear. It's hard to find that information on Azure.

I used the solution for maybe one month at the beginning of maybe March of this year. I was doing some tests with Microsoft Azure. I was deploying some services.

The stability is good. There are no bugs or glitches. It doesn't crash or freeze. It's reliable. 

The scalability is fine. However, it may be another thing to improve. I haven't look looked at it in some time, however, I remember at the beginning, I tried to research for the price, for rates, and things. I didn't find it easy to locate, which made it hard to gauge the cost of scaling. 

From my side, I don't plan to increase usage. Right now, I'm working for other clients, and with the solutions of the clients. For research purposes, I will do maybe one or two instances, just for testing. It's not a big deal.

While I've never needed technical assistance, my understanding is that it's pretty good.

It was not very difficult to set up the solution. In the beginning, it's a bit difficult to just find the services and things like that. They need a kind of list or something, something more visible. That would help. 

Our implementation was not too big. It took maybe two days. Another deployment we did took maybe three. I'm not really a complete expert. It might have taken a bit longer for me due to my lack of experience.

I did not use consultants or resellers for deployment. I did it myself. There wasn't too much pressure. I was doing the deployment more for research purposes. 

The price of the solution is unclear. it's hard to find the costs. 

The company I am working for is a Microsoft partner.

I'd advise potential new users to try to get as much information as possible about licensing and about the products that they are going to use. That will be good to have a very clear understanding of. Beyond that, it's not a problem to get started and go.

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

The use case varies by client. Sometimes it's financial tools or websites. We build tools for DevOps applications too. Our most recent use cases are retail and construction.

Virtual machine services, in SaaS services, M365, and Data Lake are all popular with our clients. 

When you use one feature in six months or a year, it changes for the others, and it isn't very easy. The filters are too complicated. I'd like to see better integration with S/4HANA integrated and other services, like monitoring, for example.

I've used Microsoft Azure for approximately two or three years.

Azure is highly scalable.

In my experience, Microsoft support is outstanding. We're Microsoft partners, so when we need support, we get it immediately. 

I think the setup is complicated, but if you have experience with other Microsoft products, you should be able to figure it out. The time needed for deployment depends on the client and the solution. For example, it's very different in the case of Data Analytics, which took us two or three months to deliver the solution. 

The price of Azure is competitive with other cloud providers. 

I rate Azure nine out of 10. 

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.

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.

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.

I have been using Microsoft Azure for approximately five years.

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.

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.

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.

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.

We did the implementation internally.

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

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.

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.

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.

We use Microsoft Azure to store our data and build analytical tools on the platform. Our Trade Insight Dashboards allow users to explore trade and investment data for more than 150 countries. Users can discover the most traded products of each country, where they are sent to, where do opportunities lie, and which industry has the most potential. 

Our data is kept in a secure, reliable, scalable platform. Data is easily available to our consultants and customers from anywhere around the world. We no more have on-premise servers. Azure has helped our digitalisation process and was key to our latest success. 

The ability to scale up and down the azure services when needed. We could better manage our costs. 

We work mostly with the data services and the SQL database features. We like the optimisation recommendations we get such as creation of indexes etc. What I would like to see further is  some basic data profiling stats or charts representing data stored to be integrated in the SQL database services instead of using other services such as the Azure Data Catalog.

I have been using Microsoft Azure for approximately two years.

Microsoft Azure has been stable for us, we have not faced any issues.

We have found Microsoft Azure to be scalable. Our business has not been growing very fast on the solution but it has the capability of expanding.

We can keep track of how many people are downloading the applications and there are approximately 2,000 people using the solution.

We have been in touch with technical support several times. The assistance and support provided was very good. 4 to 5 stars on average. 

The initial setup is not complicated.

My advice to others before implementing this solution is to be well-documented in your needs and to have support from a solution provider. Additionally, be aware of exactly what support you might require before starting.

I rate Microsoft Azure a seven out of ten.

Most workloads can be migrated to Azure. For example, say a small business wants to have a website or even do development. 

Azure services like EDM and Batch are all famous, but one of the most popular services for development is Azure Functions, especially the PaaS option. Depending on a customer's environment, they can go for the PaaS.

The management portal can be confusing sometimes. We have difficulty navigating the menus because the terminology is unclear, especially when referring to the content or actionable items. 

I've been working as an Azure trainer for about a year and a half. In my last job, I was working with on-premises solutions, but the whole industry is transitioning to the cloud, so Azure, AWS, Google, and many other cloud providers are trying to get a market share now.  

I don't have any issues with scalability or stability. We moved migrated from our physical infrastructure earlier, and we haven't seen any problems. It's more about the organization getting comfortable with the solution. That's the only thing.

Azure setup is straightforward. There is no comparison to on-premises deployment because it's all automated. It's very fast, but I can't compare the speed to other vendors because I've never deployed AWS or Google.

AWS is good, but Azure's license is reasonably priced, and Microsoft is gaining market share with a competitive package overall. Moreover, Microsoft is well ahead of AWS in terms of ease of use and billing, so I think I still love Microsoft. Obviously, both have a market, but customers working on development projects or using Microsoft products often go for Azure because of the license benefits and product support. 

I rate Microsoft Azure eight out of 10.