Currently we have some commands that are prefixed with the API they use, eg graph teams add or azmgmt flow list. The graph or azmgmt part of the command name indicates the API that we're using in the command to communicate with Office 365 and is a technicality irrelevant to the user. We should remove the API part from the command name so that it begins with the service, eg. teams add, flow list or spo app list. Simplifying command names will make it easier for users to work with the CLI and don't have to understand how they work internally. Additionally, it will isolate us from breaking changes in case an API that was originally available only through one API, has been released in another, which is regularly the case with MS Graph.
This is a breaking change that will be included in v2.
Currently we have some commands that are prefixed with the API they use, eg
graph teams addorazmgmt flow list. Thegraphorazmgmtpart of the command name indicates the API that we're using in the command to communicate with Office 365 and is a technicality irrelevant to the user. We should remove the API part from the command name so that it begins with the service, eg.teams add,flow listorspo app list. Simplifying command names will make it easier for users to work with the CLI and don't have to understand how they work internally. Additionally, it will isolate us from breaking changes in case an API that was originally available only through one API, has been released in another, which is regularly the case with MS Graph.This is a breaking change that will be included in v2.