APIM Classic Tiers Only - Add Support for v2 Tiers (Basic v2 / Standard v2 / Premium v2)

Description of the new feature / enhancement

The New-WinGetSource cmdlet and its underlying ARM templates only deploy classic APIM tiers (Developer, Basic, Standard) via the ImplementationPerformance parameter. The newer v2 tiers (Basic v2, Standard v2, Premium v2) — which are generally available and recommended for new deployments — are not supported.

This means private endpoint and VNet integration scenarios are impossible when APIM is deployed as part of the WinGet REST source, because:

• Classic Developer / Basic / Standard do not support outbound VNet integration
• Classic Developer supports inbound private endpoints (for testing only), but Classic Basic and Standard do not
• Only Standard v2+ supports both inbound private endpoints and outbound VNet integration

Proposed technical implementation details

1. Deploy a WinGet REST source with private endpoints:

   New-WinGetSource -Name "corpwinget" -ResourceGroup "rg-winget" `
       -ImplementationPerformance "Basic" `
       -Region "westeurope"
   

2. Note the APIM instance is deployed as Basic (classic).

Start with the New-WinGetSource cmdlet and its underlying ARM templates, then trace how the ImplementationPerformance parameter selects the APIM tier. Add support for Basic v2, Standard v2, and Premium v2, and verify that deployments can support the stated private endpoint and VNet integration scenarios.