How to Resolve the Resource Provider Not Registered In Subscription Error

Issue

You receive the following error message:

Subscription sub_id of remote Private Link Service /subscriptions/sub_id/resourceGroups/rg_name/providers/Microsoft.Storage/storageAccounts/storage_account_name is not registered with Microsoft.Network resource provider

Environment

• All database connectors
• Connection method: Private networking

Understanding the problem

• Azure resource providers: Every Azure service is managed by a provider. You must register a provider in a subscription before deploying or using its resources.
• Microsoft.Network provider: Manages networking resources (Private Endpoints, Private Link Services, VNets, NSGs, etc.).

The error indicates you’re creating a Private Endpoint to the Storage account storage_account_name in subscription sub_id, but Microsoft.Network isn’t registered there. Even though the target is a Microsoft.Storage resource, Private Endpoint is a networking feature, so Microsoft.Network must be registered in that subscription.

Causes and solutions

The Microsoft.Network resource provider isn’t registered in the subscription hosting storage_account_name and possibly the subscription creating the Private Endpoint.

Register Microsoft.Network in the affected subscriptions, then retry the Private Endpoint creation.

Resolution

Register Microsoft.Network in the subscription that owns the target storage account (sub_id). You can register it through the Azure portal, Azure CLI, or Azure PowerShell.

Option 1: Azure Portal (recommended for ease of use)

1. Sign in to the Azure portal.
2. In the top search bar, type Subscriptions and open Subscriptions.
3. Click the subscription that owns the storage account (sub_id from the error).
4. In the left menu under Settings, select Resource providers.
5. In Filter by name…, type Microsoft.Network.
6. Check the Status column:
   • If it shows NotRegistered, select Microsoft.Network and click Register at the top.
   • The status changes to Registering, then to Registered (this can take a few minutes).
7. (Optional) Repeat the search for Microsoft.Storage to confirm it’s also registered.
8. Re-run the Private Endpoint creation.

Option 2: Azure CLI

1. Open Azure Cloud Shell (Bash) or a local terminal with Azure CLI logged in.
2. Set the subscription context:

   az account set --subscription "sub_id"
   

   Replace sub_id with the actual subscription ID from the error message.
3. Register the resource provider:

   az provider register --namespace Microsoft.Network
   

4. (Optional) Verify registration:

   az provider show --namespace Microsoft.Network --query registrationState
   

   It should show Registered.

Option 3: Azure PowerShell

1. Open Azure Cloud Shell (PowerShell) or a local PowerShell session logged in to Azure.
2. Set the subscription context:

   Set-AzContext -Subscription "sub_id"
   

   Replace sub_id with the actual subscription ID from the error message.
3. Register the resource provider:

   Register-AzResourceProvider -ProviderNamespace Microsoft.Network
   

4. (Optional) Verify registration:

   Get-AzResourceProvider -ProviderNamespace Microsoft.Network | Select-Object ProviderNamespace, RegistrationState
   

   It should show Registered.

Once the Microsoft.Network resource provider is successfully registered in the subscription of the target storage account, retry the operation that caused this error (for example, creating the Private Endpoint). It should now proceed without this specific error.