Replies: 1 comment
-
You are correct, it is confusing. Extension Management is the ExtensionSettings policy. I followed Chrome's convention in that it's called ExtensionSettings in the code, but Extension Management in the UI. One of the things that's missing in my documentation is that name of the entry in the ADMX templates. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Just a little confused with the documentation on Extensions, I'm sure I'm just missing something easy here.
It appears that the "Extensions" method will be deprecated and that I should use "ExtensionSettings" however I don't see an "ExtensionSettings" in the ADMX templates I only see "\Mozilla\Firefox\Extensions" and then the Extension Management Policy, Extension Management (JSON on one line), and a couple other extension policies, has the new ExtensionSettings policy not been added to the templates yet?
I don't have a problem using a custom OMA-URI but the templates make organization so much easier.
Utilizing Intune for this, and have imported the most recent ADMX templates.
Beta Was this translation helpful? Give feedback.
All reactions