Azure APIs
237 APIs4,900 Endpoints17 Categories
Categories
API Catalog
ACE Provisioning ManagementPartner
Jentic publishes the only available OpenAPI specification for ACE Provisioning ManagementPartner, keeping it validated and agent-ready. This API manages the linkage between an Azure customer subscription and a Microsoft Cloud Solution Provider partner identifier (MPN ID), exposing operations to register, retrieve, update, and delete the partner association under Microsoft.ManagementPartner. It is the surface a partner uses to claim Partner Admin Link or Partner Earned Credit visibility on a customer tenant.
6 endpointsApplicationInsightsManagementClient
ApplicationInsightsManagementClient is the Azure Resource Manager surface for the Application Insights web-test alerting feature. It exposes the metadata operation that Azure Portal and tooling use to enumerate the supported Microsoft.Insights provider operations for application performance monitoring resources. This is a control-plane companion to the broader Azure Monitor Application Insights stack, focused specifically on web-test based availability alerts.
1 endpointsAppPlatformManagementClient
AppPlatformManagementClient is the Azure Resource Manager API for Azure Spring Cloud (Azure Spring Apps). It lets you provision Spring service instances, deploy and version Spring Boot apps, manage bindings to Azure resources, configure custom domains and SSL certificates, and stream logs and metrics. The API covers the full app lifecycle from creating a service to rolling out new deployments and listing test endpoints.
Connect Your Agent
1
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" | sh2
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" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.