Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing

GET STARTED

API DirectoryBrowse 10,000+ APIs ready for AI agent integrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI readiness using our scorecardArazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
All ResourcesEverything in one placeBlogLatest articles and insightsTech Talk NewsletterAPIs, AI agents, architecture and strategyWebinarsLive sessions and on-demand recordingsReports & WhitepapersOriginal research on enterprise AI
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
All ResourcesBlogTech Talk NewsletterWebinarsReports & Whitepapers
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

AICPA SOC for Service Organizations logoAICPA SOC for Service Organizations logo

SOC 2® Type 1 report

Audited by Prescient Assurance

Terms & Conditions•Privacy Policy•
© 2026 Jentic Technology Ltd. All rights reserved.
2 Grattan Court East, Dublin, D02 VX86, Ireland
Switch to light modeSwitch to dark mode
APIs / Cloud Infrastructure / Azure / customproviders
customproviders logo

Microsoft Azure customproviders

Browse all Azure APIs
45
AI ReadinessFoundational (D)45/100
See full scorecard
Agent-ready OpenAPI document · curated by JenticCloud InfrastructureComputeoauth211 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Register Azure custom resource providers and associate Azure resources with them through 11 operations on the Microsoft.CustomProviders resource manager surface.

Use for: I need to register a custom resource provider that proxies our internal API, List all custom resource providers in a subscription, I want to associate a resource group with our custom resource type, Find all associations under a given Azure scope

Not supported: Does not implement the custom resource logic, host the proxy endpoint, or run custom workflows - use for registering providers and associations on the Microsoft.CustomProviders namespace only.

Jentic 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.

Jentic One on GithubView OpenAPI Document

Install Jentic One Beta

Connect the customproviders to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the customproviders, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

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%2Fazure-custom-providers" | sh
2

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%2Fazure-custom-providers" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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.

Capabilities

What an agent can do with customproviders API.

Register a custom resource provider with proxy or cache resource types and custom actions

List and update existing custom resource providers within a subscription or resource group

Create associations between an Azure resource and a custom resource type defined by a provider

List all associations under any ARM scope to inventory custom-typed resources

Delete custom resource providers and their associations during clean-up

Enumerate Microsoft.CustomProviders operations available to the caller

Use Cases

Patterns agents use customproviders API for, with concrete tasks.

★ Publish Internal Tools as ARM Resources

Expose an internal platform tool (a feature flag service, internal database, or partner SaaS) as a first-class Azure resource type by registering a custom resource provider that proxies to the tool's API. After registration, ops teams can manage the tool through Azure CLI, Bicep, ARM templates, and Portal alongside native resources, with the same RBAC, tags, and audit log behaviour.

Register a custom resource provider 'feature-flags-rp' in resource group 'rg-platform' with a proxy resource type 'flags' pointing to https://flags.internal/api/{flagName}

Custom Tags via Resource Associations

Use associations to attach a custom resource type to any Azure resource, effectively giving that resource a typed sidecar object with arbitrary metadata. Compliance teams use this to mark resources with structured custom data (data classification, business unit ownership, lifecycle stage) that goes beyond what Azure tags allow. The associations endpoints support listing across any ARM scope and deletion when resources are decommissioned.

Create an association 'classification' under /subscriptions/{id}/resourceGroups/rg-prod with targetResourceId pointing to a custom resource type registered earlier

Custom Provider Inventory and Cleanup

List all custom resource providers in a subscription or resource group to inventory which extensions exist, who deployed them, and whether their endpoints still respond. Pair with the associations list to identify orphaned associations whose target provider is gone. Delete obsolete providers and associations as part of platform clean-up cycles.

List all custom resource providers in subscription /subscriptions/{id} and report any whose provisioningState is not 'Succeeded'

AI Agent Platform Extension

An AI agent supporting platform engineering can register, update, and clean up custom resource providers through Jentic. The agent searches by intent ('register custom resource provider'), Jentic returns the CustomResourceProvider_CreateOrUpdate operation with its schema, and the agent executes the call with managed Azure credentials to extend ARM with new resource types on demand.

Search Jentic for 'register an Azure custom resource provider', load the CustomResourceProvider_CreateOrUpdate schema, and execute it with the user-supplied resource type and proxy endpoint

Key Endpoints

11 endpoints — jentic publishes the only available openapi specification for azure custom providers, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/subscriptions/{subscriptionId}/providers/Microsoft.CustomProviders/resourceProviders

List custom resource providers in a subscription

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.CustomProviders/resourceProviders

List custom resource providers in a resource group

DELETE

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.CustomProviders/resourceProviders/{resourceProviderName}

Delete a custom resource provider

GET

/{scope}/providers/Microsoft.CustomProviders/associations

List associations under any ARM scope

DELETE

/{scope}/providers/Microsoft.CustomProviders/associations/{associationName}

Delete an association

GET

/subscriptions/{subscriptionId}/providers/Microsoft.CustomProviders/resourceProviders

List custom resource providers in a subscription

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.CustomProviders/resourceProviders

List custom resource providers in a resource group

DELETE

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.CustomProviders/resourceProviders/{resourceProviderName}

Delete a custom resource provider

GET

/{scope}/providers/Microsoft.CustomProviders/associations

List associations under any ARM scope

DELETE

/{scope}/providers/Microsoft.CustomProviders/associations/{associationName}

Delete an association

Jentic AI Readiness Score

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

C

customproviders

- Foundational (D)
45/100
100
Foundational Compliance
63
Developer Experience & Jentic Compatibility
21
AI-Readiness & Agent Experience
94
Agent Usability
35
Security
100
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
100

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4
98%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

63

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4
0%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

21

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4
84%

Description Coverage

Coverage of descriptions across API elements.

0%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

0%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

0%

Summary Coverage

Coverage of summaries across operations/tags/info.

94

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1
94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

35

Security

Trust, risk posture, and security compliance.

Grade: FSignals: 1
35%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1
100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

View full reportHow the score is calculatedMore about the dimensions

Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

Score your own APIScoring CLI agent skill
npx @jentic/api-scorecard-cli score <openapi-url>

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring Azure Custom Providers by hand means registering an Azure AD app, handling MSAL token exchange against management.azure.com with the user_impersonation scope, and polling long-running ARM operations for provider and association changes yourself. Through Jentic you install once, import Custom Providers from the API Directory, store the Azure service principal credential once, and your agent calls it.

Permission scoping

Custom Providers puts the provider and association names in the URL path (/subscriptions/{id}/resourceGroups/{rg}/providers/Microsoft.CustomProviders/resourceProviders/{resourceProviderName}), so a rule can pin your agent to a specific resource group scope. You choose the operations it may call, so destructive ones like CustomResourceProvider_Delete or Associations_Delete are not included unless you add them.

Credential isolation

Your Azure service principal credential is stored once, encrypted, by your own Jentic One instance and injected as a scoped ARM bearer token at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'register an Azure custom resource provider' or 'create a resource association', and Jentic returns the matching Custom Providers operation with its input schema so the agent calls the right endpoint without reading the ARM reference docs.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Resource Management

→

Manage native ARM resources alongside the custom resource types defined by Custom Providers.

Use Resources for built-in Azure resource CRUD; use Custom Providers when extending ARM with bespoke resource types.

Complementary

Policy Client

→

Apply Azure Policy to custom resource types once they are registered through Custom Providers.

Use after registering a custom provider to enforce compliance rules across your custom resource type.

Complementary

Authorization Management

→

Grant RBAC roles on custom resource providers to control who can manage them.

Use when an agent needs to grant Contributor or a custom role over a Microsoft.CustomProviders scope.

FAQs

Specific to using customproviders API through Jentic.

Why is there no official OpenAPI spec for customproviders?

Microsoft Azure does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call customproviders via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Custom Providers API use?

It uses Azure Active Directory OAuth 2.0 against https://management.azure.com/ with the user_impersonation scope. The caller needs Contributor or a custom role with Microsoft.CustomProviders/* permissions on the resource group. Jentic stores the service principal credentials encrypted and issues bearer tokens at execution time.

Can I register both proxy and cache resource types?

Yes. The CustomResourceProvider create-or-update body accepts a resourceTypes array, where each entry defines a name, mode (Proxy or Cache), routingType, and an endpoint URL that ARM forwards requests to. Cache types persist resource state in ARM, proxy types do not.

What are the rate limits for the Custom Providers API?

Azure Resource Manager applies subscription-level read and write throttling (around 1,200 requests per hour). Calls that fan out to the underlying provider endpoint also depend on that endpoint's own rate handling.

How do I associate a resource through Jentic?

Run pip install jentic and search for 'create an azure custom provider association'. Jentic returns the Associations_CreateOrUpdate operation; load its schema and execute it with the {scope}, associationName, and a body containing targetResourceId pointing to a registered custom resource type.

Does this API run my custom logic for me?

No. Custom Providers route ARM calls to your endpoint - your endpoint implements the logic. This API only registers the provider, defines its resource types, and manages associations.

Can I limit what my agent is allowed to do with the Custom Providers API?

Yes. Because Jentic One is self-hosted, you decide which Custom Providers operations your agent may call, so read-only calls like listing providers and associations can be allowed while destructive ones such as CustomResourceProvider_Delete or Associations_Delete stay out unless you add them. Since the provider and association names live in the ARM URL path, your own rules can pin the agent to a single subscription or resource group scope. The Azure service principal credential is stored encrypted by your instance and injected as a scoped bearer token at execution time, never entering the agent's prompt or logs.

GET STARTED

Start building with customproviders API

Explore with Jentic One
View OpenAPI Document