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.