AppPlatformManagementClient

Name: AppPlatformManagementClient API
Brand: AppPlatformManagementClient
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCloud InfrastructureContainer Orchestrationoauth233 EndpointsREST

For Agents

Provision Azure Spring Cloud services, deploy and version Spring Boot applications, manage bindings, custom domains, and certificates from an AI agent.

Quickstart

Get started with AppPlatformManagementClient in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"deploy an Azure Spring Cloud app"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with AppPlatformManagementClient API.

Provision and configure Azure Spring Cloud service instances inside a resource group

Create, update, and version Spring Boot app deployments with active deployment switching

Bind Spring apps to backing Azure services such as databases and caches

Configure custom domains and upload TLS certificates for Spring apps

GET STARTED

Start building with AppPlatformManagementClient API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for AppPlatformManagementClient, keeping it validated and agent-ready.

AppPlatformManagementClient is the Azure Resource Manager API for Azure Spring Cloud (Azure Spring Apps). It lets you provision Spring service instances, deploy and version Spring Boot apps, manage bindings to Azure resources, configure custom domains and SSL certificates, and stream logs and metrics. The API covers the full app lifecycle from creating a service to rolling out new deployments and listing test endpoints.

Use Cases

Patterns agents use AppPlatformManagementClient API for, with concrete tasks.

★ Blue-Green Deployment for Spring Boot Apps

Platform teams running Spring Boot workloads on Azure Spring Cloud need a controlled way to ship new versions without downtime. The API lets you create a parallel deployment under the same app, push the new JAR or source archive, run smoke tests against the test endpoint, and then switch the active deployment pointer. Rollback is a single PATCH call to flip the pointer back.

Create a new deployment named green under the target app, upload the new artifact, poll until status is Running, then PATCH the app to set activeDeploymentName to green.

Custom Domain and TLS Setup

Production Spring apps need branded URLs and managed certificates. The API exposes endpoints to upload a certificate, attach it to an app, and bind a custom domain — all idempotent control-plane calls that fit a Terraform-style or agent-driven setup. SSL binding propagation is asynchronous and reflected in the resource provisioningState field.

Upload a certificate to the Spring service, create a custom domain resource pointing the hostname to the app, and verify provisioningState reaches Succeeded.

Service Discovery for Internal Tools

Internal developer portals need a live inventory of Spring Cloud services and apps across the org. Listing services per subscription and apps per service gives a current map of which workloads run where, which deployment is active, and what bindings each app has. This data feeds catalogues, dashboards, and incident-response tooling.

List all Spring services in the subscription, then for each service list its apps and active deployment, returning a flat inventory of app name, service, region, and active version.

Agent-Driven Spring App Deployment via Jentic

An AI agent receiving a 'ship version 1.4 of payments-api to staging' instruction can use Jentic to find the Azure Spring Cloud deploy operation, supply the artifact URL and target app, and watch the deployment to completion — all without holding the Azure subscription credentials in its context. Jentic returns the schema and Azure ARM polls the long-running operation transparently.

Search Jentic for 'deploy a Spring Cloud app version', execute the deployments PUT with the artifact URI, then poll the operation status until provisioningState is Succeeded.

Key Endpoints

33 endpoints — appplatformmanagementclient is the azure resource manager api for azure spring cloud (azure spring apps).

METHOD

PATH

DESCRIPTION

GET

/subscriptions/{subscriptionId}/providers/Microsoft.AppPlatform/Spring

List all Spring services in the subscription

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.AppPlatform/Spring/{serviceName}

Create or update a Spring service instance

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.AppPlatform/Spring/{serviceName}/apps

List apps within a Spring service

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.AppPlatform/Spring/{serviceName}/apps/{appName}

Create or update an app and its active deployment pointer

POST

/subscriptions/{subscriptionId}/providers/Microsoft.AppPlatform/locations/{location}/checkNameAvailability

Check Spring service name availability in a region

GET

/subscriptions/{subscriptionId}/providers/Microsoft.AppPlatform/Spring

List all Spring services in the subscription

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.AppPlatform/Spring/{serviceName}

Create or update a Spring service instance

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.AppPlatform/Spring/{serviceName}/apps

List apps within a Spring service

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.AppPlatform/Spring/{serviceName}/apps/{appName}

Create or update an app and its active deployment pointer

POST

/subscriptions/{subscriptionId}/providers/Microsoft.AppPlatform/locations/{location}/checkNameAvailability

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Azure AD bearer tokens are vaulted in Jentic's MAXsystem. Agents receive a scoped session token only for the duration of the call; client secrets and refresh tokens never enter agent context.

Intent-based discovery

Agents search by intent ('deploy a Spring Cloud app') and Jentic returns the matching ARM operation with its parameter schema and required api-version, so the agent does not have to discover the right path among 33 endpoints.

Time to first call

Direct ARM integration: 1-3 days for AAD app registration, RBAC scoping, ARM token plumbing, and long-running operation handling. Through Jentic: under 30 minutes — search, load, execute, poll.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Web Apps API Client

Azure App Service Web Apps for general-purpose web hosting beyond Spring Boot

Choose Web Apps when the workload is .NET, Node, Python, or Java but not a Spring Boot service that benefits from Spring Cloud features.

Complementary

AppServicePlans API Client

Manage the underlying compute plans that host App Service workloads

Use App Service Plans when sizing the compute tier; Spring Cloud Standard and Enterprise tiers manage their own plans, so this is mainly relevant when comparing alternatives.

Complementary

Monitor Management Client

Configure alerts, action groups, and diagnostic settings for Spring services

Pair with this client when the agent needs to set up alerting on Spring app metrics after deployment.

FAQs

Specific to using AppPlatformManagementClient API through Jentic.

What authentication does the AppPlatformManagementClient use?

Azure Active Directory OAuth 2.0 bearer tokens scoped to https://management.azure.com/. Through Jentic the bearer token is held in the encrypted vault and a short-lived scoped session is issued to the agent at call time.

Can I deploy a new Spring Boot version with this API?

Yes. Create a deployment under the target app via PUT on the deployments path, upload the JAR or source archive URL in the deployment resource, and then PATCH the parent app to set activeDeploymentName to the new deployment. The deployment is a long-running ARM operation; poll provisioningState until it reaches Succeeded.

What are the rate limits for the AppPlatformManagementClient?

Calls go through Azure Resource Manager and are subject to ARM's per-subscription throttling — typically 12,000 reads and 1,200 writes per hour per subscription. Long-running operation polls count toward the read budget. Check response headers x-ms-ratelimit-remaining-subscription-reads and x-ms-ratelimit-remaining-subscription-writes.

How do I list Spring services in my subscription through Jentic?

Search Jentic with 'list Azure Spring Cloud services' and execute the returned operation. Jentic loads the schema for GET /subscriptions/{subscriptionId}/providers/Microsoft.AppPlatform/Spring, supplies the scoped Azure token, and returns the parsed JSON list.

Is the AppPlatformManagementClient free to call?

Management calls do not have a per-request charge. The Azure Spring Cloud / Azure Spring Apps service itself is billed by tier (Basic, Standard, Enterprise) and by app vCPU and memory consumption. See Azure Spring Apps pricing for current rates.

Can I bind a Spring app to a backing service like Cosmos DB?

Yes. Use PUT on /Spring/{serviceName}/apps/{appName}/bindings/{bindingName} with the resourceId of the Cosmos DB account. The binding makes connection strings available to the app at runtime via injected environment variables.