Azure ML online endpoint fails with SubscriptionNotRegistered [N/A]

Question

Azure ML online endpoint fails with SubscriptionNotRegistered [N/A]

Getamesay Zegeye 0

I am creating an Azure Machine Learning managed online endpoint in westus2.

Azure accepts the endpoint write operation, but the endpoint enters Failed

provisioning state with:

SubscriptionNotRegistered

Resource provider [N/A] isn't registered with Subscription [N/A].

The failure occurred twice:

2026-09-08T07:23:36.9028473Z Correlation ID: 3f88bf3a-64a1-4059-a8ce-0f6e533cd629
2026-09-08T08:37:34.9741912Z Correlation ID: 0d84ac12-4011-4ec0-8f86-5adc522a3fdc

Operation:

Microsoft.MachineLearningServices/workspaces/onlineEndpoints/write

Microsoft.MachineLearningServices, Microsoft.Network, Microsoft.Cdn,

Microsoft.PolicyInsights, Microsoft.Storage, Microsoft.ContainerRegistry,

Microsoft.KeyVault, Microsoft.Compute, and other relevant providers were

verified as Registered before the second failure.

The workspace is Succeeded, but the endpoint is Failed. No online deployment

was created, no container started, and no traffic was assigned.

Which resource provider or Azure ML backend dependency is represented by

[N/A], and what supported remediation is required?

0 comments

4 answers

Your answer

Answer 1

Hello - @Getamesay Zegeye

Thanks for the question and using MS Q&A forum.

Glad to know that the issue has been resolved.

Issue: When creating an Azure Machine Learning managed online endpoint in westus2.

Azure accepts the endpoint write operation, but the endpoint enters Failed

provisioning state with: SubscriptionNotRegistered

Resource provider [N/A] isn't registered with Subscription [N/A].

Resolution: After verifying the standard Azure ML providers, I found that Microsoft.Web was NotRegistered. I registered Microsoft.Web, waited for propagation, and created a new managed online endpoint named level8-bank-endpoint-r3.

The endpoint creation completed successfully in westus2 with provisioning state Succeeded. The create command returned exit code 0, and the authoritative follow-up query also returned Succeeded.

No deployment or traffic was created during this test. This strongly indicates that registration or propagation of Microsoft.Web resolved the earlier SubscriptionNotRegistered [N/A] endpoint-write failure.

Please do let us know if you have any further questions or concerns. We’ll be happy to assist you.

Answer 2

Resolved: After verifying the standard Azure ML providers, I found that Microsoft.Web was NotRegistered. I registered Microsoft.Web, waited for propagation, and created a new managed online endpoint named level8-bank-endpoint-r3.

The endpoint creation completed successfully in westus2 with provisioning state Succeeded. The create command returned exit code 0, and the authoritative follow-up query also returned Succeeded.

No deployment or traffic was created during this test. This strongly indicates that registration or propagation of Microsoft.Web resolved the earlier SubscriptionNotRegistered [N/A] endpoint-write failure.

Answer 3

Getamesay Zegeye 0

I completed the current-state verification. The endpoint level8-bank-marketing-endpoint remains in Failed provisioning state with empty traffic. The online deployment inventory returns [], confirming that no deployment object was created. All relevant resource providers report Registered, and Azure CLI authentication and the ML extension are functioning. The failure therefore occurs during the Azure ML endpoint control-plane write operation, before model deployment, image creation, container startup, or traffic assignment. The exact error remains SubscriptionNotRegistered [N/A].

0 comments

Answer 4

[N/A] is not identified in the available guidance as a specific Azure ML backend dependency name. The supported remediation in the available guidance is to treat this as a resource provider registration issue and explicitly verify or re-register providers commonly required by Azure Machine Learning online endpoint deployments.

Supported actions:

List providers that are not fully registered:

   az provider list --query "[?registrationState!='Registered'].{Provider:namespace, State:registrationState}" -o table

Re-register providers that are commonly required for Azure ML online endpoint deployments, even if they already appear registered. The guidance specifically calls out these providers as common dependencies:
- Microsoft.MachineLearningServices
- Microsoft.CDN
- Microsoft.PolicyInsights
- Microsoft.Storage
- Microsoft.ContainerRegistry
- Microsoft.KeyVault
- Microsoft.Notebooks
- Microsoft.Network if virtual networking is involved
- Microsoft.ContainerService if Kubernetes is involved
- In similar cases, Microsoft.ContainerInstance, Microsoft.Web, Microsoft.OperationalInsights, and Microsoft.ManagedIdentity were also called out as commonly required for AML deployments
Wait a few minutes after registration and retry, because provider registration is not instant.

Check endpoint and deployment state during retry:

   az ml online-endpoint show -n <endpoint-name>

For deployments that exist, use:

   az ml online-deployment show -e <endpoint-name> -n <deployment-name> --query '{name:name,state:provisioning_state}'

If a deployment object is created, retrieve logs to determine whether the failure is actually authorization, image pull, model download, or network related:
```
   az ml online-deployment get-logs -e <endpoint-name> -n <deployment-name> -l 100
```
If all relevant providers are registered and the error still shows SubscriptionNotRegistered with provider [N/A], the available guidance indicates this can be an Azure backend issue tied to the subscription. In that case, the supported remediation is to open an Azure support ticket and include the failing operation and correlation IDs so support can inspect backend logs for the exact provider name.

From the available guidance, there is no supported statement that a special Azure ML real-time inference feature flag is required for managed online endpoints.