Microsoft Azure SeaBreezeManagementClient
Browse all Azure APIs★ Only Publicly Available OpenAPI DocumentCloud InfrastructureContainer Orchestrationoauth236 EndpointsREST
For Agents
Provision and operate Azure Service Fabric Mesh container applications, gateways, networks, secrets, and volumes without managing the underlying cluster.
Use for: I want to deploy a Service Fabric Mesh application, List all mesh networks in a subscription, Get the running replicas of a mesh service, Provision a gateway for a mesh application
Not supported: Does not orchestrate Kubernetes, manage VM clusters, or build container images — use for Service Fabric Mesh application, network, gateway, secret, and volume management only.
Jentic publishes the only available OpenAPI specification for SeaBreezeManagementClient, keeping it validated and agent-ready. The Azure Service Fabric Mesh management API provisions and operates serverless container applications composed of services, gateways, networks, secrets, and volumes. Agents declare an application with its services and dependencies, deploy it without managing a cluster, and inspect runtime topology including replicas and code packages. The API is scoped to ARM and reaches the Service Fabric Mesh control plane in any subscription.
Install Jentic One Beta
Connect the SeaBreezeManagementClient to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the SeaBreezeManagementClient, 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 SeaBreezeManagementClient API.
Declare and deploy a Service Fabric Mesh application with its services and dependencies
Provision gateways that route traffic into mesh applications
Define mesh networks that connect services across applications
Store and rotate secret values consumed by mesh services
Mount and manage persistent volumes for mesh services
Inspect running services, code packages, and replicas inside an application
Use Cases
Patterns agents use SeaBreezeManagementClient API for, with concrete tasks.
★ Serverless Container Application Deployment
Platform teams use SeaBreezeManagementClient to deploy multi-service container applications without provisioning Service Fabric clusters. The application resource holds a list of services, each with code packages, replica counts, and resource requests, and the service composes networks and gateways automatically. Updates flow through ARM PUT calls so deployments fit existing IaC pipelines.
PUT /subscriptions/{subscriptionId}/resourceGroups/{rg}/providers/Microsoft.ServiceFabricMesh/applications/{appName} with services definition and poll provisioning until Succeeded
Mesh Networking and Gateway Configuration
When two mesh applications need to talk, operators define a network resource and attach gateway configurations to expose specific services externally. The networks endpoint manages the address spaces and the gateways endpoint binds protocols and ports to backing services. The two together replace the manual load balancer and VNet wiring that traditional Service Fabric clusters require.
PUT a gateway named storefront-gw that binds HTTP port 80 to backend service storefront in the mesh application
Secret and Volume Lifecycle for Mesh Workloads
Mesh services consume database connection strings, API keys, and persistent volume mounts the same way Kubernetes pods do. The secrets and secretValues endpoints store and rotate sensitive values, and the volumes endpoint manages persistent storage that services mount. Both resource types are ARM-managed so they share the access control and tagging that govern the rest of the mesh application.
PUT a new secretValue under secret database-password and PATCH the dependent service so it picks up the new version on next replica restart
Agent-Driven Mesh Operations via Jentic
Through Jentic, a platform agent can search for deploy service fabric mesh app, load the application PUT schema, populate it from a higher-level spec, and execute the deployment with a managed Azure OAuth token. The same flow handles networks, gateways, and secrets so a single agent can own the full mesh lifecycle.
Search Jentic for deploy service fabric mesh app, load the application PUT schema, execute it with a two-service definition, then call list services to confirm both are reporting Healthy
Key Endpoints
36 endpoints — jentic publishes the only available openapi specification for seabreezemanagementclient, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ServiceFabricMesh/applications/{applicationResourceName}
Create or update a mesh application
GET
/subscriptions/{subscriptionId}/providers/Microsoft.ServiceFabricMesh/applications
List applications in subscription
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ServiceFabricMesh/networks/{networkResourceName}
Create or update a network
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ServiceFabricMesh/gateways/{gatewayResourceName}
Create or update a gateway
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ServiceFabricMesh/secrets/{secretResourceName}
Create or update a secret
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ServiceFabricMesh/volumes/{volumeResourceName}
Create or update a volume
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ServiceFabricMesh/applications/{applicationResourceName}
Create or update a mesh application
GET
/subscriptions/{subscriptionId}/providers/Microsoft.ServiceFabricMesh/applications
List applications in subscription
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ServiceFabricMesh/networks/{networkResourceName}
Create or update a network
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ServiceFabricMesh/gateways/{gatewayResourceName}
Create or update a gateway
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ServiceFabricMesh/secrets/{secretResourceName}
Create or update a secret
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ServiceFabricMesh/volumes/{volumeResourceName}
Create or update a volume
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Azure service principal credentials are stored encrypted in the Jentic vault. Agents receive scoped OAuth tokens for the management.azure.com audience only — the underlying client secret never enters the agent context.
Intent-based discovery
Agents search by intent such as deploy service fabric mesh app or expose mesh service, and Jentic returns the matching SeaBreeze operation with its full input schema across applications, services, networks, gateways, secrets, and volumes.
Time to first call
Direct integration: 3-5 days to wire MSAL and the multiple resource-type schemas. Through Jentic: under an hour to search, load, and execute a mesh application deployment.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using SeaBreezeManagementClient API through Jentic.
Why is there no official OpenAPI spec for SeaBreezeManagementClient?
Microsoft Azure does not publish a unified OpenAPI specification for the Service Fabric Mesh control plane. Jentic generates and maintains this spec so that AI agents and developers can call SeaBreezeManagementClient via structured tooling. It is validated against the live Azure Resource Manager API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does SeaBreezeManagementClient use?
It uses Azure Active Directory OAuth 2.0 via the azure_auth flow defined in the spec. Acquire a bearer token for https://management.azure.com/.default and pass it as Authorization: Bearer. Jentic stores the underlying service principal in its vault so the agent only sees a scoped token.
Can I deploy a multi-service container app with this API?
Yes. PUT to .../applications/{applicationResourceName} with a body that lists services, each containing code packages, replica counts, and resource requests. The platform deploys the application without you provisioning a cluster.
How do I expose a mesh service to the internet?
Define a gateway resource with PUT .../gateways/{gatewayResourceName} that maps inbound HTTP or TCP listeners to the backing service. Combine that with a network resource for internal routing. Both resources are ARM-managed so RBAC and tagging are inherited.
What are the rate limits for the Service Fabric Mesh API?
Calls count against Azure Resource Manager subscription throttling, roughly 12,000 reads and 1,200 writes per hour per subscription. The Service Fabric Mesh service itself is in preview, so capacity per region may be lower than other Azure services.
How do I deploy a mesh application through Jentic?
Search Jentic for deploy service fabric mesh app, call client.load on the application PUT operation to receive its input schema, then call client.execute with subscriptionId, resourceGroupName, applicationResourceName, and the services definition. Jentic injects the OAuth token and returns the created application.
GET STARTED