APIM built-in policy: Update allowed values for SKUs in VNETEnabled_A… #1510
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
kledsonhugo
requested review from
robga,
rogergzou,
hanheuljo,
cemheren,
gokmen-msft and
calecarter
as code owners
VitaliyKurokhtin
approved these changes
Sep 20, 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 pull request updates the
VNETEnabled_Audit.jsonpolicy definition for API Management SKUs to include support for new SKU variants. The main change is the addition ofStandardV2andPremiumV2to both the allowed values and the default values, ensuring the policy can be applied to these newer SKUs.Policy SKU support updates:
StandardV2andPremiumV2to the list of allowed API Management SKUs in theVNETEnabled_Audit.jsonpolicy definition.StandardV2andPremiumV2, alongsidePremium.