Microsoft Azure FeatureClient
Browse all Azure APIs45
AI ReadinessFoundational (D)45/100
Agent-ready OpenAPI document · curated by JenticCloud InfrastructureComputeoauth25 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
List Azure preview features available through AFEC, read individual features, and register a preview feature for a subscription.
Use for: List every preview feature available to subscription 1111-2222-3333-4444, Show all preview features under provider namespace Microsoft.Compute, Get the registration state of the AKS preview feature EnableEncryptionAtHost, Register the preview feature AllowUserPathPrefixes under Microsoft.Storage
Not supported: Does not unregister features, manage application-level feature flags, or change resource provider registrations - use only to list, read, and register Azure preview features through AFEC for a subscription.
Jentic 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.
Install Jentic One Beta
Connect the FeatureClient to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the FeatureClient, 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%2Ffeature-client" | 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%2Ffeature-client" | 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.
Capabilities
What an agent can do with FeatureClient API.
List all preview features available to a subscription through AFEC
List preview features for a specific resource provider namespace
Read the registration state of a single preview feature by name
Register a preview feature for the current subscription
Discover the available Microsoft.Features REST API operations
Use Cases
Patterns agents use FeatureClient API for, with concrete tasks.
★ Inventory Preview Features for a Subscription
Platform engineering teams audit which Azure preview features are exposed to a subscription before promoting workloads. GET /subscriptions/{subscriptionId}/providers/Microsoft.Features/features returns every feature visible through AFEC, with each entry's registration state, so the audit can flag features the subscription has opted into and those still pending.
List all preview features for subscription 1111-2222-3333-4444 and emit the names of any with state Registered
Opt In to a Preview Behaviour
When a team wants to use a preview behaviour of a resource provider (for example, a new Microsoft.Compute capability), they register the feature on the subscription. POST /subscriptions/{subscriptionId}/providers/Microsoft.Features/providers/{resourceProviderNamespace}/features/{featureName}/register flips the feature into the registered state, after which the provider re-registration unlocks the behaviour.
Register the feature EncryptionAtHost under Microsoft.Compute for subscription 1111-2222-3333-4444 and read it back to confirm the state is Registered or Pending
Verify a Feature State Before Deploying
Pipelines that depend on a preview feature gate the deployment on the feature's registration state. GET /subscriptions/{subscriptionId}/providers/Microsoft.Features/providers/{resourceProviderNamespace}/features/{featureName} returns the current state so the pipeline can fail fast if the feature is not Registered, instead of failing deep inside an ARM template.
Get feature EncryptionAtHost under Microsoft.Compute for subscription 1111-2222-3333-4444 and return true only if state == Registered
Agent-Driven Subscription Hardening
An AI agent running subscription readiness checks can list every preview feature, register the ones a tenant policy requires, and report any still pending - all through Jentic. Intent search returns the Features list, get, and register operations with their schemas; the AAD token is held in the vault so the agent never sees the service principal secret.
Search Jentic for 'register an Azure preview feature', execute Features_Register for each feature in a tenant policy list, then call Features_Get on each to report the resulting state
Key Endpoints
5 endpoints — jentic publishes the only available openapi specification for the azure featureclient, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/subscriptions/{subscriptionId}/providers/Microsoft.Features/features
List all preview features for a subscription
GET
/subscriptions/{subscriptionId}/providers/Microsoft.Features/providers/{resourceProviderNamespace}/features
List preview features for a provider namespace
GET
/subscriptions/{subscriptionId}/providers/Microsoft.Features/providers/{resourceProviderNamespace}/features/{featureName}
Get a single preview feature
POST
/subscriptions/{subscriptionId}/providers/Microsoft.Features/providers/{resourceProviderNamespace}/features/{featureName}/register
Register a preview feature for the subscription
GET
/providers/Microsoft.Features/operations
List Microsoft.Features REST API operations
GET
/subscriptions/{subscriptionId}/providers/Microsoft.Features/features
List all preview features for a subscription
GET
/subscriptions/{subscriptionId}/providers/Microsoft.Features/providers/{resourceProviderNamespace}/features
List preview features for a provider namespace
GET
/subscriptions/{subscriptionId}/providers/Microsoft.Features/providers/{resourceProviderNamespace}/features/{featureName}
Get a single preview feature
POST
/subscriptions/{subscriptionId}/providers/Microsoft.Features/providers/{resourceProviderNamespace}/features/{featureName}/register
Register a preview feature for the subscription
GET
/providers/Microsoft.Features/operations
List Microsoft.Features REST API operations
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.
F
FeatureClient
- Foundational (D)45/100
74
Foundational Compliance56
Developer Experience & Jentic Compatibility24
AI-Readiness & Agent Experience94
Agent Usability35
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
74
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A-Signals: 4
97%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
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.
56
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: CSignals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
25%
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.
24
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
74%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
20%
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.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Azure FeatureClient by hand means minting Azure AD OAuth 2.0 tokens against management.azure.com, building the Microsoft.Features paths for AFEC preview features, and backing off on ARM subscription throttling. Through Jentic you install once, import FeatureClient from the API Directory, store the Azure AD client credentials once, and your agent calls it.
Permission scoping
The API puts the subscription, provider namespace, and feature name in the URL path (/subscriptions/{subscriptionId}/providers/Microsoft.Features/providers/{resourceProviderNamespace}/features/{featureName}/...), so a rule can scope your agent to one provider namespace such as Microsoft.Compute. You choose the operations it may call, so the state-changing Features_Register is not included unless you add it, leaving the agent with the list and get reads.
Credential isolation
Your Azure AD client credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time as a scoped bearer token. The service principal secret never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'list Azure preview features' or 'register an Azure preview feature', and Jentic returns the matching Features_List, Features_Get, or Features_Register operation with its input schema so the agent calls the right endpoint without remembering the Microsoft.Features path layout.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using FeatureClient API through Jentic.
Why is there no official OpenAPI spec for FeatureClient?
Microsoft Azure does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call FeatureClient 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 FeatureClient use?
The API uses Azure Active Directory OAuth 2.0 bearer tokens (the azure_auth scheme) on management.azure.com. Through Jentic, the AAD service principal secret is stored in your Jentic One instance and exchanged for a short-lived bearer token per call.
Can I register an Azure preview feature with this API?
Yes. Call POST /subscriptions/{subscriptionId}/providers/Microsoft.Features/providers/{resourceProviderNamespace}/features/{featureName}/register. The feature transitions to Pending or Registered; you may also need to re-register the parent resource provider before the new behaviour takes effect.
How do I list every preview feature available to my subscription?
Call GET /subscriptions/{subscriptionId}/providers/Microsoft.Features/features. To narrow to a single resource provider, call GET .../providers/Microsoft.Features/providers/{resourceProviderNamespace}/features instead.
What are the rate limits for the FeatureClient?
Azure Resource Manager applies subscription-level throttling. Listing features is cheap and safe to poll on the order of seconds; the register call is rarer in practice and does not need aggressive retries. On HTTP 429, back off using the Retry-After header.
How do I register a preview feature from an agent through Jentic?
Run pip install jentic, then search Jentic with 'register an Azure preview feature'. Load Features_Register, supply the subscription, provider namespace, and feature name, and execute. Read it back with Features_Get to confirm the state. The AAD token is sourced from the vault on every call.
Can I limit what my agent is allowed to do with the Azure FeatureClient API?
Yes. Because you run Jentic One yourself, your own rules decide which Microsoft.Features operations and credentials the agent may use. Since the subscription, provider namespace, and feature name all sit in the URL path, a rule can scope the agent to a single namespace such as Microsoft.Compute, and you choose the operations it may call. That lets you leave the agent with the read-only Features_List and Features_Get calls while withholding the state-changing Features_Register unless you explicitly grant it.
GET STARTED