Microsoft Azure LogicManagementClient

Name: LogicManagementClient API
Brand: LogicManagementClient
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCloud InfrastructureServerlessoauth2106 Endpoints

Install Jentic One Beta

Connect the LogicManagementClient to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the LogicManagementClient, 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

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 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 LogicManagementClient API.

Create, update, enable, disable, and delete Logic App workflows in a resource group

Trigger workflow runs, retrieve run history, and cancel in-flight runs

Manage integration accounts and their schemas, maps, partners, and agreements for B2B/EDI scenarios

GET STARTED

Start building with LogicManagementClient API

Explore with Jentic

View OpenAPI Document

For Agents

Provision and manage Azure Logic App workflows, runs, integration accounts, and integration service environments through Azure Resource Manager. Use for workflow lifecycle and B2B/EDI configuration, not for running connector calls.

Use for: I want to create a new Logic App workflow that processes incoming orders, Trigger a manual run of the 'invoice-processing' workflow with a JSON payload, List all failed Logic App runs in the last 24 hours, Disable the 'nightly-sync' workflow before maintenance

Not supported: Does not execute connector calls, manage on-premises gateways, or store secrets in connections - use only for workflow, run, integration account, and ISE lifecycle in the Microsoft.Logic provider.

Use Cases

Patterns agents use LogicManagementClient API for, with concrete tasks.

★ Workflow Lifecycle Automation

Platform teams managing dozens of Logic App workflows across environments need programmatic create-update-disable control. LogicManagementClient exposes Workflows_CreateOrUpdate (PUT on /workflows/{workflowName}), Workflows_Disable, and Workflows_Enable so a CI/CD pipeline can promote a workflow definition from staging to production, disable it before a maintenance window, and re-enable it afterwards. The full workflow JSON definition is the request body - the same shape exported from the Logic Apps designer.

PUT a new workflow definition for 'order-processing' to /subscriptions/{subscriptionId}/resourceGroups/integrations-prod/providers/Microsoft.Logic/workflows/order-processing with the exported workflow JSON, then call Workflows_Enable.

Run Monitoring and Triage

Operations teams responding to integration failures use the WorkflowRuns and WorkflowRunActions endpoints to find which step failed, inspect inputs and outputs, and resubmit. Listing runs filtered by status=Failed across all workflows in a resource group is the standard daily triage query. Each run's actions can be drilled into for the exact connector response that failed.

List runs of the 'invoice-processing' workflow with status=Failed in the last 24 hours, then for each run list the actions and return the action name and error code where status is Failed.

B2B and EDI Integration

Companies exchanging EDI documents with trading partners use Azure integration accounts to store schemas (X12, EDIFACT, XML), maps (XSLT), partners, and agreements. LogicManagementClient manages all of these as ARM resources - IntegrationAccountSchemas, IntegrationAccountMaps, IntegrationAccountPartners, and IntegrationAccountAgreements. Batch configurations allow high-volume scenarios where messages are aggregated before transmission.

Create an integration account named 'b2b-prod' in eastus, then upload an X12 schema and a partner agreement that points at trading partner 'ACME-Corp' for inbound 850 purchase orders.

Dedicated Integration Service Environment Provisioning

Regulated industries that need Logic Apps to run inside a virtual network use Integration Service Environments (ISE). Provisioning an ISE with the Premium SKU and configuring its subnet integration is a long-running PUT - the call returns 202 Accepted with an Azure-AsyncOperation URL to poll. Once provisioned, network health endpoints surface DNS, NSG, and outbound connectivity status for ongoing operations.

Provision an Integration Service Environment 'ise-prod' in eastus with Premium SKU, integrating subnet '/subscriptions/.../subnets/ise-subnet', then poll the network health endpoint until status is Healthy.

AI Agent Workflow Operations

AI agents that own integration platforms use Jentic to discover and call Logic Apps management operations on demand. Instead of bundling the full ARM SDK, the agent searches for an intent like 'trigger a logic app workflow run', loads the operation schema from Jentic, and executes against management.azure.com with a scoped token retrieved from your Jentic One instance.

Use Jentic to search 'trigger a logic app workflow run', load the Workflows_TriggerHistories or run-trigger operation, and POST the trigger payload to start the workflow with the agent's Azure credential.

Key Endpoints

106 endpoints — jentic publishes the only available openapi specification for logicmanagementclient, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Logic/workflows/{workflowName}

Create or update a Logic App workflow

GET

/subscriptions/{subscriptionId}/providers/Microsoft.Logic/workflows

List workflows in a subscription

DELETE

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Logic/workflows/{workflowName}

Delete a Logic App workflow

GET

/subscriptions/{subscriptionId}/providers/Microsoft.Logic/integrationAccounts

List integration accounts for B2B/EDI

GET

/subscriptions/{subscriptionId}/providers/Microsoft.Logic/integrationServiceEnvironments

List Integration Service Environments

GET

/providers/Microsoft.Logic/operations

List Microsoft.Logic provider operations

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Logic/workflows/{workflowName}

Create or update a Logic App workflow

GET

/subscriptions/{subscriptionId}/providers/Microsoft.Logic/workflows

List workflows in a subscription

DELETE

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Logic/workflows/{workflowName}

Delete a Logic App workflow

GET

/subscriptions/{subscriptionId}/providers/Microsoft.Logic/integrationAccounts

List integration accounts for B2B/EDI

GET

/subscriptions/{subscriptionId}/providers/Microsoft.Logic/integrationServiceEnvironments

List Integration Service Environments

Why Jentic?

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

Credential isolation

Your Azure AD credential for the Logic control plane 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.

Intent-based discovery

Agents search Jentic by intent such as 'list Logic Apps workflows' or 'read an integration account', and Jentic returns the matching Logic operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using LogicManagementClient API through Jentic.

Why is there no official OpenAPI spec for LogicManagementClient?

Microsoft Azure does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call LogicManagementClient 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 LogicManagementClient use?

Azure Active Directory OAuth 2.0 bearer tokens scoped to https://management.azure.com/. With Jentic, the AAD client secret is held in the encrypted vault and short-lived tokens are injected into the Authorization header - agents never see the underlying secret.

Can I trigger a workflow run with this API?

Yes. The Workflows and WorkflowTriggers resources include trigger operations (POST on the trigger child resource) that fire a workflow run. The corresponding WorkflowRuns endpoints then expose run status, action history, and cancellation.

What are the rate limits for the LogicManagementClient?

Standard Azure Resource Manager throttling applies - typically 12,000 reads and 1,200 writes per hour per subscription per region. Workflow run trigger operations are subject to the Logic App's own throughput limits as defined by its plan (Consumption or Standard).

How do I deploy a Logic App workflow through Jentic?

Run pip install jentic, then search Jentic for 'create a logic app workflow'. Jentic returns the Workflows_CreateOrUpdate schema - the agent loads it, supplies the workflow definition JSON, and executes a PUT against /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Logic/workflows/{workflowName}.

What is the difference between an integration account and an integration service environment?

An integration account stores B2B/EDI artefacts (schemas, maps, partners, agreements) referenced by workflows. An Integration Service Environment is a dedicated, VNet-integrated runtime for the Logic Apps engine itself. Both are managed here, but they solve different problems - artefacts versus runtime isolation.

Can I limit what my agent is allowed to do with the Microsoft Azure Logic Apps API?

Yes. Because Jentic One is self-hosted, you set the rules that decide which operations and credentials your agent may use, and those rules run on your own instance. This API puts the workflow in the URL path (/resourceGroups/{resourceGroupName}/providers/Microsoft.Logic/workflows/{workflowName}), so you can pin the agent to a single workflow and allow only read operations such as listing and reading workflows and integration accounts. Creating, deleting, or triggering a workflow is excluded unless you explicitly add those operations to what the agent is allowed to call.

Microsoft Azure LogicManagementClient

Connect the LogicManagementClient to your agent

Capabilities

Start building with LogicManagementClient API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs