az network list-service-tags requires subscription level rights
See original GitHub issueDescribe the bug
Command Name
az network list-service-tags
Errors: Returns empty list if the user does not have subscription level rights. I didn’t debug which rights are required but compared two logins; one that has Service Administrator to a subscription and other that does not have any role.
To Reproduce:
az network list-service-tags --location westeurope
Expected Behavior
Listing service tags doesn’t of public Azure services does not require subscription level rights.
Environment Summary
macOS-10.15.3-x86_64-i386-64bit
Python 3.8.1
Shell: bash
azure-cli 2.0.80 *
Extensions:
azure-devops 0.17.0
Issue Analytics
- State:
- Created 4 years ago
- Comments:15 (4 by maintainers)
Top Results From Across the Web
Azure service tags overview - Virtual Network - Microsoft Learn
Tag Can use inbound or outbound? Can be regional? Can use...
ActionGroup Inbound No No
ApiManagement Inbound Yes Yes
ApplicationInsightsAvailability Inbound No No
Read more >Azure service tags REST API and subscription level rights
To use servicetags api you have to register Microsoft.Netowork resource provider at azure subscription level. In you subscription blade.
Read more >haflidif/network/azurerm - Terraform Registry
Subnet delegation gives explicit permissions to the service to create service-specific resources in the subnet using a unique identifier during ...
Read more >azure | Journey Of The Geek
At the most basic level, Private Endpoints are a way to control network access to instances of PaaS (platform-as-a-service) services you consume ...
Read more >Setting up azure firewall for analysing outgoing traffic in AKS
The following will allow dns, time and the service tags for the azure container registry. az network firewall network-rule create --firewall-name $FW_NAME ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

I’m running into a similar issue even when I have read access at the subscription level. I can’t pull back AzureCloud tags. It ends at WindowsVirtualDesktop tags.
Also, why should it be required to have read access at the subscription level to pull back publicly known IPs? You provide that info in a weekly file that requires no authentication, but you can’t provide it without having read access at the subscription level?
@allegradomel I understand this is by design, but apparently this is bad design. 😃
I fully support @matthewfrye here.