Share via

Not able to create NSP

NAVEEN Mittal 130 Reputation points Microsoft External Staff
2026-01-14T07:40:33.5533333+00:00

when i am creating the NSP for this RG:

synapseworkspace-managedrg-efbecbe1-6029-41ab-8633-5eab0416f854 i am getting the attach error, nothing is shown on any tab, could you please suggest us

RG: Synapseworkspace-managedrg-efbecbe1-6029-41ab-8633-5eab0416f854
Profile name: swatsynapse

Azure Private Link
Azure Private Link
An Azure service that provides private connectivity from a virtual network to Azure platform as a service, customer-owned, or Microsoft partner services.
0 comments
Answer accepted by question author
  1. Venkatesan S 3,800 Reputation points Microsoft External Staff Moderator
    2026-01-14T09:09:11.7433333+00:00

    Hi NAVEEN Mittal,

    As discussed, you don't have permission to access the resource.

    Use Azure portal, CLI, or ARM templates; requires Owner or Contributor role on the subscription/resource group, with Microsoft.Network/networkSecurityPerimeters/write permission.

    Reference:

    https://learn.microsoft.com/en-us/azure/role-based-access-control/custom-roles

    Please do not forget to 210246-screenshot-2021-12-10-121802.pngand “up-vote” wherever the information provided helps you, this can be beneficial to other community members.

    0 comments

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Q&A Assist
    2026-01-14T07:40:46.6833333+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    When encountering an error while creating a Network Security Profile (NSP) for your resource group, there are several common troubleshooting steps you can take:

    1. Check Permissions: Ensure that you have the necessary permissions for the resource group and the Azure Synapse workspace. You may need roles such as Owner or Contributor on the resource group.
    2. Validate Resource Group: Confirm that the resource group synapseworkspace-managedrg-efbecbe1-6029-41ab-8633-5eab0416f854 exists and is in a valid state.
    3. Review Networking Configuration: Ensure that the networking settings for the Azure Synapse workspace are correctly configured. This includes checking if public network access is enabled and if any IP access rules are properly set.
    4. Check for Existing NSPs: If there are existing NSPs associated with the resource group, it might cause conflicts. Verify if any NSPs already exist and their configurations.
    5. Look for Error Messages: If there are no visible error messages, check the Azure portal notifications or logs for any hidden errors that might provide more context on the issue.

    If these steps do not resolve the issue, consider reaching out to Azure support for further assistance, as they can provide more detailed insights based on your specific setup.

    References:

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.