

If we do not plan to distribute our extension via the Microsoft Edge Web Store, we will need a certificate.

The high-level steps for building & packaging a simple extension are as follows: Before we can continue, we need a simple extension to deploy. There are multiple steps to building a Microsoft Edge Extension, in this post I will focus on extension distribution & deployment. In this blog post I would like to explore how we can distribute our custom Microsoft Edge extensions within the Enterprise. Chromium brings with it an excellent extensibility model for customers and 3rd parties to extend the browsing experience, these extensions can also be published to the public Microsoft Edge Web Store.

Microsoft decided to base the latest version of Microsoft Edge on Chromium, this results in a much more standards-based browsing experience where Microsoft can innovate in other areas like UI etc.
