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 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 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.
42 endpointsAppServicePlans API Client is the Azure Resource Manager API for managing App Service plans (server farms) — the compute units that host Web Apps, Function Apps, and API Apps. It covers plan creation, SKU and capacity changes, listing the apps that run on a plan, hybrid connection management, and per-plan capability inspection. Use this client to size and scale the underlying compute for App Service workloads.
29 endpointsJentic publishes the only available OpenAPI specification for Azure Action Groups, keeping it validated and agent-ready. Azure Action Groups lets you define a reusable set of notification and automation receivers (email, SMS, voice call, webhook, Azure Function, Logic App, ITSM, Automation Runbook) that Azure Monitor alerts trigger when conditions fire. The API exposes seven operations across the microsoft.insights/actionGroups resource type, covering create, read, update, delete, list by subscription, list by resource group, and a subscribe-receiver flow for confirming opt-in receivers. It is part of the broader Azure Monitor management surface and is intended for programmatic configuration of alert routing.
7 endpointsThe Azure Addons Resource Provider API manages Canonical Ubuntu Advantage support plans purchased through Azure as a third-party addon. It exposes the Microsoft.Addons resource provider operations for listing available support plan types, retrieving the current state of a plan in a subscription, and creating, updating, or deleting plan assignments. This is a control-plane API for governing third-party support entitlements alongside other Azure resources.
5 endpointsJentic publishes the only available OpenAPI specification for Azure Advisor Management Client, keeping it validated and agent-ready. Azure Advisor analyses subscription telemetry and returns personalised recommendations across cost, performance, reliability, and security. This API exposes operations to list and act on those recommendations, suppress noise on specific resources, manage subscription-level Advisor configurations, and trigger fresh recommendation generation on demand.
15 endpointsProvision, configure, and operate virtual machines, scale sets, availability sets, and dedicated hosts across Azure regions. The API covers the full VM lifecycle from image selection and disk configuration to power management and diagnostics, plus proximity placement groups and host groups for latency-sensitive workloads.
109 endpointsJentic publishes the only available OpenAPI specification for Azure Managed Applications Client, keeping it validated and agent-ready. This API manages ARM Managed Applications and Application Definitions: catalogue templates that publishers offer to consumers, the deployed Managed Application instances inside customer subscriptions, and the operations to list, get, create, update, and delete them. It is the surface used by ISVs to ship turnkey Azure solutions and by customers to track deployed instances.
14 endpointsJentic publishes the only available OpenAPI specification for Azure Migrate, keeping it validated and agent-ready. The Azure Migrate API in this version manages Microsoft.Migrate projects, the discovered machines inside them, group definitions, assessments, and assessed machine output. Operators can create a Migrate project, group machines for assessment, run readiness and sizing assessments, download assessment reports, and check name availability for new projects. All requests authenticate with Azure AD OAuth 2.0 against Azure Resource Manager.
24 endpointsJentic publishes the only available OpenAPI specification for Azure Migrate Hub, keeping it validated and agent-ready. Azure Migrate Hub is the Microsoft.Migrate resource provider for tracking and orchestrating workload migrations to Azure. It exposes 23 endpoints for managing migrate projects and the discovered assets inside them, including servers, databases, database instances, web applications, and migrate events. Agents can register solutions against a project, refresh discovered inventory summaries, and inspect machine and database details that have been collected by Azure Migrate appliances.
23 endpointsJentic publishes the only available OpenAPI specification for Azure Monitor Private Link Scopes, keeping it validated and agent-ready. The API manages Azure Monitor Private Link Scopes (AMPLS) under the microsoft.insights provider, allowing teams to gate Application Insights and Log Analytics ingestion to private network endpoints. It exposes 16 endpoints covering scope CRUD, scoped resource binding, private endpoint connection approval, and private link resource discovery.
16 endpointsJentic publishes the only available OpenAPI specification for Azure Resource Graph, keeping it validated and agent-ready. Azure Resource Graph runs Kusto Query Language (KQL) queries across every Azure resource a caller has access to, returning structured JSON results. The 2019-04-01 surface exposes the resources query endpoint and the operations listing for the Microsoft.ResourceGraph provider, the foundation for cross-subscription inventory, FinOps, and policy reporting.
2 endpointsJentic publishes the only available OpenAPI specification for Azure Resource Graph Query, keeping it validated and agent-ready. The API stores named KQL graph queries as ARM resources under Microsoft.ResourceGraph/queries, so teams can persist, share, and version the queries that drive inventory, FinOps, and policy reports. It supports create-or-update, get, list, patch, and delete on graph query resources scoped to a resource group.
5 endpointsJentic publishes the only available OpenAPI specification for Azure SQL Server API spec, keeping it validated and agent-ready. The API manages the connection policy on an Azure SQL logical server, letting agents read or update whether the server uses Default, Proxy, or Redirect connection routing for clients. It targets the Microsoft.Sql resource provider on Azure Resource Manager and is intended for low-latency or hybrid-network configurations rather than database, login, or firewall management.
2 endpointsJentic publishes the only available OpenAPI specification for Azure Stack Azure Bridge Client, keeping it validated and agent-ready. The API exposes the operations catalogue for the Microsoft.AzureStack resource provider, which is the bridge between Azure Stack hybrid deployments and the public Azure cloud. It returns the list of operations available on the provider and is intended for tooling that introspects available actions rather than for direct workload management.
1 endpointsJentic publishes the only available OpenAPI specification for Azure Web Resource Provider API Client, keeping it validated and agent-ready. This client surfaces the subscription-level Microsoft.Web operations that sit underneath Azure App Service, including listing geo regions and deployment locations, retrieving billing meters, checking site name availability, listing apps assigned to a hostname, and managing the publishing user and source control tokens. It is the cross-cutting management surface used before provisioning App Service plans and web apps.
17 endpointsJentic publishes the only available OpenAPI specification for AzureBridgeAdminClient, keeping it validated and agent-ready. The API runs on the Azure Stack admin plane and manages Azure Bridge activations — the registration that links an Azure Stack hub to a public Azure subscription so syndicated marketplace items can flow into the hub. It targets the Microsoft.AzureBridge.Admin resource provider and is intended for Azure Stack operators administering registration objects, not for tenant-side workloads.
4 endpointsJentic publishes the only available OpenAPI specification for AzureDeploymentManager, keeping it validated and agent-ready. The Azure Deployment Manager (ADM) API orchestrates safe, staged rollouts of Azure resources across regions using artifact sources, service topologies, and step-by-step rollouts. It coordinates pre and post deployment health checks, manual intervention gates, and wait steps so multi-region updates can be staged, monitored, and cancelled if a region fails. Use it to model service topologies, define rollout steps, and track or cancel in-flight rollouts via the Azure Resource Manager.
27 endpointsJentic publishes the only available OpenAPI specification for AzureStack Azure Bridge Client, keeping it validated and agent-ready. The Azure Stack Azure Bridge API manages CustomerSubscription resources that link Azure Stack registrations to Azure subscriptions. Operators use it to register, list, and remove the Azure-side bridge entries that allow an on-premises Azure Stack stamp to consume marketplace items, identity, and billing from public Azure.
4 endpointsJentic publishes the only available OpenAPI specification for BatchManagement, keeping it validated and agent-ready. The Azure Batch management API provisions and operates Batch accounts, the parallel compute service used for HPC, rendering, and stress testing on Azure. It manages account-level concerns like keys and quotas plus the resources inside an account — applications, application packages, certificates, and pools — including pool resizing, auto-scale, and key rotation operations.
35 endpointsJentic publishes the only available OpenAPI specification for BlockchainManagementClient, keeping it validated and agent-ready. The Azure Blockchain Service management API provisions blockchain members and transaction nodes that participate in a managed Quorum or Ethereum-like consortium. It exposes lifecycle, key listing, and key regeneration operations for both members and transaction nodes, plus consortium discovery and SKU listings to plan deployments.
21 endpointsJentic publishes the only available OpenAPI specification for BlueprintClient, keeping it validated and agent-ready. BlueprintClient is the Azure Blueprints management surface for inspecting blueprint assignment operations as they apply governance artifacts (policies, role assignments, resource groups, ARM templates) to subscriptions or management groups. The 2018-11-01-preview API exposes long-running assignment operation tracking so that automation can poll the progress of a blueprint rollout and react to per-artifact failures. It targets Azure Resource Manager and authenticates through Azure Active Directory OAuth2.
2 endpointsJentic publishes the only available OpenAPI specification for CdnManagementClient, keeping it validated and agent-ready. The Azure CDN management API administers CDN profiles, endpoints, custom domains, and origins through Azure Resource Manager. It exposes lifecycle operations plus the operational primitives content teams rely on — purge, prefetch, start, stop, custom HTTPS enable/disable, and SSO URI generation — so a CDN deployment can be fully managed from code.
35 endpointsJentic publishes the only available OpenAPI specification for Compute Admin Client, keeping it validated and agent-ready. The Compute Admin Client is the Azure Stack admin-plane entry point for the Microsoft.Compute.Admin resource provider. This 2015-12-01-preview revision exposes a single endpoint that returns the list of supported provider operations, used for capability discovery before invoking other Azure Stack compute admin clients. It is most useful as a probe ahead of automating compute-side fabric tasks on a stamp.
1 endpointsJentic publishes the only available OpenAPI specification for ComputeDiskAdminManagementClient, keeping it validated and agent-ready. The Admin Compute Disk Management Client manages disk migration jobs on an Azure Stack stamp — used by operators to move tenant disks between storage shares to rebalance capacity or evacuate failing hardware. It exposes 4 endpoints covering listing, getting, creating, and cancelling diskMigrationJobs scoped to a location. It is an admin-plane API, distinct from the tenant-side disk APIs.
4 endpointsJentic publishes the only available OpenAPI specification for ComputeManagementConvenienceClient, keeping it validated and agent-ready. This convenience client wraps a single Azure Resource Manager endpoint that creates or updates a Microsoft.Resources deployment, used as the canonical 'deploy this ARM template' call when a workflow only needs to land a VM-shaped deployment without pulling in the full Compute Management Client surface. It accepts an ARM template plus parameters and returns the deployment's provisioning status.
1 endpointsJentic publishes the only available OpenAPI specification for ContainerInstanceManagementClient, keeping it validated and agent-ready. The Container Instance Management Client is the Azure Resource Manager API for Azure Container Instances (ACI) — running serverless container groups without managing a Kubernetes cluster. It exposes 16 endpoints covering container group create/update/delete, restart, stop, log retrieval, command execution, cached image lookup, and per-region capabilities and usage. Use it when an agent needs to run a one-shot container, exec into a running container, or pull logs.
16 endpointsJentic publishes the only available OpenAPI specification for ContainerServiceClient, keeping it validated and agent-ready. The 2017-01-31 Container Service Client manages classic Azure Container Service (ACS) clusters — the pre-AKS managed cluster product that supported DC/OS, Kubernetes, and Docker Swarm orchestrators. Its 5 endpoints cover listing container services in a subscription or resource group, getting a single cluster, and creating, updating, or deleting one. Treat this API as the legacy entry point; new clusters should target AKS via the Container Service (Managed) API.
5 endpointsJentic publishes the only available OpenAPI specification for Azure Custom Providers, keeping it validated and agent-ready. Custom Providers extend the Azure Resource Manager control plane with first-class custom resource types backed by your own webhook or proxy endpoint. The API exposes 11 operations across 6 paths to register custom resource provider endpoints, define resource types and actions, and associate Azure resources with those custom resource types. Use it to publish custom resources (e.g. an internal application or vendor SaaS object) so they can be created, listed, and tagged through ARM tooling alongside native Azure resources.
11 endpointsJentic publishes the only available OpenAPI specification for DeletedWebApps API Client, keeping it validated and agent-ready. The API surfaces the soft-deleted web apps left behind on App Service after a delete operation, scoped at subscription, region, and individual deleted-site level. Agents and recovery scripts use it to enumerate recently deleted apps before invoking a separate restore action elsewhere in the App Service control plane.
3 endpointsJentic publishes the only available OpenAPI specification for DeploymentAdminClient, keeping it validated and agent-ready. The API exposes Azure Stack deployment action plans under Microsoft.Deployment.Admin: a global per-subscription list and a per-plan get. Operators use it to inspect the action plans an Azure Stack deployment generates so they can audit or correlate them with deployment workflows.
2 endpointsJentic publishes the only available OpenAPI specification for DiskResourceProviderClient, keeping it validated and agent-ready. The Azure Disk Resource Provider Client manages Azure managed disks and snapshots through the Microsoft.Compute resource provider. It exposes 16 endpoints covering disk and snapshot CRUD, plus grant and revoke access operations that issue short-lived SAS URIs for direct blob-level read or write. Use it to provision data disks for virtual machines, take and restore snapshots, and copy disk content between subscriptions or regions.
16 endpointsJentic publishes the only available OpenAPI specification for DnsManagementClient, keeping it validated and agent-ready. The Azure DNS Management Client manages public DNS zones and record sets through the Microsoft.Network resource provider. It exposes 14 endpoints covering zone CRUD, record set CRUD across A, AAAA, CNAME, MX, NS, PTR, SOA, SRV, TXT, and CAA types, and a reverse-lookup endpoint that returns the DNS records pointing at a given Azure resource. Use it to host authoritative DNS for owned domains entirely within Azure.
14 endpointsJentic publishes the only available OpenAPI specification for DomainRegistrationProvider API Client, keeping it validated and agent-ready. The Azure DomainRegistrationProvider API Client exposes the operations metadata for the Microsoft.DomainRegistration resource provider — the namespace that powers Azure App Service custom domain registration and the Domains API. It exposes a single endpoint that returns the list of available CSM operations, used for RBAC role definition, audit, and feature discovery against the provider.
1 endpointsJentic publishes the only available OpenAPI specification for Domains API Client, keeping it validated and agent-ready. The Azure Domains API Client manages domain names purchased through Azure App Service Domains. It exposes 15 endpoints covering domain availability checks, recommendation lookups, domain CRUD, renewal, ownership identifiers, and a single sign-on request endpoint that hands off to the App Service domain control center.
15 endpointsJentic publishes the only available OpenAPI specification for EventGridManagementClient, keeping it validated and agent-ready. The Azure EventGrid Management Client is the control-plane API for Azure Event Grid — the fully managed event routing service that fans Azure resource events out to webhooks, Azure Functions, Logic Apps, and other subscribers. It exposes 40 endpoints covering custom topics, domains, domain topics, event subscriptions (global, regional, and per-topic-type), shared access keys, and topic type discovery.
40 endpointsJentic publishes the only available OpenAPI specification for EventHub2018PreviewManagementClient, keeping it validated and agent-ready. This Azure Event Hubs management API provisions and configures dedicated Event Hubs clusters along with the namespaces hosted on them. It also exposes per-namespace network controls including IP filter rules and virtual network rules so platform teams can restrict ingress to known networks and address ranges.
26 endpointsJentic publishes the only available OpenAPI specification for the Azure ExpressRoute Cross Connection REST APIs, keeping it validated and agent-ready. This API manages ExpressRoute cross connections that providers create on behalf of customers to extend on-premises networks into Azure over a private circuit. It exposes operations to read cross connections, update tags, configure peerings, and inspect the live ARP table, route table, and route table summary on a peering device.
12 endpointsJentic publishes the only available OpenAPI specification for the Azure Stack FabricAdminClient, keeping it validated and agent-ready. This narrow administrative API returns the status of fabric application operation results at a given Azure Stack location. Operators use it to check whether long-running fabric application operations have succeeded, failed, or are still in progress.
2 endpointsJentic publishes the only available OpenAPI specification for the Azure FeatureClient, keeping it validated and agent-ready. This API surfaces the preview features that Azure exposes through AFEC (Azure Feature Exposure Control) so subscriptions can opt into preview behaviours of resource providers. It supports listing all preview features, listing features in a specific provider namespace, reading a single feature, and registering a feature for the subscription.
5 endpointsJentic publishes the only available OpenAPI specification for FrontDoorManagementClient, keeping it validated and agent-ready. The Azure Front Door Management API lets agents provision and manage Azure Front Door instances through Azure Resource Manager, including frontend endpoints, routing rules, backend pools, and HTTPS configuration. It supports global HTTP/HTTPS load balancing, custom domain validation, and on-demand cache purging across the Front Door edge network. Authentication uses Azure AD OAuth2 against the management.azure.com control plane.
13 endpointsJentic publishes the only available OpenAPI specification for GalleryManagementClient, keeping it validated and agent-ready. The Azure Stack Admin Gallery Management API exposes the discoverable operations surface for the marketplace gallery on an Azure Stack Hub deployment. Operators use it to enumerate the administrative actions available against the Microsoft.Gallery.Admin resource provider on a private Azure Stack environment. It runs against the Azure Stack admin endpoint at adminmanagement.local.azurestack.external with Azure AD OAuth2.
1 endpointsJentic publishes the only available OpenAPI specification for HanaManagementClient, keeping it validated and agent-ready. The SAP HANA on Azure Management API manages dedicated HANA Large Instance bare-metal hardware and the SAP monitor companion service through Azure Resource Manager. Operators provision and patch HANA instances, restart or shut them down, and create SAP monitors that observe the broader SAP landscape. The API is authenticated via Azure AD OAuth2 against management.azure.com and exposes 15 operations split between hanaInstances and sapMonitors.
15 endpointsJentic publishes the only available OpenAPI specification for HDInsightManagementClient, keeping it validated and agent-ready. The HDInsight Management API manages HDInsight cluster applications — the optional add-on workloads that can be installed onto a running HDInsight cluster, such as third-party tools or custom services. This 2018-06-01-preview surface is focused specifically on the application lifecycle: list, get, create, and delete. Authentication is Azure AD OAuth2 against management.azure.com, and the resource is scoped under Microsoft.HDInsight/clusters/{clusterName}/applications.
4 endpointsJentic publishes the only available OpenAPI specification for HybridComputeManagementClient, keeping it validated and agent-ready. The Azure Hybrid Compute Management API manages Azure Arc-enabled servers — the resource projection that makes on-premises and other-cloud machines first-class Azure resources. It exposes machine and machine-extension lifecycle operations alongside a reconnect endpoint used when an agent needs to re-onboard a machine. Authentication is Azure AD OAuth2 against management.azure.com, scoped under Microsoft.HybridCompute.
13 endpointsJentic publishes the only available OpenAPI specification for HybridDataManagementClient, keeping it validated and agent-ready. The Azure Hybrid Data Management API provisions and operates Microsoft.HybridData data managers that move data between on-premises stores and Azure cloud services. It exposes 29 ARM endpoints to create data managers, configure data services and data stores, define job definitions, and run, cancel, or resume hybrid data movement jobs across resource groups and subscriptions.
29 endpointsJentic publishes the only available OpenAPI specification for InstanceMetadataClient, keeping it validated and agent-ready. The Azure Instance Metadata Service (IMDS) is a non-routable endpoint reachable from inside an Azure VM at 169.254.169.254 that returns information about the running instance and issues managed identity tokens. It exposes 4 endpoints to fetch instance metadata, an attested document, managed identity info, and an OAuth 2.0 access token for the VM's assigned identity.
4 endpointsJentic publishes the only available OpenAPI specification for KustoManagementClient, keeping it validated and agent-ready. KustoManagementClient is the Azure Resource Manager control plane for Azure Data Explorer (ADX) — it provisions and manages Kusto clusters, the databases inside them, attached database configurations, and data ingestion connections (Event Hub, IoT Hub, Event Grid). It does not run KQL queries or ingest data; it shapes the infrastructure that the ADX query engine runs on.
34 endpointsJentic publishes the only available OpenAPI specification for LogicAppsManagementClient, keeping it validated and agent-ready. LogicAppsManagementClient is the Azure Resource Manager surface for the connector and gateway plane behind Azure Logic Apps. It manages on-premises connection gateways, the catalog of managed APIs available to Logic Apps, custom API definitions extracted from WSDL or Swagger, and connection objects that bind a Logic App to an external system. It does not run workflows or trigger Logic App executions.
26 endpointsJentic publishes the only available OpenAPI specification for LogicManagementClient, keeping it validated and agent-ready. LogicManagementClient is the Azure Resource Manager surface for the Microsoft.Logic provider — the workflow plane behind Azure Logic Apps. It provisions and manages Logic App workflows, workflow versions and runs, integration accounts (with their schemas, maps, partners, and agreements), batch configurations, and integration service environments. It is the orchestration control plane, not a runtime data path.
106 endpointsJentic publishes the only available OpenAPI specification for MaintenanceManagementClient, keeping it validated and agent-ready. MaintenanceManagementClient is the Azure Resource Manager surface for the Microsoft.Maintenance provider — Azure Maintenance Configurations. It defines maintenance windows, assigns those configurations to virtual machines and other resources, and tracks the status of pending or applied platform updates. It does not patch operating systems or install application updates.
18 endpointsJentic publishes the only available OpenAPI specification for ManagedNetworkManagementClient, keeping it validated and agent-ready. ManagedNetworkManagementClient is the Azure Resource Manager surface for the Microsoft.ManagedNetwork provider — Azure Virtual Network Manager's managed network construct. It defines a managed network that groups virtual networks, subscriptions, or management groups under one connectivity boundary, and manages the groups, scope assignments, and peering policies inside it.
19 endpointsJentic publishes the only available OpenAPI specification for ManagedServicesClient, keeping it validated and agent-ready. The Azure ManagedServices API powers Azure Lighthouse, letting service providers manage customer Azure resources from their own tenant through delegated resource management. Use it to register a managed service offer in a customer scope, list and inspect registration definitions and assignments, and remove access when an engagement ends. The API operates over Azure Resource Manager scopes (subscriptions or resource groups) and is authenticated through Azure Active Directory OAuth 2.0.
9 endpointsJentic publishes the only available OpenAPI specification for Management Groups, keeping it validated and agent-ready. The Azure Management Groups API organises subscriptions into a hierarchical tree so policy, RBAC, and cost governance can be applied at scale across a tenant. Use it to create and update management groups, move subscriptions between groups, walk the descendant tree, and check whether a group ID is available before creating it. The API is hosted on Azure Resource Manager and authenticated through Azure Active Directory OAuth 2.0.
13 endpointsJentic publishes the only available OpenAPI specification for ManagementLinkClient, keeping it validated and agent-ready. The Azure Resource Links API records logical relationships between Azure resources, even across different resource groups within the same subscription. Use it to create a directional link from a source resource to a target, list every link declared at a subscription or scope, and clean up dangling links when one side is deleted. Each resource can hold up to 50 outbound links and the API is authenticated via Azure Active Directory OAuth 2.0 on Azure Resource Manager.
6 endpointsJentic publishes the only available OpenAPI specification for ManagementLockClient, keeping it validated and agent-ready. The Azure Management Locks API applies CanNotDelete and ReadOnly locks to subscriptions, resource groups, or individual resources so users cannot accidentally modify or delete production assets. Use it to create, list, get, and delete locks at any ARM scope, including by-scope variants for arbitrary nested resource paths. Authentication is via Azure Active Directory OAuth 2.0 on Azure Resource Manager.
17 endpointsJentic publishes the only available OpenAPI specification for Marketplace RP Service, keeping it validated and agent-ready. The Azure Marketplace private store API lets organisations curate which marketplace offers their users can deploy by managing private stores at the tenant level. Use it to create or update a private store, list available stores, and admit specific offers into a store so only approved publishers and SKUs are visible to end users. Authentication is via Azure Active Directory OAuth 2.0 on Azure Resource Manager.
9 endpointsJentic publishes the only available OpenAPI specification for MarketplaceOrdering.Agreements, keeping it validated and agent-ready. The Azure Marketplace Ordering API manages the legal agreements that must be accepted before a marketplace plan can be deployed in a subscription. Use it to retrieve the current agreement for a publisher, offer, and plan combination, sign or cancel an agreement, and list every signed agreement in a subscription. Authentication is via Azure Active Directory OAuth 2.0 on Azure Resource Manager.
7 endpointsJentic publishes the only available OpenAPI specification for MicrosoftSerialConsoleClient, keeping it validated and agent-ready. The Azure Serial Console API enables and disables text-based serial console access at the subscription level for virtual machines and VM scale set instances. Serial Console is the recovery channel that operators reach for when SSH or RDP is unavailable, allowing direct keyboard input to the VM bootloader, single-user mode, or kernel debugger. The control plane exposed here governs subscription-wide enablement of the feature; the actual console stream is delivered over a separate websocket channel established through the Azure portal or CLI.
4 endpointsJentic publishes the only available OpenAPI specification for Azure Mixed Reality, keeping it validated and agent-ready. The Mixed Reality Resource Provider provisions and manages Spatial Anchors accounts, the cloud resource that backs Azure Spatial Anchors apps for HoloLens, iOS, and Android. The control plane lets developers create accounts in a region, list them across a subscription or resource group, regenerate primary or secondary access keys, and check name availability before provisioning. Spatial Anchors accounts are the gating credential boundary for any client SDK call against the Spatial Anchors data plane.
10 endpointsJentic publishes the only available OpenAPI specification for the Azure Stack network admin load balancer surface, keeping it validated and agent-ready. NetworkAdminManagementClient is the operator-facing control plane for an Azure Stack Hub deployment, exposing the cloud admin view of physical infrastructure objects rather than tenant resources. The 2015-06-15 slice covers the admin load balancers endpoint, which lists the load balancer resources active across the Azure Stack region. The base URL adminmanagement.local.azurestack.external is reached only from inside an Azure Stack environment with operator credentials.
1 endpointsJentic publishes the only available OpenAPI specification for NetworkManagementClient, keeping it validated and agent-ready. The Azure Network management API exposes 97 operations across the Microsoft.Network resource provider for managing virtual networks, subnets, network interfaces, public IP addresses, network security groups, load balancers, application gateways, route tables, ExpressRoute circuits, and VPN gateways. It supports the full lifecycle of Azure networking primitives — provisioning, configuration changes, peering setup, security rule updates, and traffic inspection — at subscription and resource group scope.
97 endpointsJentic publishes the only available OpenAPI specification for PeeringManagementClient, keeping it validated and agent-ready. The Azure Peering Service management API exposes 26 operations on the Microsoft.Peering resource provider for managing Internet peerings between ISPs and Microsoft's global network. Use it to register peer ASNs, list peering locations, provision direct and exchange peerings, register and validate peering services and prefixes, and check service provider availability for a specific customer location.
26 endpointsJentic publishes the only available OpenAPI specification for Power BI Embedded Management Client, keeping it validated and agent-ready. The API manages Microsoft.PowerBI workspace collections in Azure Resource Manager, covering provisioning, listing, updates, deletes, and access-key rotation for the dedicated capacity that hosts embedded Power BI dashboards. It also includes name availability checks and a workspace listing endpoint used to surface workspaces inside a collection.
12 endpointsJentic publishes the only available OpenAPI specification for PowerBIDedicated, keeping it validated and agent-ready. The API manages Power BI Dedicated capacities under Microsoft.PowerBIDedicated in Azure Resource Manager — the per-tenant compute capacities (A SKUs) that back embedded Power BI workloads. It covers the full capacity lifecycle, including provisioning, scaling, suspend and resume, plus SKU listings and name availability checks.
12 endpointsJentic publishes the only available OpenAPI specification for PrivateDnsManagementClient, keeping it validated and agent-ready. The API manages Azure Private DNS zones under Microsoft.Network — the private name resolution surface used to resolve hostnames inside Azure virtual networks without exposing them publicly. It covers the zone lifecycle, virtual network links that bind zones to VNETs, and the full set of record sets (A, AAAA, CNAME, MX, PTR, SOA, SRV, TXT) that hold the records inside each zone.
17 endpointsJentic publishes the only available OpenAPI specification for Provider API Client, keeping it validated and agent-ready. The API exposes the Microsoft.Web resource provider's discovery endpoints — the operations available on the provider, the runtime stacks (such as .NET, Node.js, PHP, Python, and Java versions) supported by Azure App Service, and the equivalent stacks at subscription scope. It is the lookup surface used to populate stack pickers and validate desired runtimes before provisioning App Service resources.
3 endpointsJentic publishes the only available OpenAPI specification for Recommendations API Client, keeping it validated and agent-ready. The API exposes the Microsoft.Web Recommendations resource — performance, scaling, and reliability suggestions that Azure App Service generates for sites and hosting environments. It covers reading current and historical recommendations, listing them at subscription, hosting environment, or site scope, and resetting or disabling individual recommendations after they have been actioned.
15 endpointsJentic publishes the only available OpenAPI specification for Relay, keeping it validated and agent-ready. The API manages Azure Relay resources under Microsoft.Relay through Azure Resource Manager — namespaces that host the relay endpoints, hybrid connections that bridge on-premises services to cloud clients, and WCF relays that expose legacy WCF services. It also covers the authorization-rule and access-key surface used by clients on each side of the relay.
34 endpointsJentic publishes the only available OpenAPI specification for RemediationsClient, keeping it validated and agent-ready. The Azure Policy Insights RemediationsClient API creates and manages remediation tasks that bring non-compliant Azure resources back into compliance with assigned policies. Agents can launch remediations at management group, subscription, resource group, or individual resource scope, list deployments triggered by a remediation, and cancel in-progress remediation jobs. The service operates against the Azure Resource Manager control plane and integrates with Azure Policy assignments to drive bulk drift correction.
24 endpointsJentic publishes the only available OpenAPI specification for the ResourceHealthMetadata API Client, keeping it validated and agent-ready. The API exposes Azure App Service resource health metadata, which describes how the platform reports availability and signals for web apps and deployment slots. Agents can list metadata at the subscription, resource group, app, or slot level to understand what health categories Azure is tracking before correlating those signals with diagnostics or alerts. The service runs against the Azure Resource Manager control plane for the Microsoft.Web provider.
6 endpointsJentic publishes the only available OpenAPI specification for ResourceManagementClient, keeping it validated and agent-ready. The Azure Resource Management API is the control plane for ARM deployments, resource groups, individual resources, and tags across subscriptions and management groups. Agents can submit and validate ARM template deployments at any scope, list and update resources by id, manage resource groups and their tags, and inspect deployment operations to debug failures. It is the foundational API for everything Azure builds on top of subscriptions.
78 endpointsJentic publishes the only available OpenAPI specification for RunCommandsClient, keeping it validated and agent-ready. The Azure Compute Run Commands API lets agents execute scripts on Azure virtual machines and Virtual Machine Scale Set instances without opening RDP, SSH, or installing additional agents. It exposes the catalogue of supported commands per region and triggers script execution against a specific VM or VMSS instance, returning a long-running operation handle for polling. This is the standard mechanism for ad-hoc remote execution on Azure VMs.
4 endpointsJentic publishes the only available OpenAPI specification for SeaBreezeManagementClient, keeping it validated and agent-ready. The Azure Service Fabric Mesh management API provisions and operates serverless container applications composed of services, gateways, networks, secrets, and volumes. Agents declare an application with its services and dependencies, deploy it without managing a cluster, and inspect runtime topology including replicas and code packages. The API is scoped to ARM and reaches the Service Fabric Mesh control plane in any subscription.
36 endpointsJentic publishes the only available OpenAPI specification for SearchManagementClient, keeping it validated and agent-ready. The Azure Cognitive Search ARM control plane API provisions, scales, and manages search service resources inside a subscription. Agents can create or delete a search service, change its replica and partition counts, regenerate admin keys, mint or revoke query keys, and check name availability before creation. This is the lifecycle API behind any Cognitive Search deployment.
13 endpointsJentic publishes the only available OpenAPI specification for ServerManagement, keeping it validated and agent-ready. The Azure Server Management API exposes the Microsoft.ServerManagement resource provider, which lets agents register on-premises Windows servers as managed nodes, pair them to a gateway, open remote sessions, and run PowerShell commands against them through the Azure control plane. It models gateways, nodes, sessions, and PowerShell sub-sessions, and is the underlying API for the Server Management Tools experience that Microsoft offered for hybrid and Server Core deployments.
25 endpointsJentic publishes the only available OpenAPI specification for ServiceBusManagementClient, keeping it validated and agent-ready. The Azure Service Bus management API exposes the Microsoft.ServiceBus resource provider so agents can provision Service Bus namespaces, create queues and topics with subscriptions and rules, manage authorization rules and shared access keys, configure network rule sets, and orchestrate geo-disaster-recovery pairings between namespaces. It is the control plane for setting up messaging infrastructure — the data plane for sending and receiving messages lives separately.
65 endpointsJentic publishes the only available OpenAPI specification for ServiceFabricManagementClient, keeping it validated and agent-ready. The Azure Service Fabric resource provider API lets agents register application types and versions, deploy applications, and create or update services on a Service Fabric cluster through Azure Resource Manager. It models clusters as the parent scope, application types as registered packages, applications as deployed instances, and services as the runtime units, plus an operations endpoint that lists every action exposed by the Microsoft.ServiceFabric provider.
19 endpointsJentic publishes the only available OpenAPI specification for SharedImageGalleryServiceClient, keeping it validated and agent-ready. The Azure Shared Image Gallery API (now Azure Compute Gallery) lets agents create galleries, register custom VM image and gallery application definitions, and publish versioned image and application artefacts that can be replicated across Azure regions and shared with other subscriptions or tenants. It models galleries, images, image versions, applications, and application versions under the Microsoft.Compute resource provider.
26 endpointsJentic publishes the only available OpenAPI specification for SiteRecoveryManagementClient, keeping it validated and agent-ready. The Azure Site Recovery API exposes the replication surface of the Microsoft.RecoveryServices resource provider so agents can configure fabrics, protection containers, replication policies, recovery plans, network mappings, and individual replicated items. It supports the full disaster-recovery and migration lifecycle — protecting VMs, running planned and unplanned failovers, executing test failovers, committing migrations, and managing alerts and events on a Recovery Services vault.
126 endpointsJentic publishes the only available OpenAPI specification for SqlVirtualMachineManagementClient, keeping it validated and agent-ready. The SQL virtual machine management API exposes RESTful operations to provision and manage SQL Server installations running on Azure Compute, including individual SQL virtual machines, SQL virtual machine groups, and availability group listeners. It coordinates with Azure Compute, Network, and Storage to install, configure, and tear down SQL Server VMs, and to wire them into Always On availability groups. Use it for IaaS SQL Server lifecycle management, not Azure SQL Database PaaS schemas.
18 endpointsJentic publishes the only available OpenAPI specification for StorageManagementClient, keeping it validated and agent-ready. The Admin Storage Management Client exposes the Azure Stack on-premises admin endpoint for the Microsoft.Storage.Admin resource provider. It returns the list of storage acquisitions in a given Azure Stack location, which represents disk acquisitions made by the storage service inside an Azure Stack stamp. Use it for operator-side observability of Azure Stack storage rather than public Azure cloud workloads.
1 endpointsJentic publishes the only available OpenAPI specification for SubscriptionClient, keeping it validated and agent-ready. The User Subscription Management Client exposes the public-tenant offers catalogue used during Azure subscription acquisition, including offers presented directly and offers presented via delegated providers. It supports listing offers and retrieving a specific offer scoped to a delegated provider id. Use it to enumerate the subscription offers a tenant can acquire and to integrate the offer catalogue into custom signup or procurement flows.
3 endpointsJentic publishes the only available OpenAPI specification for SubscriptionDefinitionsClient, keeping it validated and agent-ready. The Subscription Definitions client exposes a programmatic interface to create, retrieve, and list Azure subscription definitions, plus a long-running-operation status endpoint. It is part of the Microsoft.Subscription resource provider and is intended for tenants and CSPs that automate subscription provisioning at scale. Use it to script subscription creation flows that previously required manual portal steps.
5 endpointsJentic publishes the only available OpenAPI specification for SubscriptionsManagementClient, keeping it validated and agent-ready. The Admin Subscriptions Management Client exposes the Azure Stack admin endpoint for managing the plans acquired by tenant subscriptions on a stamp. It supports listing, retrieving, creating, and deleting plan acquisitions associated with a target subscription. Use it for operator-side control of which Azure Stack plans are attached to which tenant subscriptions.
4 endpointsJentic publishes the only available OpenAPI specification for TopLevelDomains API Client, keeping it validated and agent-ready. The TopLevelDomains API Client is part of the Azure App Service Domain Registration provider and exposes a read-only catalog of top-level domains (such as .com, .net, .org) that Azure customers can register through Microsoft.DomainRegistration. Agents can list every supported TLD, fetch detail for a specific TLD by name, and retrieve the legal agreements a buyer must accept before purchasing a domain in that TLD. Authentication uses Azure Active Directory OAuth 2.0 against the Azure Resource Manager endpoint at management.azure.com.
3 endpointsJentic publishes the only available OpenAPI specification for TrafficManagerManagementClient, keeping it validated and agent-ready. The Azure Traffic Manager Management Client is the ARM control plane for Microsoft.Network/trafficmanagerprofiles. It lets agents create, update, and delete Traffic Manager profiles, attach endpoints (Azure, external, or nested) for global DNS-level traffic routing, query geographic hierarchies for geo routing, manage user metrics keys for Real User Measurements, and pull heat map analytics. Authentication uses Azure Active Directory OAuth 2.0 against management.azure.com.
16 endpointsJentic publishes the only available OpenAPI specification for Update Management, keeping it validated and agent-ready. The Azure Update Management API is part of Azure Automation and lets agents define, schedule, and remove softwareUpdateConfigurations — the objects that drive patching campaigns across Windows and Linux VMs (Azure, Arc-enabled, or hybrid). A configuration captures the OS, classification filters, included or excluded KB or package lists, target machines or saved searches, scheduling, and reboot behaviour. Authentication uses Azure Active Directory OAuth 2.0 against management.azure.com.
4 endpointsJentic publishes the only available OpenAPI specification for UpdateAdminClient, keeping it validated and agent-ready. The Update Admin Management Client is the Azure Stack Hub admin-plane API for the Microsoft.Update.Admin resource provider. It lets a Stack Hub operator enumerate the operations the Update RP exposes — useful for capability discovery, documentation generation, and scripting tools that build admin dashboards over a privately deployed Azure Stack region. Authentication uses Azure Active Directory OAuth 2.0 against the local admin endpoint adminmanagement.local.azurestack.external.
1 endpointsJentic publishes the only available OpenAPI specification for VirtualMachineImageTemplate, keeping it validated and agent-ready. The Azure VM Image Builder API (Microsoft.VirtualMachineImages) lets agents define imageTemplate resources that describe a source image, a list of customizers (shell, PowerShell, Windows-update, file copy), and one or more distribute targets (Managed Image, Shared Image Gallery, VHD). Once the template is created, agents trigger a build via the run action, list runOutputs to inspect generated artefacts, and use the resulting images to provision standardised VM fleets. Authentication uses Azure Active Directory OAuth 2.0.
10 endpointsJentic publishes the only available OpenAPI specification for VirtualWANAsAServiceManagementClient, keeping it validated and agent-ready. The Azure Virtual WAN management client lets agents create and operate the building blocks of a global Virtual WAN: virtualWans themselves, virtualHubs in each region, hubVirtualNetworkConnections, vpnGateways and their vpnConnections (with link-level vpnLinkConnections for resilience), point-to-site p2sVpnGateways with associated p2sVpnServerConfigurations, and vpnSites describing on-premises endpoints. Operators also pull P2S connection health, supported security providers, and downloadable VPN configuration. Authentication uses Azure Active Directory OAuth 2.0.
49 endpointsJentic publishes the only available OpenAPI specification for VM Insights Onboarding, keeping it validated and agent-ready. The Azure VM Insights Onboarding API exposes a single Microsoft.Insights resource — vmInsightsOnboardingStatuses/default — that returns whether a given VM, VM Scale Set, or resource group is onboarded to VM Insights along with its associated Log Analytics workspace and data status. Agents use it to audit observability coverage, gate deployments on monitoring being present, and drive VM Insights enablement workflows. Authentication uses Azure Active Directory OAuth 2.0.
1 endpointsJentic publishes the only available OpenAPI specification for VMwareCloudSimple, keeping it validated and agent-ready. The Azure VMwareCloudSimple API provisions and manages CloudSimple-hosted VMware private clouds, dedicated cloud nodes, virtual machines, virtual networks, and customisation policies inside Microsoft Azure. It exposes 34 management plane operations across 25 resource paths under the Microsoft.VMwareCloudSimple provider, covering private cloud lifecycle, node placement on dedicated hardware, VM templates, and SKU availability lookups by region. Use it to drive infrastructure-as-code workflows for VMware workloads on Azure without leaving the ARM control plane.
34 endpointsThe Azure WebApps API Client is the management plane for Azure App Service web apps, function apps, and API apps. It exposes 349 operations across 252 resource paths under the Microsoft.Web/sites provider, covering site lifecycle, deployment slots, configuration, app settings, custom hostnames, SSL bindings, source control, backups, scaling, host name bindings, and diagnostics. Use it to script the full lifecycle of an App Service site, from creation and configuration through to backup, slot swaps, and decommissioning.
349 endpointsThe Azure WebSite Management Client is the original 2015-era management plane covering Azure Websites, App Service domain registration, and certificate orders through Azure Resource Manager. It exposes 295 operations across 213 resource paths, including site creation and lifecycle, app settings, source control configuration, custom domain registration, top-level domain lookups, domain recommendations, certificate orders, and certificate validation. Use it where existing automation targets the 2015-08-01 API version, or where domain and certificate registration flows must be scripted alongside site management.
295 endpointsStep 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 | shStep 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.