Unable to update API version for Microsoft.Cache/redisEnterprise resource type.

Hello John Lee

Thank you for posting your query on Microsoft Q&A platform.

You can’t force an existing Redis Enterprise resource to use a newer apiVersion. In Azure Resource Manager (ARM), apiVersion is the request contract used by the client (ARM/CLI/Portal) to talk to the resource provider (RP). It is not a property that is persisted on the resource, so changing it in an exported template or a CLI command does not upgrade the resource’s API surface. The RP (platform) decides which version it exposes for a given resource type and region.

Why your deployments “succeed” but nothing changes:

• When you redeploy with a different apiVersion (e.g., 2025-07-01), ARM validates the request against that schema.
• The resource itself does not store apiVersion; therefore, after deployment, the RP may still serve the resource via the currently available surface (e.g., 2025-05-01-preview).
• This is expected behavior across Azure—not specific to Redis.

Reference: https://learn.microsoft.com/en-us/azure/azure-resource-manager/templates/syntax#api-version

1. Use the newer apiVersion in your IaC for new or supported deployments (where the RP accepts it in your region).
2. Wait for the RP rollout on existing resources. Once Microsoft enables 2025-07-01 for Redis Enterprise in your region/tenant, the resource will be served via that version automatically and no manual “upgrade” step is required or supported.
3. Optionally create a new instance (if the region supports the newer version) and migrate workloads if you must adopt features only available in 2025-07-01 before the RP updates existing resources.

Note: You can refer below link for azure updates such as service announcements & rollouts

https://azure.microsoft.com/en-us/updates

Why “export → modify → redeploy” didn’t persist:

• Portal Export → Deploy and ARM/Bicep/CLI redeploy both set the request schema for the operation, not a property on the resource.
• Because the RP controls the active API surface, the resource continues to report the RP’s current version until the platform is updated.
• No customer‑side operation can force the RP to serve a newer version for an existing instance.

Kindly let us know if the solution provided worked for you.

If you need any further assistance, please feel free to reach out.

Thanks,

Suchitra.

I’ve seen this before with Redis Enterprise, and the reason you can’t “upgrade” the API version is simple: you cannot force-change the API version on an existing managed Redis resource.

Azure ignores the version in your template and keeps using whatever version the service currently exposes for that resource type.

For Redis Enterprise, the API version is controlled by the platform, not by your ARM template.

Right now there is no action you can take from your side.

Microsoft has not yet rolled out the 2025-07-01 API version for existing Redis Enterprise resources, so your deployment keeps falling back to 2025-05-01-preview.

The only two options that Microsoft supports today are:

Wait for Microsoft to update the underlying resource provider. Once they roll the new API version globally, your resource will automatically start reporting it.

Create a brand-new Redis Enterprise instance using the new API version (if the region supports it). Only new deployments can pick up a newer API version.

Exporting the ARM template, changing the JSON, and redeploying does nothing because the API version is not client-controlled.

So, you’re not doing anything wrong. You can’t manually upgrade the API version on an existing Redis Enterprise instance, and the API version will only change when Microsoft updates the service itself.