Unable to activate "AllowPrivateEndpoints" in my subscription

I am trying to register the 'AllowPrivateEndpoints' feature of Microsoft.Network to my subscription. According to the command, 'az feature show --namespace Microsoft.Network --name AllowPrivateEndpoints --query properties.state --output tsp', it has been in state 'Pending' for about five days now. I have tried to activate it multiple times. Apparently I need Microsoft Support help to nudge it forward.

I tried using Microsoft Q&A, Allen Solomon Mejia helped. He said, in part:

'At this point, I recommend that a Microsoft moderator review the subscription's backend registration state and confirm: Whether the AllowPrivateEndpoints feature is still available and supported for this subscription. Whether the feature registration is stuck in the backend and requires manual intervention. Whether there are any subscription, region, or enrollment restrictions preventing registration. Whether the feature has been superseded or enabled by default, making explicit registration unnecessary. If requested by Microsoft, you can provide your Subscription ID privately for investigation. Avoid posting it publicly.'

I got a private message in Microsoft Q&A from Shree Hima Bindu Maganti, who sent me a link, which takes me back to the original troubleshooting page which sent me to Microsoft Q&A in the first place - in other words, back in a circle. I need help from someone with access to the back end at Microsoft.

@Matt White I hope you are doing well, I'm going to scale this thread base in your information seems a backend issue.

My registration is still in "Pending" state

Hello Matt White,

It sounds like you’re trying to feature-register Microsoft.Network/AllowPrivateEndpoints in your subscription, but the Azure CLI shows it stuck in Pending for several days and manual re-attempts don’t move it forward. You also already got confirmation from the forum that this may require a deeper backend look.

Based on the relevant docs provided, here’s what we can safely suggest publicly:

What likely matters for this kind of “Pending” feature registration

From the provided Q&A context, AllowPrivateEndpoints is essentially a subscription feature flag/rollout control that can be required for certain Private Link scenarios even if you already successfully use Private Endpoints for other services. In some cases, this registration can take several hours up to ~48 hours to propagate.

Public, self-serve checks you can do

1. Retry/check the feature state
   • Keep using your CLI command to confirm whether the state changes from Pending to the expected registered/active state.
2. Check Microsoft.Network provider/resource registration (if relevant to your scenario)
   • The docs you provided include guidance for cases where operations fail because the subscription is not registered with the Microsoft.Network resource provider.
   • Public steps:
   • Azure portal → Subscriptions → your subscription → Resource providers
   • Search for Microsoft.Network
   • If it’s Not registered, select Register
   • Then retry the operation

Can you please update us if the action plan provided was helpful?

Should there be any follow-up questions or concerns, please let us know and we shall try to address them.

If these answer your question, click "Upvote" which may be beneficial to other community members reading this thread.

Hello **Matt White,

**following up to see if you had a chance to check the above response and if it was helpful. Please let me know if you have any questions.