main to live - 9/19/2025

microsoft-edge/devtools/customize/extensions.md

@@ -16,7 +16,7 @@ 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/addons/) contains extensions that typically extend 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.
 
 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.
 
@@ -26,7 +26,7 @@ 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/addons/), 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 [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.
 
    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:
 

microsoft-edge/devtools/remote-debugging/windows.md

@@ -70,9 +70,9 @@ To set up the host (debuggee) machine, use the following sub-sections, in order.
 
 1. Open the **Settings** app.  In **Find a setting**, enter `Developer settings` and select it.  Toggle on **Developer Mode**.  You can now turn on the **Device Portal** by setting **Turn on remote diagnostics over local area network connections** to **On**.  You can then optionally turn **Authentication** on so that the client (debugger) device must provide the correct credentials to connect to this device.
 
-1. If **Turn on remote diagnostics over local area network connections.** was previously turned on, you must turn it off and turn it on again for **Device Portal** to work with the [Remote Tools for Microsoft Edge (Beta)](https://www.microsoft.com/store/apps/9P6CMFV44ZLT).
+1. If **Turn on remote diagnostics over local area network connections.** was previously turned on, you must turn it off and turn it on again for **Device Portal** to work with [Remote Tools for Microsoft Edge](https://apps.microsoft.com/detail/9p6cmfv44zlt).
 
-   If  a **For developers** section isn't displayed in **Settings**, **Device Portal** may already be turned on, so try restarting the Windows 10 or later device instead.
+   If a **For developers** section isn't displayed in **Settings**, **Device Portal** may already be turned on, so try restarting the Windows 10 or later device instead.
 
    ![The Settings app with Developer Mode and Device Portal configured](./windows-images/remote-debugging-windows-media-host-settings.png)
 

microsoft-edge/devtools/whats-new/2023/01/devtools-109.md

@@ -132,7 +132,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/addons/).
+* [Heap Snapshot Visualizer](https://microsoftedge.microsoft.com/addons/detail/heap-snapshot-visualizer/fceldlhognbemkgfacnffkdanocidgce) at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com).
 
 
 <!-- ====================================================================== -->

microsoft-edge/devtools/whats-new/2023/08/devtools-116.md

@@ -42,7 +42,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/addons/).
+* [React Developer Tools](https://microsoftedge.microsoft.com/addons/detail/react-developer-tools/gpphkfbcpidddadnkolkpfckpihlkkil) extension at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com).
 * [What's New entries about Focus Mode](/search/?scope=Microsoft%20Edge&terms=focus%20mode)
 
 

microsoft-edge/extensions/contact.md

@@ -23,7 +23,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/addons/) (the store) that affect all Edge extension developers or all Microsoft Edge extension users.
+  * 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 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.
@@ -50,7 +50,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/addons/).
+   * Discuss how to improve UI features that are at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com).
    * 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.
 
@@ -67,7 +67,7 @@ See also:
 <!-- ====================================================================== -->
 ## Report copyright or trademark infringement
 
-If you think an item at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/) 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 [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.
 
 
 <!-- ====================================================================== -->

microsoft-edge/extensions/developer-guide/alternate-distribution-options.md

@@ -14,7 +14,7 @@ ms.date: 05/05/2023
 per https://developer.chrome.com/docs/extensions/how-to/distribute/install-extensions
 -->
 
-Generally, a Microsoft Edge extension is distributed by publishing it at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/).  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 [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:
 
 1. The extension is associated with other software, and it should be installed together with the rest of the bundled software.
 
@@ -34,7 +34,7 @@ See also:
 <!-- ====================================================================== -->
 ## Gather initial information
 
-Make sure that you publish your extension at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/)<!-- todo: but Intro says other scenarios -->, 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 [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com)<!-- todo: but Intro says other scenarios -->, 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:
 
@@ -58,7 +58,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/addons/).
+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).
 
     ```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/addons/) on macOS and Linux:
+   *  Copy the following code to your preferences JSON file when installing from [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) on macOS and Linux:
 
       ```json
       {

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/addons/).
+* [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).

microsoft-edge/extensions/developer-guide/best-practices.md

@@ -10,7 +10,7 @@ ms.date: 11/20/2023
 ---
 # Best practices for extensions
 
-Follow these Best Practices to implement your extension and list it at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/).
+Follow these Best Practices to implement your extension and list it at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com).
 
 
 <!-- ====================================================================== -->

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/addons/) 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.  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.
 
 For Microsoft Edge extension, host permission and content script pattern matching works as follows.
 

microsoft-edge/extensions/developer-guide/migrate-your-extension-from-manifest-v2-to-v3.md

@@ -16,7 +16,7 @@ This article lists important changes being implemented as part of Manifest V3, w
 <!-- ====================================================================== -->
 ## 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/addons/), 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 [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com), 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.
 

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/addons/), and your extension prompts users to install the host.
+*  Or, install your extension from [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com), 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/addons/).  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 [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.
 
 
 <!-- ====================================================================== -->
@@ -201,7 +201,7 @@ The `HKEY_CURRENT_USER\SOFTWARE\WOW6432Node` registry node is not searched on 64
 
 #### Extension IDs required for both stores
 
-If you have an extension both at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/) and the Chrome Web Store, you must add the extension IDs that correspond to both of the stores<!-- todo: copy 'stores' def'n to top? --> in the `allowed_origins` of the native messaging host manifest file.
+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<!-- todo: copy 'stores' def'n to top? --> 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.
 

microsoft-edge/extensions/developer-guide/port-chrome-extension.md

@@ -26,7 +26,7 @@ To port your Chrome extension:
 
 1. If you face any issues, you can debug your extensions in Microsoft Edge by using the DevTools, or [contact us](mailto:ext_dev_support@microsoft.com).
 
-1. Follow the [publishing guidelines](../publish/publish-extension.md) to publish your extension at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/).
+1. Follow the [publishing guidelines](../publish/publish-extension.md) to publish your extension at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com).
 
 
 <!-- ====================================================================== -->
@@ -38,6 +38,6 @@ If your extension exchanges messages with a native app by using `chrome.runtime.
 <!-- ====================================================================== -->
 ## Next steps
 
-After your extension package is ready to publish at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/):
+After your extension package is ready to publish at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com):
 1. [Register as a Microsoft Edge extension developer](../publish/create-dev-account.md)
 1. [Publish a Microsoft Edge extension](../publish/publish-extension.md)

microsoft-edge/extensions/getting-started/extension-sideloading.md

@@ -10,7 +10,7 @@ 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/addons/) 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 [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com) and then install the extension from there.
 
 
 <!-- ====================================================================== -->
@@ -53,7 +53,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/addons/):
+   The extension is installed in your browser, similar to extensions that are installed from [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com):
 
    ![Installed extensions page, showing a sideloaded extension](./extension-sideloading-images/installed-extension.png)