Fix Microsoft managed loadbalancer in other tenant issue #47
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When trying to visualize a resource group with a resource which is dependent on Microsoft managed services like a load balancer for an Azure Firewall, Network Watcher will include them in the topology. Get-AzResource will then try to get the resource outside of this tenant which causes the process to abort because of authentication issues.
The Microsoft managed load balancers start with the name gsa-