What changed
Microsoft's documentation describes how to configure an inbound access rule that uses an Azure service tag in a network security perimeter profile. The packet describes a service tag as a group of IP address prefixes for an Azure service. Microsoft maintains the group and updates it as addresses change. You no longer have to chase IP ranges yourself.
Early adopters have already written about it. Microsoft MVP blogger Stefano Demiliani reported that Microsoft announced public preview support for service tags as inbound access rules in NSP for third-party customers on October 6, 2026. His example is a Business Central-to-Storage scenario. That Storage scenario deserves care, as the limitations section below explains.
Microsoft's Azure Updates entry for this item (ID 579201) rendered as "0 Updates found" when the packet was captured. I couldn't confirm its text from that page. The facts below come from Microsoft Learn documentation and the NSP REST reference.
Why it matters
NSP is a logical boundary around supported PaaS resources. By default it restricts public access to resources inside the boundary, and you grant exceptions through explicit inbound and outbound access rules.
Before this preview, inbound rules for traffic from outside the perimeter relied on subscription-based rules and IP-based rules. IP-based rules mean copying prefix lists from Microsoft's downloadable service-tag JSON files. One Sentinel guide for Storage connectors says service tag ranges update over time and you should refresh regularly to keep rules current. That is a chore that is easy to forget until something breaks.
Service tags remove that chore for supported scenarios. Learn's FAQ says you no longer manage the IP addresses. CIDR rules still work, because the tags are meant to complement existing inbound rule capabilities.
Where it works, and where it doesn't
Eligibility is narrower than "any Azure service." The Learn page, last updated November 11, 2026 in the captured copy, says service-tag inbound rules can be configured for these NSP-associated resources:
- Azure Key Vault
- Azure Monitor
- Azure AI Search
- Azure Event Hubs
- Azure Service Bus
An earlier indexed version of the same page listed only Key Vault and Azure Monitor. That version said support was currently limited to Azure Key Vault and Azure Monitor. The list is clearly still growing, so check the current page before you plan around it.
Other limits to know:
- Not every tag works. Learn says not all service tags can be used as inbound rules in NSP, so choose tags carefully. The portal list shows only supported tags.
- Azure Storage is excluded. Microsoft says Storage doesn't currently support service tags as inbound rules. Some access scenarios might appear to work while others fail or behave inconsistently, so it advises against using service tags to control inbound Storage access. The one noted exception is Azure Storage used for Azure Databricks, which has its own firewall guidance.
- Sample tag names are not a guarantee. Learn's examples include PowerPlatform, AzureMonitor, AzureDatabricks, MicrosoftDiscoveryService and Storage.WestUS. Confirm that a tag appears in the portal for your resource.
The Storage restriction and the Storage.WestUS example can look contradictory. Don't read the example as endorsement. Treat the explicit Storage warning as the controlling guidance. Demiliani's Business Central-to-Storage walkthrough is also a reason to read Microsoft's current Storage caveat carefully before copying it. His post says that for now you need to create an inbound rule using the IP addresses associated with the Dynamics365BusinessCentral service tag.
How to add a service-tag rule
Prerequisites from Microsoft:
- An Azure subscription
- An existing network security perimeter and profile
- An Azure resource associated with the perimeter
- Permission to manage inbound access rules for the perimeter
Portal steps:
- In the Azure portal, search for and open Network security perimeters, then select your perimeter.
- Select Profiles, then pick the profile you want to change.
- Select Inbound access rules, then + Add.
- Set Source type to Service Tag.
- Choose a supported tag from the list.
- Fill in the remaining settings and select Add to save.
Microsoft's example rule is named Allow-PowerPlatform. It uses source type Service Tag, the PowerPlatform tag, the Allow action and defaultProfile.
Verify it
Open Inbound access rules on the profile page and confirm the new rule is listed. Then test connectivity from the Azure service in question. Review the NSP access logs to confirm the expected traffic is allowed.
Discovering tags programmatically
Microsoft's REST API reference documents a list operation for NSP-supported tags. It is a GET request on the Microsoft.Network provider, scoped by subscription ID and location, under nspServiceTags with API version 2025-01-01. It uses Azure AD OAuth2 authentication. It returns a paged result with value and, when needed, nextLink. Microsoft's sample response includes tags such as ActionGroup, AzureCloud and ApiManagement. Treat that as an illustration, not a full inventory.
Best practices from Microsoft
- Use the narrowest tag that meets your needs.
- Prefer a regional tag when one exists.
- Validate in Transition mode before moving to Enforced mode.
- Review access logs after deployment.
- Remove redundant CIDR rules only after the tag-based rule is proven.
Troubleshooting
| Symptom | What to check |
|---|---|
| Traffic is blocked | Confirm you chose the correct service tag. |
| Rule exists but the connection fails | Confirm the source IP actually belongs to that tag. |
| Tag isn't in the list | It may not be supported for NSP inbound rules. |
| Works in Transition, fails in Enforced | Read the access logs and add the missing rules. |
The security trade-off
Service tags are convenient, but they are broad. Microsoft warns that a tag can include traffic from multiple Microsoft-owned service instances. It also says tags can represent multitenant workloads that might run third-party or untrusted code, which could expose your resources to associated risks. Demiliani makes the same point, noting that tags are broad by design.
In practical terms, a tag tells the perimeter where traffic comes from at the network level. It doesn't tell the perimeter whether the caller is authorized. This is my analysis, not a Microsoft claim. You still need identity and application-level controls such as managed identities and RBAC.
If you need tighter isolation, Microsoft points to more granular controls such as specific IP ranges and subscriptions. A reasonable pattern is to use tags where broad service-level trust is acceptable and where the churn of IP prefixes is a real operational burden. Keep stricter rules for sensitive resources.
Bottom line
- Who benefits: Admins running NSP-protected Key Vault, Monitor, AI Search, Event Hubs or Service Bus who must accept traffic from Azure services whose IP ranges keep changing.
- Who should wait: Anyone planning production Storage access rules, or anyone who needs an SLA. Microsoft marks this as preview and not for production use.
- Next step: Test in a non-production perimeter, using Transition mode and the access logs to confirm behavior before you enforce anything.
References
- (In preview) Public Preview: Service tags for inbound rules in network security perimeter Azure Updates · 2026-11-17T20:52:28Z
- Azure updates | Microsoft Azure azure.microsoft.com
- Securing your Azure Storage Account: a guide to enabling Business Central-only access using Network Security Perimeter (part2) demiliani.com