Microsoft Azure RedisManagementClient
Browse all Azure APIs★ Only Publicly Available OpenAPI DocumentStorageDatabaseoauth226 EndpointsREST
For Agents
Provision Azure Redis Cache instances, rotate access keys, configure firewall rules and patch schedules, and link servers for geo-replication.
Use for: Provision a new Azure Redis Cache instance, Rotate the primary access key on an Azure Redis Cache, Configure a firewall rule for an Azure Redis Cache, Set the patch schedule on an Azure Redis Cache
Not supported: Does not run Redis commands, manage cluster shards from inside Redis, or query keys — use for the Microsoft.Cache control-plane lifecycle, firewall rules, patch schedules, linked servers, and access keys only.
Jentic publishes the only available OpenAPI specification for RedisManagementClient, keeping it validated and agent-ready. The API manages Azure Redis Cache resources under Microsoft.Cache, covering the full lifecycle of cache instances along with firewall rules, patch schedules, geo-replication via linked servers, access-key rotation, RDB import and export, and forced reboots. It is the control-plane surface for every aspect of running a managed Redis on Azure short of the Redis protocol itself.
Install Jentic One Beta
Connect the RedisManagementClient to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the RedisManagementClient, 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with RedisManagementClient API.
Provision an Azure Redis Cache instance with a chosen SKU and capacity
Rotate primary or secondary Redis access keys without downtime
Configure IP firewall rules that restrict access to a Redis cache
Schedule weekly patch windows for a Redis cache instance
Link a secondary Redis cache for geo-replication failover
Import or export Redis data via RDB files in Azure Blob Storage
Force a reboot of one or more Redis cache nodes for testing
Use Cases
Patterns agents use RedisManagementClient API for, with concrete tasks.
★ Provision a managed Redis cache
Application teams need a managed Redis instance for session caching, leaderboard data, or rate-limiting counters. The API provisions the cache at the chosen SKU and capacity, returns the access keys, and exposes firewall and patch-schedule endpoints so the cache can be hardened before traffic arrives.
Create an Azure Redis cache 'cache-prod-eu' at SKU Standard C2 in resource group 'cache-rg' in West Europe with non-SSL port disabled
Access key rotation
Redis access keys are long-lived secrets used by application code, so they need to be rotated on a schedule and after suspected compromise. The API exposes listKeys and regenerateKey on each cache so rotation can be staged across the application without downtime.
Regenerate the secondary access key for cache 'cache-prod-eu' and return the new value for the application config
Geo-replication via linked servers
Production workloads that need cross-region failover can pair a primary and secondary Redis Premium cache as linked servers. The API manages the linked-server resources under each cache so the geo-replication relationship can be created, inspected, and torn down through automation.
Link cache 'cache-prod-westus' to 'cache-prod-eastus' as the secondary, then verify the link state is Succeeded
Patch schedule and forced reboot for resilience testing
SRE teams test failover behaviour by setting a known patch window or by forcing a reboot of the primary node. The API exposes patchSchedules at default scope and a forceReboot endpoint that targets specific shards or roles, so resilience testing can be scripted and rerun on demand.
Set a Sunday 02:00 UTC patch window on cache 'cache-prod-eu' and force a reboot of the primary node afterwards to validate failover
Agent-driven Redis automation
An AI agent fronting an internal cache provisioning portal accepts a workload's requirements, validates the desired cache name, provisions the cache, configures firewall rules from the workload's allowlist, and stores the access key in the workload's secret store. Jentic isolates the AAD client secret so the agent only sees scoped bearer tokens.
Given a workload spec (name, region, SKU, allowed CIDRs), provision the cache, add firewall rules, return the primary access key
Key Endpoints
26 endpoints — jentic publishes the only available openapi specification for redismanagementclient, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Cache/Redis/{name}
Create or update a Redis cache
GET
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Cache/Redis/{name}
Get a specific Redis cache
POST
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Cache/Redis/{name}/listKeys
List access keys for a cache
POST
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Cache/Redis/{name}/regenerateKey
Regenerate an access key
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Cache/Redis/{cacheName}/firewallRules/{ruleName}
Create or update a firewall rule
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Cache/Redis/{name}/patchSchedules/{default}
Set the patch schedule on a cache
POST
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Cache/Redis/{name}/forceReboot
Force a reboot of the cache
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Cache/Redis/{name}/linkedServers/{linkedServerName}
Link a secondary cache for geo-replication
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Cache/Redis/{name}
Create or update a Redis cache
GET
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Cache/Redis/{name}
Get a specific Redis cache
POST
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Cache/Redis/{name}/listKeys
List access keys for a cache
POST
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Cache/Redis/{name}/regenerateKey
Regenerate an access key
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Cache/Redis/{cacheName}/firewallRules/{ruleName}
Create or update a firewall rule
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Cache/Redis/{name}/patchSchedules/{default}
Set the patch schedule on a cache
POST
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Cache/Redis/{name}/forceReboot
Force a reboot of the cache
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Cache/Redis/{name}/linkedServers/{linkedServerName}
Link a secondary cache for geo-replication
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Azure AD OAuth 2.0 client credentials are stored encrypted in the Jentic vault. Agents receive a scoped bearer token at execute time; client secrets and Redis access keys never linger in the agent's context.
Intent-based discovery
Agents search by intent (e.g., 'provision azure redis cache') and Jentic returns the matching create operation with subscriptionId, resourceGroupName, name, location, and SKU parameters resolved from the spec.
Time to first call
Direct integration with the Microsoft.Cache Redis API, including AAD setup and async polling for cache provisioning, typically takes 1-2 days. Through Jentic: under 1 hour to first successful cache creation.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using RedisManagementClient API through Jentic.
Why is there no official OpenAPI spec for RedisManagementClient?
Microsoft Azure does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call RedisManagementClient 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 Azure Redis Management API use?
The API runs through Azure Resource Manager and uses OAuth 2.0 bearer tokens issued by Azure Active Directory under the azure_auth scheme with the user_impersonation scope. Through Jentic, the AAD client secret is held in the encrypted vault and a short-lived access token is supplied at execute time so the secret never appears in the agent's context.
Can I rotate Redis access keys without downtime?
Yes. Use POST .../Redis/{name}/regenerateKey to regenerate one of the two keys while applications continue to use the other. Once the application has switched, regenerate the second key as well. The listKeys POST endpoint returns the current pair.
What are the rate limits for the Azure Redis Management API?
Azure Resource Manager applies subscription-level read and write throttles (around 12,000 reads per hour and 1,200 writes per hour per region per subscription) and returns 429 with a Retry-After header when exceeded. Cache create, update, import, and export are long-running operations and should be polled with backoff.
How do I provision an Azure Redis cache through Jentic?
Search Jentic for 'provision azure redis cache', load the schema for PUT .../Microsoft.Cache/Redis/{name}, then execute with subscriptionId, resourceGroupName, name, location, and an sku block. The pip install jentic Python SDK uses the async search, load, execute pattern.
Is the Azure Redis Management API free?
There is no per-call charge for the management API itself; you pay for the Redis cache SKU and capacity by the hour. Premium SKUs are billed higher than Basic and Standard but are required for features like linked-server geo-replication, persistence, and clustering.
GET STARTED