release note for azure cli 2.24.2

[azclibot]

No description provided.

[opbld31]

Docs Build status updates of commit 0782cc8:

⚠️ Validation status: warnings

File	Status	Preview URL	Details
docs-ref-conceptual/release-notes-azure-cli.md	⚠️Warning	View	Details
docs-ref-conceptual/includes/current-version.md	✅Succeeded	View

docs-ref-conceptual/release-notes-azure-cli.md

• Line 134, Column 160: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/service-fabric/service-fabric-cluster-security-update-certs-azure#add-a-secondary-certificate-using-azure-resource-manager' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
• Line 210, Column 1: [Warning-disallowed-heading] Heading 'H3 'Feedback'' matches the text of a disallowed Docs template heading.
• Line 3799, Column 1: [Warning-disallowed-heading] Heading 'H3 'Feedback'' matches the text of a disallowed Docs template heading.
• Line 4185, Column 1: [Warning-disallowed-heading] Heading 'H3 'Feedback'' matches the text of a disallowed Docs template heading.
• Line 5378, Column 1: [Warning-duplicate-h2s] Duplicate heading: 'H2 'July 3, 2018''. Each second level heading (H2) in an article must be unique.
• Line 5386, Column 1: [Warning-duplicate-h2s] Duplicate heading: 'H2 'July 3, 2018''. Each second level heading (H2) in an article must be unique.
• Line 5552, Column 1: [Warning-duplicate-h2s] Duplicate heading: 'H2 'June 13, 2018''. Each second level heading (H2) in an article must be unique.
• Line 5560, Column 1: [Warning-duplicate-h2s] Duplicate heading: 'H2 'June 13, 2018''. Each second level heading (H2) in an article must be unique.
• Line 5576, Column 1: [Warning-duplicate-h2s] Duplicate heading: 'H2 'June 5, 2018''. Each second level heading (H2) in an article must be unique.
• Line 5584, Column 1: [Warning-duplicate-h2s] Duplicate heading: 'H2 'June 5, 2018''. Each second level heading (H2) in an article must be unique.
• Line 6269, Column 1: [Warning-disallowed-heading] Heading 'H3 'Feedback'' matches the text of a disallowed Docs template heading.
• Line 134, Column 160: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/en-us/azure/service-fabric/service-fabric-cluster-security-update-certs-azure#add-a-secondary-certificate-using-azure-resource-manager' will be broken in isolated environments. Replace with a relative link.
• Line 3955, Column 1: [Suggestion-sensitive-language-wl] Term 'whitelisted' is sensitive and should not be used in content or code. Usage: '* Print a friendly message when the subscription is not whitelisted to use Azure Red Hat OpenShift'
• Line 6973, Column 1: [Suggestion-sensitive-language-bl] Term 'blacklist' is sensitive and should not be used in content or code. Usage: '* Removed human names from the admin name blacklist for `[vm|vmss] create`'
• Line 7691, Column 131: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/cli/azure/account#az_account_get_access_token' will be broken in isolated environments. Replace with a relative link.
• Line 7696, Column 109: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/cli/azure/use-cli-effectively#work-behind-a-proxy' 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 Docs 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 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 docs.microsoft.com contributor guides
• Post your question in the Docs support channel