Skip to content

Commit 0d68403

Browse files
authored
Merge pull request #203016 from mbender-ms/vnet-service-tags
Updates to Note on API vs JSON data
2 parents 1069053 + b17d581 commit 0d68403

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

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

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

158158
> [!NOTE]
159-
>
160-
> - It takes up to 4 weeks for new Service Tag data to propagate in the API results across all Azure regions.
159+
>
160+
> - The API data represents those tags that can be used with NSG rules in your region. Use the API data as the source of truth for available Service Tags as it may be different than the JSON downloadable file.
161+
> - It takes up to 4 weeks for new Service Tag data to propagate in the API results across all Azure regions. Because of this process, your API data results may be out of sync with the downloadable JSON file as the API data represents a subset of the tags currently in the downloadable JSON file.
161162
> - 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.
163163
164164
### Discover service tags by using downloadable JSON files
165165
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)