Microsoft.ApiManagement/service@2024-05-01 No registered resource provider found

[slavizh]

Bicep version
Bicep CLI version 0.30.23 (ec3612efc7)

Describe the bug
This becomes a trend and puts bad name on Bicep. APIs are published somewhere and available in Bicep but are not actually deployed on public Azure. Besides the surprise of trying to deploy something and finding out that the version does not work it makes the rule for latest API useless. It is already useless due to some resource providers publishing only Preview versions and non-preview versions are available but old with missing features but in this case the latest non-preview version is not available and the latest working version is preview which generates warning. I would consider also re-writing that rule and providing more options around if preview versions are allowed to be counted.

No registered resource provider found for location 'westeurope' and API version '2024-05-01' for type 'service'. The supported api-versions are '2014-02-14, 2015-09-15, 2016-07-07, 2016-10-10, 2017-03-01, 2018-01-01, 2018-06-01-preview, 2019-01-01, 2019-12-01-preview, 2019-12-01, 2020-06-01-preview, 2020-12-01, 2021-01-01-preview, 2021-04-01-preview, 2021-08-01, 2021-12-01-preview, 2022-04-01-preview, 2022-08-01, 2022-09-01-preview, 2023-03-01-preview, 2023-05-01-preview, 2023-09-01-preview'. The supported locations are 'centralindia, uaenorth, australiacentral, germanywestcentral, westcentralus, norwayeast, switzerlandnorth, koreasouth, westindia, koreacentral, southafricanorth, ukwest, brazilsouth, eastasia, southindia, canadacentral, canadaeast, australiasoutheast, japaneast, northcentralus, southeastasia, westus2, centralus, uksouth, australiaeast, japanwest, westus, francecentral, southcentralus, eastus2, eastus, northeurope, westeurope, westus3, jioindiacentral, jioindiawest, swedencentral, qatarcentral, polandcentral, italynorth, spaincentral, mexicocentral, israelcentral'.

To Reproduce
Steps to reproduce the behavior:

Additional context
Add any other context about the problem here.

[stephaniezyen]

Unfortunately these are issues with the RP not updating their swagger properly. We are trying our best to get resource providers to update their swagger to account for new APIs, but it is up to each RP, and not ARM Deployments/Bicep. We're looking into how best to raise this issue up, but in the meantime, support tickets are the best way to go.