Microsoft Azure Reviews

As the solution is cloud-based, we always use the latest solution. 

We make use of the solution in the cloud for specific internal applications.

Use of the solution could be easier. It is too complex.

The solution is not sufficiently informative and there is a need to wade through much information. 

Moreover, we find it lacking when it comes to active dashboards. This is problematic when looking to Teams, as it does not allow one to know what is transpiring in real time, such as when there are concurrent conferences. This information only becomes available the following day. 

I have been using Microsoft Azure Review for three years.

The solution is stable. 

The solution is scalable. 

Microsoft's technical support is good. There is no room for improvement. 

We looked at web user before going with the solution. 

As the solution is cloud-based there is no installation involved. 

The license is on a monthly basis.

There are approximately 100 users utilizing the solution in our organization.

I would definitely recommend it to others.

I rate Microsoft Azure as a seven out of ten. 

We wanted to deploy applications and have them interact with services on the back-end, so we deployed Azure for this. The performance has been quite good.

It was easy to deploy our applications on Azure. It provides more compatibility and scalability than the .NET application. This is why we chose to use Azure.

We are looking for the Azure to get involved in the case of other applications, like the Java application. Because it is predefined and has been set by Microsoft, who is providing better compatibility to the .NET application, so we are looking for the same from Azure for the Android app. Therefore, we are looking for better compatibility and scalability.

It is stable. I have not seen it have any downtime.

We have faced some challenges trying to deploy a new ESP application.

The technical support was good. I would give them an eight out of 10 rating.

The initial setup was straightforward.

The pricing is very competitive.

We evaluated AWS. 

If I were advising a colleague in my organization who is looking for a solution and is comparing AWS and Azure, I would prefer that they go for Azure, or any software using Microsoft technologies because we have had good experiences with them. If I were advising on Java, I wouldn't advise him to specifically use another tool rather he should do research and use my comparison history on IT Central Station.

I would rate this solution a seven out of 10. 

Most important criteria for selecting a vendor: The client will choose the license and buy it. We can try to convince them, but we can not compel them to use a specific vendor's license. Ultimately, the decision-maker is the client.

• Virtual machines, both Windows and Linux based
• Blob storage
• Azure file storage
• SQL server

This product has facilitated development, testing, rapid deployment, spot resource needs, with a remote off-site that compliments on-premises for the hybrid cloud.

The user interface is great if you like tablet, a.k.a., Windows type functionally. The PowerShell is robust. However, there is not much in between, although you can do a lot of customizing views, dashboards, and other things.

I like the extensiveness of the new VS classic interface. At times, I still find the AWS dashboards simpler and more streamlined. Nevertheless, Azure is more elegant.

I have used the product for several years.

I had no stability issues.

There were no issues, as long as your credit card can also scale.

I don't know about technical support, as I have not had to deal with them. But the various communities, forums, and resources are outstanding.

We have deployed, and continue to use:

• AWS EC2
• EBS
• S3 Glacier
• Route 53
• Lightsail
• Google
• Bluehost DPS
• An onsite mix of Microsoft Hyper-V and VMware

We are doing hybrid to address different needs.

Having used AWS, VMware, as well as Windows, there was a little bit of a learning curve, just as there was for others.

However, navigating the UI, shells, and figuring out what was where, without spending weeks in seminars, training, and watching videos, was actually pretty intuitive.

If you are not used to working with AWS or others, or if you have some tools, Azure is actually pretty extensible and getting easier to working from Windows and vice versa.

Do your homework, understand the type and sizes of resources, see if there are any extra fees, and find out what tools are needed.

Check what level of performance, availability, capacity and economic (PACE) budget, as well as the services that are needed.

Watch your costs and look for value versus the lowest cost.

We looked at AWS, Rackspace, Google, Microsoft, Bluehost, and VMware.

Don't be scared, be prepared; do your homework.

Look beyond lower cost and instead focus on value, enablement, ease of use, compatibility, resiliency, ability to scale with the stability of performance, capacity, and availability.

Look at the extensiveness of services versus a simple check box.

You also need to identify any concerns about the cloud, categorize them, and then discuss with others how to address them, or seek a workaround.

If you cannot find somebody to chat with, drop me a note.

The fully integrated capabilities of a PaaS service.

Basically we would not be building the Healthcare IT application if it were not for Azure.

The management console needs work and the pricing calculator is truly user hostile.

I have been using the solution 3 years.

We have some issues with functional differences between Azure Active Directory and how Ad is implemented on a standalone server.

We have had a few outages with Visual Studio Online – though they have not been a major work impact.

None so far.

Customer Service: Mixed. Microsoft still has too many support queues and if you end up in the wrong one you can spend hours being bounced from one to the other. OTOH once you figure out how to get to the Business support queue – response times are fantastic for “business outage” issues.Technical Support: When in the right queue – the understanding is unparalleled.

I have previously used AWS and Amazon Elastic Beanstalk. Azure is a PaaS whereas AWS is a server stack environment and thus AWS does not provide the OpEx cost reductions that Azure does. Elastic Beanstalk is a PaaS but it is not as fully developed as Azure.NET is.

Very straightforward. In fact almost too much so. Its easy to try and overthink the setup and waste time looking for things you don’t need to be looking for.

Combination of in-house and vendor. Vendor team was new to Azure.

Full ROI on the current project is still to be determined as we are not shipping yet. But I would estimate a 100% cost reduction over the traditional way of building a server based app.

Our monthly dev costs for infrastucture are running $300-$500 for the initial work and we expect to have full OpEx costs of $1,000-$3,000/mo once we are launched.

AWS and Elastic Beanstalk.

Have a team that understands .NET development and particularly someone who understands Active Directory very well

We use the solution for PaaS, web services, databases, and AD. 

The tool's most valuable features are SQL servers and Managed Instance databases. 

Microsoft Azure needs to be simplified to make it better understood for users. 

I have been using the product for five years. 

I rate Microsoft Azure's stability a nine out of ten. 

I rate the tool's scalability an eight out of ten. My company has ten users. 

I haven't contacted the tool's technical support. My Microsoft partner takes care of it. 

I rate Microsoft Azure's deployment a seven out of ten. It takes around half an hour to complete. You need two resources to handle the deployment. I am involved in its maintenance. 

A Microsoft partner helped us with the deployment. 

I rate the tool's pricing a six out of ten. 

Our workflow has been good since using Azure Data Factory. There are previews of new features available, which I am happy about. I rate the product an eight out of ten. 

Microsoft Azure

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.

Public Cloud

Microsoft Azure

We use the solution for executing the ADF pipelines through the database port. We provide the scripts in the database, we run it, and it goes through the ADF pipeline. Afterward, through the database command, the ADF pipeline will run and push the data into Azure SQL. 

I have found the solution to be flexible, easy to use, and the documents are straightforward to understand. For example, it is flexible, we have a single pipeline that has three phases, within approximately 15 minutes the records get transferred into this solution efficiently.

Additionally, the solution is well integrated with other solutions such as Power BI.

When we are doing transfers of records in large amounts, for example, petabytes of data or few long datasets, the performance should not degrade as it does. I am working on big data platforms like Informatica and others and even though there are terabytes of data being transferred it does it immediately. However, in this solution, I would like the performance to be there when building a large dataset to integrate the data.

I have been using the solution for the past three years.

The solution is stable.

I have found the solution to be scalable. We use Teradata for large data and we are building the pipelines for it, so far it has operated well. We have approximately 25 individuals using the solution in my organization.

The technical support is very good, if you have an issue they will be able to help.

I have used Informatica in the past and it has some performance advantages compared to this solution.

The solution does require a license.

I would recommend this solution to others and we are going to continue using it in the future. We have numerous clients switching to this solution.

I rate Microsoft Azure a nine out of ten.

Public Cloud

It is great for computer resource management at reduced cost. Also in a large environment, it gives you a lot of flexibility to provide different services, like disaster recovery and business continuity.

In terms of computer resource management and reduced cost, it is very, very effective. In large environments, it gives you a lot of flexibility to provide different services, like disaster recovery and business continuity with simple and great options because you don't have to spend a lot of time for maintenance, upgrades, and security. Also, Microsoft Azure provides a lot of services that can be managed by Microsoft like NetApp and SQL Server on a database.

Microsoft Azure has services such as ACS, Azure Container Service. This is very useful for improvements in running applications in a scalable environment. You will not need to spend time building the cluster on-premises, and you can improve your clusters with a lot of administration options.

I think Azure Active Directory and also the backup solutions provided in Azure need to be improved by Microsoft. The backup solution is not a very enterprise solution, and it is very simple. I think in comparison with other backup solutions like Nakivo and Veeam Backup, it can be improved to have a lot of options.

Along with this, one of the lack of options in Azure is managing antiviruses in virtual machines in the Azure environment. For example, if we have a lot of virtual machines on-premises and have to migrate them in Azure, there is no handy tool for the central management of antivirus software in all virtual machines in Azure.

On-premises, we have a lot of options like Kaspersky, Norton, and a lot of others, but in the Azure environment, you are limited to Windows ATP.

Windows ATP solutions are limited and can be improved by Microsoft, specifically the central management of the GUI for configuring agents on virtual machines.

I think Microsoft Azure should provide more innovation and new services to get better performance in the market.

The documentation for how to connect to CLI could also be improved.

I've been using Microsoft Azure for around three years.

It is very scalable and can be distributed to different regions.

I'm not involved in using technical support because I directly work with an Azure architect on my team who is responsible for providing support and leading the team as well as contacting the Microsoft support team. In general, however, I think, one of the best advantages of Microsoft services is the support team made up of technical engineers who help solve problems.

As for the initial setup, the GUI in Microsoft is very simple and very handy, but in Azure Container Service, it is not very handy and is very complex. You would need to go forward with CLI.

I would rate Microsoft Azure at eight on a scale from one to ten. 

Public Cloud