Install Jentic One Beta

Connect the ManagedLabsClient to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the ManagedLabsClient, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fazure.com%2Fazure-managedlabsclient" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fazure.com%2Fazure-managedlabsclient" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with ManagedLabsClient API.

Create and manage lab accounts that group labs under a billing and policy boundary

Provision labs inside a lab account with size limits, expiration, and shared password policy

Configure environment settings that define the VM template, size, and network for a lab

GET STARTED

Start building with ManagedLabsClient API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use ManagedLabsClient API for, with concrete tasks.

★ Classroom Lab Provisioning

Universities and corporate training providers deliver hands-on courses by provisioning a lab per cohort. ManagedLabsClient creates the lab account, the lab itself, and the environment setting that ties the lab to a Windows or Linux gallery image. Students are added by email and Lab Services creates a per-user environment cloned from the template, ready before class starts.

Create lab account 'data-science-training' in westus, then provision a lab 'spring-2026-cohort' with 30 maxUsersInLab and an environmentSetting using gallery image 'Win11-DataScience' on Standard_D2s_v3, then add student emails from a CSV.

Per-Student Environment Lifecycle

Instructors start a student's lab VM right before class and stop it at the end to keep compute spend predictable. The Environments resource exposes Start and Stop on each per-user environment, and the GlobalUsers GetEnvironment endpoint lets a student-facing portal fetch the connection details on demand. Reset returns the environment to template state for a fresh session.

List environments in lab 'spring-2026-cohort' with status=Stopped, call Start on each one assigned to today's session attendees, and return their RDP connection URLs.

Cohort Cost Control

Operations teams cap classroom spend by stopping all running environments in a lab at the end of the day and removing expired labs from the lab account. Listing environments by status and bulk-stopping is a common end-of-day routine. Lab expiration is enforced through the lab's expirationDate property, and Labs_Delete cleans up everything underneath.

List all labs in the lab account, stop every Environment with status=Started across labs, then DELETE any lab whose expirationDate is more than 7 days in the past.

Gallery Image Curation

Course owners curate which VM images students can launch by approving gallery images for a lab account. GalleryImages_List returns every available image in the lab account; updating an image's isEnabled flag controls whether instructors can select it when configuring environment settings. This keeps lab launches consistent with curriculum requirements.

List GalleryImages in lab account 'data-science-training', then PATCH the image named 'Win10-Office' setting isEnabled=true so instructors can use it in new environment settings.

AI Agent Lab Operations

Operations agents that own classroom infrastructure use Jentic to discover Lab Services operations on demand. Searching for an intent like 'start a lab services environment' returns the matching schema; the agent loads it and executes against management.azure.com using a token retrieved from your Jentic One instance, so per-cohort routines do not require bundling the Lab Services SDK.

Use Jentic to search 'start an azure lab services environment for a user', load the Environments_Start schema, and POST to start the per-user environment for each student in the day's session.

Key Endpoints

55 endpoints — jentic publishes the only available openapi specification for managedlabsclient, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/providers/Microsoft.LabServices/users/{userName}/listEnvironments

List all environments assigned to a global user

POST

/providers/Microsoft.LabServices/users/{userName}/listLabs

List labs a global user is enrolled in

POST

/providers/Microsoft.LabServices/users/{userName}/getEnvironment

Fetch a single environment with connection details

POST

/providers/Microsoft.LabServices/users/{userName}/register

GET

/providers/Microsoft.LabServices/operations

List Microsoft.LabServices provider operations

POST

/providers/Microsoft.LabServices/users/{userName}/getPersonalPreferences

Get a global user's personal lab preferences

POST

/providers/Microsoft.LabServices/users/{userName}/listEnvironments

List all environments assigned to a global user

POST

/providers/Microsoft.LabServices/users/{userName}/listLabs

List labs a global user is enrolled in

POST

/providers/Microsoft.LabServices/users/{userName}/getEnvironment

Fetch a single environment with connection details

POST

/providers/Microsoft.LabServices/users/{userName}/register

GET

/providers/Microsoft.LabServices/operations

List Microsoft.LabServices provider operations

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Microsoft.LabServices management API by hand means registering an Azure AD app, negotiating OAuth 2.0 tokens for management.azure.com, and carrying user and lab scope through every classroom lab call. Through Jentic you install once, import ManagedLabsClient from the API Directory, store the Azure AD credential once, and your agent calls it.

Permission scoping

This API puts the user in the URL path (/users/{userName}/listLabs, /users/{userName}/getEnvironment), so a rule can pin your agent to one user: it can list that user's labs and environments and read their preferences. You choose the operations it may call, so registering the user to a lab is not included unless you add it.

Credential isolation

Your Azure AD credential for the LabServices control plane is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'list a lab user's environments' or 'read lab personal preferences', and Jentic returns the matching LabServices operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using ManagedLabsClient API through Jentic.

Why is there no official OpenAPI spec for ManagedLabsClient?

Microsoft Azure does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call ManagedLabsClient via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the ManagedLabsClient use?

AAD OAuth 2.0 bearer tokens scoped to https://management.azure.com/. With Jentic, AAD client credentials are stored encrypted in the vault and a short-lived bearer token is injected at call time.

Does this API replace Azure DevTest Labs?

No - Azure Lab Services (Microsoft.LabServices) and Azure DevTest Labs (Microsoft.DevTestLab) are separate offerings. Lab Services is built for classroom and training scenarios with simple per-user VMs; DevTest Labs is aimed at developer and test environments with formulas, artifacts, and policies for engineering teams.

What are the rate limits for the ManagedLabsClient?

Standard Azure Resource Manager throttling - typically 12,000 reads and 1,200 writes per hour per subscription per region. Environment Start and Stop calls are asynchronous and return 202 Accepted; the GlobalUsers GetOperationStatus endpoint surfaces progress.

How do I start a student VM through Jentic?

Run pip install jentic, then search Jentic for 'start an azure lab services environment for a user'. Jentic returns the Environments_Start operation; load it, supply the lab account, lab name, environment setting name, and environment name, and POST to /environments/{environmentName}/start.

Can I use this API to run production workloads?

No. Lab Services VMs are scoped to short-lived training scenarios with shared-password access and no SLA-grade guarantees. Production workloads should use Microsoft.Compute virtual machines or virtual machine scale sets via the standard compute APIs.

Can I limit what my agent is allowed to do with the Azure Lab Services API?

Yes. Because you run Jentic One yourself, your own rules decide which Lab Services operations and credentials the agent may use. This API puts the user in the URL path, as in /users/{userName}/listLabs and /users/{userName}/getEnvironment, so a rule can pin the agent to a single user and let it list that user's labs and read their environments and preferences. You choose the operations it may call, so an action like registering a user to a lab or starting an environment is only available when you add it.

Microsoft Azure ManagedLabsClient

Name: ManagedLabsClient API
Brand: ManagedLabsClient
Availability: InStock

Browse all Azure APIs

Agent-ready OpenAPI document · curated by JenticEducationLmsoauth255 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Provision and manage Azure Lab Services accounts, labs, gallery images, and per-user training environments. Use for classroom and training VM lifecycle, not for production virtual machine workloads.

Use for: Create a new lab account for the data science training programme, Provision a lab inside the 'training' lab account with a 30-user cap, Set up environment settings using a Windows 11 gallery image with Standard_D2s_v3 VMs, List all environments assigned to user 'student@example.com' across labs

Not supported: Does not run production VMs, manage Microsoft.Compute virtual machines, or act as a learning management system - use only for Microsoft.LabServices classroom and training lab lifecycle.

Jentic publishes the only available OpenAPI specification for ManagedLabsClient, keeping it validated and agent-ready. ManagedLabsClient is the Azure Resource Manager surface for the Microsoft.LabServices provider - Azure Lab Services. It provisions lab accounts, the labs inside them, gallery images for VM templates, environment settings, and the per-user environments that students and trainees connect to. It is purpose-built for classroom and training scenarios where many short-lived VMs must be created from a shared template.

Jentic One on Github View OpenAPI Document

Connect the ManagedLabsClient to your agent

Capabilities

Start building with ManagedLabsClient API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Microsoft Azure ManagedLabsClient