Microsoft Azure ServiceFabricManagementClient

Name: ServiceFabricManagementClient API
Brand: Service Fabric Management
Availability: InStock

★ 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.

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-servicefabricmanagementclient" | 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-servicefabricmanagementclient" | 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 ServiceFabricManagementClient API.

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

GET STARTED

Start building with ServiceFabricManagementClient API

Explore with Jentic One

View OpenAPI Document

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}

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}

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}

Why Jentic?

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

Setup

Wiring the Microsoft.ServiceFabric resource provider by hand means standing up an Azure AD app, driving the OAuth2 token exchange, and polling the asyncOperation URLs that application registration and deploy operations return with 202. Through Jentic you install once, import Service Fabric Management from the API Directory, store the Azure AD service principal credential once, and your agent calls it.

Permission scoping

Service Fabric puts the subscription, resource group, and cluster in the URL path (/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ServiceFabric/clusters/{clusterName}/...), so a rule can pin your agent to one cluster and its application types and services. You choose the operations it may call, so destructive ones like deleting an application type version or removing a deployed application are not included unless you add them.

Credential isolation

Your Azure AD service principal credential 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, even when a deploy references a private package URL.

Intent-based discovery

Agents search Jentic by intent such as 'deploy a Service Fabric application' or 'register an application type', and Jentic returns the matching Microsoft.ServiceFabric operation with its input schema so the agent calls the right endpoint without reading the ARM reference.

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 with Jentic One, the self-hosted execution layer.

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 your Jentic One instance 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.

Can I limit what my agent is allowed to do with the Service Fabric Management API?

Yes. Because your Jentic One instance is self-hosted, you set the rules that decide which Microsoft.ServiceFabric operations and credentials the agent may use. Since the subscription, resource group, and cluster are all in the URL path, you can pin the agent to a single cluster and only the application types, applications, and services under it. You also choose which operations it may call, so destructive ones like deleting an application type version or removing a deployed application stay off unless you add them.

Microsoft Azure ServiceFabricManagementClient

Connect the ServiceFabricManagementClient to your agent

Capabilities

Start building with ServiceFabricManagementClient API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs