Redis Management Is Missing from Azure Portal Interface after I moved Resource Groups

Hi Geoff Hawes,
Thankyou for reaching microsoft Q&A!
Thank you for contacting Microsoft Azure Support regarding the missing Azure Cache for Redis interface after moving resource groups.

Based on your description, the Redis instance is still active, billing continues, and your application is connecting successfully. This indicates the service itself is healthy. In most cases, this behavior occurs due to portal scope or permission changes after a resource group move, which can make the resource appear missing in the Azure portal even though it is still running.

First, verify the portal scope. The message “No Azure Managed Redis clusters to display” usually appears when the portal is filtered to a different Directory (tenant) or Subscription than where the resource currently exists. In the Azure portal, switch to the correct tenant and subscription associated with your billing account. Then open the Azure Managed Redis blade and reset any active filters. You can also use the portal search bar to locate the Redis instance by its resource name, hostname (for example mycache.redis.cache.windows.net), or the resource ID used in your application configuration.

Next, confirm the resource location. Navigate to All Resources in the portal and filter by resource type Microsoft.Cache/redis or Microsoft.Cache/RedisEnterprise to identify the current Resource Group and Subscription. You can also verify this using Azure CLI by running az account list -o table to confirm the active subscription, followed by az redis list --subscription <subscription-id> or az resource list --resource-type Microsoft.Cache/redis --output table.

Another common cause is RBAC permissions after the move. When a resource group is moved across subscriptions or scopes, existing permissions are not always inherited. The resource may continue operating but becomes invisible in the portal if your account does not have access in the new scope. In this case, a Subscription or Resource Group Owner will need to reassign your account the appropriate role such as Reader or Contributor.

If the resource is confirmed through CLI or billing but still does not appear in the portal even with correct scope and permissions, please capture the Resource ID from CLI or billing details and create a support request under Help + Support → New support request → Technical → Redis Cache → Management visibility so the control-plane metadata can be validated and re-synchronized.

Additional reference: https://learn.microsoft.com/en-us/answers/questions/5654589/azure-subscription-is-missing-invisible-in-portal

Your Redis cache remains operational and continues serving application traffic during this process.

Please let us know the results of the portal search or CLI verification so we can assist you further.