Skip to content

Conversation

@karpikpl
Copy link

Private endpoints were using resource group location while other resources were using location parameter.
This change makes it consistent.

@gukoff
Copy link

gukoff commented Jul 16, 2025

@karpikpl private endpoints must be in the same location as their subnet.

How about we export output virtualNetworkLocation string from network-agent-vnet.bicep and pass it to private-endpoint-and-dns.bicep?

@karpikpl
Copy link
Author

@karpikpl private endpoints must be in the same location as their subnet.

How about we export output virtualNetworkLocation string from network-agent-vnet.bicep and pass it to private-endpoint-and-dns.bicep?

sure, I've added virtualNetworkLocation

@karpikpl
Copy link
Author

@meerakurup - any chance this can get merged, it's a small improvement

@karpikpl
Copy link
Author

@meerakurup I was just helping another customer with this, using resourceGroup().location is a bug and should be fixed

Px8Studio pushed a commit to Px8Studio/foundry-samples that referenced this pull request Nov 14, 2025
* Add azure function tool support

* Add azure function tool support
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