Trying to get a clearer understanding of what "enable" means. In this doc, and in the feature description, Msft implies that you if you enable an app "End users should see this app as an option to add to sites". So I would expect to have to remove the app from a site once added to stop it functioning. But if you uncheck "enable", it seems the app does stop working.

Example: I uploaded an spfx extension to the app catalog that injects a stylesheet. Since I want this to be optional by site, I didn't deploy tenant wide. When "enabled", I can add the app to a site via "add an app" and the stylesheet renders in the code for that site. If I uncheck "enable", the app is no longer available in add an app as expected, but also the functionality no longer works and the stylesheet doesn't get called.

Once the functionality is confirmed, I can make the description associated with the enabled field more accurate, but don't want to change it till I'm sure.


2 Answers 2


It's not just about enabling the app. It's also about making it available.

So when I say making the App available it means it should be available for the entire context wherein you want to make use of it .

In your case, it wouldn't be possible to enable the app , use it's properties to drive something and then disable it by unchecking .

Once you uncheck and disable the App, the app becomes meaningless in the context and all it's properties and functions all become meaningless to SharePoint .

So this wouldn't help you .


Per my understanding, enabling an app provides the capability of full function of this feature.

When you add the spfx extension to the app catalog, you have access to the app feature, but it is not in function. “Enable” means "switch on".

When you disable a feature, it gets turned off, but it is still reachable in the site (collection).

  • 1
    That was my assumption too, but isn't what Msft's description implies: "End users should see this app as an option to add to sites".Nothing there about turning the app's functionality on or off. So sounds like just another case of Msft's loose command of language/
    – matt
    Sep 1, 2019 at 19:22
  • It’s just a matter of expression. Microsoft will use more official and professional language in the documents, leading to less user-friendly. Sep 3, 2019 at 7:49

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.