Microsoft Azure ServiceFabricManagementClient
Browse all Azure APIs★ Only Publicly Available OpenAPI DocumentCloud InfrastructureContainer Orchestrationoauth219 EndpointsREST
For Agents
Register Service Fabric application types and versions, deploy applications, and create services on a Service Fabric cluster through the Azure control plane.
Use for: Register a Service Fabric application type on a cluster, Upload version 2.0.0 of an application type, Deploy an application from a specific application type version, Create a stateful service under a deployed application
Not supported: Does not provision the cluster, manage cluster nodes, or run cluster health queries — use for application type, application, and service registration on an existing Service Fabric cluster only.
Jentic publishes the only available OpenAPI specification for ServiceFabricManagementClient, keeping it validated and agent-ready. The Azure Service Fabric resource provider API lets agents register application types and versions, deploy applications, and create or update services on a Service Fabric cluster through Azure Resource Manager. It models clusters as the parent scope, application types as registered packages, applications as deployed instances, and services as the runtime units, plus an operations endpoint that lists every action exposed by the Microsoft.ServiceFabric provider.
Install Jentic One Beta
Connect the ServiceFabricManagementClient to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the ServiceFabricManagementClient, 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 ServiceFabricManagementClient API.
Register a Service Fabric application type on a cluster
Upload a new version of a registered application type
Deploy an application from a registered type and version
Create stateful or stateless services under a deployed application
Update a deployed application to a new application type version
List every application type and version registered on a cluster
Inspect the services running under a specific application instance
Use Cases
Patterns agents use ServiceFabricManagementClient API for, with concrete tasks.
★ Application Rollout Pipeline
Platform teams ship Service Fabric application updates through a release pipeline that registers a new version of the application type, then updates the deployed application to that version. The applicationTypes/versions endpoint accepts the package URL and the applications endpoint takes a typeVersion parameter, so an agent can drive the rolling update without using PowerShell or sfctl.
PUT a new applicationTypes/{applicationTypeName}/versions/{version} resource pointing at the package URL, then PATCH the application to set typeVersion to the new version
Cluster Application Inventory
Operations teams need a clean inventory of what is registered and deployed on each Service Fabric cluster. The applicationTypes and applications endpoints return the full set of registered types, their versions, and the deployed applications that consume them, so an agent can build a coverage report and flag stale versions for cleanup.
List applicationTypes for the cluster, then for each type list versions and return type, version, and provisioningState
Service Provisioning
Developers add new services to an existing Service Fabric application without redeploying the whole application package. The services endpoint creates a stateful or stateless service with its partition scheme, replica or instance count, and placement constraints, giving an agent a way to expand an application with a single ARM call.
PUT a services/{serviceName} resource under the application with serviceKind Stateful, partitionDescription UniformInt64Range, and targetReplicaSetSize 3
AI Agent Deployment Bot
An agent built on Jentic accepts a natural-language deploy request and drives the full Service Fabric registration and deployment flow. The agent registers the application type, uploads the version, deploys the application, and reports back the provisioning state, all from a single chat instruction grounded in the cluster's existing inventory.
Search Jentic for deploy service fabric application, load the schemas for applicationTypes/versions and applications, and execute them in order with the package URL the user provided
Key Endpoints
19 endpoints — jentic publishes the only available openapi specification for servicefabricmanagementclient, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ServiceFabric/clusters/{clusterName}/applicationTypes/{applicationTypeName}
Register an application type on a cluster
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ServiceFabric/clusters/{clusterName}/applicationTypes/{applicationTypeName}/versions/{version}
Upload a version of an application type
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ServiceFabric/clusters/{clusterName}/applications/{applicationName}
Deploy or update an application instance
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ServiceFabric/clusters/{clusterName}/applications/{applicationName}/services/{serviceName}
Create or update a service under an application
GET
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ServiceFabric/clusters/{clusterName}/applications
List applications on a cluster
DELETE
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ServiceFabric/clusters/{clusterName}/applicationTypes/{applicationTypeName}/versions/{version}
Delete a registered application type version
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ServiceFabric/clusters/{clusterName}/applicationTypes/{applicationTypeName}
Register an application type on a cluster
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ServiceFabric/clusters/{clusterName}/applicationTypes/{applicationTypeName}/versions/{version}
Upload a version of an application type
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ServiceFabric/clusters/{clusterName}/applications/{applicationName}
Deploy or update an application instance
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ServiceFabric/clusters/{clusterName}/applications/{applicationName}/services/{serviceName}
Create or update a service under an application
GET
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ServiceFabric/clusters/{clusterName}/applications
List applications on a cluster
DELETE
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ServiceFabric/clusters/{clusterName}/applicationTypes/{applicationTypeName}/versions/{version}
Delete a registered application type version
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Azure AD service principal credentials sit encrypted in the Jentic vault. Agents receive a short-lived bearer token scoped to user_impersonation — raw secrets never enter the agent context, even when deploying applications referencing private package URLs.
Intent-based discovery
Agents search Jentic by intent such as deploy service fabric application or register application type and Jentic returns the matching Microsoft.ServiceFabric operation with its full input schema.
Time to first call
Direct integration with the Microsoft.ServiceFabric ARM endpoints: 1-2 days for AAD setup, package URL hosting, and async operation polling. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using ServiceFabricManagementClient API through Jentic.
Why is there no official OpenAPI spec for ServiceFabricManagementClient?
Microsoft Azure does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call ServiceFabricManagementClient 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 Service Fabric management API use?
It uses Azure AD OAuth 2.0 with the implicit flow against https://login.microsoftonline.com/common/oauth2/authorize and the user_impersonation scope. When called through Jentic, your AAD service principal credentials live in the Jentic vault and only short-lived bearer tokens reach the agent.
Can I provision the underlying Service Fabric cluster with this API?
No — this preview API focuses on application types, applications, and services on an existing cluster. Cluster creation is exposed by an earlier ServiceFabric resource provider API version. Use this API after the cluster resource is already provisioned.
How do I deploy a new application version through Jentic?
Search Jentic for upload service fabric application version, load the schema for PUT /.../applicationTypes/{applicationTypeName}/versions/{version}, and execute it with the package URL. Then PATCH the application resource to point typeVersion at the new version. The Jentic Python SDK ships this search, load, execute pattern after pip install jentic.
What are the rate limits for this API?
Azure Resource Manager applies subscription-level throttling around 12,000 reads and 1,200 writes per hour per principal, surfaced via x-ms-ratelimit-remaining-subscription-reads and x-ms-ratelimit-remaining-subscription-writes headers. Application registration and deploy operations are async — they return 202 with an asyncOperation URL to poll.
Can I create stateful services through this API?
Yes. PUT /.../applications/{applicationName}/services/{serviceName} accepts a serviceKind of Stateful or Stateless, a partitionDescription (UniformInt64Range, Singleton, or Named), and replica or instance counts. Stateful services additionally accept hasPersistedState and minReplicaSetSize.
Is Service Fabric being deprecated?
Service Fabric remains supported by Microsoft for both Windows and Linux clusters, but most net-new microservices workloads on Azure target AKS. Use this API for existing Service Fabric estates and consider AKS or Container Apps for greenfield projects.
GET STARTED