New command: Enable a feature

Enable a feature on site collection

command: spo site feature add -u|--url <url> -f|--featureId <featureId> --force

• url: The URL of the site collection on which to enable feature
• featureId: The ID of the site collection scoped feature to enable
• force: Specifies whether to overwrite an existing feature with the same feature identifier. This parameter is ignored if there are no errors.

Enable a feature on site

command: spo web feature add -u|--webUrl <webUrl> -f|--featureId <featureId> --force

• webUrl: The URL of the site on which to enable feature
• featureId: The ID of the web scoped feature to enable
• force: Specifies whether to overwrite an existing feature with the same feature identifier. This parameter is ignored if there are no errors.

[stijnbrouwers]

Feel free to assign it to me…

[stijnbrouwers]

@waldekmastykarz @phawrylak I took a quick look at how it’s done in the PnP PowerShell solution. It’s correct that the scope is optional, but that’s just because it always defaults to scope = Web. It doesn’t change, based on the feature that you are trying to enable and the scope to which it applies (web/site). When no scope is provided, it’s always web.

Now, when trying to enable a web scoped feature on a site or vice versa, you don’t get any error message. It just finishes without any output and it’s quite fast, so I suspect nothing is happening behind the scenes.

Example Retrieve web scoped features Apply web scoped feature to site scope As mentioned before, same behaviour the other way around