Microsoft Azure DevSpacesManagement
Browse all Azure APIs★ Only Publicly Available OpenAPI DocumentDeveloper ToolsCi Cdoauth29 EndpointsREST
For Agents
Manage Azure Dev Spaces Controllers — provision controllers, list them, update tags, retrieve connection details, and delete controllers under Microsoft.DevSpaces.
Use for: Provision a new Dev Spaces controller in a resource group, List all Dev Spaces controllers in a subscription, Retrieve the connection details for a Dev Spaces controller, Delete a Dev Spaces controller that is no longer needed
Not supported: Does not manage AKS clusters themselves, deploy applications into Dev Spaces, or run developer-side debugging — use for Microsoft.DevSpaces controller lifecycle only.
Jentic publishes the only available OpenAPI specification for DevSpacesManagement, keeping it validated and agent-ready. The API manages Azure Dev Spaces Controllers under Microsoft.DevSpaces — the legacy preview service that paired with AKS to give developers per-developer namespaces and live debugging. It covers controller create, get, update, delete, listing at subscription and resource-group scope, and the listConnectionDetails action used to bootstrap kubectl access.
Install Jentic One Beta
Connect the DevSpacesManagement to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the DevSpacesManagement, 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.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic 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 DevSpacesManagement API.
Provision a Dev Spaces controller in a resource group
List Dev Spaces controllers at subscription and resource-group scope
Retrieve a specific Dev Spaces controller and its configuration
Patch tags and configuration on an existing controller
Delete a Dev Spaces controller
List connection details (kubeconfig and endpoint) for a controller
Use Cases
Patterns agents use DevSpacesManagement API for, with concrete tasks.
★ Per-developer AKS workspaces
Engineering teams using Azure Dev Spaces provision a controller against their AKS cluster so each developer gets an isolated namespace for live debugging and inner-loop testing. The API creates the controller, returns its configuration, and exposes connection details so the developer's tooling can wire up kubectl without manual portal steps.
Create a Dev Spaces controller named 'team-controller' in resource group 'team-rg' targeting the AKS cluster 'team-aks' in West Europe
Connection details bootstrap
When a new developer joins, their tooling needs the controller's connection details — endpoint and kubeconfig payload — to start operating against their namespace. The listConnectionDetails endpoint returns this information for the named controller so an onboarding script can configure the developer's machine programmatically.
Call listConnectionDetails for controller 'team-controller' in resource group 'team-rg' and return the endpoint and kubeconfig payload
Decommissioning legacy controllers
Azure Dev Spaces is deprecated and teams need to remove leftover controllers from subscriptions to stop accruing related costs and clutter. A cleanup job lists every Dev Spaces controller in the subscription and deletes those that no longer back an active AKS environment.
List all Dev Spaces controllers in the subscription and delete each controller whose underlying AKS cluster has been removed
Agent-driven workspace provisioning
An AI agent fronting an internal developer portal accepts a 'give me a workspace' request, searches Jentic for the Dev Spaces controller create operation, provisions the controller, and returns the connection payload. Jentic isolates the operator's Azure credentials so the agent never sees the underlying AAD secret.
Provision a Dev Spaces controller for the requesting developer, then return the connection details so their local tooling can attach
Key Endpoints
9 endpoints — jentic publishes the only available openapi specification for devspacesmanagement, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/subscriptions/{subscriptionId}/providers/Microsoft.DevSpaces/controllers
List Dev Spaces controllers in a subscription
GET
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DevSpaces/controllers
List controllers in a resource group
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DevSpaces/controllers/{name}
Create or update a Dev Spaces controller
GET
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DevSpaces/controllers/{name}
Get a specific Dev Spaces controller
PATCH
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DevSpaces/controllers/{name}
Update a Dev Spaces controller
DELETE
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DevSpaces/controllers/{name}
Delete a Dev Spaces controller
POST
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DevSpaces/controllers/{name}/listConnectionDetails
List connection details for a controller
GET
/subscriptions/{subscriptionId}/providers/Microsoft.DevSpaces/controllers
List Dev Spaces controllers in a subscription
GET
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DevSpaces/controllers
List controllers in a resource group
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DevSpaces/controllers/{name}
Create or update a Dev Spaces controller
GET
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DevSpaces/controllers/{name}
Get a specific Dev Spaces controller
PATCH
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DevSpaces/controllers/{name}
Update a Dev Spaces controller
DELETE
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DevSpaces/controllers/{name}
Delete a Dev Spaces controller
POST
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DevSpaces/controllers/{name}/listConnectionDetails
List connection details for a controller
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Azure AD OAuth 2.0 client credentials are stored encrypted in the Jentic vault. Agents receive a scoped bearer token at execute time; client secrets and refresh tokens never reach the agent's context.
Intent-based discovery
Agents search by intent (e.g., 'provision azure dev spaces controller') and Jentic returns the matching create operation with its required resource-group, controller-name, and location parameters resolved from the spec.
Time to first call
Direct integration with Microsoft.DevSpaces, including AAD setup and long-running provisioning, typically takes 1-2 days. Through Jentic: under 1 hour to first successful provisioning.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using DevSpacesManagement API through Jentic.
Why is there no official OpenAPI spec for DevSpacesManagement?
Microsoft Azure does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call DevSpacesManagement via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the Dev Spaces Management API use?
The API runs through Azure Resource Manager and uses OAuth 2.0 bearer tokens issued by Azure Active Directory. Through Jentic, the AAD client secret or managed identity refresh token is held in the encrypted vault and a short-lived access token is supplied at execute time so the bearer token never appears in the agent's context.
Can I retrieve the connection details for a Dev Spaces controller with this API?
Yes. POST /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DevSpaces/controllers/{name}/listConnectionDetails returns the controller endpoint and the kubeconfig payload required to attach a developer's local tooling.
What are the rate limits for the Dev Spaces Management API?
Azure Resource Manager applies subscription-level read and write throttles (around 12,000 reads per hour and 1,200 writes per hour per region per subscription) and returns 429 with a Retry-After header when exceeded. Controller create and delete are long-running and should be polled with backoff.
How do I provision a Dev Spaces controller through Jentic?
Search Jentic for 'create azure dev spaces controller', load the schema for PUT .../controllers/{name}, then execute with subscriptionId, resourceGroupName, location, and the target host SKU. The pip install jentic Python SDK uses the async search, load, execute pattern.
Is the Dev Spaces Management API free?
Azure Dev Spaces was a free preview service that has since been retired in favour of Bridge to Kubernetes; you pay for the underlying AKS cluster, not the controller. The management API itself does not bill per call.
GET STARTED