Microsoft Azure Reviews & Product Details

I have been using azure storage explorer since 9 months. Being an Cloud Engineer I absolutely love how this tool on your local machine works exactly as the azure portal interface. You can download very big files in just few seconds. You do not have to login to portal each time to upload files to your blob. You can just do it from your local machine just giving your one time credentials. You can see all your storage account names in the left side pane for easy access to each blob.

One thing that comes to mind is frequent updates reminder. Every alternate day I see an reminder asking to update the azure storage explorer version. Although it is not very annoying to see the updates, I think Microsoft should inform the users what the update is about.

Ok, before whenever we want to upload a large file (say 300mb) we used to upload them via azure portal which is very slow.I believe it used to take around 45 mins. to upload the file to blob. After the introduction of Azure Storage Explorer, the time took to upload the same file was around 2-3 mins. Also we were able to do other tasks on Azure Portal while the upload is in place in Storage explorer.

It meets the needs of performance and capacity-centric applications and gives you a complete hybrid cloud storage solution for enterprises.

Lack of Hyper-V snapshot support, Inability to upload custom Images.

Accelerate disaster recovery , improve compliance.

Load Balancer is simple to create and well integrate with other Azure resources such as Scale Set, Web App and it provides almost feature we need with layer 4 Load balancer: Destination selection, Port forwarding, Automatic reconfiguration, Health probes... We could use the Basic SKU for free and it has all the features we need for small or medium applications

Documentation is not clear enough and configures health probes base on backend service in the portal is confusing

We create VM scale set with Load Balancer and it works well. It supports scale up and down, distribute traffic to all VM in scale set and we do not need to care about VM scale set just Load Balancer Load Balancer provides good build in metric and Resource health report to troubleshoot issue

Starting with the standard offering, it's great for caching least accessed data. I usually ccache all software builds on extra standard HDDs. They're remarkably cheap per disk access and letting Azure manage it reduces the cost for on-premises deployment and management. The SSDs though are the real deal. Fast software development leaves plenty of time to focus on what matters the most (bugs bashing, improving and implementing features, etc).

They're costly. If you can squeeze out the resources for SSD, it is awesome. Otherwise you're pretty much stuck with their standard offering. Trust me, the lower tier is only good for storage, that's it. Also, you're pretty much limited with the size selection. HDDs allow variable disk size. I guess having variable size for higher tiers will make it more cost effective and ensuring only the amount required is allocated and deployed.

We mostly automate software builds on our virtual machines powered by the Azure managed disk storage. Our code is stored on SSDs while any local caching is performed on the standard tier. I know this causes a little bottleneck but most software changes (such as releases) usually require a complete clean build.

I like the authenticating and managing access the software provides to keep containers secure.

I thought the training function was lacking.

We have used Azure to integrate our cloud based applications to all employees.

I liked the simplicity of adding your VMS to availability sets then being able to easily target and set health probes and rules to the selected VM's

The inability to add an existing VM to an availability set

I am testing how to evenly distribute work on a set of virtual servers.

Azure Container Registry provides an Azure-native container and all the Azure security / access control features comes with it, which is very handy when managing Enterprise-y applications.

There is a little bit of a learning curve if you are inexperienced with containers and Azure, but after you've got the basics things start to get more straightforward. If you are experienced with Azure CLI, you will find it more intuitive.

Azure Container Registry provides a robust way to implement microservices and experiment with containerised applications through Azure Container Instances. It became quicker and more reliable to deploy and test our applications.

I have been able to run PostgreSQL on Azure with no hassle. This is not what I thought at the beginning.

I have not seen anything bad actually. Everything went well.

Run my database on azure to work with my other azure applications.

I love how scalable Azure is. The database queries run pretty fast and it's never an issue for me when I need to execute large queries. MySQL is supported easily and connector to my web app is also seamless.

The pricing for Azure is kind of high. Not the cheapest out there for sure.

Azure database service really allows me to run queries on data and scale the dataset out.

The virtual machines from Azure has multiple ways of spinning one up, Portal, PowerShell, Json Templates and other SDKs. The virtual machines are easy to spin up, and they are usually quite easy to use and setup with the NSG, data disks and all the other things Microsoft tries to cram down people's list.

When the VM RDP/SSH connection fails, it's really hard for the users to get it fix by themselves. Yes, there is redeploy, reset password, run commands and serial console but it doesn't help us to get it fix for the customer.

We solve people's problems with Azure VMs, it helps them create multiple VM to use with different users and different images. Benefits I realized, is that it helps people streamline their machines to be more powerful then the machine on-premises.

Geo replication - I think It's the killer feature, works seamless. just check a box and a region and replicated there, so one push and many regions can be served from it Also being a helm charts museum is a great call and the integration with build tasks, and base patching has very interesting potential

the fact I need to choose a 'tier" and a volume, why can't it just scale to what I need, and in the while I pay only for what I use . Although the service is quite cheap it's still annoying Also integration with some other azure tools could be better (events on change for example)r + more webhook information

Build a container once (in CI) to be used in multiple regions Saving containers privately with easy effortless integration with our managed k8 clusters in azure

Offers a lot of features and is a great option for cloud storage.

The cost is not down to our liking, but we deal.

Response time in our clients is for sure a big benefit!

Azure is very dependable, it is decently easy to use, and has good support for when you run into problems.

It can be a time-consuming product to implement

Basic data storage and access for our database. The newer additions of the program were even better.

Not provided

Not provided

Not provided

It really performs outstanding for Microsoft suite of applications and can be tailored to meet the business requirements.

Azure should also focus on providing capabilities for developers that focus on the development of native applications in the cloud that will not only run seamlessly in the cloud, but will stand out in each space and be efficient, resilient and scalable in the cloud.

Azure gives us the ability to create hybrid environments that allow us to take advantage of local resources and the benefits of the cloud. Azure can also help in the construction of hybrid applications.

It works very well with some mission critical solutions that I am running. Scalable and easy to add instances

A bit on the expensive side compared to mid tier providers. Not as customizable

Scalability and uptime are very good. No missed business so far

Initially, the team will need some guidance but once they follow the guide it's very easy to set up like for creating a template for services deployment. If org is in continuous integration it's very easy to work with Azure infra setup

Freshers need to follow the guide to set up initiale templates. It may also require a learning exercise.You also need to follow with upcoming features periodically so that developers dont invest time again in learning

Its the main infra setup within our organization

It was very easy to implement and set up on Azure Portal. We use the basic cache mainly for testing and find it very secure and reliable.

The time it takes to create the Redis Cache is a bit too long. It would also be beneficial if we could override the default SSL ports, which is not an existing feature yet.

We use this for testing. The pricing is not bad at all and for what it offers, the value is reasonable. We wanted to scale to the Standard tier, but that was not an option available.

Me encanta poder tener alta disponibilidad en mis aplicaciones y saber que azure balancer podra verificar cual tiene el mejor rendimiento para realizar la conexion. Puedes protejes tu red interna y externa con el nat. Es compatible con la nueva tecnologia ipv6.

Al no ser un balanceador fisico se pierde el poder de manipulación y actualización.

Logramos tener alta disponibilidad en las aplicaciones core.

in our company we use azure to manage our storage and we have always found it to be an excellent tool that optimizes work and increases productivity with an organized work environment.

There is nothing that I dislike of blue, however, what I would add would be more documentation or tutorials.

we manage all our files on this platform to keep all our equipment connected with the same information * synchronize all our work * organize our projects * facilitate access to our team