An Azure service that provides private connectivity from a virtual network to Azure platform as a service, customer-owned, or Microsoft partner services.
Hello Anurag Choudhary
Feature registration can take up to 48 hours to complete. If it's been less than that, you may just need to wait a bit longer.
Make sure there are no other dependencies or prerequisites that haven't been met. Some features may require specific configurations or settings in your resources.
- Re-register the Resource Provider: Since you've already tried re-registering via CLI, you might want to do it again with a slightly different approach:
Register-AzProviderFeature -FeatureName AllowPrivateEndpoints -ProviderNamespace Microsoft.Network - Delete and Recreate: If it remains stuck after trying the steps above, a common solution is to delete the affected resource and recreate it. Make sure that when you recreate, all required configurations are correctly applied.
Check Registration Status Again
Azure PowerShell
az feature show --namespace Microsoft.Network --name AllowPrivateEndpoints --query "properties.state"
- If it still shows
Pending, continue with the next steps. - Retry Provider Registration Sometimes re-registering the provider helps:
Azure CLI
az provider register --namespace Microsoft.Network
If you're still having trouble, here are a few questions that might help narrow down the issue:
- How long has it been since you ran the registration command?
- Can you confirm that your Azure subscription has the appropriate permissions to finalize the feature registration?
- Have you recently made any changes to your Azure environment that could affect
Microsoft.Network?
I hope this has been helpful!
If the above is unclear or you are unsure about something, please add a comment below.