Skip to content

Fix Microsoft managed loadbalancer in other tenant issue#47

Open
theneedyguy wants to merge 1 commit intoPrateekKumarSingh:masterfrom
theneedyguy:master
Open

Fix Microsoft managed loadbalancer in other tenant issue#47
theneedyguy wants to merge 1 commit intoPrateekKumarSingh:masterfrom
theneedyguy:master

Conversation

@theneedyguy
Copy link
Copy Markdown

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-

@claw0ry
Copy link
Copy Markdown
Contributor

claw0ry commented May 31, 2021

When a Azure Public IP is deployed for Bastion it will also have an association with a Microsoft managed loadbalancer, but it is then called "DeploymentLB".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants