Microsoft Azure Machine Learning Studio Reviews

We primarily use the solution for sales forcasting and for creating a pipeline in Azure. We are publishing the pipeline from Azure DevOps, and through the AML endpoint so that the pipeline will run one after the other models. These predictions will be stored and we can visualize everything. 

The designer and notebooks are great. We like the pipelines we are able to deploy and the process is very simple.

The visualizations are great. It makes it very easy to understand which model is working and why.

The setup is simple. 

It is stable and reliable.

I have had no trouble scaling.

Technical support is good. 

The solution cannot connect to private block storage. It does not allow this connection, which is a pain point. The confidential data needs to be removed from the block, and that becomes a security issue. 

In Azure Databricks, how we are promoting the models could be easier. The UI in Daabricks is a bit easier. We'd like ML Studio to be streamlined. 

I've used the solution for about two and a half years. 

The solution is stable and reliable. There are no bugs or glitches. It doesn't crash or freeze. The performance is good. 

The solution can scale. I haven't used Azure Kubernetes services yet. However, I haven't had issues with scaling so far. 

We have around ten to 20 people on our project using the solution. Many users use it in our company - not just on my team.

I've reached out to technical support. They have SLAs in place that help us to troubleshoot issues. Even critical issues get sorted out quickly. We're using premium Microsoft technical support. 

We also use Databricks. In Databricks, there is no designer module to design pipelines. There are other features available. 

They do behave in the same way; however, in Databricks, I do need to do more configurations and a bit more work with it. Still, it allows me to connect to private blocks, which I cannot do in this product. It also requires me to run job clusters separately. 

Security-wise, Databricks is more secure. 

This is easy to deploy. I did not fid the process to be overly complex. 

The solution has a higher price. I'd rate it three out of ten in terms of affordability. 

I am an end user. 

I'd rate the solution eight out of ten. I'm pretty happy with its capabilities. 

I use the solution in my company for some product prediction purposes and in the retail processes. My company collects data in Azure and Cynet. My company develops some ML algorithms in Microsoft Azure Machine Learning Studio. Two years ago, I had a training session with Microsoft, so now I can develop ML algorithms in the retail sector.

The high price of the product is an area of concern where improvements are required. The product needs to be available at a cheaper price. I think the tool needs to be made available to children for free, especially if you have a student's or a teacher's email ID from a university.

I have been using Microsoft Azure Machine Learning Studio for two years. I am a user of the solution.

It is a stable solution. I have seen a lot of products, but I feel that Microsoft Azure Machine Learning Studio is the most stable tool in the market. Stability-wise, I rate the solution an eight out of ten.

It is a scalable solution. Scalability-wise, I rate the solution an eight out of ten.

For development purposes, there are ten people, and since my institute expanded its use, I think it will increase to fifty.

I plan to increase the tool's usage.

I got support for the tool in Turkey with the help of Mircorsoft's admins and consultants and they were okay. I rate the technical support an eight out of ten.

Positive

I evaluated DataIQ against Microsoft Azure Machine Learning Studio. Most of the applications I used were small or niche tools, while Microsoft Azure Machine Learning is huge and expandable.

The product's initial setup phase is easy. I rate the product's initial setup phase as an eight out of ten.

The solution is deployed using Azure's cloud services.

The solution time for deployment can take a few hours. I work in an enterprise with a medium range of data.

I rate the product price as a nine on a scale of one to ten, where ten means it is very expensive.

You can take care of the input of the datasets, and then Microsoft Azure Machine Learning Studio will provide everything for you. The tool has drag-and-drop options, and it becomes easy to develop anything, acting as a time-saver.

The drag-and-drop options in Microsoft Azure Machine Learning Studio influence the machine learning workflow as it allows you to put in some links, and it integrates with nearly all of your systems. You can use the datasets with the tool program to see the features and dimensions of all the datasets. Then you can choose some ML algorithm about the datasets, and it recommends the program, after which you can test a lot of models, but normally, you can't do it because it's not in Python or something else, leaving you confused. In Microsoft Azure Machine Learning Studio, there is a system from beginning to end that covers everything one should do.

The tool does have an influence on performance as it makes things faster and more productive.

I can recommend the tool to my colleagues. It provides the developer or product owner the ability to watch the system overall. If you use the tool you can begin learning about ML and you become more effective and faster which is important for enterprise.

I rate the tool a nine out of ten.

Microsoft Azure Machine Learning Studio can be used for a variety of machine learning tasks, including deployment and creation of new components.

The stability and performance of the solution are good. But there is nothing specific to point out since it works smoothly.

Though I won't outrightly state it is an expensive solution, I think it should be made cheaper for certain people.

I have been using Microsoft Azure Machine Learning Studio for six to eight months. There are no versions of the solution since it is a complete set of tools that Microsoft provides. Hence, I highly doubt if there is some version.

It is a pretty stable solution. Stability-wise, I rate the solution a nine out of ten.

It is a scalable solution. I do not know how many users are using the solution in my company since I am not from the administration department. So, maybe people from the administration department might know the number of users in our company.

I am not aware of how many technical staff members are needed for deployment and maintenance.

I have never contacted the technical support team of Microsoft since I never need their help.

The solution's initial setup process was pretty straightforward.

I just worked with the company, and so the installment and everything else were taken care of by their infra team.

Since I am a normal employee working in my company, I don't know whether the company has experienced any return on investment using the solution.

The solution operates on a pay-per-use model.

I can recommend the solution to others planning to use it. It is important to note that the solution is a bit costly. But, then the cost depends on the requirements of the person planning to buy it.

It's difficult to say whether Microsoft Azure is costly or not since it depends on individual needs. Time is important for some, and the tool is very time-efficient, making it seem less costly. It may appear costlier for those who don't consider time important.

Overall, I rate the solution a nine out of ten.

Developing and operationally implementing a powerful lead scoring model for a major Multiufamily developer and operator of apartment properties throughout major western states. The work included 3 years of data across over 60 properties with more than 500,000 leads and 3 million transactions.

Increased sales force productivity by permitting them to prioritize activity during peak leasing periods on those leads most likely to close

The ability to do the templating and be able to transfer it so that I can easily do multiple types of models and data mining is a valuable aspect of this solution. You only have to set up the flows, the templates, and the data once and then you can make modifications and test different segmentations throughout.

We were working across a number of internal departments as well as some outside departments and this solution made it extremely easy to communicate across functional area because it was all in flow chart and data form so that if somebody had an issue, like changing the data set or something like that, they could point right to it and we could get that handled and incorporated into the model. It's extremely efficient on the computer. We had to do a number of resets on the data in the model and to be able to turn things around and validate the model and the new set in two hours, was just incredible for me.

It was very robust. The ability to move the objects around so easily and then communicate is really its power. Then to be able to show it to the sales and senior management, in terms of what was employed and made it very easy to get my job done.

In terms of improvement, I'd like to have more ability to understand the detailed impact of the variables on the model and their interactions. Their algorithms are very powerful and they explain overall the net contribution of each of the variables to the solution. In terms of being able to say to people "If you did this, you'll get this much more improvement" Azure (at least my understanding of it) doesn't provide readily accessible tools to assess from a management perspective the impact of their changing a sinimized, the better.gle value - for instance in closing a lead, decreasing response time by 10%.

I recognize that the multivariate algorithms used from decision trees to neural nets do not readily provide the coefficients for each variable ala the older regression modeling approaches. My experience over my 50 years of developing and implementing predictive models has been that more than half the value of modeling lies in improving management's understanding of the process being modeled, often leading to major organization and operational structure changes. More ability to understand the variables impacting the end result being optimized would be very useful. 

I have worked extensively with this solution for the last three years. 

I haven't had any problems with stability. 

I didn't have any issues with the scale. we rapidly went from test to full implementation across all datasets.

I never had to use technical support.

I have used SPSS modeler (part of WATSON really) but because client was a Microsoft shop, I switched to Azure.

I found the setup to be very easy. I've been doing this type of work for 50 years so the modern terminology isn't always the same as what I grew up with. It took me a while to understand that, but the setups were very easy. As with anything, the hardest part is always getting the data together, but the outside consultants had built up a very, very good data warehouse. The ability to manipulate the data and create variables was very nice.

THIS IS THE ONLY MODELING APPROACH THAT EVER WORKED THE VERY TIME I RAN IT!!

Because client isa Microsoft shop, everything was Microsoft in terms of having solutions like Power BI and stuff like that. Azure is very useful and very inexpensive.

The major advice I give is that clients must get the user,somebody who understands the business issues, to be deeply involved with it and the data transformation. Most people don't. And that's true for data science applications. We don't just follow the data in a big pile and remodel, we advance the process that we're modeling. Consider what transformations of the data you need to make it workable and usable.

Remember, over half the initial value of modeling is the strategic understanding provided re the importance of different variables to the model and hence the organizaion's performance. Very often the modeling identifies opportunities for changing structures, decision rules, etc. even prior to the model's actual implementation technically.

I would rate it a nine out of ten.

We have data from our business, and we want to make AI models. The question is how we want to use those models in our business. That's what we're going to do next year.

The product is well organized. The thing is how we will get the models to work within our code. We have some suggestions there, but we want to gain more experience and be ready to answer that because we are currently working on this and don't have all the answers yet.

The tool is well organized. What I am very happy about is the ease of deploying new resources. You can easily create your pipeline within minutes.

One problem I experience is that switching between multiple accounts can be difficult. I don't think there are any major issues. Mostly, the biggest challenge is to identify business solutions to this. 

The tool should keep on updating new algorithms and not stay static. 

I have been working with the product for ten years. 

I rate Microsoft Azure Machine Learning Studio's stability as nine out of ten. 

I rate the solution's scalability a ten out of ten. I am the single user of Microsoft Azure Machine Learning Studio. 

We haven't had any experience with the tool's support because we didn't use it. We are mature developers and don't need it at this time. We don't have any complex business needs.

The tool's deployment time depends on the resource you will deploy. Some resources are deployed within minutes, while others may take more than 15-20 minutes. I have deployed mostly web applications, REST APIs, and databases.

We're trying to provide robust solutions to our customers, which previously involved multiple steps. Now, we're going to provide it in one step. That is our benefit because the customer will get a final solution, not a solution in steps. We will formalize and streamline them to align with our new solutions.

We pay only the Azure costs for what we use, which involves some subscription costs. But essentially, you pay for what you use. There are no extra costs in addition to the standard licensing fees.

We are trying to find some commercial value. I have learned how to use it, and we will integrate it into the project. That's our next goal.

I rate Microsoft Azure Machine Learning Studio a ten out of ten. If you want to use it, get the certifications, and then work on some projects to gain more experience.

We used this product as implementers. For example, a client wanted to use the Azure stack, specifically Azure Machine Learning Studio. Microsoft was a consultant on the project, and we were the implementation partner.

There are actually two tools. One is Azure Machine Learning Designer (which used to be called Azure Machine Learning Studio), and the other is Azure Machine Learning. Designer is a drag-and-drop interface, primarily for those without extensive coding expertise.

Azure Machine Learning has become the de facto product, and it allows you to write code and provides numerous components for building machine learning models.

We build all our machine-learning models using ML Studio. That's the primary purpose for us. We build standard models that use data and various algorithms.

My expertise was focused on the analytics aspect. We worked in a large firm with different teams responsible for MLOps and integrating outputs with other systems. 

My responsibility was to get data, build models, and provide the output. How the output was rendered and the process of doing so was handled by other teams. 

Additionally, there's a separate team that handles the productionalization of machine learning models. It's a diverse team structure, so the scope of the totality of the integration process varied. Essentially, they take the model I build, use Azure DevOps for versioning, and then deploy it to production.  

Everything in Azure is very intuitive. As a Microsoft product, it's designed that way. You can easily search for things, and many features are built-in. Many things can be easily done via drag-and-drop.

We often use custom code that we can template or create as boilerplate code for different teams. It sounds difficult, but Azure makes it very easy. 

The learning curve is very low. Operationalizing the model is also very easy within the Azure ecosystem.

The drag-and-drop interface specifically improves our workflow a lot. Designer simplifies the process when we want to create a quick model. It makes things very, very easy. It's a great starting point.

When we want to create models, model management and deployment are crucial. We had boilerplate code ready, and Azure made it significantly easier to deploy using its services. That was the easy part.

In terms of data capabilities, if we compare it to Google Cloud's BigQuery, we find a difference. When fetching data from web traffic, Google can do a lot of processing with small queries or functions. Azure didn't have that same inbuilt feature for website traffic or analytics, unlike Google DB and BigQuery.

I started using it around the year 2020. We used it up to 2023, so roughly two years.

It is a stable product. I would rate the stability a nine out of ten. 

It is a scalable solution because it works well for large databases.

I would rate the scalability a nine out of ten. 

The customer service and support are good. 

Positive

We've used Google Vertex AI and AWS SageMaker.

I was not involved in the deployment process. But there is maintenance. It was quite a headache. 

Maintenance does require attention. With any cloud implementation, cost optimization is a major factor. Our team had discussions about it. 

I would rate the pricing an eight out of ten, with ten being very expensive. Not very expensive, not very cheap.

It was on a yearly basis, and there were also usage-based costs.

If it's my recommendation, it's a very competent product. It has all the necessary features for data engineering, data science, and model management. 

It's a complete suite of products that can address your end-to-end data needs.

Overall, I would rate the solution a nine out of ten. 

The first time that I used this tool was in a project related to bike usage in the city of Boston. This project was part of a course that I concluded some months ago. In this project I used components to read data, for exploratory analysis, for steps of data munging, to split data, select hyperparameters, and some machine learning algorithms. In some steps I needed to insert R modules to apply some data transformation.

The target of this exercise was to predict bike usage in a day.

With this tool we could have all benefits of a cloud environment, such as scalability and access to machine-learning applications. These features are very important when you have large datasets and critical applications.

• It is very easy to test different kinds of machine-learning algorithms with different parameters. You choose the algorithm, drag and drop to the workspace, and plug the dataset into this component.
• When you import the dataset you can see the data distribution easily with graphics and statistical measures.
• Easy to deploy and provide the project like a service.

For my project/exercise, this tools was perfect. I would like to see modules to handle Deep Learning frameworks.

No issues with stability.

No issues with scalability.

I didn’t need to use the support, but this tool has great documentation.

Nowadays I use Python (Anaconda and Jupyter Notebook) and R (RStudio) to create my solutions and machine-learning models.

It was very simple and straightforward. It is really simple to start building a project.

There are two kinds of licenses, Free and Standard.

Free

• 100 modules per experiment.
• 1 hour per experiment.
• 10GB storage space.
• Single Node Execution/Performance.

Standard – $9.99/seat/month (probably a data scientist)

• $1 per Studio Experimentation Hour. You will pay according to the number of hours your experiments run.
• Unlimited modules per experiment.
• Up to seven days per experiment, 24 hours per module.
• Unlimited BYO storage space.
• On-premises SQL data processing.
• Multiple Nodes Execution/Performance.
• Production Web API.
• SLA.

You will be able to create your machine-learning project and extract insights from it just by dragging and dropping components and adjusting some parameters. This tool is very user-friendly, so without a lot of programming skills you can build machine-learning projects. 

If you need more control over machine-learning modules you will need to add R or Python modules to create a customized machine-learning model.

We use Microsoft Azure Machine Learning Studio to generate predictive sales analytics and determine customer behavior.

Through the solution's customer data analysis, we conduct customer data experiments, test hypotheses, and develop sales strategies.

The solution is integrated with our Microsoft Azure tenant, and we don't have to go anywhere else outside the tenant. The solution's data pipelines are easier to configure, and the solution provides a range of tools and libraries we can access.

It would be great if the solution integrated Microsoft Copilot, its AI helper.

I have been using Microsoft Azure Machine Learning Studio for one year.

The solution's stability depends on the fragility of libraries and the availability of services. Sometimes, the demand is very high in the public cloud, and performance and availability issues have occurred.

I rate the solution a six out of ten for stability.

Microsoft Azure Machine Learning Studio is a very scalable solution. Three people are using the solution in our organization.

I rate the solution an eight out of ten for scalability.

I rate the solution a seven out of ten for the ease of its initial setup.

The solution’s deployment takes one hour.

There is a lack of certainty with the solution's pricing. The risk is the pricing is high without you necessarily knowing. The workload drives the solution's pricing. If you give it a lot to do, it will cost a lot of money. It's about committing to how much you want to pay for. You don't necessarily know what you'll get for the price level that you agree.

On a scale from one to ten, where one is cheap and ten is expensive, I rate the solution's pricing a seven out of ten.

Before choosing the solution, we evaluated Databricks. We chose Microsoft Azure Machine Learning Studio to get as close to the Microsoft pattern as possible. We have a Microsoft first policy, and therefore, unless there's a reason not to use Microsoft, we choose Microsoft.

I would recommend Microsoft Azure Machine Learning Studio to other users. I would also ask users to compare the solution with Microsoft Fabric, which is a collection of components to put a workflow together end to end.

Overall, I rate Microsoft Azure Machine Learning Studio a seven out of ten.