Skip to content

Commit d693557

Browse files
Remove email from "Contact the Microsoft Edge extensions team" (#3460)
* Update contact-extensions-team.md The form is irrelevant. Hence, removing * Update contact-extensions-team.md We are trying to remove email contact and guide all developers through GIthub * writer pass * Use Issues page specifically * add-on -> extension * h2 See also, GitHub: when use which * Sync Issues list & Discussions list w/ Readme * Discussing -> Discussions * focus Extension team or Other devs * link correct --------- Co-authored-by: Michael S. Hoffman <v-mihoffman@microsoft.com>
1 parent ac8a102 commit d693557

2 files changed

Lines changed: 47 additions & 34 deletions

File tree

microsoft-edge/extensions-chromium/publish/contact-extensions-team.md

Lines changed: 45 additions & 32 deletions
Original file line numberDiff line numberDiff line change
@@ -6,57 +6,62 @@ ms.author: msedgedevrel
66
ms.topic: conceptual
77
ms.service: microsoft-edge
88
ms.subservice: extensions
9-
ms.date: 02/11/2025
9+
ms.date: 05/30/2025
1010
---
1111
# Contact the Microsoft Edge extensions team
1212

1313
You can contact the Microsoft Edge extensions support team to request help, submit feedback, or report a copyright or trademark infringement.
1414

1515

1616
<!-- ====================================================================== -->
17-
## Inquire about an extension's review status or certification status
18-
19-
For questions about a specific developer account, or questions about the review status or certification status of your extension after submitting the extension via Partner Center, email extensions developer support at [ext_dev_support@microsoft.com](mailto:ext_dev_support@microsoft.com).
20-
21-
For questions about a specific developer account or the certification status of a specific extension, don't use the public **Issues** tab or the **Discussions** tab in the MicrosoftEdge-Extensions repo; use email instead.
17+
## Issues page in the MicrosoftEdge-Extensions repo
18+
<!-- sync:
19+
https://learn.microsoft.com/microsoft-edge/extensions-chromium/publish/contact-extensions-team#issues-page-in-the-microsoftedge-extensions-repo
20+
https://github.com/microsoft/MicrosoftEdge-Extensions/blob/main/README.md#issues
21+
-->
2222

23-
See also:
24-
* [Publish a Microsoft Edge extension](./publish-extension.md)
23+
Use the [Issues](https://github.com/microsoft/MicrosoftEdge-Extensions/issues) page of the **MicrosoftEdge-Extensions** repo for:
2524

25+
* Communicating with the Extensions team:
26+
* 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.
27+
* Report bugs or issues about Microsoft Partner Center that affect all Edge extension developers or all Microsoft Edge extension users.
28+
* Suggest new features that could impact or benefit all Microsoft Edge extension developers.
29+
* Inquire about your Partner Center developer account for Microsoft Edge extensions.
30+
* Inquire about the review status or certification status of your Edge extension after submitting the extension via Partner Center.
2631

27-
<!-- ====================================================================== -->
28-
## Send email to extensions developer support
32+
* Communicating with other extension developers:
33+
* Connect with other extension developers about technical questions related to building Microsoft Edge extensions.
34+
* Ask about aspects of extensions that affect all extension developers or all Microsoft Edge extension users.
2935

30-
To discuss issues about a specific developer account or extension, you can privately contact extensions developer support at [ext_dev_support@microsoft.com](mailto:ext_dev_support@microsoft.com).
36+
See also:
37+
* [GitHub Issues](https://docs.github.com/get-started/using-github/communicating-on-github#github-issues) in _Communicating on GitHub_.
38+
* [Scenarios for issues](https://docs.github.com/get-started/using-github/communicating-on-github#scenarios-for-issues) in _Communicating on GitHub_.
3139

3240

3341
<!-- ====================================================================== -->
3442
## Discussion forum in the MicrosoftEdge-Extensions repo
43+
<!-- sync:
44+
https://learn.microsoft.com/microsoft-edge/extensions-chromium/publish/contact-extensions-team#discussion-forum-in-the-microsoftedge-extensions-repo
45+
https://github.com/microsoft/MicrosoftEdge-Extensions/blob/main/README.md#discussions
46+
-->
3547

36-
Participate in the [Discussions](https://github.com/microsoft/MicrosoftEdge-Extensions/discussions) forum in the **MicrosoftEdge-Extensions** repo. You can:
37-
* Discuss developing extensions.
38-
* Share best practices with other developers on building, managing or acquiring more users for their browser extension.
39-
* Connect with other extension developers about technical questions related to developing a Microsoft Edge extension.
40-
* Share ideas about Microsoft Edge extensions.
41-
* Share ideas about UI features that are at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/).
42-
* Request a feature for extensions.
43-
* Share inputs or suggestions to the Microsoft Edge extensions team.
44-
* Discuss how to improve extension publishing, management and listing processes or workflows.
45-
* Provide early feedback to the Microsoft Edge extensions team about new features for managing and publishing extensions.
46-
47-
See also:
48-
* [README.md](https://github.com/microsoft/MicrosoftEdge-Extensions/blob/main/README.md) of the **MicrosoftEdge-Extensions** repo.
49-
48+
Use the [Discussions](https://github.com/microsoft/MicrosoftEdge-Extensions/discussions) page of the **MicrosoftEdge-Extensions** repo for:
5049

51-
<!-- ====================================================================== -->
52-
## Issues page in the MicrosoftEdge-Extensions repo
50+
* Discussions with the Extensions team:
51+
* Follow the latest announcements and updates from the Microsoft Edge extensions team.
52+
* Request a feature for Edge extensions.
53+
* Discuss how to improve UI features that are at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/).
54+
* Discuss how to improve extension publishing, management and listing processes or workflows.
55+
* Provide feedback about features for extensions publishing, extensions management, or processes or workflows for extensions listings.
5356

54-
To publicly report or discuss an issue about extensions, use the [Issues](https://github.com/microsoft/MicrosoftEdge-Extensions/issues) page in the **MicrosoftEdge-Extensions** repo.
57+
* Discussions with other extension developers:
58+
* Discuss technical questions about developing an Edge extension.
59+
* Share best practices, tips, and tricks with other developers on building, publishing, managing, or acquiring more users for their browser extension.
60+
* Share ideas about features for Microsoft Edge extensions.
5561

56-
Use this **Issues** page for:
57-
* Aspects of Microsoft Partner Center that affect all extension developers.
58-
* Aspects of extensions that affect all extension developers or all Microsoft Edge extension users.
59-
* Aspects of the UI that's at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/) that affect all extension developers or all Microsoft Edge extension users.
62+
See also:
63+
* [GitHub Discussions](https://docs.github.com/get-started/using-github/communicating-on-github#github-discussions) in _Communicating on GitHub_.
64+
* [Scenarios for GitHub Discussions](https://docs.github.com/get-started/using-github/communicating-on-github#scenarios-for-github-discussions) in _Communicating on GitHub_.
6065

6166

6267
<!-- ====================================================================== -->
@@ -82,3 +87,11 @@ You can follow what's happening with Microsoft Edge extensions via [#EdgeExtensi
8287
<!-- not specific to extensions -->
8388

8489
For news and updates about developing for the web with Microsoft Edge, follow the [Microsoft Edge Dev (@MSEdgeDev)](https://x.com/msedgedev/) team on X (Twitter).
90+
91+
92+
<!-- ====================================================================== -->
93+
## See also
94+
95+
* [Publish a Microsoft Edge extension](./publish-extension.md)
96+
* [README.md](https://github.com/microsoft/MicrosoftEdge-Extensions/blob/main/README.md) of the **MicrosoftEdge-Extensions** repo.
97+
* [Communicating on GitHub](https://docs.github.com/en/get-started/using-github/communicating-on-github) - When to use **Issues** vs. **Discussions**.

microsoft-edge/extensions-chromium/update/api/using-addons-api.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -109,7 +109,7 @@ To use the Microsoft Edge Add-ons API, you first need to enable the API for your
109109

110110
##### [v1.1](#tab/v1-1)
111111

112-
1. At your [Partner Center developer dashboard](https://partner.microsoft.com/dashboard/microsoftedge/public/login?ref=dd), sign in to the account that you used to publish an add-on.
112+
1. At your [Partner Center developer dashboard](https://partner.microsoft.com/dashboard/microsoftedge/public/login?ref=dd), sign in to the account that you used to publish an Edge extension.
113113

114114
1. Under the **Microsoft Edge** program, select **Publish API**.
115115

@@ -138,7 +138,7 @@ To use the Microsoft Edge Add-ons API, you first need to enable the API for your
138138

139139
##### [v1](#tab/v1)
140140

141-
1. At your [Partner Center developer dashboard](https://partner.microsoft.com/dashboard/microsoftedge/public/login?ref=dd), sign in to the account that you used to publish an add-on.
141+
1. At your [Partner Center developer dashboard](https://partner.microsoft.com/dashboard/microsoftedge/public/login?ref=dd), sign in to the account that you used to publish an Edge extension.
142142

143143
1. Under the **Microsoft Edge** program, select **Publish API**.
144144

0 commit comments

Comments
 (0)