Add App Gateway Private Endpoint to APIM infrastructure #99
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
simonkurtz-MSFT
added
enhancement
simonkurtz-MSFT
added a commit
that referenced
this pull request
Dec 5, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is a significant PR as it finally adds initial App Gateway support. This one is for private endpoint connectivity to an APIM Standard V2 instance as that has been sought after by many. This is using VNET integration. Eventually, there may be one for VNET injection.
This is functional for creating and cleaning up the App Gateway infrastructure. It has also been verified with one sample, general. It has not yet been tested with other samples.
To-Do:
Closes #95