Skip to content

The following two scenarios don't require you to publish your extension in the Microsoft Edge Add-ons website -> Enterprise Policy. #2916

@Ormus85

Description

@Ormus85

Can you elaborate on:
"The following two scenarios don't require you to publish your extension in the Microsoft Edge Add-ons website.

Extensions distributed using Enterprise policy."

I am aware of a self-hosting option, one that is itself poorly documented here: [https://learn.microsoft.com/en-us/deployedge/microsoft-edge-manage-extensions-webstore], which third parties have stepped in to explain: https://www.meziantou.net/self-hosting-chromium-extensions.htm

but this suggests that it's possible to perhaps host the file on a fileshare somewhere? or.. something? that would be ideal..

We have an extension that has had to be published to the public Chrome store in order to be delivered via "control which extensions are installed silently" gpo.. it's not ideal.. but thus far nobody internally seems to want to go ahead with the above self-hosting option. I'm hoping the above mentions an alternative? but it doesn't explain... the extension itself was developed by Oracle for us, so although we have the unpacked files, i'm not sure how (other than the self-hosting option described above) we would publihs this WITHOUT making it available publicly?


Document Details

Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

AB#47625993

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions