We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
spo tenant applicationcustomizer remove
Remove an application customizer that is installed tenant wide.
-t, --title [title]
title
id
clientSideComponentId
-i, --id [id]
-c, --clientSideComponentId [clientSideComponentId]
Removes an application customizer by title.
m365 spo tenant applicationcustomizer remove --title "Some customizer"
Removes an application customizer by id.
m365 spo tenant applicationcustomizer remove --id 3
Removes an application customizer by clientSideComponentId.
m365 spo tenant applicationcustomizer remove --clientSideComponentId 7096cded-b83d-4eab-96f0-df477ed7c0bc
Removes the list item from the tenant wide extensions list.
spo tenant applicationcustomizer get
The text was updated successfully, but these errors were encountered:
Can I work on this?
Sorry, something went wrong.
You sure can!!
c9c252e
nicodecleyre
Successfully merging a pull request may close this issue.
Usage
spo tenant applicationcustomizer remove
Description
Remove an application customizer that is installed tenant wide.
Options
-t, --title [title]
title
,id
orclientSideComponentId
.-i, --id [id]
title
,id
orclientSideComponentId
.-c, --clientSideComponentId [clientSideComponentId]
title
,id
orclientSideComponentId
.Examples
Removes an application customizer by title.
m365 spo tenant applicationcustomizer remove --title "Some customizer"
Removes an application customizer by id.
Removes an application customizer by clientSideComponentId.
Additional Info
Removes the list item from the tenant wide extensions list.
spo tenant applicationcustomizer get
command implementation)The text was updated successfully, but these errors were encountered: