Azure service-tag requirements and limitations
Microsoft's edit ·
Microsoft's commit message in MicrosoftDocs/azure-docs · commit 438c68e · +1 −1 lines · also on GitHub
⋯ 66 unchanged lines
6767
| Tag | Purpose | Can use inbound or outbound? | Can be regional? | Can use with Azure Firewall? |
6868
| --- | -------- |:---:|:---:|:---:|
6969
| **[ActionGroup](/azure/azure-monitor/ip-addresses)** | Action Group. | Inbound | No | Yes |
70
−| **AgentFabric** | Allow customers to author NSG policies with explicit Allow rules to AgentFabric's dataplane components | Both | Yes | Yes |
70
+| **AgentFabric** | Allow customers to author NSG policies with explicit Allow rules to and from AgentFabric's dataplane components | Both | Yes | Yes |
7171
| **ApiManagement** | Management traffic for Azure API Management-dedicated deployments. <br/><br/>**Note**: This tag represents the Azure API Management service endpoint for control plane per region. The tag enables customers to perform management operations on the APIs, Operations, Policies, NamedValues configured on the API Management service. | Inbound | Yes | Yes |
7272
| **[ApplicationInsightsAvailability](/azure/azure-monitor/app/availability-private-test)** | Application Insights Availability. | Inbound | No | Yes |
7373
| **AppConfiguration** | App Configuration. | Outbound | No | Yes |
⋯ 161 unchanged lines
Microsoft's Markdown source from MicrosoftDocs/azure-docs, © Microsoft Corporation, under CC BY 4.0. Changed lines with up to 3 unchanged lines around each; ChangeIntel kept this copy 5 Nov 05:53 UTC. The commit date is when the source changed, which can be hours or days before Learn published it.