Azure APIs
237 APIs4,900 Endpoints17 Categories
Categories
API Catalog(96 of 237)
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 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.
33 endpointsAppServiceEnvironments API Client
AppServiceEnvironments API Client is the Azure Resource Manager API for App Service Environment v2 (ASE) — Azure's single-tenant, isolated deployment of App Service that runs inside a customer virtual network. It covers ASE provisioning, capacity and virtual IP inspection, virtual network rebinding, diagnostics, multi-role pool scaling, worker pool sizing, metric retrieval, and operation tracking. Use this client to manage the dedicated infrastructure that hosts isolated App Service apps.
Connect Your Agent
1
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 | sh2
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 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.