Extend non-list commands' docs with information about how to get the ID

[waldekmastykarz]

Should we consider extending docs of our non-list commands with information about how to get an ID of the particular item?

When working with non-list APIs (APIs that operate on one item like get, update or delete), one of the things people often struggle with, is how to get the ID of the item. In CLI, we strive to let people reference the item by human-readable values, but that's not always the case. While we have these gaps, do you think it would be worth the effort to extend our docs (where relevant) with information about how to retrieve the ID of the item for use in the particular non-list command? Meanwhile, we could also create items to extend these commands with options to let people reference items by values other than IDs.

If you use CLI regularly and are familiar with Microsoft 365, you'd likely find it self-explanatory to use the corresponding list command and lookup the ID of the item in question, but if you're new to CLI/M365 and just landed on a non-list command, I wonder if we're not sending you down a rabbit hole right now.