Fixing the "Register the Azure resource provider" error in a Marketplace deployment

A CloudRadial AutomationAI runner deployment from the Azure Marketplace can stop within its first minute or so with an error that asks you to register an Azure resource provider, most often Microsoft.App. This article explains why the deployment stops, how to register the provider, and how to redeploy. It is for the technician installing the runner, working with someone who is an Owner or Contributor of the Azure subscription.

• Recognizing the Error
• Why the Deployment Stops
• Registering the Resource Provider
• Redeploying the Runner
• Avoiding the Error on Future Installs

Recognizing the Error

The deployment fails with the code DeploymentScriptError. The failing step is the crrun-preflight deployment script, which checks the subscription before anything else is created. The error message begins like this:

The provided script failed with the following error: System.Management.Automation.RuntimeException: Register the Azure resource provider(s) Microsoft.App on subscription <subscription-id>, then click Redeploy on this failed deployment.

The rest of the message repeats the fix, includes a link to the subscription's resource providers page, and gives the Azure CLI command to run. To see the full message, open the failed deployment in the Azure portal and select the error details.

An older form of the same problem can appear as a function app error instead: Unable to integrate function app with subnet, followed by Please check if 'Microsoft.App' is registered as a resource provider. The cause and the fix are the same.

Why the Deployment Stops

An Azure subscription only allows resource types whose resource provider is registered. Registration is a one-time, subscription-wide switch, and new or lightly used subscriptions often do not have every provider turned on yet. Nothing is misconfigured; the subscription simply has not enabled that service.

The runner's Flex Consumption function apps connect to the runner's virtual network through the Microsoft.App provider. The runner template never creates a Microsoft.App resource directly, so Azure does not register it automatically the way it does for the providers a template declares. Without it, every function app in the deployment fails.

Microsoft.App is the only provider you need to register yourself. The other resource providers the runner uses, such as Microsoft.Web, Microsoft.Network, Microsoft.Storage, and Microsoft.KeyVault, are resources the template creates directly, so Azure registers them automatically during deployment.

The deployment cannot register the provider for you. Registering a provider is a subscription-level action, and a Marketplace deployment runs inside a single resource group with only a resource-group role. The preflight check attempts the registration and, when it is not allowed, stops the deployment with the fix in the message.

Stopping early is deliberate. Left to run, the deployment would retry internally for well over an hour and then fail anyway, with the real cause buried in an error about subnet integration.

Registering the Resource Provider

Registration must be done by an Owner or Contributor of the subscription. It takes under a minute and only needs to be done once per subscription. Register every provider named in the error message. With the current Marketplace offer, that is Microsoft.App.

In the Azure Portal

1. Open the link from the error message, or search for Subscriptions, select the subscription named in the error, then select Settings > Resource providers in the left menu
2. Type the provider name (for example, Microsoft.App) in the Filter by name box and select its row
3. Select Register in the toolbar at the top of the list
4. Select Refresh until the provider's status reads Registered. It may show Registering for a short time first.

With the Azure CLI

Sign in to the subscription named in the error, then run one command per provider. The --wait flag returns only when registration is complete.

az account set --subscription <subscription-id>
az provider register --namespace Microsoft.App --wait
az provider show --namespace Microsoft.App --query registrationState --output tsv

The last command should print Registered.

Redeploying the Runner

Once every provider named in the error shows Registered, run the deployment again. The deployment stopped before it created the runner apps, so you can redeploy into the same resource group.

1. In the Azure portal, open the failed deployment. You can find it under the resource group's Deployments page, or from the notification for the failed deployment.
2. Select Redeploy
3. Check that the subscription, resource group, and region are the same as before
4. Re-enter the runner secret, the supervisor secret, and any AI provider API key. Azure does not keep secret values from a previous deployment, so these fields are blank on a redeploy.
5. Review and create

Redeploy runs the preflight check again. If a provider still reads Registering, the deployment fails the same way; wait until it reads Registered and redeploy again.

In rare cases, a later step can fail with MissingSubscriptionRegistration and name a different provider, which means Azure could not register it automatically. Register the named provider the same way, then redeploy.

If you no longer have the runner secret or the supervisor secret, neither can be retrieved, but you can issue a new one. In AutomationAI, open the runner from Runners, select Manage secrets, and select Regenerate next to the secret you need. Paste the new value into the redeploy. You can also start a fresh deployment from the Marketplace offer instead of using Redeploy; choose the same resource group. See Deploying a runner from the Azure Marketplace.

When the deployment succeeds, return to Runners in AutomationAI and confirm the runner reports in. If it does not, see Verifying and troubleshooting runner connectivity.

Avoiding the Error on Future Installs

Provider registration is per subscription. Once Microsoft.App is registered, later runner installs into the same subscription do not hit this error. When you install a runner into a new subscription, register Microsoft.App first.

The deploy wizard also checks for you. If Microsoft.App is not registered in the selected subscription, or its state cannot be read, the Runner identity tab shows a warning with the same registration steps. Selecting the warning opens the subscription's resource providers page in a new tab. Register the provider, then continue through the wizard. See Runner prerequisites and Azure requirements for the full list of subscription requirements.

If you are still having trouble, we're here to help! Submit a ticket here for assistance, and don't forget to check our status page to ensure there are no outages in your area.