FeatureClient

★ Only Publicly Available OpenAPI DocumentCloud InfrastructureComputeoauth25 EndpointsREST

For Agents

List Azure preview features available through AFEC, read individual features, and register a preview feature for a subscription.

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.

Install Jentic One Beta (Self-Hosted)

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 | sh

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

GET STARTED

Start building with FeatureClient API

Explore with Jentic

View OpenAPI Document

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 document for FeatureClient, keeping it validated and agent-ready.

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.

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

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

GET

/providers/Microsoft.Features/operations

List Microsoft.Features REST API operations

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Azure AD OAuth 2.0 tokens are minted and rotated inside the Jentic vault (MAXsystem). Service principal client secrets stay encrypted; agents call Microsoft.Features with a short-lived scoped token only.

Intent-based discovery

Agents search by intent (e.g., 'register an Azure preview feature') and Jentic returns Features_Register or Features_Get with its input schema, so the agent does not have to remember the long Microsoft.Features path layout.

Time to first call

Direct ARM integration: half a day for AAD setup, token acquisition, and feature path construction. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Azure Policy Client

Encodes and enforces tenant policies that often govern which preview features may be enabled.

Use Policy to assert that only allowed features are registered; use FeatureClient to read or change feature state.

Complementary

Azure Advisor Management Client

Surfaces recommendations that may depend on, or be unlocked by, preview feature registrations.

Use Advisor to find what to enable; use FeatureClient to enable the underlying preview feature.

Alternative

LaunchDarkly REST API

Application-level feature flag service used to gate code paths in customer apps rather than Azure platform features.

Choose LaunchDarkly for feature flagging in your own application code. Stay with FeatureClient for Azure subscription-level preview features.

Alternative

ConfigCat API

Hosted feature flag and config management service for application code paths.

Choose ConfigCat for app-level feature flags. Stay with FeatureClient when the flag governs Azure platform behaviour.

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 at https://app.jentic.com/sign-up.

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 the MAXsystem vault 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.