APIM minimum API version breaking change document does not mention Azure Portal behavior

[yichungyu]

If customers followed this documentation to enable minimum API version enforcement via Azure Portal, they will see that the option to re-disable the configuration will be greyed out. I am able to reproduce this in my lab APIM instance, and I've seen similar discussions on the Azure Q&A site: https://learn.microsoft.com/en-us/answers/questions/1663620/cannot-set-the-minimum-api-version-for-api-managem.

I believe this is by-design behavior, but it should be mentioned in the breaking changes documentation. We should remind the customers that once the configuration is enabled, they will not be able to disable/modify it via Azure Portal, and they would have to disable/modify it programmatically. Today, I had a support case where the customer did not anticipate the consequences of updating the minimum API version configuration without updating their code, and it resulted in many errors during their pipeline runs.

Document Details

⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

• ID: c5dad566-d91f-f7cf-3e0f-c6c0413c2ee0
• Version Independent ID: 01e5a466-5dbb-1afb-84d5-f2683aa9c074
• Content: Azure API Management - API version retirements (June 2024)
• Content Source: articles/api-management/breaking-changes/api-version-retirement-sep-2023.md
• Service: api-management
• GitHub Login: @dlepow
• Microsoft Alias: danlep

[TPavanBalaji]

@yichungyu
Thanks for your feedback! We will investigate and update as appropriate.

[dlepow]

@yichungyu - Thanks for pointing out this behavior. I've started a doc update to clarify this behavior and will confirm the details with the product team before publishing. According to our usual process, I'll now proceed to close this issue. thanks again.
#please-close