Skip to content

Commit 6da52d3

Browse files
Merge pull request #274408 from tfitzmac/0504tags
add ARM service tag guidance
2 parents 397fd41 + 879c3ad commit 6da52d3

File tree

2 files changed

+42
-0
lines changed

2 files changed

+42
-0
lines changed
Lines changed: 40 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,40 @@
1+
---
2+
title: Use service tag for Azure Resource Manager
3+
description: Learn how to use the service tag for Azure Resource Manager to create security rules that allow or deny traffic.
4+
ms.topic: conceptual
5+
ms.date: 05/07/2024
6+
---
7+
8+
# Understand how to use Azure Resource Manager service tag
9+
10+
By using the `AzureResourceManager` service tag, you can define network access for the Azure Resource Manager service without specifying individual IP addresses. The service tag is a group of IP address prefixes that you use to minimize the complexity of creating security rules. When you use service tags, Azure automatically updates the IP addresses as they change for the service. However, the service tag isn't a security control mechanism. The service tag is merely a list of IP addresses.
11+
12+
## When to use
13+
14+
You use service tags to define network access controls for:
15+
16+
* Network security groups (NSGs)
17+
* Azure Firewall rules
18+
* User-defined routing (UDR)
19+
20+
In addition to these scenarios, use the `AzureResourceManager` service tag to:
21+
22+
* Restrict access to linked templates referenced within an ARM template deployment.
23+
* Restrict access to a Kubernetes control plane accessed via Bicep extensibility.
24+
25+
## Security considerations
26+
27+
The Azure Resource Manager service tag helps you define network access, but it shouldn't be considered as a replacement for proper network security measures. In particular, the Azure Resource Manager service tag:
28+
29+
* Doesn't provide granular control over individual IP addresses.
30+
* Shouldn't be relied upon as the sole method for securing a network.
31+
32+
## Monitoring and automation
33+
34+
When monitoring your infrastructure, use the specific IP address prefixes that are associated with a service tag in the Azure networking stack.
35+
36+
For deployment automation and monitoring, make sure that only public IPs from the service's tagged ranges are used on customer-facing portions of the service.
37+
38+
## Next steps
39+
40+
For more information about service tags, see [Virtual network service tags](../../virtual-network/service-tags-overview.md).

articles/azure-resource-manager/management/toc.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -26,6 +26,8 @@
2626
href: tls-support.md
2727
- name: Security baseline
2828
href: /security/benchmark/azure/baselines/azure-resource-manager-security-baseline?toc=/azure/azure-resource-manager/management/toc.json
29+
- name: Service tag
30+
href: service-tags.md
2931
- name: Security controls by Azure Policy
3032
displayName: regulatory, compliance, standards, domains
3133
href: ./security-controls-policy.md

0 commit comments

Comments
 (0)