Microsoft Azure Recommendations API Client

What authentication does the Azure App Service Recommendations API use?

The API runs through Azure Resource Manager and uses OAuth 2.0 bearer tokens issued by Azure Active Directory under the azure_auth scheme with the user_impersonation scope. Through Jentic, the AAD client secret is held in the encrypted vault and a short-lived access token is supplied at execute time so the secret never appears in the agent's context.

Can I disable a single recommendation without affecting others?

Yes. POST .../recommendations/{name}/disable disables only the named recommendation at the chosen scope (subscription, hosting environment, or site). Other recommendations continue to fire normally, and the disable can be cleared later with the matching reset endpoint.

What are the rate limits for the App Service Recommendations API?

Azure Resource Manager applies subscription-level read and write throttles (around 12,000 reads per hour and 1,200 writes per hour per region per subscription) and returns 429 with a Retry-After header when exceeded. Listing endpoints support the standard $filter query parameter to narrow results.

How do I list recommendations through Jentic?

Search Jentic for 'list azure app service recommendations', load the schema for GET .../sites/{siteName}/recommendations, then execute with subscriptionId, resourceGroupName, and siteName. The pip install jentic Python SDK uses the async search, load, execute pattern.

Is the App Service Recommendations API free?

There is no per-call charge for the management API itself; recommendations are produced as part of the App Service platform and are not separately metered. You pay for the underlying App Service plans and sites.

Can I limit what my agent is allowed to do with the Azure App Service Recommendations API?

Yes. Because your Jentic One instance is self-hosted, your own rules decide which operations and credentials the agent may use. The subscription, resource group, site, and hosting environment names all travel in the URL path, so you can pin the agent to a single site and only the operations it needs, such as listing recommendations and reading recommendation history. State-changing operations like disabling a recommendation or resetting all recommendations are not available to the agent unless you explicitly add them.