Tools· Software Development & Technical Infrastructure

    Azure Machine Learning Studio

    Microsoft enterprise platform for the full model lifecycle, from training and model catalog through to secured endpoints inside your own Azure network.

    executabledata-drivenautomatingkommerziell

    Description

    Strengths

    Full ML lifecycle
    Training, deployment, monitoring, and governance run in one system, from the workspace as the organizing unit through to a production managed endpoint.
    Extensive model catalog
    More than 1,900 models from providers such as Azure OpenAI, Mistral, Meta, Cohere, NVIDIA, and Hugging Face are searchable, with a leaderboard and benchmark metrics for select models.
    Automated ML
    AutoML takes over featurization and algorithm selection, otherwise a repetitive, time-consuming manual task, usable through the studio interface or the Python SDK.
    Managed endpoints for inferencing
    Standard deployment, online endpoints, and batch endpoints abstract away the infrastructure for real-time and batch model scoring.
    Enterprise security through Azure
    Access control through Microsoft Entra ID and roles, network isolation through virtual networks, encryption of data in transit and at rest.

    Assessment

    AI features

    • Prompt Flow A development tool that covers prototyping, experimenting, iterating, and deploying LLM-powered applications in one continuous cycle.
    • Model catalog (Foundry Models) Foundation, reasoning, small language, and multimodal models can be found through keyword search and filters and deployed directly from the catalog.
    • Serverless model deployment Microsoft hosts selected models on managed infrastructure with API access and mostly token-based billing, without consuming your own compute quota.
    • Hosted fine-tuning For models that support serverless deployment, fine-tuning with your own data can be run directly through the platform.

    Suitable for

    • Teams already running on Azure that operate ML workloads with governance, role, and audit requirements
    • Data science teams that want to stay in one continuous platform from training through to a production managed endpoint
    • Generative AI projects that need pretrained or fine-tunable foundation models from the model catalog, for example for Prompt Flow or RAG applications
    • Less suitable for Less suitable for individual developers or small teams without an Azure footprint who want to try out a single model through an API quickly and with minimal setup

    Limitations and notes

    • Compute quota required For endpoint types with dedicated compute, sufficient VM quota must already exist in the Azure subscription, otherwise the deployment cannot start.
    • CSP subscriptions excluded Cloud Solution Provider subscriptions cannot purchase standard deployment models from the model catalog.
    • SSH access sits outside role management SSH access to compute instances and compute clusters runs on public and private key pairs, not through Microsoft Entra ID, and Azure RBAC does not govern it.
    • Separate billing for additional services Using Azure Machine Learning itself costs nothing extra, but compute and consumed services such as Blob Storage, Key Vault, Container Registry, and Application Insights are billed separately.

    Quick start

    1. Create a workspace from the studio welcome screen, the Python SDK, or the Azure CLI, as the central organizing unit for the project.
    2. Create a compute instance for the development environment.
    3. In the studio web portal, open the included sample notebooks or create a new notebook.
    4. Run a training script or select a suitable model from the model catalog.
    5. Deploy the model as a standard, online, or batch endpoint, depending on latency and volume requirements.

    Tips

    • Do not grant access to the workspace's storage account to users who should not have access to its compute resources, since it holds the code that runs on the workspace computes, and whoever can change it gains access to workspace data and credentials.
    • For prototyping LLM applications, try Prompt Flow first instead of building the infrastructure for it manually.
    • Before a production deployment, choose the right endpoint type: standard deployment for supported foundation models, online endpoints for low latency, batch endpoints for large data volumes without latency requirements.
    • For stable, predictable workloads, check reserved VM instances; for changing workloads with a fixed hourly commitment, check the Azure savings plan for compute, to lower ongoing costs.

    Access

    Last reviewed: · Pricing, plans and features are a snapshot in time. Check the provider's own page before deciding.

    In the workshop this becomes your method.

    Whoever sees this process run once wants the agent behind it next. We build that in the workshop From Process to Agent.

    View workshops

    Related resources

    Browse all resources

    Conversation, not pitch

    Understand first, then decide. We take time for an initial conversation, without sales pressure, without obligation.

    Schedule a call