What authentication does the Azure Managed Applications Client use?

The API uses Azure Active Directory OAuth 2.0 bearer tokens (the azure_auth scheme) on management.azure.com. Through Jentic, the AAD app secret is held in your Jentic One instance and exchanged for a short-lived bearer token at execution time, so agents never see the raw secret.

Can I deploy a Managed Application from a published definition with this API?

Yes. PUT /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Solutions/applications/{applicationName} creates a Managed Application bound to an Application Definition by id, with the consumer parameters in the request body. Poll the returned operation until it succeeds.

How do I find every Managed Application in a subscription?

Call GET /subscriptions/{subscriptionId}/providers/Microsoft.Solutions/applications. The response paginates with nextLink and includes each application's name, applicationDefinitionId, and provisioningState, which is the data you need for inventory and renewal workflows.

What are the rate limits for this API?

Azure Resource Manager applies subscription-level throttling. List operations are inexpensive but pagination adds calls; create and delete are async and trigger long-running operations. Honour HTTP 429 Retry-After values and avoid back-to-back create attempts on the same name.

How do I list and audit Managed Applications through Jentic?

Run pip install jentic, then search Jentic with 'list Azure Managed Applications'. Jentic returns the subscription-scope list endpoint with its input schema. Execute it, then for each entry call the get-by-id endpoint; the OAuth token is resolved from the vault automatically.

Can I limit what my agent is allowed to do with the Azure Managed Applications Client API?

Yes. Because you self-host Jentic One, your own rules decide which operations and credentials the agent may use. Managed Applications and Application Definitions are addressed by path parameters like /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Solutions/applications/{applicationName}, so a rule can pin the agent to a single subscription and resource group. You also choose the operations it may call, so you can grant read-only listing and get while withholding destructive ones such as deleting a Managed Application or an Application Definition.