Add a rule for API Management to use a SKU that supports AZ and multi-region deployments

[jtracey93]

Existing rule

No response

Description of the issue

The following rules are being skipped in the AVM tests for no apparent reason for this resource, can you please advise:

• Azure.APIM.AvailabilityZone
• Azure.APIM.MultiRegion
• Azure.APIM.MultiRegionGateway

Error messages

No response

Reproduction

Example AVM Workflows that have ran this for this resource can be seen here:

• https://github.com/Azure/bicep-registry-modules/actions/runs/8471591476/job/23211999871

Version of PSRule

2.9.0

Version of PSRule for Azure

v1.35.0-B0116

Additional context

No response

[BernieWhite]

@jtracey93 Multi-region and availability zones only apply to premium SKU it's not supported on any other SKU, so these rules are not run if the resource uses a non-premium SKU. From my understanding e2e tests use the parameter default SKU of Developer.

We could add a rule to suggest that any APIM deployment should use the premium SKU, but it's likely this would not be ideal in a number of customer cases, so we have not so far. Although realistically it's the only option for AZ support currently, although Standard V2 I believe will drop with this at some point.

https://learn.microsoft.com/en-gb/azure/api-management/v2-service-tiers-overview#preview-limitations

[jtracey93]

Agreed. I think the premium being the only way to get AZ support that is the WAF guidance means we should add a rule for it. It can always be suppressed.