[all hosts] (Event-based activation) Consolidate Outlook and WXP autorun information (#5269)

* Consolidate Outlook and WXP autorun information

* Update links and troubleshooting article

* Fix links

* Update docs/word/add-headers-on-document-open.md

Co-authored-by: Copilot <[email protected]>

* Fix more links

* Consolidate Outlook and WXP autorun documentation

* Apply suggestions from code review

Co-authored-by: Sam Ramon <[email protected]>

* PR feedback

* Update docs/word/add-headers-on-document-open.md

Co-authored-by: Copilot <[email protected]>

* Apply suggestions from code review

* Fix links

* Apply suggestions from code review

Co-authored-by: Sam Ramon <[email protected]>
Co-authored-by: Copilot <[email protected]>

* PR feedback

---------

Co-authored-by: Copilot <[email protected]>
Co-authored-by: Sam Ramon <[email protected]>

Author: 3 people

.openpublishing.redirection.json

@@ -483,6 +483,14 @@
             "source_path": "docs/outlook/add-in-commands-for-outlook.md",
             "redirect_url": "/office/dev/add-ins/develop/create-addin-commands"
         },
+        {
+            "source_path": "docs/outlook/troubleshoot-event-based-and-spam-reporting-add-ins.md",
+            "redirect_url": "/office/dev/add-ins/testing/troubleshoot-event-based-and-spam-reporting-add-ins"
+        },
+        {
+            "source_path": "docs/outlook/autolaunch.md",
+            "redirect_url": "/office/dev/add-ins/develop/event-based-activation"
+        },
         {
             "source_path": "docs/publish/centralized-deployment.md",
             "redirect_url": "/office/dev/add-ins/publish/publish"
@@ -1290,6 +1298,14 @@
             "source_path": "docs/reference/overview/project-add-ins-reference-overview.md",
             "redirect_url": "/office/dev/add-ins/project/overview"
         },
+        {
+            "source_path": "docs/outlook/autolaunch-store-options.md",
+            "redirect_url": "/office/dev/add-ins/publish/autolaunch-store-options"
+        },
+        {
+            "source_path": "docs/outlook/debug-autolaunch.md",
+            "redirect_url": "/office/dev/add-ins/testing/debug-autolaunch"
+        },
         {
             "source_path": "docs/outlook/match-strings-in-an-item-as-well-known-entities.md",
             "redirect_url": "/office/dev/add-ins/outlook/contextual-outlook-add-ins"
@@ -1302,6 +1318,10 @@
             "source_path": "docs/outlook/use-regular-expressions-to-show-an-outlook-add-in.md",
             "redirect_url": "/office/dev/add-ins/outlook/contextual-outlook-add-ins"
         },
+        {
+            "source_path": "docs/outlook/use-sso-in-event-based-activation.md",
+            "redirect_url": "/office/dev/add-ins/develop/use-sso-in-event-based-activation"
+        },
         {
             "source_path": "docs/develop/extended-overrides.md",
             "redirect_url": "/javascript/api/manifest/extendedoverrides"

docs/concepts/browsers-used-by-office-web-add-ins.md

@@ -79,7 +79,7 @@ To determine whether Office 2016 or Office 2019 is retail or volume-licensed, us
 
 <sup>2</sup> When you use either EdgeHTML or WebView2, the Windows Narrator (sometimes called a "screen reader") reads the `<title>` tag in the page that opens in the task pane. In Trident+, the Narrator reads the title bar of the task pane, which comes from the add-in name that's specified in the add-in's manifest.
 
-<sup>3</sup> If your add-in uses an add-in only manifest and includes the **\<Runtimes\>** element in the manifest or it uses the unified manifest and it includes an "extensions.runtimes.lifetime" property, then it won't use EdgeHTML. If the conditions for using WebView2 are met, then the add-in uses WebView2. Otherwise, it uses Trident+. For more information, see [Runtimes](/javascript/api/manifest/runtimes) and [Configure your Outlook add-in for event-based activation](../outlook/autolaunch.md?tabs=jsonmanifest).
+<sup>3</sup> If your add-in uses an add-in only manifest and includes the **\<Runtimes\>** element in the manifest or it uses the unified manifest and it includes an "extensions.runtimes.lifetime" property, then it won't use EdgeHTML. If the conditions for using WebView2 are met, then the add-in uses WebView2. Otherwise, it uses Trident+. For more information, see [Runtimes](/javascript/api/manifest/runtimes) and [Activate add-ins with events](../develop/event-based-activation.md).
 
 ### Microsoft 365 subscription versions of Office on Windows
 
@@ -100,7 +100,7 @@ For subscription Office on Windows, the browser that's used is determined by the
 
 <sup>3</sup> When you use either EdgeHTML or WebView2, the Windows Narrator (sometimes called a "screen reader") reads the `<title>` tag in the page that opens in the task pane. In Trident+, the Narrator reads the title bar of the task pane, which comes from the add-in name that's specified in the add-in's manifest.
 
-<sup>4</sup> If your add-in uses an add-in only manifest and includes the **\<Runtimes\>** element in the manifest or it uses the unified manifest and it includes an "extensions.runtimes.lifetime" property, then it won't use EdgeHTML. If the conditions for using WebView2 are met, then the add-in uses WebView2. Otherwise, it uses Trident+. For more information, see [Runtimes](/javascript/api/manifest/runtimes) and [Configure your Outlook add-in for event-based activation](../outlook/autolaunch.md?tabs=jsonmanifest).
+<sup>4</sup> If your add-in uses an add-in only manifest and includes the **\<Runtimes\>** element in the manifest or it uses the unified manifest and it includes an "extensions.runtimes.lifetime" property, then it won't use EdgeHTML. If the conditions for using WebView2 are met, then the add-in uses WebView2. Otherwise, it uses Trident+. For more information, see [Runtimes](/javascript/api/manifest/runtimes) and [Activate add-ins with events](../develop/event-based-activation.md).
 
 ## Working with Trident+ (Internet Explorer 11)
 

docs/concepts/duplicate-legacy-metaos-add-ins.md

@@ -96,7 +96,7 @@ If you have users on older or perpetual license versions for which these excepti
 There are also some scenarios where you might want to maintain both both versions of the add-in for an extended period. For example, there are two features of add-ins that aren't supported with the unified manifest because they're little used or deprecated. You may choose to maintain a version of your add-in that uses these features. The following are the features that aren't supported in the unified manifest.
 
 - [Outlook modules](../outlook/extension-module-outlook-add-ins.md) aren't supported. But you can provide a nearly identical experience using the unified manifest by [including a Teams Tab with your add-in in a single app](/microsoftteams/platform/m365-apps/combine-office-add-in-and-teams-app).
-- [Outlook contextual add-ins](../outlook/contextual-outlook-add-ins.md) (also known as "activation rules") aren't supported. But you can provide similar experiences using the unified manifest and [Event-based activation](../outlook/autolaunch.md).
+- [Outlook contextual add-ins](../outlook/contextual-outlook-add-ins.md) (also known as "activation rules") aren't supported. But you can provide similar experiences using the unified manifest and [Event-based activation](../develop/event-based-activation.md).
 
 The critical requirement for making two versions available is to be sure that the two of them appear distinct in the Outlook UI.
 

docs/develop/addressing-same-origin-policy-limitations.md

@@ -42,7 +42,7 @@ Another way to address same-origin policy limitations is to provide server-side
 To learn more about cross-origin resource sharing, see the many resources available on the web, such as [Cross-Origin Resource Sharing (CORS)](https://web.dev/cross-origin-resource-sharing/).
 
 > [!NOTE]
-> For information on how to use CORS in an Outlook add-in that implements event-based activation or integrated spam reporting (preview), see [Use single sign-on (SSO) or cross-origin resource sharing (CORS) in your event-based or spam-reporting Outlook add-in](../outlook/use-sso-in-event-based-activation.md).
+> For information on how to use CORS in an Outlook add-in that implements event-based activation or integrated spam reporting (preview), see [Use single sign-on (SSO) or cross-origin resource sharing (CORS) in your event-based or spam-reporting Outlook add-in](../develop/use-sso-in-event-based-activation.md).
 
 ## Build your own proxy using IFRAME and POST MESSAGE (Cross-Window Messaging)