Microsoft Azure Machine Learning Studio Reviews

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.

I've had experience working for two distinct companies. My previous employer operated in the telecom domain, primarily focused on telecom-related projects. In my current role, which is in the shipping domain, we primarily manage shipping cases. Furthermore, our current work predominantly revolves around a machine learning platform implemented on storage systems.

In the Machine Learning Studio, particularly the Designer part, which is essentially Azure's demo designer, there is room for improvement. Many customers and users tend to switch to Microsoft Azure Multi-Joiners, which is a more basic version, but they do so internally.

One area that could use enhancement is the process of connecting components. Currently, every time you want to connect a component, such as linking it to your storage or an instance like EC2, you have to input your username and password repeatedly. This can be quite cumbersome. Google, for instance, has made it more user-friendly by allowing easy access for connecting services within a workspace. In a workspace, you can set up various resources like storage, a database cluster, machine learning studio, and more. When connecting these services, there's no need to enter your username and password each time, making it a more efficient process. Another aspect to consider is the role of the designer, and they were to integrate a large language model to handle various tasks, it could significantly enhance the overall scalability and usability of the platform.

I have been working with Microsoft Azure Machine Learning Studio for three years. 

I would rate it eight out of ten. 

I would rate it eight out of ten.

Yes, I have worked with Azure in my previous experiences.

There isn’t any such expensive costs and only a standard license is required. 

My company uses Microsoft Azure Machine Learning Studio to help our company's customers view AI solutions.

My company's clients' use cases will be that they use the solution to feed information to the system about their customers who purchase from them. The solution also helps one to combine products to engage in cross-selling and upselling activities while keeping track of customer lifetime value. The solution also helps its users with the pricing simulation part to figure out what prices are good for the business and maximize the closing of the sale.

The most valuable feature of the solution is the availability of ChatGPT in the solution.

Improvement will be possible with more machine learning functionalities in Microsoft Azure Machine Learning Studio since, at times, the current accuracy of the solution is not good enough. It would be good if Microsoft Azure Machine Learning Studio could have a generative AI tool similar to ChatGPT.

I have been using Microsoft Azure Machine Learning Studio for three years. My company functions as a reseller and a partner of Microsoft.

Stability-wise, I rate the solution a seven out of ten. With ML, you may face some data-related issues, especially considering that when dealing with customers at times, the data that comes in might not be clean. Stability-wise, you may face certain problems when you fail to refresh the data in the solution.

Scalability-wise, I rate the solution a seven out of ten. My company still has to do some of our own optimizations to the data part of the solution until and unless we subscribe to some third-party data lake services, which is a better option but comes at a higher cost.

My company's client's organization has around 10 to 50 users of the solution.

My company caters to the requirements of medium and enterprise-sized companies.

I rate the technical support a six out of ten.

Neutral

I rate the initial setup phase of the solution a six on a scale of one to ten, where one is difficult, and ten is easy. The initial setup phase of the solution was a bit complex. The setup phase is a bit difficult if you want to view Microsoft Azure Machine Learning Studio as an application.

The solution is deployed 50 percent on the cloud and 50 percent on-premises.

Considering the fact that my company currently builds some standard solutions, Microsoft Azure Machine Learning Studio's deployment takes us around two to three months.

I rate the solution's pricing a four on a scale of one to ten, where one is cheap, and ten is expensive.

There are some additional payments to be made apart from the licensing fees of the solution since buying Microsoft Azure Machine Learning Studio alone won't make it a complete solution. You will need the database and data lake services.

Microsoft Azure Machine Learning Studio does not allow users to have a PnP option, like an ERP or a CRM system, where everything works if you include the data with the system. Sometimes, it is difficult to generate good patterns using the solution. You need to have good experience with the solution to move around with the data from the beginning before coming up with different strategies to end different problems. In general, the product is not a straightforward solution.

There is a need for Microsoft Azure Machine Learning Studio's users to put in some programming efforts to make the solution work accurately under different scenarios.

I rate the overall solution a six out of ten.

Our use cases  involve customer segmentation for targeted marketing, where I use machine learning to identify potential customers interested in a new product. Another is a recommendation system on our company website, where I use machine learning to suggest additional products to customers based on their browsing or purchase history. Lastly, there is pricing estimation, where I use machine learning to predict the price of an item or article.

The features of Azure Machine Learning Studio that I find most valuable depend on the type of model I'm working with. For integration, knowing halfway indicators is crucial to assess model performance. For classification models, the confusion matrix is important for evaluation, while for regression models, statistical tests like the provision statistics are valuable.

One area where Azure Machine Learning Studio could improve is its user interface structure. Simplifying the initial information presented upon first use could make it more accessible, especially for users with limited technical skills. Providing only essential information upfront would enhance the user experience and reduce complexity.

I have been working with Microsoft Azure Machine Learning Studio for three years.

I would rate the stability of the solution at a six out of ten. Improving stability involves finding people with the right skills to handle problems that arise. While stability depends on how well the solution is installed, ongoing efforts are needed to address issues and refine the system. We are working step by step to identify and solve problems, but there's room to find more comprehensive solutions as they come up.

I would rate the scalability of Azure Machine Learning Studio at about a seven out of ten. While it offers high scalability, it can be challenging for less technical users and may encounter issues with defects and industrial licensing, particularly in logistics projects.

At our company, we use Azure Machine Learning Studio daily.

Before Microsoft Azure Machine Learning Studio, we used on-premises solutions. We made the switch to Azure Machine Learning and the cloud to modernize our projects and leverage the benefits of cloud computing.

I use Azure Machine Learning Studio for predictive modeling in my project. I follow a workflow that involves selecting data, preprocessing it, training models, and deploying them. The Studio's tools cover all these steps, making it convenient for me to build and deploy predictive models.

In a specific scenario, I used Azure Machine Learning Studio for data preprocessing by creating new variables. This involved tasks like transforming variable types or combining multiple variables to create new ones. Additionally, I employed cross-validation techniques, such as k-fold validation, to assess model performance and select appropriate metrics for evaluation.

The most important aspect of my machine learning projects is the quality of the data. It is crucial to determine whether the data can provide meaningful information relevant to the project's use case, regardless of the specific tools or features used.

The drag-and-drop interface of Azure Machine Learning Studio has greatly improved my workflow. It is easy to use and increases productivity by allowing quick experimentation and visualization of data pipelines. This feature enables me to iterate rapidly and efficiently, especially for small projects or presentations.

I would rate the performance of the solution at an eight out of ten for my team. However, our data volume is not the largest. While I believe our performance is strong, other companies might rate it lower due to different circumstances.

My advice for someone considering installing Azure Machine Learning Studio is that it is user-friendly, especially for technical users. You can easily upload data and analyze it with the examples provided. The drag-and-drop interface makes it intuitive, and upgrading to this tool for data analysis is a good idea.

Overall, I would rate Azure Machine Learning Studio as a nine out of ten.

I've developed a couple of chatbots using Azure OpenAI, leveraging its documented solutions and APIs. The tools available make it straightforward to implement machine learning solutions. However, there are challenges, such as hallucinations and security issues, but overall, it works well and is quite fast, allowing for the development of interesting projects.

The main issue is identifying a solid business case. There are many exciting use cases, and we have done numerous proofs of concept, prototyping, and piloting, which generated a lot of excitement. However, determining which business case to implement, especially when it competes against other applications, becomes challenging.

Improvement in integration is crucial, and it'll be interesting to see how it develops, especially with SAP's move towards cloud-based solutions like SAP Rise and its collaboration with hyper scalers like AWS. Integrating SAP with hyperscaler machine learning solutions could simplify operations, although SAP's environment is complex. SAP has initiated deals with AWS for this purpose, but I'm not as familiar with Microsoft Azure Machine Learning Studio's involvement.

We started exploring Azure Machine Learning Studio about three years ago. We conducted POCs with it, but very few projects made it to production. After that, our company shifted to AWS. We did several POCs there, too, but none went into production. So, my experience with Azure Machine Learning Studio and AWS is mostly on the POC and experimentation side, without actually deploying any solutions into production.

The technical support is very good. We receive regular calls and have a key account assigned to our company because we are a large client. This makes it easy to get the information and help we need. However, for smaller companies that do not have a key account executive assigned, it might be a bit more difficult. Overall, the experience with the tool's technical support has been very positive.

Neutral

Microsoft takes an application-based approach with Azure Machine Learning Studio. It started as an application development company and moved into the cloud. On the other hand, AWS is built up from bits and bytes, which is a different approach. AWS offers many ways to accomplish the same tasks, which can be initially confusing. They are working to make it more application-oriented. Microsoft focuses more on solving business problems by first building application solutions, with technology supporting those solutions. 

Working with clients who prefer AWS for their hyperscaling needs, such as hosting SAP systems on the AWS cloud, aligns better with AWS products than using another hyperscaler like Microsoft Azure Machine Learning Studio. That's the advantage of choosing AWS—it offers high hyperscale capabilities.

AWS is recommended for companies that have strategically decided to prioritize security and are considering cloud providers like AWS. Initially, the main concern was security. Once security concerns are addressed, the next challenge is how well the various services integrate and work together. AWS can be a suitable choice if a company has determined that it needs flexibility and a wide range of services. Developing solutions with AWS took significant time for the company I work with.

I would rate the product a nine out of ten. Compared to AWS SageMaker Studio, it is easier to use, especially when handling data and working with Python. AWS is a bit tougher because it relies heavily on containerization, which can be tricky for organizations due to security or cost issues.

I don't know much about MLOps, especially the full circle, which includes monitoring and observability. From an experimentation point of view, the tool and AWS are good, but I'd rate Azure slightly higher because it is simpler. You don't need to understand various underlying services as much as you do with AWS. This difference is due to Microsoft's top-down design approach, coming from their application background.

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.

Our customers use the solution for its automated machine-learning features.

The solution's learning models developed using Python coding are not robust. The AI features need to summarize vast amounts of data into simple models. It must understand all the mathematical parameters and formulas within the models for reliable predictions. They need to work on this particular area. Also, they should provide integration with Microsoft Teams as well.

We have been using the solution for three and a half years.

The solution is stable. I rate its stability an eight compared to Mathematica.

The solution is scalable.

The solution's technical support is excellent. They respond and resolve queries promptly, irrespective of the type of subscription one has purchased.

Positive

In comparison, Mathematica is more expensive than the solution.

The solution's initial setup process is complicated. We need to get details on web service activities, identify internet services, manage service identity, etc. The time taken for deployment depends on the complexity of the specific model. It takes around a quarter of an hour per model to complete, on average.

We have to pay for the solution's machine and storage. The cost depends on the specific models. Some of them cost 18 to 25 cents per hour. At the same time, some CPU machines cost €30 per hour.

The solution is easy to use. I advise others to train to know how it works while learning the mathematics behind it. I rate it an eight out of ten.

Microsoft Azure Machine Learning Studio can be used for developing models, such as predicting energy usage, as I did for my bachelor's project, where I predicted future energy usage for a city in Norway. The solution can also be used for classification tasks, such as identifying objects in images.

In terms of features, I personally find Azure to be clearer and better than Google because it provides better quality and clarity regarding what needs to be done.

The icons in the solution could be improved to include examples of how to use each container, as sometimes it's unclear which container to choose. It would be helpful to provide examples to understand better which virtual machine or how many courses to use. Overall, the icons in the solution could be improved to provide better guidance to users.

Additionally, the setup process for the solution could be made easier.

I have been using Microsoft Azure Machine Learning Studio for half a year. I am a student and user of the solution.

I think Microsoft Azure Machine Learning Studio is more stable than Google.

In terms of scalability, I believe that the solution is good. Although I have only used it for two projects, I think that it provides a good level of scalability. However, as I have only used it within my organization, I may not have experienced all of the possibilities that the solution offers.

Regarding the technical support for the solution, I find the documentation provided comprehensive and helpful. It is often the case that everything one needs is already in the documentation, so I haven't had to use the support much. Even when I have reached out for support, I have always received a prompt response.

The initial setup for me was initially quite complex, but after completing a course related to Microsoft Azure Machine Learning Studio, it became less complex. However, one needs to have a good understanding of the required parameters and what the model needs to do in order to achieve good performance. So sometimes, it's not that simple. The deployment process took me a couple of hours to complete. I was able to do it quickly because I was using Azure Machine Learning Designer and Python SDK while also learning automation. The setup process for AltaML was easy and could be completed in hours. With Python SDK, the setup process was quite long because of the code that needed to be written, so one needs to know what to write.

I used the free student license for a few months to operate the solution, but I'll have to pay for it if I want to do more now.

Before choosing Microsoft Azure Machine Learning Studio, I only evaluated Google Cloudpath.

If you plan to use this solution, I suggest you not be intimidated by its complexity at first. You will gain more clarity regarding the solution over time with perseverance and practice. Overall, I rate the solution an eight out of ten.