az sentinel | missing examples in reference content #8421
Labels
bug
This issue requires a change to an existing behavior in the product in order to be resolved.
sentinel
Service Attention
This issue is responsible by Azure service team.
Describe the bug
Bug category:
Missing information
Request:
The Azure CLI reference guidelines specifiy at least two examples for each command. Please review the Azure CLI reference guidelines for examples and parameters and add missing content to your source code.
If a parameter accepts JSON content, provide a JSON example in the parameter long or short summary, or in a separate code block.
Issue summary:
Understanding that not all “create” commands directly generate Microsoft revenue, every “create” or “add” minimally make a revenue-producing Azure resource possible. Consequently, create commands are the most important examples to add. Of secondary importance are reference commands with complex parameters (JSON, YAML, URLs, complex Azure resource IDs, multi-valued lists, key:value pairs, conditional parameters, parameter pairs ...).
Subgroups with no examples:
The commands for these subgroups are in the second table (below). Page views (PVs) for a subgroup are "the sum of all PVs for every autogenerated reference doc in that subgroup." When there is > 1 command in a single GitHub file, the same PV amount is counted for both commands. PVs are being provided as a general idea of customer interest.
Create reference commands with no examples:
As there are 107
az sentinel
reference commands without examples, the following table is a list ofcreate
oradd
commands that have the potential to increase Microsoft revenue.Related command
az sentinel
Errors
.
Issue script & Debug output
.
Expected behavior
Azure CLI published guidelines for reference examples
Environment Summary
Version 2.68.0
Additional context
No response
The text was updated successfully, but these errors were encountered: