Skip to content

Commit cea4bbb

Browse files
committed
Updates to Note on API vs JSON data
1 parent e626e5d commit cea4bbb

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

articles/virtual-network/service-tags-overview.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -156,10 +156,12 @@ $storage.Properties.AddressPrefixes
156156
```
157157

158158
> [!NOTE]
159-
>
159+
>
160+
> - The API data represents those tags that can be used with NSG rules in your region. Use the data as the source of truth for available service tags.
161+
> - Because of the process used to propagate the service tags to all Azure regions, your API data results may be out of sync with the downloadable JSON file as the API data is a as represents a subset of the tags currently in the downloadable JSON file.
160162
> - It takes up to 4 weeks for new Service Tag data to propagate in the API results across all Azure regions.
161163
> - You must be authenticated and have a role with read permissions for your current subscription.
162-
> - The API data represents those tags that can be used with NSG rules, which represents a subset of the tags currently in the downloadable JSON file.
164+
163165

164166
### Discover service tags by using downloadable JSON files
165167
You can download JSON files that contain the current list of service tags together with IP address range details. These lists are updated and published weekly. Locations for each cloud are:

0 commit comments

Comments
 (0)