Share via

Azure Network Secuirty Group: Unable to find service tag 'ApiManagement' in inbound and outbound rules

Nishant Sharma 21 Reputation points
2022-01-24T15:49:49.71+00:00

I need to add inbound and outbound security rules to an NSG for my API Management instance, the documentation states that there are few rules to create and those rules should use the service tag "ApiManagement" for source in inbound rules for example. Unfortunately, on my side, the service tag "ApiManagement" is not available in the list of service tags, I only have Internet, Virtual Network and AzureLoadBalancer... Do I need to do something special to have those tags available? Maybe, I missed several permissions on the Subscription/Resource group?

Azure Storage Accounts
Azure Storage Accounts
Globally unique resources that provide access to data management services and serve as the parent namespace for the services.
2,817 questions
Azure Virtual Network
Azure Virtual Network
An Azure networking service that is used to provision private networks and optionally to connect to on-premises datacenters.
2,227 questions

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. SaiKishor-MSFT 17,216 Reputation points
    2022-01-25T03:05:18.46+00:00

    @Nishant Sharma Thank you for reaching out to Microsoft Q&A. The Service Tag 'ApiManagement' will be available only in the inbound direction. Please take a look at this table for more details regarding Service Tags. Are you looking at the inbound Security Group rules but cannot find the "ApiManagement" Tag? If so, please share your subscription/region and NSG details so I can further investigate. Thank you!

    Please let us know if you have any further questions and we will be glad to assist you further. Thank you!

    Remember:

    Please accept an answer if correct. Original posters help the community find answers faster by identifying the correct answer. Here is how.

    Want a reminder to come back and check responses? Here is how to subscribe to a notification.

  2. SaiKishor-MSFT 17,216 Reputation points
    2022-01-26T00:53:39.427+00:00

    @Nishant Sharma If you find the VMs of type virtual machines (classic) on the Azure portal's VM pane, then it is a classic VM and which is why all the tags are not showing. Since VMs created using the classic deployment model will follow the Modern Lifecycle Policy for retirement, it is advisable that you migrate to the Resource Model Deployment model.

    Here are steps to migrate to the VM from the Classic deployment model to the Resource Manager Deployment model. If you instead plan to create a new VM in the Resource Model Deployment model, then you must first create a Virtual Network also in the the Resource Manager Deployment model. You can follow this Powershell script to configure a VM in the Resource Manager Model or you can use the Portal to do the same here. Hope this helps.

    Please let us know if you have any further questions and we will be glad to assist you further. Thank you!

    Remember:

    Please accept an answer if correct. Original posters help the community find answers faster by identifying the correct answer. Here is how.

    Want a reminder to come back and check responses? Here is how to subscribe to a notification.

  3. kkc 6 Reputation points Microsoft Employee
    2023-01-11T18:49:11.8566667+00:00

    What's the solution to this problem? I am having the same issue. @SaiKishor-MSFT