Hi AJITH KUMAR RAI,
Thanks for reaching out in Microsoft Q&A forum,
It looks like you’re having an issue with the visibility of service tags in relation to your NSP Profile inbound rule and are specifically only seeing the AzureDatabricksServerless option.
Here’s what you need to know: The behavior you’re experiencing is expected! The only Service Tag available for Azure Databricks in NSG inbound rules is indeed the AzureDatabricksServerless tag, meaning you won't see any additional options because they’re simply not supported for this specific service at the moment.
Steps:
- Service Tags Overview: Understand that Azure manages the available service tags, and they vary based on the service and context. This means, for Azure Databricks, you won’t be able to add more service tags for NSG inbound rules – it’s by design.
- Alternatives:
- If you need to manage IP-based rules, consider using the Service Tags JSON, which is updated weekly. You can find more information about this here.
- You might want to explore using Azure Firewall, which can support a more extensive list of service tags.
- Consider using Private Endpoints where applicable for accessing services directly within your virtual network.
CLI / PowerShell Options:
While you can view the Service Tags available in your environment using PowerShell commands like Get-AzNetworkServiceTags or az network list-service-tags, any tags not showing up in the Azure portal simply aren’t supported for use.
If you’re looking for specific CLI scripts related to the available Service Tags, you might check out the relevant documentation linked below.
Documentation:
Hope this clears things up for you! If you have any more questions or need further clarification, feel free to ask!
Please do not forget to
and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.