[METADATA UPDATE] Global metadata changes

[opbld17]

This Pull Request was generated automatically as part of a global effort to improve metadata quality. Please review and merge this Pull Request within 5 days. If you have any questions or concerns about these metadata updates, please contact [email protected]. If you are not the correct contact for this content and repository, please notify [email protected].

Fixing#559143 Remove ms.technology value azure-cli

If this Pull Request is not merged within 14 days, it will be automatically merged by our system to ensure the timeliness of the metadata update.Please notify [email protected] if you would like Pull Requests for metadata updates to merge automatically in future.

After you accept changes of metadata used in reports and they're merged, standard dashboards and reports will reflect new values, so you'll need to use new filter values.If you have any custom dashboards or Kusto queries, you might need to update those also.

Why we make metadata updates
Metadata updates are a normal part of business.For example, we update our metadata to reflect a new product name when a product is rebranded.Metadata updates require content to be updated because some metadata values(slugs) are included in the content(YAML header).
For metadata used internally, these updates make reports cleaner, easier to use, more consistent, and more reflective of current business.For metadata exposed to Learn Platform users, these updates ensure our users are exposed to up-to-date information consistent with their overall Microsoft experience.

Frequently Asked Questions
Why does this Pull Request appear to be made by the Repository Owner? We open Pull Requests two different ways.For Git Repos with a permissioned Service Account, we open the request from our org's Service Account.For Git Repos that we either do not have Service Account permission for or the repo is in Azure Dev Ops(ADO) we are able to open the Pull Requests in an automated way, but only with the PR creator as the Repo owner.

[opbld31]

Learn Build status updates of commit 1d6bf0c:

⚠️ Validation status: warnings

File	Status	Preview URL	Details
docs-ref-conceptual/azure-cli-extensions-list.md	⚠️Warning	View	Details

docs-ref-conceptual/azure-cli-extensions-list.md

• Line 39, Column 2: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/azure/azure-arc/data/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
• Line 39, Column 113: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/azure/azure-arc/data/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
• Line 39, Column 2: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/azure/azure-arc/data/' will be broken in isolated environments. Replace with a relative link.
• Line 39, Column 113: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/azure/azure-arc/data/' will be broken in isolated environments. Replace with a relative link.
• Line 44, Column 2: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/python/api/overview/azure/ml/?view=azure-ml-py' will be broken in isolated environments. Replace with a relative link.
• Line 44, Column 2: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: https://docs.microsoft.com/python/api/overview/azure/ml/?view=azure-ml-py
• Line 44, Column 167: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/python/api/overview/azure/ml/?view=azure-ml-py/HISTORY.rst' will be broken in isolated environments. Replace with a relative link.
• Line 44, Column 167: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL. Otherwise, remove the view parameter. URL: https://docs.microsoft.com/python/api/overview/azure/ml/?view=azure-ml-py/HISTORY.rst

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

[RetYn]

#sign-off

[dbradish-microsoft]

This PR is being closed because it is updating an autogenerated article and will be overwritten. Please see PR Azure/azure-cli-extensions#5499 for the replacement.