diff --git a/microsoft-edge/devtools/customize/extensions.md b/microsoft-edge/devtools/customize/extensions.md index 2451fb578f..b6dcd96d8e 100644 --- a/microsoft-edge/devtools/customize/extensions.md +++ b/microsoft-edge/devtools/customize/extensions.md @@ -16,9 +16,9 @@ In addition to the tools available in Microsoft Edge DevTools, you can add new t ## Find an extension that extends DevTools -The [Developer tools](https://microsoftedge.microsoft.com/addons/category/Developer-Tools) category at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) contains extensions that typically extend DevTools. +The [Developer tools](https://microsoftedge.microsoft.com/addons/category/Developer-Tools) category at the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) website contains extensions that typically extend DevTools. -There is no way to know whether an extension extends the DevTools **Activity Bar**, without running it or looking at its source code, but the **Developer tools** category at Microsoft Edge Add-ons is a good place to look. +There is no way to know whether an extension extends the DevTools **Activity Bar**, without running it or looking at its source code, but the **Developer tools** category at the Microsoft Edge Add-ons website is a good place to look. @@ -26,11 +26,15 @@ There is no way to know whether an extension extends the DevTools **Activity Bar To install a Microsoft Edge extension that extends DevTools: -1. Go to [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com), such as the [Developer tools](https://microsoftedge.microsoft.com/addons/category/Developer-Tools) category, and go to the extension you want to install. +1. Go to the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) website. + +1. Go to a category, such as [Developer tools](https://microsoftedge.microsoft.com/addons/category/Developer-Tools). + +1. Go to the extension that you want to install. For example, go to the [React Developer Tools](https://microsoftedge.microsoft.com/addons/detail/react-developer-tools/gpphkfbcpidddadnkolkpfckpihlkkil) extension, which is the example used for the steps below: - ![The React Developer Tools page at Microsoft Edge Add-ons](./extensions-images/react-add-on-listing.png) + ![The React Developer Tools page at the Add-ons store](./extensions-images/react-add-on-listing.png) 1. Click the **Get** button. An installation dialog opens, **Add \ to Microsoft Edge?** diff --git a/microsoft-edge/devtools/whats-new/2023/01/devtools-109.md b/microsoft-edge/devtools/whats-new/2023/01/devtools-109.md index eab21b80cd..a09fe5a46e 100644 --- a/microsoft-edge/devtools/whats-new/2023/01/devtools-109.md +++ b/microsoft-edge/devtools/whats-new/2023/01/devtools-109.md @@ -135,7 +135,7 @@ Tree view: ![Heap Snapshot Visualizer in Tree mode](./devtools-109-images/heap-snapshot-visualizer-tree.png) See also: -* [Heap Snapshot Visualizer](https://microsoftedge.microsoft.com/addons/detail/heap-snapshot-visualizer/fceldlhognbemkgfacnffkdanocidgce) at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). +* [Heap Snapshot Visualizer](https://microsoftedge.microsoft.com/addons/detail/heap-snapshot-visualizer/fceldlhognbemkgfacnffkdanocidgce) at the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) website. diff --git a/microsoft-edge/devtools/whats-new/2023/08/devtools-116.md b/microsoft-edge/devtools/whats-new/2023/08/devtools-116.md index a6fc648a33..7d8651022a 100644 --- a/microsoft-edge/devtools/whats-new/2023/08/devtools-116.md +++ b/microsoft-edge/devtools/whats-new/2023/08/devtools-116.md @@ -44,7 +44,7 @@ See also: Prior to Microsoft Edge 116, if you were in Focus Mode while using the React Developer Tools extension, the state of a tool in DevTools wasn't maintained when you switched to another tool and then switched back. This issue has been fixed. See also: -* [React Developer Tools](https://microsoftedge.microsoft.com/addons/detail/react-developer-tools/gpphkfbcpidddadnkolkpfckpihlkkil) extension at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). +* [React Developer Tools](https://microsoftedge.microsoft.com/addons/detail/react-developer-tools/gpphkfbcpidddadnkolkpfckpihlkkil) extension at the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) website. * [What's New entries about Focus Mode](/search/?scope=Microsoft%20Edge&terms=focus%20mode) @@ -55,7 +55,7 @@ In the **Memory** tool, when there's more than one heap snapshot, a **Containmen ![The Containment Diff view in the Memory tool](./devtools-116-images/containment-diff.png) -The **Containment Diff** view shows only the new objects, deleted objects, or objects in the retaining chain that will eventually lead to either a new or deleted node. The dot symbol • means that it's a node in the retaining chain. Expanding the view displays the node that's new or deleted. +The **Containment Diff** view shows only the new objects, deleted objects, or objects in the retaining chain that will eventually lead to either a new or deleted node. The dot symbol * means that it's a node in the retaining chain. Expanding the view displays the node that's new or deleted. For example: diff --git a/microsoft-edge/extensions/contact.md b/microsoft-edge/extensions/contact.md index 7852888557..fd34148d4b 100644 --- a/microsoft-edge/extensions/contact.md +++ b/microsoft-edge/extensions/contact.md @@ -25,7 +25,7 @@ https://github.com/microsoft/MicrosoftEdge-Extensions/blob/main/README.md#issues Use the [Issues](https://github.com/microsoft/MicrosoftEdge-Extensions/issues) page of the **MicrosoftEdge-Extensions** repo for: * Communicating with the Extensions team: - * Report bugs or issues about [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) (the store) that affect all Edge extension developers or all Microsoft Edge extension users. + * Report bugs or issues about the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) website that affect all Edge extension developers or all Microsoft Edge extension users. * Report bugs or issues about Microsoft Partner Center that affect all Edge extension developers or all Microsoft Edge extension users. * Suggest new features that could impact or benefit all Microsoft Edge extension developers. * Inquire about your Partner Center developer account for Microsoft Edge extensions. @@ -52,7 +52,7 @@ Use the [Discussions](https://github.com/microsoft/MicrosoftEdge-Extensions/disc * Discussions with the Extensions team: * Follow the latest announcements and updates from the Microsoft Edge extensions team. * Request a feature for Edge extensions. - * Discuss how to improve UI features that are at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). + * Discuss how to improve UI features that are at the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) website. * Discuss how to improve extension publishing, management and listing processes or workflows. * Provide feedback about features for extensions publishing, extensions management, or processes or workflows for extensions listings. @@ -69,7 +69,7 @@ See also: ## Report copyright or trademark infringement -If you think an item at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) violates a copyright or trademark, complete the [Reporting Infringement](https://www.microsoft.com/concern/dmca) form. When filling in **Step 3: Where can the infringing material be found?**, in the **Product/Service/App** option, make sure to select **Microsoft Store on Windows**. The Microsoft Edge extensions team will review your report and then take the necessary action. +If you think an item at the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) website violates a copyright or trademark, complete the [Reporting Infringement](https://www.microsoft.com/concern/dmca) form. When filling in **Step 3: Where can the infringing material be found?**, in the **Product/Service/App** option, make sure to select **Microsoft Store on Windows**. The Microsoft Edge extensions team will review your report and then take the necessary action. diff --git a/microsoft-edge/extensions/developer-guide/alternate-distribution-options.md b/microsoft-edge/extensions/developer-guide/alternate-distribution-options.md index a80d9b9cea..79d9fdf1b7 100644 --- a/microsoft-edge/extensions/developer-guide/alternate-distribution-options.md +++ b/microsoft-edge/extensions/developer-guide/alternate-distribution-options.md @@ -11,13 +11,13 @@ ms.date: 05/05/2023 # Alternative ways to distribute an extension -Generally, a Microsoft Edge extension is distributed by publishing it at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). There are some scenarios where you might need to distribute an extension by using alternate methods. For example: +Generally, a Microsoft Edge extension is distributed by publishing it at the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) website. There are some scenarios where you might need to distribute an extension by using alternate methods. For example: 1. The extension is associated with other software, and it should be installed together with the rest of the bundled software. 1. Network administrators want to distribute an extension throughout their organization. -Extensions that aren't loaded from Microsoft Edge Add-ons are called _externally installed extensions_. The following are alternate methods of distributing externally installed extensions: +Extensions that aren't loaded from the Microsoft Edge Add-ons website are called _externally installed extensions_. The following are alternate methods of distributing externally installed extensions: * Use the Windows registry (Windows only). * Use a preferences JSON file (macOS and Linux). @@ -32,7 +32,7 @@ See also: ## Gather initial information -Make sure that you publish your extension at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com), or package a `.crx` file and ensure that it installs successfully on your computer. If you install the `.crx` file using the `update_url`, make sure you can go to your extension at that URL. +Make sure that you publish your extension at the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) website, or package a `.crx` file and ensure that it installs successfully on your computer. If you install the `.crx` file using the `update_url`, make sure you can go to your extension at that URL. Also, make sure that you have the following information: @@ -57,7 +57,7 @@ To distribute your extension using the Windows registry: 1. Create a new key, or folder, under **Extensions** with the same name as the ID of your extension. For example, create the key with the name `aaaaaaaabbbbbbbbccccccccdddddddd`. -1. In the **Extensions** key, create the `update_url` property, and set the value to `https://edge.microsoft.com/extensionwebstorebase/v1/crx`. The `update_url` property points to the `.crx` file of your extension at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). +1. In the **Extensions** key, create the `update_url` property, and set the value to `https://edge.microsoft.com/extensionwebstorebase/v1/crx`. The `update_url` property points to the `.crx` file of your extension at the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) website. ```json { @@ -122,7 +122,7 @@ To distribute your extension by using a preferences JSON file: } ``` - * Copy the following code to your preferences JSON file when installing from [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) on macOS and Linux: + * Copy the following code to your preferences JSON file when installing from the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) website on macOS and Linux: ```json { diff --git a/microsoft-edge/extensions/developer-guide/api-support.md b/microsoft-edge/extensions/developer-guide/api-support.md index fd3c6fcc7b..fa7d32cac9 100644 --- a/microsoft-edge/extensions/developer-guide/api-support.md +++ b/microsoft-edge/extensions/developer-guide/api-support.md @@ -133,4 +133,4 @@ This work is licensed under a [Creative Commons Attribution 4.0 International Li * [Chrome Extensions API reference for Manifest V2](https://developer.chrome.com/docs/extensions/mv2/reference/) * [Chrome Extensions API reference for Manifest V3](https://developer.chrome.com/docs/extensions/reference/api/) -* [Use the REST API to update an extension at Microsoft Edge Add-ons](../update/api/using-addons-api.md) - to update an extension at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). +* [Use the REST API to update an extension](../update/api/using-addons-api.md) - to update an extension at the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) website. diff --git a/microsoft-edge/extensions/developer-guide/best-practices.md b/microsoft-edge/extensions/developer-guide/best-practices.md index 7e39078809..cf6bce0daa 100644 --- a/microsoft-edge/extensions/developer-guide/best-practices.md +++ b/microsoft-edge/extensions/developer-guide/best-practices.md @@ -10,7 +10,7 @@ ms.date: 09/22/2025 --- # Best practices for extensions -Follow these best practices to implement your extension and list it at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). Build an extension that conforms to Microsoft's standards for security, privacy, performance, and user experience. These principles help ensure your extension is safe, reliable, and valuable to users. +Follow these best practices to implement your extension and list it at the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) website. Build an extension that conforms to Microsoft's standards for security, privacy, performance, and user experience. These principles help ensure your extension is safe, reliable, and valuable to users. The Microsoft Edge extensions team continues to gather feedback from developers and users to evolve these best practices. To ensure that your extension remains compliant and competitive, review this guidance regularly. @@ -89,4 +89,4 @@ Follow these best practices, to improve the quality, reliability, and user exper * [Minimize an extension's impact on page load time](./minimize-page-load-time-impact.md) External: -* [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) +* [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) website diff --git a/microsoft-edge/extensions/developer-guide/manifest-v3.md b/microsoft-edge/extensions/developer-guide/manifest-v3.md index 1ed89f92a2..147e7d490b 100644 --- a/microsoft-edge/extensions/developer-guide/manifest-v3.md +++ b/microsoft-edge/extensions/developer-guide/manifest-v3.md @@ -10,14 +10,14 @@ ms.date: 08/07/2026 --- # Timeline for migrating to Manifest V3 -To plan the migration of your extension from Manifest V2 to Manifest V3, the following timeline shows the planned end of support for Manifest V2 at Microsoft Partner Center, at the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) store, and in Microsoft Edge. +To plan the migration of your extension from Manifest V2 to Manifest V3, the following timeline shows the planned end of support for Manifest V2 at Microsoft Partner Center, at the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) website, and in Microsoft Edge. | Date | Changes | |---|---| -| Jul. 2022 | Partner Center (and the Edge Add-ons store) no longer accepts new Manifest V2 extensions. To publish a new extension, use Manifest V3. | +| Jul. 2022 | Partner Center (and the Microsoft Edge Add-ons website) no longer accepts new Manifest V2 extensions. To publish a new extension, use Manifest V3. | | Aug. 2026 | At Partner Center, if your extension uses Manifest V2, a Manifest V2 deprecation warning is displayed. | | Early 2027 | For enterprise customers, deprecation of Manifest V2 extensions is expected to begin. | -| TBD | Partner Center (and the Edge Add-ons store) will no longer accept updates to extensions that continue to use Manifest V2. You can submit an update that migrates a Manifest V2 extension to Manifest V3. | +| TBD | Partner Center (and the Microsoft Edge Add-ons website) will no longer accept updates to extensions that continue to use Manifest V2. You can submit an update that migrates a Manifest V2 extension to Manifest V3. | @@ -53,8 +53,8 @@ For information about end of support for Manifest V2 extensions in the Chromium * [Migrate an extension from Manifest V2 to V3](./migrate-your-extension-from-manifest-v2-to-v3.md) -* [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) store. -* [Manifest V3 changes are now available to test in Microsoft Edge](https://blogs.windows.com/msedgedev/2020/10/14/extension-manifest-chromium-edge/) - blog post. +* [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) website +* [Manifest V3 changes are now available to test in Microsoft Edge](https://blogs.windows.com/msedgedev/2020/10/14/extension-manifest-chromium-edge/) blog post Chromium docs: * [Chromium project](https://www.chromium.org/Home/) diff --git a/microsoft-edge/extensions/developer-guide/match-patterns.md b/microsoft-edge/extensions/developer-guide/match-patterns.md index 7068020448..19cf641e6b 100644 --- a/microsoft-edge/extensions/developer-guide/match-patterns.md +++ b/microsoft-edge/extensions/developer-guide/match-patterns.md @@ -23,7 +23,7 @@ See the License for the specific language governing permissions and limitations under the License. --> # Defining match patterns for an extension to access file URLs -A Microsoft Edge extension can request access to `file` URLs. To enable this feature, you need to explicitly configure this access. Access to `file` URLs isn't automatic. You must visit the **Extensions management** page at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) to opt into `file` access for each Microsoft Edge extension that requests access to `file` URLs. +A Microsoft Edge extension can request access to `file` URLs. To enable this feature, you need to explicitly configure this access. Access to `file` URLs isn't automatic. To opt into `file` access for each Microsoft Edge extension that requests access to `file` URLs, you must visit the **Extensions management** page at the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) website. For Microsoft Edge extension, host permission and content script pattern matching works as follows. diff --git a/microsoft-edge/extensions/developer-guide/migrate-your-extension-from-manifest-v2-to-v3.md b/microsoft-edge/extensions/developer-guide/migrate-your-extension-from-manifest-v2-to-v3.md index e25bb6a02a..a1136c2b47 100644 --- a/microsoft-edge/extensions/developer-guide/migrate-your-extension-from-manifest-v2-to-v3.md +++ b/microsoft-edge/extensions/developer-guide/migrate-your-extension-from-manifest-v2-to-v3.md @@ -38,9 +38,9 @@ Migrating an extension from using Manifest V2 to using Manifest V3 brings severa ## Remotely hosted code -Today, some parts of the extensions code are hosted remotely, and aren't included as part of the extension package during the validation process. Although this offers the flexibility to change code without resubmitting the extension at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com), it's possible to exploit the code after installation. +Today, some parts of the extensions code are hosted remotely, and aren't included as part of the extension package during the validation process. Although this offers the flexibility to change code without resubmitting the extension at the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) website, it's possible to exploit the code after installation. -To ensure that the extensions at Microsoft Edge Add-ons are validated, the Microsoft Edge extensions team disallows extensions from using remotely hosted code. This change makes extensions more secure. +To ensure that the extensions at the Microsoft Edge Add-ons website are validated, the Microsoft Edge extensions team disallows extensions from using remotely hosted code. This change makes extensions more secure. You'll need to package and submit all code that is used by the extension, for validation. Alternatively, you can use the `eval()` function in a sandboxed iframe. See [Use eval() in sandboxed iframes](https://developer.chrome.com/docs/extensions/how-to/security/sandboxing-eval). @@ -107,7 +107,7 @@ The Microsoft Edge extensions team publishes updates at our blog. You can provi External: * [Manifest V3 changes are now available in Microsoft Edge](https://techcommunity.microsoft.com/t5/articles/manifest-v3-changes-are-now-available-in-microsoft-edge/m-p/1780254) - blog post. * [Extensions](/deployedge/microsoft-edge-policies#extensions) in _Microsoft Edge – Policies_. -* [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) store. +* [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) website Chromium docs: * [Migrate to Manifest V3](https://developer.chrome.com/docs/extensions/develop/migrate) diff --git a/microsoft-edge/extensions/developer-guide/native-messaging.md b/microsoft-edge/extensions/developer-guide/native-messaging.md index 48a415cf48..2399f393ac 100644 --- a/microsoft-edge/extensions/developer-guide/native-messaging.md +++ b/microsoft-edge/extensions/developer-guide/native-messaging.md @@ -18,7 +18,7 @@ To acquire the extension and native app host, there are two different distributi * Package your extension and the host together. When a user installs the package, both the extension and the host are installed. -* Or, install your extension from [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com), and your extension prompts users to install the host. +* Or, install your extension from the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) website, and your extension prompts users to install the host. To create your extension to send and receive messages with native app hosts, do the following steps. @@ -129,7 +129,7 @@ Sideload your extension to test native messaging with the host. To sideload you 1. Copy the key from `microsoft_catalog_extension_id` (ID) from the extension listing on the page. -When you're ready to distribute your extension to users, publish your extension at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). The extension ID of the published extension might differ from the ID that's used while sideloading your extension. If the ID changed, update `allowed_origins` in the native messaging host manifest file with the ID of your published extension. +When you're ready to distribute your extension to users, publish your extension at the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) website. The extension ID of the published extension might differ from the ID that's used while sideloading your extension. If the ID changed, update `allowed_origins` in the native messaging host manifest file with the ID of your published extension. @@ -199,9 +199,11 @@ HKEY_LOCAL_MACHINE\SOFTWARE\Google\Chrome\NativeMessagingHosts\ The `HKEY_CURRENT_USER\SOFTWARE\WOW6432Node` registry node is not searched on 64-bit machines, due to the way the registry works on them. For more information, see [Registry Keys Affected by Windows Installations That Include Windows on Windows (WOW) Support For Multiple Processor Architectures](/windows/win32/winprog64/shared-registry-keys). + + #### Extension IDs required for both stores -If you have an extension both at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) and the Chrome Web Store, you must add the extension IDs that correspond to both of the stores in the `allowed_origins` of the native messaging host manifest file. +If you have an extension both at the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) website and the [Chrome Web Store](https://chrome.google.com/webstore/category/extensions), you must add the extension IDs that correspond to both of the stores, in the `allowed_origins` of the native messaging host manifest file. This is required because only the native messaging host manifest file that corresponds to the first registry location that's found is read. diff --git a/microsoft-edge/extensions/developer-guide/port-chrome-extension.md b/microsoft-edge/extensions/developer-guide/port-chrome-extension.md index 0748be00da..499921b52f 100644 --- a/microsoft-edge/extensions/developer-guide/port-chrome-extension.md +++ b/microsoft-edge/extensions/developer-guide/port-chrome-extension.md @@ -38,7 +38,7 @@ If your extension exchanges messages with a native app by using `chrome.runtime. ## Publish the extension -After your extension package is ready to publish at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com): +After your extension package is ready to publish at the Microsoft Edge Add-ons website: 1. [Register as a Microsoft Edge extension developer](../publish/create-dev-account.md). diff --git a/microsoft-edge/extensions/getting-started/architecture.md b/microsoft-edge/extensions/getting-started/architecture.md index dfd22a4142..007f11b094 100644 --- a/microsoft-edge/extensions/getting-started/architecture.md +++ b/microsoft-edge/extensions/getting-started/architecture.md @@ -15,7 +15,7 @@ This article introduces Developer concepts about building a Microsoft Edge exten A Microsoft Edge *extension* is a small app that users can opt into that adds or modifies features of Microsoft Edge to provide a specialized experience or function that is important to a target audience. For an introduction, see [Overview of Microsoft Edge extensions](../index.md). -Users browse and install extensions for Microsoft Edge from [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). +Users browse and install extensions for Microsoft Edge from the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) website. **Detailed contents:** * [Understand how browsers work](#understand-how-browsers-work) @@ -105,4 +105,4 @@ An extension provides opt-in permissions at install time. You specify the exten ## See also * [Sample: Picture viewer pop-up webpage](../samples/picture-viewer-popup-webpage.md) -* [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) - Browse and install extensions for Microsoft Edge. +* [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) website diff --git a/microsoft-edge/extensions/getting-started/extension-sideloading.md b/microsoft-edge/extensions/getting-started/extension-sideloading.md index 84b56eba97..69c13ffab7 100644 --- a/microsoft-edge/extensions/getting-started/extension-sideloading.md +++ b/microsoft-edge/extensions/getting-started/extension-sideloading.md @@ -10,9 +10,9 @@ ms.date: 01/16/2025 --- # Sideload an extension to install and test it locally -To test an extension quickly and safely, sideload the extension in your own copy of Microsoft Edge, which means locally installing the extension. You can then run and test your extension without having to publish the extension at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) and then install the extension from there. +To test an extension quickly and safely, sideload the extension in your own copy of Microsoft Edge, which means locally installing the extension. You can then run and test your extension without having to publish the extension at the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) website, and then install the extension from there. -Users browse and install extensions for Microsoft Edge from [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). +Users browse and install extensions for Microsoft Edge from the Microsoft Edge Add-ons website. @@ -55,7 +55,7 @@ To sideload an extension into Microsoft Edge, so that it's locally installed in The **Select the extension directory** dialog closes. - The extension is installed in your browser, similar to extensions that are installed from [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com): + The extension is installed in your browser, similar to extensions that are installed from the Microsoft Edge Add-ons website: ![Installed extensions page, showing a sideloaded extension](./extension-sideloading-images/installed-extension.png) @@ -138,4 +138,4 @@ If running an extension causes an error, in some cases, an **Error** link is add * [Sample: Picture viewer pop-up webpage](../samples/picture-viewer-popup-webpage.md) * [Sample: Picture inserter using content script](../samples/picture-inserter-content-script.md) -* [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) - Users install Edge Extensions +* [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) website diff --git a/microsoft-edge/extensions/index-images/edge-add-ons-website.png b/microsoft-edge/extensions/index-images/edge-add-ons-website.png new file mode 100644 index 0000000000..ad1514aca5 Binary files /dev/null and b/microsoft-edge/extensions/index-images/edge-add-ons-website.png differ diff --git a/microsoft-edge/extensions/index-images/example-extension.png b/microsoft-edge/extensions/index-images/example-extension.png index c385ad3bfe..c86eb5aa36 100644 Binary files a/microsoft-edge/extensions/index-images/example-extension.png and b/microsoft-edge/extensions/index-images/example-extension.png differ diff --git a/microsoft-edge/extensions/index.md b/microsoft-edge/extensions/index.md index 3096dd72f9..76f72e538f 100644 --- a/microsoft-edge/extensions/index.md +++ b/microsoft-edge/extensions/index.md @@ -13,8 +13,6 @@ ms.date: 04/17/2026 A Microsoft Edge _extension_ is a small app that a developer creates to add or modify features of Microsoft Edge, to extend the user experience (UX) for end-users in a specialized way. An extension provides a niche experience or function that's important to a target audience. -Users browse and install extensions for Microsoft Edge from the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) site. _Add-ons_ include extensions and themes. - The present documentation is for extension developers, rather than end-users of Microsoft Edge extensions. To use extensions for Microsoft Edge, see [User docs about Microsoft Edge extensions](./getting-started/user-docs.md). @@ -24,9 +22,9 @@ The present documentation is for extension developers, rather than end-users of * [Benefits of Chromium-based extensions](#benefits-of-chromium-based-extensions) * [Browser compatibility and extension testing](#browser-compatibility-and-extension-testing) * [Browser-specific APIs](#browser-specific-apis) -* [Publish your extension to browser stores](#publish-your-extension-to-browser-stores) +* [Publish your extension to browser extension stores](#publish-your-extension-to-browser-extension-stores) * [Migrate an existing extension to Microsoft Edge](#migrate-an-existing-extension-to-microsoft-edge) - * [Publish an extension at Microsoft Edge Add-ons](#publish-an-extension-at-microsoft-edge-add-ons) + * [Publish an extension at the Microsoft Edge Add-ons website](#publish-an-extension-at-the-microsoft-edge-add-ons-website) * [The Featured badge](#the-featured-badge) * [What the Featured badge represents](#what-the-featured-badge-represents) * [Reasons why the Featured badge could be revoked](#reasons-why-the-featured-badge-could-be-revoked) @@ -36,11 +34,15 @@ The present documentation is for extension developers, rather than end-users of ## Introduction -As a browser extension developer, you publish a Microsoft Edge extension (or theme) at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). In articles about Microsoft Edge extensions, and at Partner Center, the word _store_ includes the Microsoft Edge Add-ons site. +Microsoft Edge add-ons include extensions and themes. As an extension developer, you publish a Microsoft Edge extension at the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) website. Microsoft Edge users browse and install Microsoft Edge add-ons (extensions or themes) from the Microsoft Edge Add-ons website: + +![The Microsoft Edge Add-ons website](./index-images/edge-add-ons-website.png) + +To find an extension, you use the **Search extensions, themes, and more** text box. For example, to find extensions about Bing, enter "Bing", and then click a result. + +The product detail page for the [Microsoft Bing Homepage](https://microsoftedge.microsoft.com/addons/detail/microsoft-bing-homepage/cjmjijnpnollocennnapedpaeecninea) extension appears: -On the Microsoft Edge Add-ons site, you can enter various search terms in the **Search extensions, themes, and more** text box to find extensions and themes, such as the [Microsoft Bing Homepage and Search Engine](https://microsoftedge.microsoft.com/addons/detail/microsoft-bing-homepage-a/hcfdaddfkgbmekbgcepcnpfiopaigpnn) extension: - -![The Microsoft Bing Homepage and Search Engine extension](./index-images/example-extension.png) +![The Microsoft Bing Homepage extension](./index-images/example-extension.png) You can create a Microsoft Edge extension to add features to the browser, or improve the features of specific webpages by defining a companion experience. _Companion experiences_ include ad blockers and password managers. @@ -111,9 +113,9 @@ Some tutorials for browser-specific extension store sites use browser-specific A -## Publish your extension to browser stores +## Publish your extension to browser extension stores -You can submit and seek browser extensions in the following browser extension stores. +You can submit your extension at multiple browser extension stores, including: * [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) * [Chrome Web Store](https://chrome.google.com/webstore/category/extensions) @@ -121,9 +123,9 @@ You can submit and seek browser extensions in the following browser extension st * [Apple App Store](https://apps.apple.com) * [Firefox Browser Add-ons](https://addons.mozilla.org/firefox/extensions) -Some browser extension stores allow you to download listed extensions from other browsers. However, cross-browser access isn't guaranteed by every store. To make sure your users find your extension in different browsers, you should maintain a listing on each store. +Some browser extension stores allow you to download listed extensions for other browsers. However, cross-browser access isn't guaranteed by every store. To make sure your users find your extension in different browsers, you should maintain a listing on each store. -To make sure your users find your extension in Microsoft Edge, publish your extension on the Microsoft Edge Add-ons site. See [Publish an extension at Microsoft Edge Add-ons](#publish-an-extension-at-microsoft-edge-add-ons), below. +To make sure your users find your extension in Microsoft Edge, publish the extension at the Microsoft Edge Add-ons website. See [Publish an extension at the Microsoft Edge Add-ons website](#publish-an-extension-at-the-microsoft-edge-add-ons-website), below. Users might need to install your extension in different browsers. In this scenario, you can migrate existing Chromium extensions from one browser to another. @@ -131,38 +133,38 @@ Users might need to install your extension in different browsers. In this scena #### Migrate an existing extension to Microsoft Edge -If you've already developed an extension for another Chromium-based browser, you can submit it at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). You don't need to rewrite your extension or verify that it works in Microsoft Edge. However, when you migrate an existing Chromium extension to other Chromium browsers, make certain the same APIs or alternatives are available for your target browser. +If you've already developed an extension for another Chromium-based browser, you can submit it at the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) website. You don't need to rewrite your extension or verify that it works in Microsoft Edge. However, when you migrate an existing Chromium extension to other Chromium browsers, make certain the same APIs or alternatives are available for your target browser. For more information on porting your Chrome extension to Microsoft Edge, see [Port a Chrome extension to Microsoft Edge](./developer-guide/port-chrome-extension.md). After you port your extension to the target browser, the next step is to publish it. -#### Publish an extension at Microsoft Edge Add-ons +#### Publish an extension at the Microsoft Edge Add-ons website -You publish a Microsoft Edge extension at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). +You publish a Microsoft Edge extension at the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) website. -To start publishing a Microsoft Edge extension, you must [register for a developer account](https://developer.microsoft.com/registration) with a Microsoft account (MSA) email account to submit your extension listing at Microsoft Edge Add-ons. The email address of a Microsoft account (MSA) includes `@outlook.com`, `@live.com`, or `@hotmail.com`. +To start publishing a Microsoft Edge extension, you must [register for a developer account](https://developer.microsoft.com/registration) with a Microsoft account (MSA) email account to submit your extension listing at the Microsoft Edge Add-ons website. The email address of a Microsoft account (MSA) includes `@outlook.com`, `@live.com`, or `@hotmail.com`. When you choose an email address to register, consider whether you must transfer or share ownership of the Microsoft Edge extension with other people in your organization. After registration is complete, you can submit an extension listing. -To submit an extension at Microsoft Edge Add-ons, you need to provide the following items: +To submit an extension at the Microsoft Edge Add-ons website, you need to provide the following items: * An archive (`.zip`) file that contains your code files. * All required visual assets, which include a logo and small promotional tile. * Optional promotional media, such as screenshots, promotional tiles, and a video URL. * Information that describes your extension such as the name, short description, and a privacy policy link. -Different stores might have different submission requirements. The above list summarizes the requirements for publishing an extension for Microsoft Edge; for details, see [Publish a Microsoft Edge extension](./publish/publish-extension.md). +Different browser extension stores might have different requirements for submitting extensions. The above list summarizes the requirements for publishing an extension for Microsoft Edge; for details, see [Publish a Microsoft Edge extension](./publish/publish-extension.md). -After you've successfully submitted your extension, your extension undergoes a review process and either passes or fails the certification process. You're notified of the outcome and given next steps as required. If you submit an extension _update_ at Microsoft Edge Add-ons, that begins a new review process. +After you've successfully submitted your extension, your extension undergoes a review process and either passes or fails the certification process. You're notified of the outcome and given next steps as required. If you submit an extension _update_ at the Microsoft Edge Add-ons website, that begins a new review process. ## The Featured badge -At the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) site, the **Featured** badge links to this section. The present documentation is for extension developers, rather than end-users of Microsoft Edge extensions. To use extensions for Microsoft Edge, see [User docs about Microsoft Edge extensions](./getting-started/user-docs.md). +At the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) website, the **Featured** badge links to the present article section. The present documentation is for extension developers, rather than end-users of Microsoft Edge extensions. To use extensions for Microsoft Edge, see [User docs about Microsoft Edge extensions](./getting-started/user-docs.md). -Extensions are curated to help users discover trustworthy and high-performing extensions. The **Featured** badge at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) highlights extensions that meet a high bar of quality, security, and user experience. +Extensions are curated to help users discover trustworthy and high-performing extensions. The **Featured** badge at the Microsoft Edge Add-ons website highlights extensions that meet a high bar of quality, security, and user experience. ![The Featured badge](./index-images/featured-badge.png) @@ -186,7 +188,7 @@ The **Featured** badge indicates that: The **Featured** badge is not a judgment of safety. An extension that doesn't have the **Featured** badge is not necessarily unsafe; the extension simply doesn't meet the current threshold for Featured status. -The **Featured** badge on the Microsoft Edge Add-ons Store is intended to help users discover extensions that meet a high bar for quality, reliability, security, privacy, and user experience at the time of evaluation. +The **Featured** badge at the Microsoft Edge Add-ons website is intended to help users discover extensions that meet a high bar for quality, reliability, security, privacy, and user experience at the time of evaluation. Badging decisions are based on a combination of objective signals and automated checks, and are refreshed periodically as part of Microsoft's ongoing efforts to maintain a healthy and trustworthy extensions ecosystem. diff --git a/microsoft-edge/extensions/landing/index.yml b/microsoft-edge/extensions/landing/index.yml index 0d42b295a5..f083126274 100644 --- a/microsoft-edge/extensions/landing/index.yml +++ b/microsoft-edge/extensions/landing/index.yml @@ -137,7 +137,7 @@ landingContent: - text: App Developer Agreement Addendum for Microsoft Edge program users url: /legal/microsoft-edge/extensions/ada-addendum - - text: Developer policies for the Microsoft Edge Add-ons store + - text: Developer policies for the Microsoft Edge Add-ons website url: /legal/microsoft-edge/extensions/developer-policies # ============================================================================= @@ -172,7 +172,7 @@ landingContent: - text: Extension hosting url: ../publish/hosting-and-updating.md - - text: Submission states for extensions at Microsoft Edge Add-ons + - text: Status for submitted extensions url: ../publish/submission-states.md - text: Manage account settings @@ -183,7 +183,7 @@ landingContent: - linkListType: concept links: - - text: Curation and review process for extensions at Microsoft Edge Add-ons + - text: Curation and review process for extensions url: ../publish/add-ons-curation.md # ----------------------------------------------------------------------------- @@ -198,12 +198,12 @@ landingContent: - text: Set an externally installed extension to automatically update url: ../update/auto-update.md - - text: Use the REST API to update an extension at Microsoft Edge Add-ons + - text: Use the REST API to update an extension url: ../update/api/using-addons-api.md - linkListType: reference links: - - text: REST API Reference for updating an extension at Microsoft Edge Add-ons + - text: REST API Reference for updating an extension url: ../update/api/addons-api-reference.md # ============================================================================= @@ -238,7 +238,7 @@ landingContent: linkLists: - linkListType: overview links: - - text: Microsoft Edge Add-ons site # store + - text: Microsoft Edge Add-ons website url: https://microsoftedge.microsoft.com - text: Everything to know about browser extensions # introduction for users diff --git a/microsoft-edge/extensions/publish/aad-account.md b/microsoft-edge/extensions/publish/aad-account.md index 321321342b..f88d7bed69 100644 --- a/microsoft-edge/extensions/publish/aad-account.md +++ b/microsoft-edge/extensions/publish/aad-account.md @@ -1,6 +1,6 @@ --- title: Add users to the Microsoft Edge program -description: Adding and managing users from your organization onto the Microsoft Edge program to help manage the Partner Center account. Enable your other team members to publish extensions at Microsoft Edge Add-ons using your Partner Center account. +description: Adding and managing users from your organization onto the Microsoft Edge program to help manage the Partner Center account. Enable other team members to publish extensions at the Microsoft Edge Add-ons website using your Partner Center account. author: MSEdgeTeam ms.author: msedgedevrel ms.topic: article @@ -20,7 +20,7 @@ A Microsoft account (MSA) is an Outlook.com, Live.com, or Hotmail.com account. ## Making sure you have a Partner Center account with a Microsoft account (MSA) as the Primary Owner -To create a Partner Center account that can publish Microsoft Edge extensions, you must have a Microsoft account (MSA), either by creating one directly or by using your personal GitHub account credentials. +To create a Partner Center account that can publish Microsoft Edge extensions at the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) website, you must have a Microsoft account (MSA), either by creating one directly or by using your personal GitHub account credentials. After your Partner Center account is able to publish Microsoft Edge extensions, you can link the Partner Center account to an Microsoft Entra tenant. A linked Microsoft Entra tenant enables the added users to sign in to your Partner Center developer account by using their work accounts. diff --git a/microsoft-edge/extensions/publish/add-ons-badge.md b/microsoft-edge/extensions/publish/add-ons-badge.md index 57a4a7ad6d..2bc8ff7572 100644 --- a/microsoft-edge/extensions/publish/add-ons-badge.md +++ b/microsoft-edge/extensions/publish/add-ons-badge.md @@ -1,5 +1,5 @@ --- -title: Use the Microsoft Edge Add-ons badge to promote your add-on +title: Use the Microsoft Edge Add-ons badge to promote your extension description: Use this badge in your websites, documentation, or tutorials, to promote your extension (or theme) that's at the Microsoft Edge Add-ons site. # key words before col 158 author: MSEdgeTeam ms.author: msedgedevrel @@ -7,13 +7,13 @@ ms.topic: article ms.service: microsoft-edge ms.date: 09/15/2025 --- -# Use the Microsoft Edge Add-ons badge to promote your add-on +# Use the Microsoft Edge Add-ons badge to promote your extension To promote your Microsoft Edge extension (or theme), use the Microsoft Edge Add-ons badge in your websites, documentation, tutorials, and other services or integrations. This ensures consistent, accessible, and compliant representation of the Microsoft Edge Add-ons brand. -The Microsoft Edge Add-ons badge is a visual asset designed to help you promote your Microsoft Edge add-on and build user trust. +The Microsoft Edge Add-ons badge is a visual asset designed to help you promote your Microsoft Edge extension and build user trust. -The Microsoft Edge Add-ons badge reads **Get it from Microsoft Edge**, and shows the Microsoft Edge logo: +The Microsoft Edge Add-ons badge reads **Get it from Microsoft Edge**, and shows the Microsoft Edge logo: ![The "Microsoft Edge Add-ons" badge](./add-ons-badge-images/microsoft-edge-add-ons-badge.png) @@ -53,11 +53,11 @@ For example, the PDF includes the following guidelines: * Do not use the badge as a decorative element in any context. -* The badge must always be an active, clickable link that directs users to your product detail page at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). +* The badge must always be an active, clickable link that directs users to your product detail page at the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) website. * Do not use the badge in static marketing materials, such as posters, flyers, or non-clickable images in presentations or videos. -* The badge is intended solely to facilitate direct access to your add-ons at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). +* The badge is intended solely to facilitate direct access to your add-ons at the Microsoft Edge Add-ons website. @@ -71,4 +71,4 @@ When scaling the badge, always maintain its aspect ratio; do not stretch or comp ## See also -* [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) +* [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) website diff --git a/microsoft-edge/extensions/publish/add-ons-curation.md b/microsoft-edge/extensions/publish/add-ons-curation.md index fda46affbd..e1282d6acc 100644 --- a/microsoft-edge/extensions/publish/add-ons-curation.md +++ b/microsoft-edge/extensions/publish/add-ons-curation.md @@ -1,5 +1,5 @@ --- -title: Curation and review process for extensions at Microsoft Edge Add-ons +title: Curation and review process for extensions description: How an extension that's submitted at Microsoft Edge Add-ons is curated and reviewed by the Microsoft Edge extensions team. author: MSEdgeTeam ms.author: msedgedevrel @@ -8,21 +8,21 @@ ms.service: microsoft-edge ms.subservice: extensions ms.date: 10/13/2023 --- -# Curation and review process for extensions at Microsoft Edge Add-ons +# Curation and review process for extensions -The Microsoft Edge extensions team curates the experience at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) so that users can find all the items to customize their browser in one place, such as extensions or themes. +The Microsoft Edge extensions team curates the experience at the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) website, so that users can find all the items to customize their browser in one place, such as extensions or themes. -Available _items_ to customize the user's browser include extensions and themes. +Available _items_ to customize the user's browser include extensions and themes. This article focuses on extensions. -Before installing an item from Microsoft Edge Add-ons, users can learn more about the functionality, data permissions, and publisher by viewing the item's description and listing. +Before installing an extension from the Microsoft Edge Add-ons website, users can learn more about the functionality, data permissions, and publisher by viewing the extension's description and listing. -## How items are organized at Microsoft Edge Add-ons +## How items are organized at the Microsoft Edge Add-ons website -Items at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com), including extensions and themes, are organized to help users discover the add-ons that are relevant to their interests. +Items at the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) website, including extensions and themes, are organized to help users discover the add-ons that are relevant to their interests. -Users can discover extensions they're interested in at Microsoft Edge Add-ons in several ways, including: +Users can discover extensions they're interested in at the Microsoft Edge Add-ons website in several ways, including: * The home page. * The Search bar. * Curated collections of extensions. @@ -30,7 +30,7 @@ Users can discover extensions they're interested in at Microsoft Edge Add-ons in The following factors are used to organize items: -* **Quality:** Extensions that are featured at Microsoft Edge Add-ons are selected based on their eligibility criteria. +* **Quality:** Extensions that are featured at the Microsoft Edge Add-ons website are selected based on their eligibility criteria. * **Relevancy:** Ranking takes into consideration factors such as the item name, description relevancy, popularity, and user experience. @@ -40,18 +40,18 @@ The following factors are used to organize items: ## Security review -The quality and compliance of the item that's displayed at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) is verified per the guidelines that are set in the developer policy. +The quality and compliance of the item that's displayed at the Microsoft Edge Add-ons website is verified per the guidelines that are set in the developer policy. -Extensions that violate the policy guidelines are not allowed at Microsoft Edge Add-ons. There is a standard review process for each new item submission and new versions of items, per the developer policies. +Extensions that violate the policy guidelines are not allowed at the Microsoft Edge Add-ons website. There is a standard review process for each new item submission and new versions of items, per the developer policies. See also: -* [Developer policies for the Microsoft Edge Add-ons store](/legal/microsoft-edge/extensions/developer-policies) +* [Developer policies for the Microsoft Edge Add-ons website](/legal/microsoft-edge/extensions/developer-policies) ## Ranking -Every item (such as an extension or theme) that's published at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) has detailed information about the item's characteristics, such as: +Every item (such as an extension or theme) that's published at the Microsoft Edge Add-ons website has detailed information about the item's characteristics, such as: * Screenshots. * The description of the item's features and functionality. @@ -64,12 +64,14 @@ The search ranking of the item is based on these characteristics. ## User feedback -At [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com), users can provide a rating and a written review for the item they are using. Users and developers can report an abusive review from within the review section of the item listing page. +At the Microsoft Edge Add-ons website, users can provide a rating and a written review for the item they are using. Users and developers can report an abusive review from within the review section of the item listing page. -Items are ranked for popularity based on user ratings at Microsoft Edge Add-ons. +Items are ranked for popularity based on user ratings at the Microsoft Edge Add-ons website. ## See also + -* [Developer policies for the Microsoft Edge Add-ons store](/legal/microsoft-edge/extensions/developer-policies) +* [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) website +* [Developer policies for the Microsoft Edge Add-ons website](/legal/microsoft-edge/extensions/developer-policies) diff --git a/microsoft-edge/extensions/publish/create-dev-account.md b/microsoft-edge/extensions/publish/create-dev-account.md index 9ac4e6ed61..7322ce78de 100644 --- a/microsoft-edge/extensions/publish/create-dev-account.md +++ b/microsoft-edge/extensions/publish/create-dev-account.md @@ -1,6 +1,6 @@ --- title: Register as a Microsoft Edge extension developer -description: How to register a Partner Center developer account to publish an extension at Microsoft Edge Add-ons. +description: How to register a Partner Center developer account to publish an extension at the Microsoft Edge Add-ons website. author: MSEdgeTeam ms.author: msedgedevrel ms.topic: article @@ -11,7 +11,7 @@ ms.date: 12/12/2025 # Register as a Microsoft Edge extension developer -To submit an extension at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com), you must be registered as a developer with the Microsoft Edge program. You register for the Microsoft Edge program at [Partner Center](https://partner.microsoft.com/dashboard/microsoftedge/public/login), as described below. +To submit an extension at the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) website, you must be registered as a developer with the Microsoft Edge program. You register for the Microsoft Edge program at [Partner Center](https://partner.microsoft.com/dashboard/microsoftedge/public/login), as described below. **Detailed contents:** * [Introduction](#introduction) @@ -37,7 +37,9 @@ To submit an extension at [Microsoft Edge Add-ons](https://microsoftedge.microso There is no registration fee for submitting extensions to the Microsoft Edge program. -To register for the Microsoft Edge program, you need a Microsoft account (MSA). This article helps you create a Partner Center account that you can use to submit a Microsoft Edge extension at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). This article covers company accounts (for enterprise developers), and individual accounts (for individual developers), as described in [Account type](#account-type), below. +To register for the Microsoft Edge program, you need a Microsoft account (MSA). This article helps you create a Partner Center account that you can use to submit a Microsoft Edge extension at the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) website. + +This article covers company accounts (for enterprise developers), and individual accounts (for individual developers), as described in [Account type](#account-type), below. If you have a Partner Center account, but the Primary Owner of the account isn't a Microsoft account (MSA), this article helps you create and link to a suitable account. You'll learn: * How to create a Microsoft account (MSA), if you don't have one. @@ -45,8 +47,6 @@ If you have a Partner Center account, but the Primary Owner of the account isn't To add and manage users in the Microsoft Edge program to manage extensions, you can associate your Partner Center account with your organization's Microsoft Entra tenant. -Users browse and install extensions for Microsoft Edge from [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). - ## Types of accounts related to publishing Microsoft Edge extensions @@ -129,7 +129,7 @@ In the **Account type** section, select the **Individual** or **Company** option ![Account type](./create-dev-account-images/account-type.png) -The Microsoft Edge program in [Partner Center](https://partner.microsoft.com/dashboard/microsoftedge/public/login) offers both individual and company accounts, described below. Both account types enable you to publish an extension at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). +The Microsoft Edge program in [Partner Center](https://partner.microsoft.com/dashboard/microsoftedge/public/login) offers both individual and company accounts, described below. Both account types enable you to publish an extension at the Microsoft Edge Add-ons website. @@ -147,13 +147,13 @@ Develop and publish extensions using your registered business name. A company account is associated with an organization or business. The account verification process is longer, and involves confirmation that you're authorized to create the account for your company. The duration of the process can range from a few days to a few weeks. Your company might receive phone calls from Microsoft verification partners. -For a company account, it's crucial to verify your Microsoft Edge program information when you enroll into a new Partner Center program. This verification is needed to publish an extension at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). See [Verify your company account information](./verify-microsoft-edge-program.md). +For a company account, it's crucial to verify your Microsoft Edge program information when you enroll into a new Partner Center program. This verification is needed to publish an extension at the Microsoft Edge Add-ons website. See [Verify your company account information](./verify-microsoft-edge-program.md). #### Publisher display name (Company name) -In the **Publisher display name (Company name)** text box, enter the company name to display at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com): +In the **Publisher display name (Company name)** text box, enter the company name to display at the Microsoft Edge Add-ons website: ![Company name](./create-dev-account-images/company-name.png) @@ -252,4 +252,4 @@ Other Microsoft.com sites: * [Partner Center](https://partner.microsoft.com/dashboard/microsoftedge/public/login) * [Account settings | Legal info](https://partner.microsoft.com/dashboard/account/v3/organization/legalinfo) * [account.microsoft.com](https://account.microsoft.com/account) -* [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) - Browse and install extensions for Microsoft Edge. +* [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) website diff --git a/microsoft-edge/extensions/publish/extensions-analytics.md b/microsoft-edge/extensions/publish/extensions-analytics.md index 4feb0f01a7..aac7dad722 100644 --- a/microsoft-edge/extensions/publish/extensions-analytics.md +++ b/microsoft-edge/extensions/publish/extensions-analytics.md @@ -1,6 +1,6 @@ --- title: View Microsoft Edge extensions analytics dashboard -description: View extension metrics from your Partner Center dashboard and evaluate an extension's performance at Microsoft Edge Add-ons. +description: View extension metrics from your Partner Center dashboard and evaluate an extension's performance at the Microsoft Edge Add-ons website. author: MSEdgeTeam ms.author: msedgedevrel ms.topic: article @@ -10,9 +10,9 @@ ms.date: 11/07/2022 --- # View Microsoft Edge extensions analytics dashboard -Microsoft announced the launch of the Extensions Analytics Dashboard on Sep. 8, 2021. For more information, see the blog post [Track your add-on's performance: extension analytics now available on Partner center](https://techcommunity.microsoft.com/t5/articles/track-your-add-on-s-performance-extension-analytics-now/m-p/2733351). +Microsoft announced the launch of the Extensions Analytics Dashboard on Sep. 8, 2021. See [Track your add-on's performance: extension analytics now available on Partner center](https://techcommunity.microsoft.com/t5/articles/track-your-add-on-s-performance-extension-analytics-now/m-p/2733351). -You can view extension metrics from your [Partner Center dashboard](https://partner.microsoft.com/dashboard/microsoftedge/overview) and evaluate an extension's performance at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). +You can view extension metrics from your [Partner Center dashboard](https://partner.microsoft.com/dashboard/microsoftedge/overview) and evaluate an extension's performance at the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) website. For example, you can identify regions in which the number of installations for your extension has increased in the past three months. You can also export this report as a CSV file. @@ -26,7 +26,7 @@ Follow these steps to view your extension's analytics dashboard: ## Analytics dashboard metrics -From the analytics dashboard you can view metrics for the **Last month**, **3 months**, **6 months**, or **All time** (the period since your extension has been published at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com)). +From the analytics dashboard you can view metrics for the **Last month**, **3 months**, **6 months**, or **All time** (the period since your extension was published at the Microsoft Edge Add-ons website). @@ -53,9 +53,9 @@ The following screenshot shows the **Weekly users** who have enabled and disable #### Installs -The **Installs** metric displays the total number of successful installs of your extensions per day at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). +The **Installs** metric displays the total number of successful installs of your extensions per day at the Microsoft Edge Add-ons website. -The following screenshot shows daily successful installations for the last month. +The following example shows daily successful installations for the last month: ![Installs for your extension over the last month](./extensions-analytics-images/extensions-analytics-weekly-users-installs.png) @@ -63,9 +63,9 @@ The following screenshot shows daily successful installations for the last month #### Impressions -The **Impressions** metric captures the total number of page views and user visits to your extension product page at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). The data points are based on weekly or daily totals depending on the selected time range. +The **Impressions** metric captures the total number of page views and user visits to your extension product page at the Microsoft Edge Add-ons website. The data points are based on weekly or daily totals depending on the selected time range. -The following screenshot shows **Impressions** for an extension page over a three month period: +The following example shows **Impressions** for an extension page over a three-month period: ![Impressions for your extension over the past 3 months](./extensions-analytics-images/extensions-analytics-weekly-users-impressions.png) diff --git a/microsoft-edge/extensions/publish/github.md b/microsoft-edge/extensions/publish/github.md index 34b77a4092..8601e5f661 100644 --- a/microsoft-edge/extensions/publish/github.md +++ b/microsoft-edge/extensions/publish/github.md @@ -1,6 +1,6 @@ --- title: Register and sign in to Partner Center using a GitHub account -description: Optionally sign in to Partner Center by using your GitHub account credentials, to publish Microsoft Edge extensions (add-ons). +description: Optionally sign in to Partner Center by using your GitHub account credentials, to publish a Microsoft Edge extension. author: MSEdgeTeam ms.author: msedgedevrel ms.topic: article @@ -10,7 +10,7 @@ ms.date: 02/14/2024 --- # Register and sign in to Partner Center using a GitHub account -If you're a GitHub user, you don't need to create a new Microsoft account (MSA) and remember extra passwords to sign into Partner Center. You can use your personal GitHub credentials to sign into Partner Center and publish a Microsoft Edge extension at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). +If you're a GitHub user, you don't need to create a new Microsoft account (MSA) and remember extra passwords to sign into Partner Center. You can use your personal GitHub credentials to sign into Partner Center and publish a Microsoft Edge extension at the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) website. Currently, you can only use your _personal_ GitHub account to login to Partner Center. Using your _work_ GitHub account isn't supported. diff --git a/microsoft-edge/extensions/publish/hosting-and-updating.md b/microsoft-edge/extensions/publish/hosting-and-updating.md index 0877c4faa0..f2253ea06c 100644 --- a/microsoft-edge/extensions/publish/hosting-and-updating.md +++ b/microsoft-edge/extensions/publish/hosting-and-updating.md @@ -10,19 +10,19 @@ ms.date: 12/18/2023 --- # Extension hosting -Most extensions are published at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com), to protect users from malicious extensions. +Most extensions are published at the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) website, to protect users from malicious extensions. ## Publish options for extensions -All extensions are distributed to users as a special archive (`.zip`) file with a `.crx` suffix. Extensions that are published at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) are uploaded as `.zip` files. The publishing process automatically converts the `.zip` file into a `.crx` file. +All extensions are distributed to users as a special archive (`.zip`) file with a `.crx` suffix. An extension that's published at the Microsoft Edge Add-ons website is uploaded as a `.zip` file. The publishing process automatically converts the `.zip` file into a `.crx` file. -The following two scenarios don't require you to publish your extension at Microsoft Edge Add-ons: -* Extensions that are distributed using Enterprise policy. -* Using unpacked extension directories on a local machine when Microsoft Edge is in developer mode. +The following two scenarios don't require you to publish the extension at the Microsoft Edge Add-ons website: +* Using an unpacked extension directory on a local machine, when Microsoft Edge is in developer mode. +* An extension that's distributed by using Enterprise policy. -In both cases, Microsoft Edge periodically checks extension hosts for new versions of installed extensions and automatically updates them without user intervention. +In both cases, Microsoft Edge periodically checks extension hosts for new versions of installed extensions, and automatically updates the extension without user intervention. diff --git a/microsoft-edge/extensions/publish/manage-settings.md b/microsoft-edge/extensions/publish/manage-settings.md index cbe65b7fc4..9bce8f9bd0 100644 --- a/microsoft-edge/extensions/publish/manage-settings.md +++ b/microsoft-edge/extensions/publish/manage-settings.md @@ -28,7 +28,7 @@ In the **Account details** section, review the type of your account and its stat ## Contact Details -The **Contact info** section displays the details you provided when you created your account. The Microsoft Edge extension team uses the contact details information to contact you about your account. The publisher name that's displayed at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) is also displayed in the **Contact info** section. +The **Contact info** section displays the details you provided when you created your account. The Microsoft Edge extension team uses the contact details information to contact you about your account. The publisher name that's displayed at the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) website is also displayed in the **Contact info** section. If your contact information changes you can edit the **Contact info** section. Select **Update**, make your changes, and then select **Save**. You can also select **Contact info** in the left navigation menu to open the **Contact info** section. diff --git a/microsoft-edge/extensions/publish/publish-extension.md b/microsoft-edge/extensions/publish/publish-extension.md index f0360e0ad5..43a43c1e63 100644 --- a/microsoft-edge/extensions/publish/publish-extension.md +++ b/microsoft-edge/extensions/publish/publish-extension.md @@ -1,6 +1,6 @@ --- title: Publish a Microsoft Edge extension -description: How to publish a Microsoft Edge extension at Microsoft Edge Add-ons. +description: How to publish a Microsoft Edge extension at the Microsoft Edge Add-ons website. author: MSEdgeTeam ms.author: msedgedevrel ms.topic: article @@ -24,9 +24,9 @@ out of scope: Reviews --> -After you develop and test your Microsoft Edge extension, you're ready to distribute your extension at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). To increase the extension's reach and make it available to other Microsoft Edge users, publish the extension at Microsoft Edge Add-ons, through Partner Center. +After you develop and test your Microsoft Edge extension, you're ready to distribute your extension at the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) website. To increase the extension's reach and make it available to other Microsoft Edge users, publish the extension at the Microsoft Edge Add-ons website, through Partner Center. -Users browse and install extensions for Microsoft Edge from [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). +Users browse and install extensions for Microsoft Edge from the Microsoft Edge Add-ons website. If you have an existing Chrome extension and you want to release it for Microsoft Edge users, first see [Port a Chrome extension to Microsoft Edge](../developer-guide/port-chrome-extension.md). @@ -73,7 +73,7 @@ If you have an existing Chrome extension and you want to release it for Microsof ## Step 1: Prepare the extension to be submitted -To prepare an extension to be submitted via Partner Center, to be published at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com), do the following steps. +To prepare an extension to be submitted via Partner Center, to be published at the Microsoft Edge Add-ons website, do the following steps. @@ -87,7 +87,7 @@ Before publishing your extension, you must have a working prototype of the exten To get started, visit [Partner Center](https://partner.microsoft.com/dashboard/microsoftedge/public/login?ref=dd). This is where every developer (new or existing) must go to publish or manage their extensions. -Use your active developer account to submit the extension at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). If you don't have a developer account, create a new developer account. To open a new developer account and register for the Microsoft Edge program, see [Register as a Microsoft Edge extension developer](./create-dev-account.md). +Use your active developer account to submit the extension at the Microsoft Edge Add-ons website. If you don't have a developer account, create a new developer account. To open a new developer account and register for the Microsoft Edge program, see [Register as a Microsoft Edge extension developer](./create-dev-account.md). @@ -103,11 +103,9 @@ Create a `.zip` file that's your extension package. The extension package must #### Review manifest field values -In articles about Microsoft Edge extensions, and at Partner Center, the word _store_ includes the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) site. - Before uploading your package to Partner Center, inspect the manifest file to make sure that the field values match your preferred display on the **Store Listings** page, as follows. -The following fields in the manifest file are automatically included in your extension's product listing at Microsoft Edge Add-ons: +The following fields in the manifest file are automatically included in your extension's product listing at the Microsoft Edge Add-ons website: * The `Name` field, which populates the **Extension name** on the **Details for \** page. @@ -194,13 +192,16 @@ Fill in the **Visibility** and **Markets** sections as follows. #### Visibility -Select one of the following visibility options to define whether your extension is discoverable at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com): +Select one of the following visibility options to define whether your extension is discoverable at the Microsoft Edge Add-ons website: -* `Public` (default) - Allows everyone to discover your extension through search, browsing at Microsoft Edge Add-ons, or using the listing URL for your extension at Microsoft Edge Add-ons. The listing URL is available on your Partner Center dashboard on the Extension **Overview** page. +* `Public` (default) - Allows everyone to discover your extension through: + * Search. + * Browsing at the Microsoft Edge Add-ons website. + * Using the listing URL for your extension at the Microsoft Edge Add-ons website. The listing URL is available on your Partner Center dashboard on the Extension **Overview** page. -* `Hidden` - Removes an extension from search results or browsing at Microsoft Edge Add-ons. To distribute a hidden extension at Microsoft Edge Add-ons, you must share the listing URL to the extension with your customers. +* `Hidden` - Removes an extension from search results or browsing at the Microsoft Edge Add-ons website. To distribute a hidden extension at the Microsoft Edge Add-ons website, you must share the listing URL of the extension with your customers. -You can change the visibility of your extension from **Public** to **Hidden**. Users who installed your extension while the visibility was set to **Public** retain access to your extension and receive any updates you make available at Microsoft Edge Add-ons. +You can change the visibility of your extension from **Public** to **Hidden**. Users who installed your extension while the visibility was set to **Public** retain access to your extension and receive any updates you make available at the Microsoft Edge Add-ons website. @@ -214,7 +215,7 @@ Define the specific markets in which you plan to offer your extension. The defa Or, select **Unselect all**, and then select individual markets. - You can change the markets where your extension is offered. A user who installs your extension while it's available in the user's market retains access to your extension. However, the user doesn't have access to any future updates that are submitted at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). + You can change the markets where your extension is offered. A user who installs your extension while it's available in the user's market retains access to your extension. However, the user doesn't have access to any future updates that are submitted at the Microsoft Edge Add-ons website. You have now filled in the **Availability** page for the extension at Partner Center. @@ -237,22 +238,11 @@ Define the specific markets in which you plan to offer your extension. The defa | Property name | Required? | Description | |---|---|---| | **Category** | Required | The category that best describes the extension. Listing the extension in the right category helps users find the extension easily and understand more about it. | - | **Website** | Optional | A webpage that provides additional information about the extension. The website URL must point to a webpage on your own website, not the web listing for the extension at Microsoft Edge Add-ons. The **Website** URL helps users learn more about the extension, its features, and any other relevant information. | + | **Website** | Optional | A webpage that provides additional information about the extension. The website URL must point to a webpage on your own website, not the web listing for the extension at the Microsoft Edge Add-ons website. The **Website** URL helps users learn more about the extension, its features, and any other relevant information. | | **Support contact detail** | Optional | The URL to your support webpage, or the email address to contact your support team. | - | **Mature content** | Optional | Checkbox to specify whether the extension includes mature content. This extension rating helps determine the appropriate age group of the target audience of the extension. To help determine whether the extension has _mature content_, see [Developer policies for the Microsoft Edge Add-ons store](/legal/microsoft-edge/extensions/developer-policies). | + | **Mature content** | Optional | Checkbox to specify whether the extension includes mature content. This extension rating helps determine the appropriate age group of the target audience of the extension. To help determine whether the extension has _mature content_, see [Developer policies for the Microsoft Edge Add-ons website](/legal/microsoft-edge/extensions/developer-policies). | - The properties are displayed to users at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). Your developer/organization name, **Website** URL, and **Support contact detail** that you submitted during registration are displayed to users at the Microsoft Edge Add-ons site. - - - -1. If the following text boxes are in the **Properties** page, fill them in as follows. - - | Property name | Required? | Description | - |---|---|---| - | **Privacy policy requirements** | Required | Specify whether the extension accesses, collects, or transmits any personal information. If you select **No** but it's later determined that the extension does handle personal information, the certification process might fail. If you select **Yes**, you must provide a Privacy policy URL, because this is a required field and submitting the extension won't be allowed without it. | - | **Privacy policy URL** | Required if the extension collects any privacy information | A valid privacy policy URL to communicate how the extension follows privacy laws and regulations. You're responsible for ensuring that the extension follows privacy laws and regulations. You're also responsible for providing a privacy policy URL if any personal information is being accessed, transmitted, or collected by the extension. To determine if the extension requires a privacy policy, see [Microsoft Store App Developer Agreement](https://go.microsoft.com/fwlink/?linkid=528905) and [Developer policies for the Microsoft Edge Add-ons store](/legal/microsoft-edge/extensions/developer-policies). | - - + The properties (your developer/organization name, **Website** URL, and **Support contact detail**) that you submitted during registration are displayed to users at the Microsoft Edge Add-ons website. You have now filled in the **Properties** page for the extension at Partner Center. @@ -260,20 +250,10 @@ Define the specific markets in which you plan to offer your extension. The defa The **Privacy** page opens. - - - Or, if you don't yet have the new UI that shows **Privacy** in the sequence on the left, the **Store listings** page opens. In that case, make sure the **Privacy** fields are filled in as appropriate in the **Properties** page, and then proceed to [Step 7: Enter store listing details for each language](#step-7-enter-store-listing-details-for-each-language), below. - - - ## Step 6: Enter privacy information - -**Note:** At Partner Center, privacy information is now entered in a dedicated **Privacy** page in the flow for submitting an extension, rather than as a **Privacy policy requirements** text box and a **Privacy policy URL** text box in the **Properties** page. This update is being rolled out in phases, and is planned to be available to all developers by the end of May 2026. - - In the extension's **Privacy** page at Partner Center, declare the extension's purpose, permissions, and data practices: ![The Privacy page for an extension, at Partner Center](./publish-extension-images/privacy-page.png) @@ -296,7 +276,7 @@ To enter **Privacy** information about the extension: 1. Fill in the fields in the sections of the **Privacy** page, as described below. -**Important:** All information in the **Privacy** page must be complete, accurate, and consistent with the extension's behavior and metadata. Any incomplete, misleading, or inaccurate disclosures may be considered a violation of [Developer policies for the Microsoft Edge Add-ons store](/legal/microsoft-edge/extensions/developer-policies), and can result in additional review, delayed certification, or rejection of the submitted extension. +**Important:** All information in the **Privacy** page must be complete, accurate, and consistent with the extension's behavior and metadata. Any incomplete, misleading, or inaccurate disclosures may be considered a violation of [Developer policies for the Microsoft Edge Add-ons website](/legal/microsoft-edge/extensions/developer-policies), and can result in additional review, delayed certification, or rejection of the submitted extension. @@ -407,7 +387,7 @@ The **Privacy policy** section of the **Privacy** page: 1. Ensure that the policy content is up-to-date. - This policy is displayed to users in the extension's listing at the Microsoft Edge Add-ons site. + This policy is displayed to users in the extension's listing at the Microsoft Edge Add-ons website. A privacy policy and its URL is required if the extension collects any privacy information. This is a valid privacy policy URL to communicate how the extension follows privacy laws and regulations. @@ -417,7 +397,7 @@ The **Privacy policy** section of the **Privacy** page: To determine if the extension requires a privacy policy, see: * [Microsoft Store App Developer Agreement](https://go.microsoft.com/fwlink/?linkid=528905) - * [Developer policies for the Microsoft Edge Add-ons store](/legal/microsoft-edge/extensions/developer-policies) + * [Developer policies for the Microsoft Edge Add-ons website](/legal/microsoft-edge/extensions/developer-policies) You have now filled in the sections of the **Privacy** page for the extension at Partner Center. @@ -454,19 +434,19 @@ In one or more **Details for \** pages, fill in the properties. 1. Fill in the properties, as follows. - This information is displayed to users who view the extension's listing at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). Even though some fields are optional, you should provide as much information as possible. + This information is displayed to users who view the extension's listing at the Microsoft Edge Add-ons website. Even though some fields are optional, you should provide as much information as possible. | Property name | Required? | Description | |---|---|---| | **Extension name** | Required for at least one language | The name of the extension, as specified in the manifest file of the extension. To change the extension name after submitting the extension, you can update the name in the manifest file, create a new extension package, and then re-upload the package. | | **Description** | Required for each language | Explains what the extension does, why users should install it, and any other relevant information users need to know.
* **Length:** Minimum 250 characters, maximum 10,000 characters.
* **Clarity:** Must clearly describe the full functionality of the extension.
* **Completeness:** Must be thorough and include all important details.
* **Appropriateness:** Must not contain any misleading or inappropriate content.
You can use the [Generate with AI](#generate-the-description-with-ai) button. | | **Extension logo** | Required for each language | An image (one per language) that represents your company or extension logo, with an aspect ratio of 1:1 and a recommended size of 300 x 300 pixels, with a minimum size of 128 x 128 pixels. You can copy the logo from one language to all other languages by using the **Duplicate** option, which is displayed below the field after you upload the logo. | - | **Small promotional tile** | Optional | The image (one per language) that's used to display the extension alongside other extensions at Microsoft Edge Add-ons. The size of the image must be 440 x 280 pixels. You can copy the tile from one language to all other languages by using the **Duplicate** option, which is displayed below the field after you upload the tile. | - | **Large promotional tile** | Optional | The image (one per language) that's used to display the extension more prominently at Microsoft Edge Add-ons. The image, if submitted, is visible to users. The size of the PNG files must be 1400 x 560 pixels. You can copy the tile from one language to all other languages by using the **Duplicate** option, which is displayed below the field after you upload the tile. | + | **Small promotional tile** | Optional | The image (one per language) that's used to display the extension alongside other extensions at the Microsoft Edge Add-ons website. The size of the image must be 440 x 280 pixels. You can copy the tile from one language to all other languages by using the **Duplicate** option, which is displayed below the field after you upload the tile. | + | **Large promotional tile** | Optional | The image (one per language) that's used to display the extension more prominently at the Microsoft Edge Add-ons website. The image, if submitted, is visible to users. The size of the PNG files must be 1400 x 560 pixels. You can copy the tile from one language to all other languages by using the **Duplicate** option, which is displayed below the field after you upload the tile. | | **Screenshots** | Optional | You can submit a maximum of 6 screenshots describing the functionality of the extension in detail. The size of the screenshots must be either 640 x 480 pixels or 1280 x 800 pixels. You can copy a screenshot from one language to all other languages by using the **Duplicate** option, which is displayed below the field after you upload at least one screenshot. | | **YouTube video URL** | Optional | You can include a promotional YouTube video of the extension. The URL and thumbnail of the YouTube video is displayed on the extension's store listing page. | | **Short description** | Required for at least one language | To edit the short description, you must update the description field in the manifest file of the extension package, and then re-upload the package. | - | **Search terms** | Optional | Single words or phrases that help users discover the extension when searching at Microsoft Edge Add-ons. The search terms aren't displayed to users. | + | **Search terms** | Optional | Single words or phrases that help users discover the extension when searching at the Microsoft Edge Add-ons website. The search terms aren't displayed to users. | The following Required properties must be provided for _each_ language (such as U.S. English; `en-US`) that's listed in the extension's `.zip` package: * **Description** @@ -589,7 +569,7 @@ To duplicate an asset across languages: If you are linking to a video, make sure your video meets the following requirements: -* Verify that the content of the YouTube video follows the [Developer policies for the Microsoft Edge Add-ons store](/legal/microsoft-edge/extensions/developer-policies). +* Verify that the content of the YouTube video follows the [Developer policies for the Microsoft Edge Add-ons website](/legal/microsoft-edge/extensions/developer-policies). * Turn off advertisements on your video. For more information, see [YouTube advertising formats](https://support.google.com/youtube/answer/2467968?ref_topic=7072227) and [Ads on embedded videos](https://support.google.com/youtube/answer/132596). @@ -673,7 +653,7 @@ To add notes for certification: The extension proceeds to the certification step. The certification process can take up to seven business days after you submit the extension. - After the extension passes certification, the extension is published at the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) site, and the status of the extension in the Partner Center dashboard changes to **In the Store**. + After the extension passes certification, the extension is published at the Microsoft Edge Add-ons website, and the status of the extension in the Partner Center dashboard changes to **In the Store**. @@ -722,7 +702,7 @@ See also: ## If the extension is flagged as potentially malware -If the extension is flagged as malware or a potentially unwanted application (PUA), review [1.2.2 Unwanted and malicious software](/legal/microsoft-edge/extensions/developer-policies#122-unwanted-and-malicious-software) in _Developer policies for the Microsoft Edge Add-ons store_. +If the extension is flagged as malware or a potentially unwanted application (PUA), review [1.2.2 Unwanted and malicious software](/legal/microsoft-edge/extensions/developer-policies#122-unwanted-and-malicious-software) in _Developer policies for the Microsoft Edge Add-ons website_. Make sure that your extension's code and functionality complies with all requirements and guidelines. For security reasons, Microsoft doesn't disclose exact triggers. @@ -730,7 +710,7 @@ Make sure that your extension's code and functionality complies with all require ## Responsible AI for the AI-generated description of an extension -The description of your extension at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) can optionally be generated by using AI. You can compose the description manually, or you can use AI to help generate the description. This AI-generated description feature uses responsible AI, as described below. +The description of your extension at the Microsoft Edge Add-ons website can optionally be generated by using AI. You can compose the description manually, or you can use AI to help generate the description. This AI-generated description feature uses responsible AI, as described below. @@ -738,7 +718,7 @@ The description of your extension at [Microsoft Edge Add-ons](https://microsofte To use AI to help generate a description of the extension for a particular language, you provide prompt input text, generate a description, and then edit the resulting AI-generated description. The steps are detailed in [Generate the description with AI](#generate-the-description-with-ai), above. -As a Microsoft Edge extension developer, you use Microsoft Partner Center to make your extension available to users at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). To submit an extension, you provide data for the extension's listing page, including the extension name, description, and screenshots. +As a Microsoft Edge extension developer, you use Microsoft Partner Center to make your extension available to users at the Microsoft Edge Add-ons website. To submit an extension, you provide data for the extension's listing page, including the extension name, description, and screenshots. A high-quality description for the extension is important, for the users to understand the features and functionality of the extension, and to make an informed decision whether to install the extension. @@ -758,7 +738,7 @@ The AI-generated description is based on the following inputs for the AI model: * The uploaded extension package, including the manifest, code files, and image files. These image files are part of the extension. -* Any screenshots of the running extension that you've uploaded via the **Details for \** page. These screenshots are displayed at the Microsoft Edge Add-ons site. +* Any screenshots of the running extension that you've uploaded via the **Details for \** page. These screenshots are displayed at the Microsoft Edge Add-ons website. * Any input prompt text that you enter. @@ -811,11 +791,11 @@ Partner Center: * [Partner Center developer dashboard](https://partner.microsoft.com/dashboard/microsoftedge/public/login?ref=dd) Microsoft Edge extensions: -* [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) - Browse and install extensions for Microsoft Edge. +* [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) website Developer Agreement & Legal: * [Microsoft Store App Developer Agreement](https://go.microsoft.com/fwlink/?linkid=528905) -* [Developer policies for the Microsoft Edge Add-ons store](/legal/microsoft-edge/extensions/developer-policies) +* [Developer policies for the Microsoft Edge Add-ons website](/legal/microsoft-edge/extensions/developer-policies) Support.microsoft.com: * [Extensions New Support Request](https://support.microsoft.com/supportrequestform/e7a381be-9c9a-fafb-ed76-262bc93fd9e4) diff --git a/microsoft-edge/extensions/publish/reply-user-reviews.md b/microsoft-edge/extensions/publish/reply-user-reviews.md index aac1d7f710..6fedae2c05 100644 --- a/microsoft-edge/extensions/publish/reply-user-reviews.md +++ b/microsoft-edge/extensions/publish/reply-user-reviews.md @@ -10,7 +10,7 @@ ms.date: 11/07/2022 --- # Reply to user reviews of an extension -You can view and respond to user reviews of your extension that are at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). To view your extension's reviews and ratings and engage with the user who did the review, use the Partner Center dashboard. +You can view and respond to user reviews of your extension that are at the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) website. To view your extension's reviews and ratings and engage with the user who did the review, use the Partner Center dashboard. To view your extension's **Reviews** page: @@ -52,7 +52,7 @@ To reply to a user review: A response must be between one and one thousand (1-1000) characters long. -When you post a reply using the Partner Center dashboard, your reply appears on your extension's page at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) within 15 to 20 minutes. +When you post a reply using the Partner Center dashboard, your reply appears on your extension's page at the Microsoft Edge Add-ons website within 20 minutes. diff --git a/microsoft-edge/extensions/publish/submission-states.md b/microsoft-edge/extensions/publish/submission-states.md index dd3daad66e..42616a4fcc 100644 --- a/microsoft-edge/extensions/publish/submission-states.md +++ b/microsoft-edge/extensions/publish/submission-states.md @@ -1,5 +1,5 @@ --- -title: Submission states for extensions at Microsoft Edge Add-ons +title: Status for submitted extensions description: The various processing states when submitting an extension at Microsoft Edge Add-ons. author: MSEdgeTeam ms.author: msedgedevrel @@ -8,21 +8,21 @@ ms.service: microsoft-edge ms.subservice: extensions ms.date: 11/04/2022 --- -# Submission states for extensions at Microsoft Edge Add-ons +# Status for submitted extensions -The overview page on the Partner Center displays the state of your extension in the overall submission flow. This article describes the different states your extension can be in at any time during the submission and certification process. +The overview page on the Partner Center displays the state of your extension in the overall submission flow. The following are the different states your extension can be in at any time during the submission and certification process. -In articles about Microsoft Edge extensions, and at Partner Center, the word _store_ includes [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). +After this process, the extension appears at the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) website. | # | State | Details | |---|---|---| -| 1 | In draft | You create your submission and save a draft to your account. You haven't submitted your extension package and your submission form details to publish at Microsoft Edge Add-ons. Your extension isn't available to users in this state. | +| 1 | In draft | You create your submission and save a draft to your account. You haven't submitted your extension package and your submission form details to publish at the Microsoft Edge Add-ons website. Your extension isn't available to users in this state. | | 2| In review | You've submitted your extension. Your extension package and your submission form details are reviewed by Microsoft. Your extension isn't available to users in this state. | -| 3| Waiting to publish | Your submitted extension is in this state after your extension review is complete, and your extension is being prepared for publishing at Microsoft Edge Add-ons. This state is an intermediate state between `In review` and `In the store`. This state might not appear for all submissions. | -| 4| In the store | The review is now complete, and your extension is published at Microsoft Edge Add-ons. Your extension is available at Microsoft Edge Add-ons in the markets that you specified. | -| 5 | In the store. Update in review | Your extension is published at Microsoft Edge Add-ons and you've submitted an update that is under review by Microsoft. | +| 3| Waiting to publish | Your submitted extension is in this state after your extension review is complete, and your extension is being prepared for publishing at the Microsoft Edge Add-ons website. This state is an intermediate state between `In review` and `In the store`. This state might not appear for all submissions. | +| 4| In the store | The review is now complete, and your extension is published at the Microsoft Edge Add-ons website. Your extension is available at the Microsoft Edge Add-ons website in the markets that you specified. | +| 5 | In the store. Update in review | Your extension is published at the Microsoft Edge Add-ons website and you've submitted an update that is under review by Microsoft. | | 6 | Review failed | Your submitted extension is in this state if your extension fails a review. A failed review might occur during the initial review or during an update. You need to take corrective action and resubmit your extension. | | 7 | Unavailable in store | There are three possible scenarios when your extension displays this state: **Unpublished from store**, **Removed from store**, and **Blocked**. The description of each of the three states is specified in 8, 9, and 10. | -| 8 | Unpublished from store | You unpublished your extension at Microsoft Edge Add-ons in Partner Center. In Partner Center, you chose **unpublish** on the extension submission page. After unpublishing your extension, it's no longer available at Microsoft Edge Add-ons for new users to download, but existing users can continue to use their copies of your extension. | -| 9 | Removed from store | If your extension is found to violate the terms and conditions for items at Microsoft Edge Add-ons, Microsoft might remove the extension from Microsoft Edge Add-ons, and the state then changes to this state.
After removal of your extension by Microsoft, your extension is no longer available at Microsoft Edge Add-ons for new users to download, but existing users can continue to use their copies of your extension. | -| 10 | Blocked | If your extension is found to be malicious and compromises the security and privacy of users, Microsoft has the right to block your extension from Microsoft Edge Add-ons, and the state changes to this state. If your extension is blocked, it's removed from Microsoft Edge Add-ons and from all user devices. | +| 8 | Unpublished from store | You unpublished your extension at the Microsoft Edge Add-ons website, via Partner Center. In Partner Center, you chose **unpublish** on the extension submission page. After unpublishing your extension, it's no longer available at the Microsoft Edge Add-ons website for new users to download, but existing users can continue to use their copies of your extension. | +| 9 | Removed from store | If your extension is found to violate the terms and conditions for items at the Microsoft Edge Add-ons website, Microsoft might remove the extension from the Microsoft Edge Add-ons website, and the state then changes to this state.
After removal of your extension by Microsoft, your extension is no longer available at the Microsoft Edge Add-ons website for new users to download, but existing users can continue to use their copies of your extension. | +| 10 | Blocked | If your extension is found to be malicious and compromises the security and privacy of users, Microsoft has the right to block your extension from the Microsoft Edge Add-ons website, and the state changes to this state. If your extension is blocked, it's removed from the Microsoft Edge Add-ons website and from all user devices. | diff --git a/microsoft-edge/extensions/publish/verify-microsoft-edge-program.md b/microsoft-edge/extensions/publish/verify-microsoft-edge-program.md index 2635cafe4d..c303f40dbf 100644 --- a/microsoft-edge/extensions/publish/verify-microsoft-edge-program.md +++ b/microsoft-edge/extensions/publish/verify-microsoft-edge-program.md @@ -1,6 +1,6 @@ --- title: Verify your company account information -description: Learn how to verify your account information when your company enrolls in the Microsoft Edge program on Partner Center to publish extensions at Microsoft Edge Add-ons. +description: Learn how to verify your account information when your company enrolls in the Microsoft Edge program on Partner Center to publish extensions at the Microsoft Edge Add-ons website. author: MSEdgeTeam ms.author: msedgedevrel ms.topic: article @@ -16,7 +16,7 @@ When you enroll in the Microsoft Edge program on Partner Center to publish exten You can go to [Legal info](https://partner.microsoft.com/dashboard/account/v3/organization/legalinfo#developer) in Partner Center to monitor verification status for the Microsoft Edge Developer program. -When account verification is complete, you can use your Partner Center dashboard to publish your extension at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). +When account verification is complete, you can use your Partner Center dashboard to publish your extension at the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) website. Verification usually takes three to five business days. If more than five days have passed, you can [Contact the Microsoft Edge extensions team](../contact.md) for help. diff --git a/microsoft-edge/extensions/release-notes/archive.md b/microsoft-edge/extensions/release-notes/archive.md index 79ee710058..a1a1a8c3ba 100644 --- a/microsoft-edge/extensions/release-notes/archive.md +++ b/microsoft-edge/extensions/release-notes/archive.md @@ -1,6 +1,6 @@ --- title: Archived release notes for Microsoft Edge extensions -description: Previous enhancements and issues for the user experience (UX) at Partner Center and the Microsoft Edge Add-ons site. +description: Previous enhancements and issues for the user experience (UX) at Partner Center and the Microsoft Edge Add-ons website. author: MSEdgeTeam ms.author: msedgedevrel ms.topic: article @@ -11,7 +11,7 @@ ms.date: 01/01/2026 # Archived release notes for Microsoft Edge extensions -The following updates have been deployed to production, addressing key issues and enhancements for the [Partner Center](https://partner.microsoft.com/dashboard/microsoftedge/) and Microsoft Edge Add-ons experience. +The following updates have been deployed to production, addressing key issues and enhancements for [Partner Center](https://partner.microsoft.com/dashboard/microsoftedge/) and the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) website. **Detailed contents:** * [Feb. 2025](#feb-2025) @@ -39,7 +39,7 @@ The following updates have been deployed to production, addressing key issues an * [Apr. 2021](#apr-2021) * [Support for Manifest V3 extensions](#support-for-manifest-v3-extensions) * [Feb. 2021](#feb-2021) - * [Localization of extension listings at Microsoft Edge Add-ons](#localization-of-extension-listings-at-microsoft-edge-add-ons) + * [Localization of extension listings](#localization-of-extension-listings) * [Jan. 2021](#jan-2021) * [Extension certification report link](#extension-certification-report-link) * [See also](#see-also) @@ -136,7 +136,7 @@ As an extension developer, you can now seamlessly transfer ownership of your Mic v1.1 of this REST API provides increased security. -You can integrate REST API endpoints directly into your continuous integration/continuous delivery (CI/CD) pipeline, to publish extension package updates at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) without using Partner Center. For more information, see [Use the REST API to update an extension at Microsoft Edge Add-ons](../update/api/using-addons-api.md). +You can integrate REST API endpoints directly into your continuous integration/continuous delivery (CI/CD) pipeline, to publish extension package updates at the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) website without using Partner Center. See [Use the REST API to update an extension](../update/api/using-addons-api.md). See also: * [Update an extension by using the Microsoft Edge Add-ons API](#update-an-extension-by-using-the-microsoft-edge-add-ons-api), below. @@ -299,7 +299,7 @@ Microsoft Partner Center only accepts new Manifest V3 Microsoft Edge extension s #### You can respond to user reviews about your Microsoft Edge extension -At Partner Center, you can reply to user reviews and feedback about your extension that's posted at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). +At Partner Center, you can reply to user reviews and feedback about your extension that's published at the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) website. To share your feedback and comments about this feature, see [You can now respond to user reviews on your Microsoft Edge Add-ons page](https://github.com/microsoft/MicrosoftEdge-Extensions/discussions/18) in **Discussions** in the MicrosoftEdge-Extensions repo. @@ -317,7 +317,7 @@ To share your feedback and comments about this feature, see [You can now respond #### Update an extension by using the Microsoft Edge Add-ons API -You can integrate REST API endpoints directly into your continuous integration/continuous delivery (CI/CD) pipeline, to publish extension package updates at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) without using Partner Center. For more information, see [Use the REST API to update an extension at Microsoft Edge Add-ons](../update/api/using-addons-api.md). +You can integrate REST API endpoints directly into your continuous integration/continuous delivery (CI/CD) pipeline, to publish extension package updates at the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) website without using Partner Center. See [Use the REST API to update an extension](../update/api/using-addons-api.md). Update Sep. 2024: v1.1 of this REST API provides increased security; see [Microsoft Edge Add-ons Update API, v1.1](#microsoft-edge-add-ons-update-api-v11), above. @@ -435,9 +435,9 @@ Microsoft Edge extensions now support Manifest V3. See the blog post [Manifest -#### Localization of extension listings at Microsoft Edge Add-ons +#### Localization of extension listings -You can control localization of extension listings that are at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). You can choose a subset of languages, instead of manually entering each language in the listing details on Microsoft Partner Center. You can also elect to use the same marketing assets across all marketplaces. +You can control localization of extension listings that are at the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) website. You can choose a subset of languages, instead of manually entering each language in the listing details on Microsoft Partner Center. You can also elect to use the same marketing assets across all marketplaces. See [Partner Center improvements related to Microsoft Edge extensions store listing and certification](https://techcommunity.microsoft.com/t5/articles/partner-center-improvements-related-to-microsoft-edge-extensions/m-p/2118981). diff --git a/microsoft-edge/extensions/release-notes/index.md b/microsoft-edge/extensions/release-notes/index.md index 58e281c214..ce92f56ae3 100644 --- a/microsoft-edge/extensions/release-notes/index.md +++ b/microsoft-edge/extensions/release-notes/index.md @@ -1,6 +1,6 @@ --- title: Release notes for Microsoft Edge extensions -description: Enhancements and issues for the user experience (UX) at Partner Center and the Microsoft Edge Add-ons site. +description: Enhancements and issues for the user experience (UX) at Partner Center and the Microsoft Edge Add-ons website. author: MSEdgeTeam ms.author: msedgedevrel ms.topic: article @@ -17,7 +17,7 @@ ms.date: 01/01/2026 ## Jan. 2026 -The following updates have been deployed to production, addressing key issues and enhancements for the [Partner Center](https://partner.microsoft.com/dashboard/microsoftedge/) and Microsoft Edge Add-ons experience. +The following updates have been deployed to production, addressing key issues and enhancements for [Partner Center](https://partner.microsoft.com/dashboard/microsoftedge/) and the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) website. diff --git a/microsoft-edge/extensions/samples/picture-inserter-content-script.md b/microsoft-edge/extensions/samples/picture-inserter-content-script.md index ab7feaa9c9..bb8c44b4a1 100644 --- a/microsoft-edge/extensions/samples/picture-inserter-content-script.md +++ b/microsoft-edge/extensions/samples/picture-inserter-content-script.md @@ -173,7 +173,7 @@ See also: ## Install the sample locally (sideloading) -Instead of installing the sample from [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com), you'll install the sample locally, so that you can possibly modify it and quickly test the changes. Installing locally is sometimes called _sideloading_ an extension. +Instead of installing the sample from the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) website, you'll install the sample locally, so that you can possibly modify it and quickly test the changes. Installing locally is sometimes called _sideloading_ an extension. 1. In Microsoft Edge, click the **Extensions** (![Extensions icon](./picture-inserter-content-script-images/extensions-icon.png)) button, next to the Address bar, if this icon is displayed. Or, select **Settings and more** (![The "Settings and more" icon](./picture-inserter-content-script-images/settings-and-more-icon.png)) > ![Extensions icon](./picture-inserter-content-script-images/extensions-icon.png) **Extensions**. The **Extensions** pop-up opens: @@ -197,7 +197,7 @@ Instead of installing the sample from [Microsoft Edge Add-ons](https://microsoft The **Select the extension directory** dialog closes. - The extension is installed in the browser, similar to an extension that's installed from Microsoft Edge Add-ons: + The extension is installed in the browser, similar to an extension that's installed from the Microsoft Edge Add-ons website: ![Installed extensions page, showing a sideloaded extension](./picture-inserter-content-script-images/installed-extension.png) diff --git a/microsoft-edge/extensions/samples/picture-viewer-popup-webpage.md b/microsoft-edge/extensions/samples/picture-viewer-popup-webpage.md index 8458024586..4dfc1c48d6 100644 --- a/microsoft-edge/extensions/samples/picture-viewer-popup-webpage.md +++ b/microsoft-edge/extensions/samples/picture-viewer-popup-webpage.md @@ -148,7 +148,7 @@ See also: ## Install the sample locally (sideloading) -Instead of installing the sample from [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com), you'll install the sample locally, so that you can possibly modify it and quickly test the changes. Installing locally is sometimes called _sideloading_ an extension. +Instead of installing the sample from the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) website, you'll install the sample locally, so that you can possibly modify it and quickly test the changes. Installing locally is sometimes called _sideloading_ an extension. 1. In Microsoft Edge, click the **Extensions** (![Extensions icon](./picture-viewer-popup-webpage-images/extensions-icon.png)) button, next to the Address bar, if this icon is displayed. Or, select **Settings and more** (![The "Settings and more" icon](./picture-viewer-popup-webpage-images/settings-and-more-icon.png)) > **Extensions**. The **Extensions** pop-up opens: @@ -172,7 +172,7 @@ Instead of installing the sample from [Microsoft Edge Add-ons](https://microsoft The **Select the extension directory** dialog closes. - The extension is installed in the browser, similar to an extension that's installed from Microsoft Edge Add-ons: + The extension is installed in the browser, similar to an extension that's installed from the Microsoft Edge Add-ons website: ![Installed extensions page, showing a sideloaded extension](./picture-viewer-popup-webpage-images/installed-extension.png) diff --git a/microsoft-edge/extensions/update/api/addons-api-reference.md b/microsoft-edge/extensions/update/api/addons-api-reference.md index 070957995e..de84ca939a 100644 --- a/microsoft-edge/extensions/update/api/addons-api-reference.md +++ b/microsoft-edge/extensions/update/api/addons-api-reference.md @@ -1,6 +1,6 @@ --- -title: REST API Reference for updating an extension at Microsoft Edge Add-ons -description: The Add-ons API Reference, for REST endpoints to automate updating an extension that's at Microsoft Edge Add-ons. +title: REST API Reference for updating an extension +description: The Add-ons API Reference, for REST endpoints to automate updating an extension that's at the Microsoft Edge Add-ons website. author: MSEdgeTeam ms.author: msedgedevrel ms.topic: article @@ -8,11 +8,11 @@ ms.service: microsoft-edge ms.subservice: extensions ms.date: 09/05/2024 --- -# REST API Reference for updating an extension at Microsoft Edge Add-ons +# REST API Reference for updating an extension -This article is the REST endpoint reference for the Microsoft Edge Add-ons API. This API automates publishing updates to an extension that's at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). +This article is the REST endpoint reference for the Microsoft Edge Add-ons API. This API automates publishing updates to an extension that's at the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) website. -For an overview, see [Use the REST API to update an extension at Microsoft Edge Add-ons](./using-addons-api.md). +For an overview, see [Use the REST API to update an extension](./using-addons-api.md). @@ -27,7 +27,7 @@ As of Sep. 6, 2024, both v1.1 and v1 of this Update REST API are supported. Sup Uploads a package to update an existing draft submission of an extension. -See also [Uploading a package to update an existing submission](./using-addons-api.md#uploading-a-package-to-update-an-existing-submission) in _Use the REST API to update an extension at Microsoft Edge Add-ons_. +See also [Uploading a package to update an existing submission](./using-addons-api.md#uploading-a-package-to-update-an-existing-submission) in _Use the REST API to update an extension_. @@ -96,7 +96,7 @@ This API has the following expected status codes. See also: -* [Uploading a package to update an existing submission](./using-addons-api.md#uploading-a-package-to-update-an-existing-submission) in _Use the REST API to update an extension at Microsoft Edge Add-ons_. +* [Uploading a package to update an existing submission](./using-addons-api.md#uploading-a-package-to-update-an-existing-submission) in _Use the REST API to update an extension_. @@ -105,7 +105,7 @@ See also: Gets the status of the package upload. -See also [Checking the status of a package upload](./using-addons-api.md#checking-the-status-of-a-package-upload) in _Use the REST API to update an extension at Microsoft Edge Add-ons_. +See also [Checking the status of a package upload](./using-addons-api.md#checking-the-status-of-a-package-upload) in _Use the REST API to update an extension_. @@ -220,16 +220,16 @@ This API has the following expected status codes. See also: -* [Checking the status of a package upload](./using-addons-api.md#checking-the-status-of-a-package-upload) in _Use the REST API to update an extension at Microsoft Edge Add-ons_. +* [Checking the status of a package upload](./using-addons-api.md#checking-the-status-of-a-package-upload) in _Use the REST API to update an extension_. ## Publish the product draft submission -Publishes the current draft of the product at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). +Publishes the current draft of the product at the Microsoft Edge Add-ons website. -See also [Publishing the submission](./using-addons-api.md#publishing-the-submission) in _Use the REST API to update an extension at Microsoft Edge Add-ons_. +See also [Publishing the submission](./using-addons-api.md#publishing-the-submission) in _Use the REST API to update an extension_. @@ -296,7 +296,7 @@ This API has the following expected status codes. See also: -* [Publishing the submission](./using-addons-api.md#publishing-the-submission) in _Use the REST API to update an extension at Microsoft Edge Add-ons_. +* [Publishing the submission](./using-addons-api.md#publishing-the-submission) in _Use the REST API to update an extension_. @@ -305,7 +305,7 @@ See also: Checks the status of the publish operation. -See also [Checking the publishing status](using-addons-api.md#checking-the-publishing-status) in _Use the REST API to update an extension at Microsoft Edge Add-ons_. +See also [Checking the publishing status](using-addons-api.md#checking-the-publishing-status) in _Use the REST API to update an extension_. @@ -515,7 +515,7 @@ This API has the following expected status codes. See also: -* [Checking the publishing status](using-addons-api.md#checking-the-publishing-status) in _Use the REST API to update an extension at Microsoft Edge Add-ons_. +* [Checking the publishing status](using-addons-api.md#checking-the-publishing-status) in _Use the REST API to update an extension_. @@ -548,6 +548,6 @@ Here's a list of common error codes and possible reasons. For a full list, see ## See also -* [Use the REST API to update an extension at Microsoft Edge Add-ons](./using-addons-api.md) +* [Use the REST API to update an extension](./using-addons-api.md) * [Partner Center REST error codes](/partner-center/develop/error-codes) in Partner Center docs. * [List of HTTP status codes](https://wikipedia.org/wiki/List_of_HTTP_status_codes) at Wikipedia. diff --git a/microsoft-edge/extensions/update/api/using-addons-api.md b/microsoft-edge/extensions/update/api/using-addons-api.md index 3070a9c291..6a42db5b1e 100644 --- a/microsoft-edge/extensions/update/api/using-addons-api.md +++ b/microsoft-edge/extensions/update/api/using-addons-api.md @@ -1,6 +1,6 @@ --- -title: Use the REST API to update an extension at Microsoft Edge Add-ons -description: REST endpoints to automate updating an extension that's been published at Microsoft Edge Add-ons. +title: Use the REST API to update an extension +description: REST endpoints to automate updating an extension that's been published at the Microsoft Edge Add-ons website. author: MSEdgeTeam ms.author: msedgedevrel ms.topic: article @@ -8,9 +8,9 @@ ms.service: microsoft-edge ms.subservice: extensions ms.date: 09/19/2024 --- -# Use the REST API to update an extension at Microsoft Edge Add-ons +# Use the REST API to update an extension -Use this REST API to programmatically update an extension (or a theme) that's been published at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com), to automate the process of uploading and publishing new versions of your extension. You can integrate these REST API endpoints directly into your continuous integration/continuous delivery (CI/CD) pipeline, to publish extension package updates at Microsoft Edge Add-ons without using Partner Center. +Use this REST API to programmatically update an extension (or a theme) that's been published at the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) website, to automate the process of uploading and publishing new versions of your extension. You can integrate these REST API endpoints directly into your continuous integration/continuous delivery (CI/CD) pipeline, to publish extension package updates at the Microsoft Edge Add-ons website without using Partner Center. This REST API exposes endpoints for: * [Uploading a package to update an existing submission](#uploading-a-package-to-update-an-existing-submission) @@ -97,7 +97,7 @@ Details are below. | _operation_ | A REST operation such as GET or POST. | | _operation ID_ | The ID of a REST operation. | | _package_ | The `.zip` package that contains the files for your Microsoft Edge extension. | -| _product_, _add-on_ | A Microsoft Edge extension or theme that's published at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). | +| _product_, _add-on_ | A Microsoft Edge extension or theme that's published at the Microsoft Edge Add-ons website. | | _product ID_ | The product ID of the product whose draft needs to be published. The product ID is a 128-bit GUID that is associated with a product at Partner Center. For example: `d34f98f5-f9b7-42b1-bebb-98707202b21d`. | | _submission_ | An update that is being submitted to an existing product at Partner Center. Every update to a product is a submission, regardless of whether the status is `In Draft`, `In Review`, or `In the Store` (published). | @@ -263,7 +263,7 @@ To create a new product or update a product's metadata, you must use Microsoft P Use this REST API endpoint to update the package for an add-on. This API uploads a package to update an existing draft submission of an add-on product. -See also [Upload a package to update an existing submission](./addons-api-reference.md#upload-a-package-to-update-an-existing-submission) in _REST API Reference for updating an extension at Microsoft Edge Add-ons_. +See also [Upload a package to update an existing submission](./addons-api-reference.md#upload-a-package-to-update-an-existing-submission) in _REST API Reference for updating an extension_. @@ -341,7 +341,7 @@ If the request succeeds and the update process begins, you receive a `202 Accept See also: -* [Upload a package to update an existing submission](./addons-api-reference.md#upload-a-package-to-update-an-existing-submission) in _REST API Reference for updating an extension at Microsoft Edge Add-ons_. +* [Upload a package to update an existing submission](./addons-api-reference.md#upload-a-package-to-update-an-existing-submission) in _REST API Reference for updating an extension_. @@ -352,7 +352,7 @@ Use this API to check the status of package upload. `$operationID` is the operation ID that's returned in the response header from [Uploading a package to update an existing submission](#uploading-a-package-to-update-an-existing-submission) or [Publishing the submission](#publishing-the-submission). -See also [Check the publishing status](./addons-api-reference.md#check-the-publishing-status) in _REST API Reference for updating an extension at Microsoft Edge Add-ons_. +See also [Check the publishing status](./addons-api-reference.md#check-the-publishing-status) in _REST API Reference for updating an extension_. @@ -407,16 +407,16 @@ https://api.addons.microsoftedge.microsoft.com/v1/products/$productID/submission --- See also: -* [Check the status of a package upload](./addons-api-reference.md#check-the-status-of-a-package-upload) in _REST API Reference for updating an extension at Microsoft Edge Add-ons_. +* [Check the status of a package upload](./addons-api-reference.md#check-the-status-of-a-package-upload) in _REST API Reference for updating an extension_. ## Publishing the submission -Use this API to publish the current draft of the product at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). +Use this API to publish the current draft of the product at the Microsoft Edge Add-ons website. -See also [Publish the product draft submission](./addons-api-reference.md#publish-the-product-draft-submission) in _REST API Reference for updating an extension at Microsoft Edge Add-ons_. +See also [Publish the product draft submission](./addons-api-reference.md#publish-the-product-draft-submission) in _REST API Reference for updating an extension_. @@ -477,7 +477,7 @@ https://api.addons.microsoftedge.microsoft.com/v1/products/$productID/submission If the request succeeds and the publishing process begins, you'll receive a `202 Accepted` response status code with a `Location` header. This location header contains the `operationID` that's required for checking the status of the publish operation. See also: -* [Publish the product draft submission](./addons-api-reference.md#publish-the-product-draft-submission) in _REST API Reference for updating an extension at Microsoft Edge Add-ons_. +* [Publish the product draft submission](./addons-api-reference.md#publish-the-product-draft-submission) in _REST API Reference for updating an extension_. @@ -488,7 +488,7 @@ Use this API to check the status of the publish operation. `$operationID` is the operation ID that's returned in the response header from [Uploading a package to update an existing submission](#uploading-a-package-to-update-an-existing-submission) or [Publishing the submission](#publishing-the-submission). -See also [Check the publishing status](./addons-api-reference.md#check-the-publishing-status) in _REST API Reference for updating an extension at Microsoft Edge Add-ons_. +See also [Check the publishing status](./addons-api-reference.md#check-the-publishing-status) in _REST API Reference for updating an extension_. @@ -543,7 +543,7 @@ https://api.addons.microsoftedge.microsoft.com/v1/products/$productID/submission --- See also: -* [Check the publishing status](./addons-api-reference.md#check-the-publishing-status) in _REST API Reference for updating an extension at Microsoft Edge Add-ons_. +* [Check the publishing status](./addons-api-reference.md#check-the-publishing-status) in _REST API Reference for updating an extension_. @@ -673,7 +673,7 @@ $publishStatus ## See also -* [REST API Reference for updating an extension at Microsoft Edge Add-ons](./addons-api-reference.md) - REST API for updating an extension. +* [REST API Reference for updating an extension](./addons-api-reference.md) - REST API for updating an extension. * [Supported APIs for Microsoft Edge extensions](../../developer-guide/api-support.md) - JavaScript APIs for developing an extension. GitHub: diff --git a/microsoft-edge/extensions/update/auto-update.md b/microsoft-edge/extensions/update/auto-update.md index 23facdb3b3..e6c81e3eb2 100644 --- a/microsoft-edge/extensions/update/auto-update.md +++ b/microsoft-edge/extensions/update/auto-update.md @@ -1,6 +1,6 @@ --- title: Set an externally installed extension to automatically update -description: Set up an externally installed extension (an extension that doesn't use Partner Center and isn't published at Microsoft Edge Add-ons) to automatically update in users' instances of Microsoft Edge. +description: Set up an externally installed extension (an extension that doesn't use Partner Center and isn't published at the Microsoft Edge Add-ons website) to automatically update in users' instances of Microsoft Edge. author: MSEdgeTeam ms.author: msedgedevrel ms.topic: article @@ -40,12 +40,15 @@ When you set your extension to automatically update on users' machines, your ext * Add new features or performance enhancements. * Improve the user interface. -Your extensions are hosted at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com), and you can update your extension using the same mechanism as Microsoft Edge. You don't control the update mechanism. +Your extensions are hosted at the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) website, and you can update your extension using the same mechanism as Microsoft Edge. You don't control the update mechanism. (Previously, non-store-based extensions were supported. Also, previously, you updated the native binaries and the extension at the same time.) -> [!IMPORTANT] -> Be careful when you update extensions that have a dependency on native binaries. + + +#### Updating an extension that has a dependency on native binaries + +Be careful when you update an extension that has a dependency on native binaries. diff --git a/microsoft-edge/extensions/update/transfer-ownership.md b/microsoft-edge/extensions/update/transfer-ownership.md index 05d34e83f5..36a486c4ae 100644 --- a/microsoft-edge/extensions/update/transfer-ownership.md +++ b/microsoft-edge/extensions/update/transfer-ownership.md @@ -65,7 +65,7 @@ For questions about this process, contact [ext_dev_support@microsoft.com](mailto After the ownership transfer, the new owner should publish an update of the extension promptly, to ensure that accurate and up-to-date information is displayed. -Changes to the following fields of the extension's listing don't automatically appear in the Microsoft Edge Add-ons site when the ownership is transferred: +Changes to the following fields of the extension's listing don't automatically appear at the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) website when the ownership is transferred: * Description. * Screenshots. * Privacy policy URL. diff --git a/microsoft-edge/extensions/update/update-extension.md b/microsoft-edge/extensions/update/update-extension.md index 3a70913754..db3cd982b6 100644 --- a/microsoft-edge/extensions/update/update-extension.md +++ b/microsoft-edge/extensions/update/update-extension.md @@ -1,6 +1,6 @@ --- title: Update a Microsoft Edge extension -description: How to update or remove an extension that's at Microsoft Edge Add-ons. +description: How to update or remove an extension that's at the Microsoft Edge Add-ons website. author: MSEdgeTeam ms.author: msedgedevrel ms.topic: article @@ -10,16 +10,15 @@ ms.date: 11/04/2022 --- # Update a Microsoft Edge extension -You can update or remove a published extension listing that's at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) at any time. +You can update or remove a published extension listing that's at the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) website at any time. -See also: -* [Set an externally installed extension to automatically update](./auto-update.md) - for an extension that doesn't use Partner Center and isn't at Microsoft Edge Add-ons. +For an extension that doesn't use Partner Center and isn't at the Microsoft Edge Add-ons website, see [Set an externally installed extension to automatically update](./auto-update.md). -## Update an existing extension at Microsoft Edge Add-ons +## Update an existing extension at the Microsoft Edge Add-ons website -To update an extension that's at Microsoft Edge Add-ons: +To update an extension that's at the Microsoft Edge Add-ons website: 1. Go to your [Partner Center developer dashboard](https://partner.microsoft.com/dashboard/microsoftedge/public/login?ref=dd) and select the extension that you want to update. @@ -27,15 +26,15 @@ To update an extension that's at Microsoft Edge Add-ons: 1. After you make the changes, click **Publish** to update your extension listing and start the certification process. The certification process for an update to an extension can take up to 7 business days. -1. After the `Status` column displays `In the store`, your extension update is available at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). +1. After the `Status` column displays `In the store`, the extension update is available at the Microsoft Edge Add-ons website. -After your extension has been created initially, you can update your extension by [Use the REST API to update an extension at Microsoft Edge Add-ons](./api/using-addons-api.md). +After your extension has been published, you can update the extension via the REST API; see [Use the REST API to update an extension](./api/using-addons-api.md). ## Update your extension during the certification step -While your extension is in the certification stage, and before it gets published at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com), you can update your submitted extension. You might also need to update your extension if your extension fails the certification process. +While your extension is in the certification stage, and before it gets published at the Microsoft Edge Add-ons website, you can update your submitted extension. You might also need to update your extension if your extension fails the certification process. To check the status of your extension: @@ -70,7 +69,7 @@ To edit your extension: -## Remove an extension that's at Microsoft Edge Add-ons +## Remove an extension that's at the Microsoft Edge Add-ons website To remove an extension: @@ -80,13 +79,16 @@ To remove an extension: 1. Select **Unpublish** to remove the listing. -The extension is now removed and is no longer present at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). Users who already installed your extension can continue to use it, but the extension isn't available to new users. +The extension is now removed and is no longer present at the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) website. Users who already installed your extension can continue to use it, but the extension isn't available to new users. ## See also -* [Set an externally installed extension to automatically update](./auto-update.md) - for an extension that doesn't use Partner Center and isn't at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). -* [Use the REST API to update an extension at Microsoft Edge Add-ons](./api/using-addons-api.md) +* [Set an externally installed extension to automatically update](./auto-update.md) +* [Use the REST API to update an extension](./api/using-addons-api.md) + +External: +* [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) website * [Partner Center developer dashboard](https://partner.microsoft.com/dashboard/microsoftedge/public/login?ref=dd) diff --git a/microsoft-edge/index.yml b/microsoft-edge/index.yml index c0fa952f1e..369eb3ff52 100644 --- a/microsoft-edge/index.yml +++ b/microsoft-edge/index.yml @@ -5,7 +5,7 @@ summary: Documentation, references, and code samples to help IT administrators d brand: m365 metadata: title: Microsoft Edge documentation - description: Microsoft Edge information for developers, IT administrators, and browser users; including DevTools, Edge Add-ons (such as extensions), PWAs, WebDriver, and more. + description: Microsoft Edge information for developers, IT administrators, and browser users; including DevTools, Edge Add-ons (extensions), PWAs, WebDriver, and more. ms.topic: hub-page author: MSEdgeTeam ms.author: msedgedevrel diff --git a/microsoft-edge/toc.yml b/microsoft-edge/toc.yml index 296ae02be5..5cfe6dc5be 100644 --- a/microsoft-edge/toc.yml +++ b/microsoft-edge/toc.yml @@ -1320,7 +1320,7 @@ href: /legal/microsoft-edge/extensions/ada-addendum displayName: policy, policies - - name: Developer policies for the Microsoft Edge Add-ons store + - name: Developer policies for the Microsoft Edge Add-ons website href: /legal/microsoft-edge/extensions/developer-policies displayName: policy # ----------------------------------------------------------------------------- @@ -1351,16 +1351,16 @@ - name: Extension hosting href: ./extensions/publish/hosting-and-updating.md - - name: Submission states for extensions at Microsoft Edge Add-ons + - name: Status for submitted extensions href: ./extensions/publish/submission-states.md - name: Alternative ways to distribute an extension href: ./extensions/developer-guide/alternate-distribution-options.md - - name: Curation and review process for extensions at Microsoft Edge Add-ons + - name: Curation and review process for extensions href: ./extensions/publish/add-ons-curation.md - - name: Use the Microsoft Edge Add-ons badge to promote your add-on + - name: Use the Microsoft Edge Add-ons badge to promote your extension href: ./extensions/publish/add-ons-badge.md # ------------------------------------- - name: Update an extension @@ -1370,10 +1370,10 @@ # ------------------------------------- - name: REST API for updating an extension items: - - name: Use the REST API to update an extension at Microsoft Edge Add-ons + - name: Use the REST API to update an extension href: ./extensions/update/api/using-addons-api.md - - name: REST API Reference for updating an extension at Microsoft Edge Add-ons + - name: REST API Reference for updating an extension href: ./extensions/update/api/addons-api-reference.md # ------------------------------------- - name: Set an externally installed extension to automatically update diff --git a/microsoft-edge/web-platform/sidebar.md b/microsoft-edge/web-platform/sidebar.md index 5d1d52f2bd..80b8d1620a 100644 --- a/microsoft-edge/web-platform/sidebar.md +++ b/microsoft-edge/web-platform/sidebar.md @@ -27,10 +27,10 @@ The two different ways in which you can leverage the sidebar are designed to mee | Aspect | Sidebar app | Sidebar extension | |---|---|---| | Term definition | A Progressive Web App (PWA) that runs in the sidebar. | A Microsoft Edge extension that displays content in the sidebar. | -| Distribution | Like a website, the app is hosted on the app's web server. | The extension is distributed at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). | +| Distribution | Like a website, the app is hosted on the app's web server. | The extension is distributed at the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) website. | | Capabilities | The app can make use of all web APIs and features, as well as PWA capabilities such as offline support, push, or file system access. | The extension can make use of powerful extension APIs, such as reading or modifying the current page. | | Context | The app runs in its own web context, separate from the main tab. | The extension can access the current webpage and modify the webpage via the extension's content script. | -| Installation | The user installs the app by interacting with the sidebar when visiting the app's website. | The extension is installed by users from Microsoft Edge Add-ons. | +| Installation | The user installs the app by interacting with the sidebar when visiting the app's website. | The extension is installed by users from the Microsoft Edge Add-ons website. | | User experience | The app has its own icon in the sidebar. Clicking the icon opens the sidebar if it was closed and displays the app's contents. | The user experience depends on the extension. The extension can open the sidebar depending on the websites the user visits in the browser. | | Technologies used | Web development and PWA. See [Overview of Progressive Web Apps (PWAs)](../progressive-web-apps/index.md). | Extension development. See [Overview of Microsoft Edge extensions](../extensions/index.md). | @@ -50,9 +50,9 @@ To learn more about PWAs and how to create them, see [Overview of Progressive We Microsoft Edge extensions can optionally use the sidebar API to show a custom UI in the sidebar in Microsoft Edge. This is in addition to the other places extensions also appear in, such as in the Microsoft Edge toolbar, or as popups. -If your app's experience relies on powerful extensions APIs, for example to read or modify the current page, then a sidebar extension provides these capabilities. Users can find and install these extensions at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com). +If your app's experience relies on powerful extensions APIs, for example to read or modify the current page, then a sidebar extension provides these capabilities. Users can find and install these extensions at the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) website. -The Microsoft Edge team continues to evolve these sidebar extensibility models and welcomes your feedback. To leave feedback, [create a new issue](https://github.com/MicrosoftEdge/MSEdgeExplainers/issues/new/) on the repo, or [search for existing issues](https://github.com/MicrosoftEdge/MSEdgeExplainers/issues) and join existing conversations. +The Microsoft Edge team continues to evolve these sidebar extensibility models and welcomes your feedback. To provide feedback, [create a new issue](https://github.com/MicrosoftEdge/MSEdgeExplainers/issues/new/) on the repo, or [search for existing issues](https://github.com/MicrosoftEdge/MSEdgeExplainers/issues) and join existing conversations. To learn more about Microsoft Edge extensions and how to create them, see [Overview of Microsoft Edge extensions](../extensions/index.md).