Skip to main content

spo tenant commandset set

Updates a ListView Command Set that is installed tenant wide.


spo tenant commandset set [options]


-i, --id <id>

The id of the ListView Command Set

-t, --newTitle [newTitle]

The updated title of the ListView Command Set

-l, --listType [listType]

The list or library type to register the ListView Command Set on. Allowed values List or Library.

-c, --clientSideComponentId [clientSideComponentId]

The Client Side Component Id (GUID) of the ListView Command Set.

-p, --clientSideComponentProperties [clientSideComponentProperties]

The Client Side Component properties of the ListView Command Set.

-w, --webTemplate [webTemplate]

Optionally add a web template (e.g. STS#3, SITEPAGEPUBLISHING#0, etc) as a filter for what kind of sites the ListView Command Set is registered on.

--location [location]

The location of the ListView Command Set. Allowed values ContextMenu, CommandBar or Both. Defaults to CommandBar.

-h, --help [help]

Output usage information. Optionally, specify which section of command's help you want to see. Allowed values are options, examples, remarks, response, full. Default is full.

--query [query]

JMESPath query string. See for more information and examples.

-o, --output [output]

Output type. json, text, csv, md. Default json.


Runs command with verbose logging.


Runs command with debug logging.


Escaping JSON in PowerShell

When using the --clientSideComponentProperties option it's possible to enter a JSON string. In PowerShell 5 to 7.2 specific escaping rules apply due to an issue. Remember that you can also use file tokens instead.


Updates the title of a ListView Command Set that's deployed tenant wide.

m365 spo tenant commandset set --id 4  --newTitle "Some customizer"

Updates the properties of a ListView Command Set.

m365 spo tenant commandset  set --id 3  --clientSideComponentProperties '{ "someProperty": "Some value" }'


The command won't return a response on success.