Update enterprise docs to cover extensions.allowed setting

[isidorn]

https://code.visualstudio.com/docs/setup/enterprise

We need to update those docs to reflect the new extensions.allowed settings that is sort-of documented in this comment
microsoft/vscode#84756 (comment)

[ntrogh]

@isidorn, @sandy081 docs for allowed extensions available in vext: https://github.com/microsoft/vscode-docs/blob/vnext/docs/setup/enterprise.md#configure-allowed-extensions

[isidorn]

@ntrogh I just read the docs and it looks great to me!
@sandy081 what do you think?

I think we need a note on the enterprise page that says that "Configuration Profiles are coming to macOS soon, and for Linux users should reach out to us to express interest".

And unrelated to this change - we should have an explicit mention that "update.mode" is a setting that can already be enterprise controlled. @sandy081 this is correct, right?

[ntrogh]

@isidorn thanks for reviewing. I'll add an FAQ at the end of the article about macOS and Linux. For Linux, users should reach out by creating an issue or is there a more appropriate channel?

[sandy081]

@ntrogh

Specify publishers by their publisher display name. If a key does not have a period (.), it is considered a publisher display name. If a key has a period, it is considered an extension ID.

It is publisher id and not the publisher display name. Display name is used only for Microsoft extensions. Can you please correct it

And unrelated to this change - we should have an explicit mention that "update.mode" is a setting that can already be enterprise controlled. @sandy081 this is correct, right?

Yes, we should also mention this setting. How about listing these two settings as features under Admin Controlled Features?

[ntrogh]

@sandy081 Are these the only two settings that can be configured through group policies?

[sandy081]

Yes

[ntrogh]

@sandy081 @isidorn updated the doc:

• include an FAQ about macOS and Linux
• include a section about update mode
• updated the headings

[sandy081]

@ntrogh Thanks for the changes. It might be also helpful to note that all extensions from microsoft publishers can be grouped under microsoft even though there are different publisher ids?

[isidorn]

@ntrogh for linux - just by creating an issue. Soon we should have one created by the community and once that happens we can link to it directly.

Looks good. Nick thanks for making this happen!