Registering a Resource Provider

1. Start Locally

Firstly, we need to launch Locally which we can do from a terminal by running:

Once Locally has started, the Locally Dashboard will open automatically:

2. Create a Resource Group

Next we can create a Resource Group to put a cache in later on:

There's two things to note here:

1. The Azure CLI supports Automatic Configuration, meaning that it can automatically be configured to work against Locally just by prefixing commands with locally run.
2. Locally intentionally uses a different set of locations to Azure as a safety precaution, so that you can be confident you're deploying against Locally rather than regular Azure. You can also configure Locally to use the Azure locations too, but you'll want to be extra sure that you're prefixing commands with locally run when you do.

3. Look at a Resource Provider

Every provider whose plugin is installed starts out registered in every Subscription. To see them all, along with their state:

The list depends on which plugins you've installed. Let's look at just the one we're interested in:

{
  "namespace": "Microsoft.Cache",
  "registrationState": "Registered",
  "resourceTypes": [
    "redis",
    "redis/accessPolicies",
    "redis/accessPolicyAssignments",
    "redis/firewallRules",
    "redis/linkedServers",
    "redis/privateEndpointConnections",
    "redisEnterprise",
    "redisEnterprise/databases",
    "redisEnterprise/databases/accessPolicyAssignments",
    "redisEnterprise/migrations"
  ]
}

4. Unregister it

Now let's unregister the provider from this Subscription:

WARNING: Unregistering is still on-going. You can monitor using 'az provider show -n Microsoft.Cache'

The Azure CLI warns that unregistering is still going on, since it can take a while in Azure. In Locally it's already done:

"NotRegistered"

With the provider unregistered, creating a cache is refused with the same error Azure returns:

ERROR: (MissingSubscriptionRegistration) The subscription is not registered to use namespace 'Microsoft.Cache'. See https://aka.ms/rps-not-found for how to register subscriptions.
Code: MissingSubscriptionRegistration
Message: The subscription is not registered to use namespace 'Microsoft.Cache'. See https://aka.ms/rps-not-found for how to register subscriptions.

This is a handy way to check that your deployment scripts register what they need, rather than relying on a Subscription where someone registered it by hand a while ago.

5. Register it again

To register the provider again, passing --wait so the command returns once it's done:

If the provider's plugin isn't installed, Locally installs it at this point, as long as your plan includes it. The provider shows as Registering until the plugin is ready, which is what --wait waits for. Here the plugin was already installed, so it's registered straight away:

"Registered"

And the same create now succeeds:

{
  "name": "sampleprovidersdocs1",
  "provisioningState": "Succeeded",
  "type": "Microsoft.Cache/redis"
}

6. Providers in use can't be unregistered

While the Subscription has a cache in it, Locally won't unregister Microsoft.Cache:

ERROR: (ResourceProviderHasResources) The resource provider 'Microsoft.Cache' cannot be unregistered because subscription '0f766306-391f-4f66-b9ee-927fb2db629c' still contains resources of that provider. Delete them first, then unregister it.
Code: ResourceProviderHasResources
Message: The resource provider 'Microsoft.Cache' cannot be unregistered because subscription '0f766306-391f-4f66-b9ee-927fb2db629c' still contains resources of that provider. Delete them first, then unregister it.

You can also register and unregister providers from the Resource Providers tab on a Subscription's page in the Locally Dashboard:

Providers marked Core are built into Locally, so they don't have an Unregister button.

7. Tidy up

Finally, we can tidy up. To remove the Resource Group and the cache within it:

This leaves Microsoft.Cache registered, which is how we found it.

Doing this with other tooling

Template deployments register the providers they need before deploying anything, so deploying an ARM Template or Bicep file can install a plugin too. The AzureRM provider for HashiCorp Terraform and OpenTofu registers the providers it needs through the same API, and its azurerm_resource_provider_registration resource registers one explicitly.

You can also install a plugin ahead of time with locally plugin install, which is what the other guides suggest before you start.

Next steps

Subscriptions, Tenants & Credentials covers how Resource Providers fit in with your Subscriptions. To provision and connect to the cache itself, see Azure Cache for Redis.

Should you encounter any issues, please take a look at the troubleshooting section.