Unable to create Managed Redis instance

Question

We followed the quickstart to create a Managed Redis instance, selecting the Managed Redis -> Balanced "Cache SKU" and then the "B0 (500 MB)" cache size.

The resulting deployment gives an error:

The value of the parameter 'sku.name' is invalid. CorrelationID=6fff9d50-14d1-44c8-a58c-11c25a65fd53 RequestID=4673e585-6294-47e2-b486-71af7c1de9c8 Timestamp=1/28/2025 9:14:18 AM (UTC)

and when looking into the template, this is probably what it is referring to (the only occurrence of "sku"):

...
{
            "type": "Microsoft.Cache/redisEnterprise",
            "apiVersion": "2024-09-01-preview",
            "name": "xxxxxx-xxxxx-redis-stage",
            "location": "northeurope",
            "dependsOn": [
                "Microsoft.Resources/deployments/xxxxxx-aks-vnet-stage_03fc824a-d789-4f12-b756-31341f53c016"
            ],
            "tags": {},
            "sku": {
                "name": "Balanced_B0"
            },
...

Looking into the API documentation for Microsoft.Cache/redisEnterprise, the Balanced_B0 SKU is not available there. But again, this is what the documentation says to do, the documented flow for creating a Managed Redis instance; we did not do anything except select available values in the dropdowns.

What's going wrong here? Why does this not work?

Answer 1

Hi @Jesper Lindholm

Thanks for the Question and using Microsoft Q&A

I apologize for the confusion you've encountered while attempting to create a Managed Redis instance.

Upon reviewing your situation, it seems the issue is related to the regional availability of the Managed Redis service. Currently, Managed Redis is not available in the North Europe region, which is why you encountered the error when trying to deploy there. We appreciate you pointing out the availability documentation issue.

You are correct that there is some ambiguity in the regional availability links. To clarify, Managed Redis and Cache for Redis are distinct services, and only Cache for Redis is fully supported in North Europe at this time.

where we currently support Managed Redis in regions like West Europe. This should be a more reliable resource moving forward.

To resolve your issue, you’ve already done the right thing by switching to West Europe, where Managed Redis is available, and your deployment should proceed successfully.We value your feedback regarding the deployment experience and regional selection. I will share this with the team as we work to enhance the service and improve the user experience.

Hope this helps. Do let us know if you any further queries. If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.

Answer 2

The problem was trying to deploy in North Europe. According to the table found in https://learn.microsoft.com/en-us/azure/azure-cache-for-redis/migrate/migrate-overview , the migration page, Managed Redis is not yet available there. Deploying to West Europe was successful.

The link under "Availability by region" in "Managed Redis Overview" links to https://azure.microsoft.com/en-gb/explore/global-infrastructure/products-by-region/?products=redis-cache&regions=all which makes no distinction between Cache for Redis and Managed Redis, and so shows that everything is fully available in both West and North Europe. Dare I suggest that for anyone who actually wants to know the regional availability of Managed Redis, the link being offered is not even remotely useful?

Additionally, the interactive Create process should of course warn you if you choose a region where Managed Redis is not even available - or better yet, disable those regions from being selected. This is basic input validation.

Managed Redis is either completely separate from or a variant of Cache for Redis depending on where you look, so all of this is very confusing and has been a time sink for us. I hope Microsoft is working hard to get all this sorted.