Add Warning about failures due to minAPIVersion

[tehnoonr]

A common cause for customer's opening support cases is if they set minAPIVersion property of API Management to a very recent version, newer than what we tell az mon to use to connect to us when creating a diagnostic settings object. This results in a failure and the error message is not very descriptive. Az Mon team has indicated they can't change the error message reported back to users, hence the doc update is being submitted.

[prmerger-automator[bot]]

@tehnoonr : Thanks for your contribution! The author(s) have been notified to review your proposed change.

[jborsecnik]

@dlepow,

Can you review the proposed changes? Note: The "en-us" needs to be removed from the URL. Also, should there be a "a" or a "the" before "diagnostic setting object"?

IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged" @MicrosoftDocs/public-repo-pr-review-team

[opbld31]

Learn Build status updates of commit ece98cf:

:warning: Validation status: warnings

File	Status	Preview URL	Details
articles/api-management/api-management-howto-use-azure-monitor.md	:warning:Warning		Details

articles/api-management/api-management-howto-use-azure-monitor.md

• Line 142, Column 67: [Warning: hard-coded-locale - See documentation] Link 'https://learn.microsoft.com/en-us/dotnet/api/microsoft.azure.management.apimanagement.models.apiversionconstraint.minapiversion' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
• Line 142, Column 67: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://learn.microsoft.com/en-us/dotnet/api/microsoft.azure.management.apimanagement.models.apiversionconstraint.minapiversion' will be broken in isolated environments. Replace with a relative link.

For more details, please refer to the build report.

If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Learn Build.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

[prmerger-automator[bot]]

@tehnoonr : Thanks for your contribution! The author(s) have been notified to review your proposed change.

[learn-build-service-prod[bot]]

Learn Build status updates of commit 02b6fe0:

:x: Validation status: errors

Please follow instructions here which may help to resolve issue.

File	Status	Preview URL	Details
	:x:Error		Details

• [Error: CannotMergeCommit] Cannot merge commit 02b6fe058afad1eb36f234a3c18a5d60dab34a23 in branch patch-10 of repository https://github.com/tehnoonr/azure-docs into branch main (commit 0c713ea6666b19df1dd9ba2b614c96af42f377d7). Please follow this documentation: https://help.github.com/articles/resolving-a-merge-conflict-using-the-command-line/ to use git.exe to resolve you content conflicts locally and then push to remote.

For more details, please refer to the build report.

If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Learn Build.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

[prmerger-automator[bot]]

@tehnoonr : Thanks for your contribution! The author(s) have been notified to review your proposed change.

[learn-build-service-prod[bot]]

Learn Build status updates of commit 9e15e3c:

:white_check_mark: Validation status: passed

File	Status	Preview URL	Details
articles/api-management/api-management-howto-use-azure-monitor.md	:white_check_mark:Succeeded

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

[ShannonLeavitt]

I've committed the editorial change and resolved a merge conflict. @dlepow - If this PR is ready for merge, could you sign off?

[dlepow]

#sign-off

[prmerger-automator[bot]]

@tehnoonr : Thanks for your contribution! The author(s) have been notified to review your proposed change.

[prmerger-automator[bot]]

@tehnoonr : Thanks for your contribution! The author(s) have been notified to review your proposed change.

[learn-build-service-prod[bot]]

Learn Build status updates of commit 99bdebb:

:x: Validation status: errors

Please follow instructions here which may help to resolve issue.

File	Status	Preview URL	Details
	:x:Error		Details

• [Error: GitBranchDeletedOrForcePushed]

Cannot sync git repo to specified commit because ref +refs/pull/101829/merge has been deleted or has been force pushed.
 If this is pull request, please ensure it is mergeable (no merge conflict) and open (not closed).

For more details, please refer to the build report.

If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Learn Build.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel