Microsoft Azure Reviews

We're using the product as an infrastructure as a service. I'm basically using it to host services.

The product is very easy to provision. This is one of its most valuable aspects.

The solution offers pretty good integration capabilities at this time.

We've found the pricing to be pretty good so far. It's not too expensive.

The initial setup is very straightforward.

The stability is quite good. It's a reliable product.

We have found the scalability to be very good.

The solution offers very good upgrades and updates regularly.

The product can be a bit confusing at times. It's not well laid out. The interface, for example, can be a bit hard to figure out and they seem to be constantly changing things on us.

It's a rather new product and therefore lacks the maturity of other options. There is much they can do to add to it and to improve it. That may likely come with more time.

Up until two or so years ago, they weren't even accepting customer feedback on the solution. They've just started to do so, and they have given users a sense that improvements will be on the way sometime in the future.

Technical support is lacking right now. It needs to be better.

We've been using the solution for more than 12 months at this point. It's been a while.

The solution is very stable. There are no bugs or glitches. It doesn't crash or freeze. The performance, overall, has been rather reliable for our organization.

The product has the capability to expand. If a company needs to scale it, it can do so. It's not a problem.

Technical support needs to be better. We are not quite satisfied with their level of support. They need to be more responsive to use when we have queries. 

We actually use Amazon as well. We did use it before, however, we are also still using it. We use both Azure and Amazon at this time.

We did not find the initial setup to be too complex. It's pretty straightforward. A company should be able to handle the deployment without too many issues.

The pricing is decent. We don't find that they are charging too much. It's pretty fair.

As a cloud deployment, the solution is constantly updating itself, therefore we always have access to the latest release.

We have about 300 to 400 users on it currently. It's a business unit with various users of different job descriptions.

We are planning to increase the usage in the future.

I'm not sure if the company will use this solution for the long term or if they are considering trying something new. That is yet to be determined.

Overall, I would rate the solution at a nine out of ten. We're mostly quite happy with it in general.

• Virtual Networking
• Security
• Feature packing
• Virtual Machines
• Ease of implementation
• Azure AD
• Azure AD Directory Domain Services
• Database as a Service
• Operations Management Suite
• RBAC

Mobility, no more "metal" on-premise, cloud-based directory with SSO features, sped implementing new solutions, reduced skillset for management and reporting.

We have a full Azure plus Office 365 implementation for servers and desktops, authenticating users on Azure AD over 802.1X switching and wireless. No on-premise servers, DC's, file-servers, etc.

Stability. Microsoft is implementing changes too fast and sometimes things break.

Three years, but the full stack only since January 2017.

None.

Yes. Beware of August. Microsoft makes some big changes during this month and they have an impact on customers.

None.

10 out of 10.

10 out of 10.

On-premise traditional solutions.

Complex in the beginning, because the company I was migrating had some peculiarities.

The latter move was totally stable as we did a cutoff migration and no garbage was imported. Some downtime was expected, but this was minimal.

In-house, with support from a vendor team. Excellent support: 10 out of 10.

Not yet calculated since it was a major digital transformation and an ongoing project.

Setup cost is low and Microsoft may help your project financially with services from a partner.

Be sure to know your licensing or ask for advice. It's worth it. You may be led into something you don't need, if following Microsoft or a vendor.

No.

Evaluate extensibly (the actual scenario), have a definitive vision of where you want to be in a near future, align the strategy with your management and expect that it may not be cheaper. A correct vision of a project of this kind cannot be focused on lowering costs but vision alignment, future scalability, speed on delivering services, and maintaining smaller IT crews focused on business needs.

Please do some previous math regarding actual licensing versus a costs model. Extrapolate this to a five year plan to match current hardware lifespans.

Virtual machines, Azure Web Applications, MS SQL DB, DNS, Azure Active Directory, etc. are some of the most valuable features.

It is quite easy to learn to start working with them and they are composite enough to use them in many different scenarios.

For example, you can create a web app with a few clicks from Visual Studio and publish it to Azure Web Apps. You also can integrate that Web App to CI/CD pipeline (https://www.visualstudio.com/en-us/docs/build/get-started/aspnet-4-ci-cd-azure-automatic), assign custom SSL certificates to it (https://docs.microsoft.com/en-us/azure/app-service-web/app-service-web-tutorial-custom-SSL), configure auto-scale (https://docs.microsoft.com/en-us/azure/app-service/app-service-environment-auto-scale), implement Azure AD authentication (https://docs.microsoft.com/en-us/azure/app-service-mobile/app-service-mobile-how-to-configure-active-directory-authentication?toc=%2fazure%2fapp-service%2ftoc.json), etc.

It enabled moving from the virtual machines to the Web Application-side, which in turn saved a lot of time for our developers.

I have used this solution for about two years.

There were some stability issues. Some of them were user-specific (some applications were buggy), while some were global https://azure.microsoft.com/en-us/status/history/.

There were no scalability issues. My work duties are not connected to this feature.

On a scale from 1-10 (1=worst, 10=best). I would rate the technical support a seven out of 10. First level support is awful (it works only if you have a generic issue). But if you are lucky enough, you could get a real technical person, who could help you.

The setup/installation depends from which service you start (for example, start to use DNS which is much easier vs the web applications).

If your company is big enough and oriented to the cloud, then go for the Enterprise Agreement. If you want just to try it first, then use the trial version.

Learn the fundamentals using the official documentation; for example, you have the Developer Guide and courses.

Start using new services based on the scenarios described in the official documentation.

Use communities for consulting, such as Stack Overflow, Reddit, and Slack. However, personally, I prefer the channel azured.slack.com.

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

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

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

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

It is a stable product.

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

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

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

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

I rate the overall solution a nine out of ten.

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

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.