Cannot associate a Network Security Perimeter in Azure Batch Account

Question

Cannot associate a Network Security Perimeter in Azure Batch Account

Auon Haidar Kazmi 0 Microsoft Employee

I was using this doc to associate a Network Security Perimeter to the Azure Batch account for access scenarios mentioned in the same doc: https://learn.microsoft.com/en-us/azure/batch/network-security-perimeter

I get this error: Failed to associate resource. This feature is not yet available for given subscription.

My batch account and NSP both are in WUS3 and I am trying to do in Corp tenant.

How to associate NSP?

0 comments

1 answer

Your answer

Answer 1

The error is not caused by both resources being in West US 3 or by using a corporate tenant. Batch–NSP association remains a preview; “not yet available for given subscription” means the subscription has not been enabled for that preview.

First verify that the Batch account uses a user-assigned managed identity and only simplified node communication pools; optionally set public network access to SecuredByPerimeter. In the subscription’s Preview features page, or with az feature list, inspect the relevant Microsoft.Batch and Microsoft.Network entries. Register the NSP feature only if it is exposed, wait for Registered, then re-register the related provider. Do not guess a feature name. Create the NSP profile and association in Learning mode using the Batch ARM ID and profile ID.

If no Batch NSP feature appears or registration remains Pending, no documented self-service bypass exists. Open Azure Support to request preview enablement, providing subscription and correlation IDs privately.