Microsoft Azure Machine Learning Studio Reviews

My primary use case is for supervised and unsupervised learning models.

The most valuable feature is its compatibility with Tensorflow.

In the future, I would like to see more AI consultation like image and video classification, and improvement in the presentation of data.

I've been using this solution for a year.

The stability is questionable, given that Microsoft will be retiring the classic version of this product in 2024, and it's unclear how this will affect projects created on the classic version.

This solution is scalable.

The initial setup was straightforward, though you do need some experience with Azure administration in order to install it.

I evaluated Amazon SageMaker, which is a bit more advanced than Azure Machine Learning, with more functionalities and only a slightly higher price.

I would rate this solution as seven out of ten.

I use the solution for learning purposes for the most part.

Personally, I got interested in data science and machine learning due to using this product. After some time with it, these topics didn't intimidate me.

The solution is very easy to use. It's user-friendly and simple to navigate.

The initial setup is very simple and straightforward.

The solution is quite stable.

It's the first software that I've used in terms of machine learning. Therefore, I don't have anything to compare it to, however, it was okay for me. I didn't have any problems or anything.

Maybe it can be integrated with something else. For example, business analytics. That way, you could also give creative reports. It's possible it could be integrated with the Power BI, as it's also Microsoft. That said, I'm not really sure. It if isn't possible, it's something they could consider for a future release.

Microsoft needs to be sure to monitor the security and ensure they are constantly updating it.

It would be nice if the product offered more accessibility in general.

I've only been using the solution for a short amount of time. It's just for a course at school.

The solution is stable. I didn't have any lags or anything. It was smooth. There are no bugs or glitches. I don't recall it crashing or freezing on me.

The solution seems to be able to work well for companies both large and small. However, I did not personally attempt to scale it.

I never really dealt with technical support directly. I have my teacher to teach or to ask questions to. He would often recommend these online tutorials to learn about the solution as well. I never really thought of asking a chat box, for example, of Microsoft, where I could type any help. I never really considered it. Therefore, I can't speak to how helpful or responsive they typically are.

I did not use a different solution. This is the first solution I used for machine learning.

The initial setup was not difficult or overly complex. It's very straightforward, very simple, and very easy to understand. 

Everything is just written down in a way that was an easy way to understand, even for someone who isn't used to the packages of Microsoft.

I handled the deployment myself. I did not need the help of a consultant or integrator.

I'm just a student. I was learning about machine learning via this product.

I'm not sure which deployment model we are using.

I would rate the solution at an eight out of ten.

I would advise other potential users to just start using it. If they really want to learn it, it will take a bit of time. Even though it's easy to use, you need some knowledge in data science. That will help make the process easier.

We're using the solution in order to give the customer a 360 degree view. Also, we use it if clients want to do machine learning with AI at a more reasonable cost.

Right now, we are just testing the customer insights from Microsoft.

The UI is very user-friendly and that AI is easy to use.

Usually, we also use the machine learning studio to build up the data logistics in machine learning.

On the customer side, the solution should do more to push companion marketing.

When you use different Microsoft tools, there are different pricing metrics. It doesn't make sense. The pricing metrics are quire difficult to understand and should be either clarified or simplified. It would help us sell the solution to customers.

The solution should simplify switching between platforms in the studio.

I've been dealing with the solution for two years.

I've only used the solution a couple of times. I haven't noticed any bugs and when I used it, it worked quite smoothly.

I don't have enough knowledge about the solution's scalability to be able to comment on it. Right now, we have about 5,000-6,000 users on the solution. Most are data scientists, and IT admins.

I've personally been in touch with technical support and I found them quite helpful.

I've only ever worked with Microsoft Azure. We didn't previously use a different solution.

The initial setup is very straightforward.

Our clients do the implementation with the help fo consultants like us.

The pricing and licensing are difficult to explain to clients. Their rationale for what things cost and why are not easy to explain.

I'm a consultant. Our company is partners with Microsoft.

Users will find it easy to get into Azure. Even if they aren't always in touch with Azure, they'll find themselves in touch with the dynamic field. Users have to get into Azure because once they get into the cloud, they should have some basic understanding of Azure itself.

I'd rate the solution eight out of ten. However, I don't know their competitors, so I can't really compare them to others on the market.

I wouldn't say it's necessarily about liking everything about the platform entirely. It's more about what do we want? In terms of machine learning, there are times that we have to get into it and customize it, etc. We can use the ready-made models that are available without really having to code encrypt them with our bitcoin code — our model doesn't need to be too complex. Deployments and everything, in general, can be automated from a CI/CD perspective as well.

I really can't see where it needs much improvement. My experience is only half-matured and is still maturing.

I don't think we have reached the stage where the customer has enough cohesion to really complain about anything. Also, a Microsoft team is personally involved which really simplifies the process.

In the machine learning world, when you are defining the model, typically people go for an interesting library of algorithms that are available. It's an imperfect scenario. The world is not as ideal as we think: how we draw a mathematical or theoretical formula is not exactly as it seems. With encryption, this uncertainty is actually much higher — that's why you need to tweak your mathematical formula or completely customize it. For this reason, my team has a development platform where they can customize code when it fails.

I have been using this solution since June.

Regarding the stability and scalability — so far so good; however, we're still exploring quite a bit. It's too early to really comment because the customer has already paid. They've just started their journey. We are yet to explore exactly what and how they want to use it. 

So far, we haven't had a situation where we have needed to raise a ticket for support on a technical front.

Currently, we're handling any issues internally because we're still in the initiation stage. It's going to take some time for us to really get our hands into it, but so far it's been a really good experience. Based on various conversations that I was part of, I think our customer really appreciates the support coming from our people.

 Compared to similar solutions, Microsoft Azure Machine Learning Studio is quite new so the initial setup wasn't much of a challenge. The data processor can pose a bit of a challenge, but the real complexity is determined by the skill of the implementation team.

I would Definitely recommend Azure Machine Learning Studio — no doubt about it, it's a full-contact solution. Having said that, it really depends on the customer's appetite and what they're comfortable with. For example, I have interacted with people who prefer a basic Google cloud platform — from an AML perspective, they just feel like it's primarily Google. Not because of AML per se, it's more from a data storage perspective, which in this case, works better.

Personally, I come from a VFA site in the financial sector. Over there, the customers are really conscious about hosting their station or their data, especially on the cloud. Typically, they are very restricted because they are not comfortable hosting customer data on the cloud. This is where I think Azure or Google or even AWS fall short — they don't play any role there. Because of this, people actually customize their solutions or model them to fit their custom sites and customer-based solutions. 

Overall, I would give this solution a rating of seven. It's a great option if you are fairly new and don't want to write too much code. As long as the model is not too complex, it's a pretty easy solution to roll out.

We're setting up the environment for our data science and IT project. It is a protected environment for protected data. So, there's a lot of architecturing in this solution.

Their support is helpful.

It is not easy. It is a complex solution. It takes some time to get exposed to all the concepts. We're trying to have a CI/CD pipeline to deploy a machine learning model using negative actions. It was not easy. The components that we're using might have something to do with this.

I don't know about its stability yet. We're facing some issues, and we are approaching the product team for help. It might also have something to do with our environment setup. Our environment is inside V-Net, and we have a lot of security requirements.

We're working with their team to resolve the issues. Having someone to assist you makes it easier. We have someone at Microsoft to help us with it. They're very helpful.

I have worked a little bit with Open Source.

We are only testing, and we have to be very careful of the restrictions. I'm a little bit aware of the issues about ML Ops, and I am trying to see if Azure Machine Learning Studio can address those issues. For now, I would rate it a seven out of 10. I have to explore it more.

in-house translation, time series and computer vision applications;  create models from scratch and just play around with data visualization.

Azure's AutoML feature is probably better than the competition.

The interface is a bit overloaded.

I've been using Azure ML Studio for about three months. 

Azure ML Studio has the same scalability as other similar solutions.

I haven't used Microsoft Azure support for this so far.

also using Amazon and Google solutions. In terms of performance, I think they're pretty much the same. Amazon SageMaker is a bit more mature.  Google Colaboratory and Vertex AI have better UI

Setting up ML Studio is very straightforward because it's a cloud thing. 

I rate Microsoft Azure Machine Learning Studio seven out of 10. I would definitely recommend it to customers. The autoML, in particular, has some very advanced features.

Azure Machine Learning Studio works with our ERP solution.

The most valuable feature is data normalization.

The data cleaning functionality is something that could be better and needs to be improved.

There should be special pricing for developers so that they can learn this solution without paying full price.

I have been using Azure Machine Learning Studio for more than two years.

This is a stable solution.

I believe that it is scalable. At this time, we have not more than ten users. These include programmers, as well.

I have been in contact with technical support and they are good. I am happy with their response time.

The initial setup is straightforward and not too complex.

We did the implementation by ourselves.

From a developer's perspective, I find the price of this solution high. If somebody wants to learn how to use this platform then they have to spend money doing it. I know people who are interested in learning it but do not want to pay the full cost.

Microsoft Azure Machine Learning Studio is a good solution that would recommend to others, but I would like to see more support and more information available for developers.

I would rate this solution an eight out of ten.

Exploration of connections between biodata and psychometric test results.

Visualisation, and the possibility of sharing functions.

Operability with R could be improved.