Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Inventory-App-Services-enabled-for-VNet-Integration/ #3

Open
utterances-bot opened this issue Jun 30, 2020 · 3 comments
Open

Inventory-App-Services-enabled-for-VNet-Integration/ #3

utterances-bot opened this issue Jun 30, 2020 · 3 comments

Comments

@utterances-bot
Copy link

Inventory App Services enabled for VNet Integration – Stefan Ivemo – A blog about Microsoft Azure, Microsoft 365 and occasionally AWS.

I’ve been working a lot with Azure Networking the last couple of months, re-building and implementing new networking designs all over the place. When the time comes to move services to the new VNets I’ve deployed it can sometimes be a bit difficult to find all the services connected to the old VNets(not all services are listed under connected devices in the VNet). One of them are App Services and Function Apps with VNet Integration enabled. Since VNet Integration was released for App Services and Function Apps (available for Function Apps running on App Service Plans only!) a couple of months ago it’s been spreading like a disease across Azure Subscriptions with high privileged developers enabling it left to right i

https://blog.ivemo.se/Inventory-App-Services-enabled-for-VNet-Integration/

Copy link

selevik commented Jun 30, 2020

🙏

Copy link

Thank you for this, very useful.

Copy link

Hi,
Script works fine and got what I wanted, but with many subs you have to choose them one by one.
But as Resource Graph now supports this so you can also use something like this:

resources
| where type == "microsoft.web/sites"
| where properties.virtualNetworkSubnetId == '/subscriptions/zxxxxzxzxx /subnets/SNET-WEU-dsdfsdf
| project name,properties.virtualNetworkSubnetId

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

No branches or pull requests

4 participants