Unclear how to start using (this) preview feature

@michaelw85 commented on Mon Sep 30 2019

It took me quite some time to find a blog where it shown to use az extension add --name azure-devops to be able to start using the az pipelines command. It would be nice if there would be some explanation that this is part of the azure-devops extension and should be installed.

---

Document Details

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

• ID: 66f0311f-8316-ea52-6171-9eb14b9f7bc7
• Version Independent ID: e79f2bc9-543d-9a14-a08c-911d037e108a
• Content: az pipelines
• Content Source: latest/docs-ref-autogen/pipelines.yml
• GitHub Login: @rloutlaw
• Microsoft Alias: routlaw

[michaelw85]

1. I always use google to get to the correct az cli documentation. In this case I was specifically searching if it was possible to create a variable group using the cli.
2. I noticed yesterday when looking up the page that the hierarchy shows the module name. This did not stand out to me before. I think I now made the connection since I used the install command for the first time. Now that I know it’s really clear but I didn’t even know that additional extensions could/should be installed. Up until this point I was just using some command which are available by default apparently.

[geverghe]

@michaelw85 - Thank you for the clarification - provides more context on the issue. Including a reference of the page

Proposed Update:

az pipelines

Manage Azure Pipelines. This command group is a part of the azure-devops extension.

Let me know if that works.

Two quick clarification questions to better understand your scenario:

1. Could you tell me how you landed on the pipelines command page? Google/some other starting point?
2. The intent of the tree hierarchy on the left was to show case the extensions and the command groups beneath it and thereby enable users to see which command belongs to what extension. Could you tell me if you missed this? Or looked at this, but the tree was not conveying the intended message?

Any feedback to improve our documentation page would be super useful.

Update: I do see the issue in the reference page for Pipelines commands https://docs.microsoft.com/en-us/cli/azure/pipelines?view=azure-cli-latest. The proposed fix should take care of it.