Conversation
- Fixed parameter inconsistency between Bicep and JSON templates - Replaced separate apiManagementName, apiManagementResourceGroupName, apiManagementSubscriptionId parameters with single apiManagementResourceId parameter - Updated README.md with comprehensive API Management documentation - Added API Management to template customization section - Added API Management to private endpoints documentation - Added API Management to Private DNS Zones table - Maintains consistency with other resource parameter patterns
…w with APIM integration Co-authored-by: Vijendra123 <22127810+Vijendra123@users.noreply.github.com>
Co-authored-by: Vijendra123 <22127810+Vijendra123@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Look at the current PR, @azure-ai-foundry/foundry-samples/pull/285
We need to add make changes in this PR to move out changes made in samples/microsoft/infrastructure-setup/15-private-network-standard-agent-setup folder and create a new folder
16-priva...
Create APIM-enabled network secured agent setup variant (16-private-network-standard-agent-apim-setup-preview)
Aug 22, 2025
Owner
|
@copilot Now you need to reset the 15- folder to whats in the remote repo where this is forked from |
Vijendra123
force-pushed
the
main
branch
2 times, most recently
from
5ff7329 to
8282415
Compare
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
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 PR creates a new infrastructure setup variant that adds Azure API Management (APIM) integration to the existing network-secured standard agent deployment. The new folder
16-private-network-standard-agent-apim-setup-previewprovides an enhanced version of the standard setup with optional APIM gateway capabilities.What's New
New Infrastructure Setup Variant
samples/microsoft/infrastructure-setup/16-private-network-standard-agent-apim-setup-preview/Key Features
Technical Implementation
The infrastructure templates already contained comprehensive APIM support including:
apiManagementResourceId) for optional APIM integrationprivatelink.azure-api.net) for secure name resolutionDocumentation Updates
Preserved Original Setup
15-private-network-standard-agent-setupremains completely untouchedUse Cases
This setup is ideal for organizations that want to:
The setup maintains all the security and isolation benefits of the standard network-secured deployment while adding optional enterprise API management capabilities.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.