Skip to content

Commit aa90298

Browse files
[Outlook] Remove preview tag from new Outlook on Windows and spam-reporting references (#5279)
* Remove preview tag * Fix typo Co-authored-by: Copilot <[email protected]> --------- Co-authored-by: Copilot <[email protected]>
1 parent 4b4bba3 commit aa90298

6 files changed

+6
-6
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,7 @@ Another way to address same-origin policy limitations is to provide server-side
4242
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/).
4343

4444
> [!NOTE]
45-
> 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).
45+
> For information on how to use CORS in an Outlook add-in that implements event-based activation or integrated spam reporting, 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).
4646
4747
## Build your own proxy using IFRAME and POST MESSAGE (Cross-Window Messaging)
4848

docs/testing/debug-add-ins-in-office-online.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ To debug your add-in by using Office on the web:
2929

3030
> [!NOTE]
3131
> - Office on the web won't open in Internet Explorer.
32-
> - The new Outlook on Window desktop client (preview) doesn't support the context menu or the keyboard shortcut to access the Microsoft Edge developer tools. Instead, you must run `olk.exe --devtools` from a command prompt. For more information, see the "Debug your add-in" section of [Develop Outlook add-ins for the new Outlook on Windows](../outlook/one-outlook.md#debug-your-add-in).
32+
> - The new Outlook on Windows desktop client doesn't support the context menu or the keyboard shortcut to access the Microsoft Edge developer tools. Instead, you must run `olk.exe --devtools` from a command prompt. For more information, see the "Debug your add-in" section of [Develop Outlook add-ins for the new Outlook on Windows](../outlook/one-outlook.md#debug-your-add-in).
3333
3434
## Potential issues
3535

docs/testing/debug-add-ins-overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@ There are some special cases in which the debugging process differs from normal
3838
- Outlook add-ins on a Windows development computer: [Debug function commands in Outlook add-ins](../outlook/debug-ui-less.md)
3939
- Other Office application add-ins or Outlook on a Mac development computer: [Debug a function command with a non-shared runtime](debug-function-command.md).
4040
- **Debugging an event-based or spam-reporting add-in**: [Debug event-based and spam-reporting add-ins](debug-autolaunch.md).
41-
- **Debugging an add-in in the new Outlook on Windows desktop client (preview)**: See the "Debug your add-in" section of [Develop Outlook add-ins for the new Outlook on Windows](../outlook/one-outlook.md#debug-your-add-in).
41+
- **Debugging an add-in in the new Outlook on Windows desktop client**: See the "Debug your add-in" section of [Develop Outlook add-ins for the new Outlook on Windows](../outlook/one-outlook.md#debug-your-add-in).
4242
- **Debugging a Blazor-based add-in**: Debug the add-in the same way you would debug a Blazor web application. See [Debug ASP.NET Core Blazor WebAssembly](/aspnet/core/blazor/debug/).
4343

4444
## General guidance

docs/testing/debug-add-ins-using-devtools-edge-chromium.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ To determine which webview you're using, see [Browsers and webview controls used
3636
- Right-click (or select and hold) the task pane to open the context menu and select **Inspect**, or open the [personality menu](../design/task-pane-add-ins.md#personality-menu) and select **Attach Debugger**. (The personality menu isn't supported in Outlook.)
3737

3838
> [!NOTE]
39-
> The new Outlook on Window desktop client (preview) doesn't support the context menu or the keyboard shortcut to access the Microsoft Edge developer tools. Instead, you must run `olk.exe --devtools` from a command prompt. For more information, see the "Debug your add-in" section of [Develop Outlook add-ins for the new Outlook on Windows](../outlook/one-outlook.md#debug-your-add-in).
39+
> The new Outlook on Windows desktop client doesn't support the context menu or the keyboard shortcut to access the Microsoft Edge developer tools. Instead, you must run `olk.exe --devtools` from a command prompt. For more information, see the "Debug your add-in" section of [Develop Outlook add-ins for the new Outlook on Windows](../outlook/one-outlook.md#debug-your-add-in).
4040
4141
1. Open the **Sources** tab.
4242
1. Open the file that you want to debug with the following steps.

docs/testing/debug-autolaunch.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ Use your preferred browser's developer tools to debug your event-based add-in in
1818

1919
# [Windows (new)](#tab/new-windows)
2020

21-
To debug your add-in in [new Outlook on Windows desktop client (preview)](https://support.microsoft.com/office/656bb8d9-5a60-49b2-a98b-ba7822bc7627), you must run the following command to open Microsoft Edge DevTools.
21+
To debug your add-in in [new Outlook on Windows desktop client](https://support.microsoft.com/office/656bb8d9-5a60-49b2-a98b-ba7822bc7627), you must run the following command to open Microsoft Edge DevTools.
2222

2323
```command&nbsp;line
2424
olk.exe --devtools

docs/testing/runtimes.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ The following table shows the same information organized by which type of runtim
3333
|Excel custom functions | JavaScript-only</br>(but *browser* when the runtime is shared)|browser| browser |
3434
|Outlook event-based tasks | JavaScript-only</br>(classic Outlook on Windows)</br></br>browser</br>(new Outlook on Windows) | browser | browser |
3535
|Event-based tasks on other applications | JavaScript-only | browser | browser |
36-
|Outlook integrated spam reporting feature (preview)| JavaScript-only</br>(classic Outlook on Windows)</br></br>browser</br>(new Outlook on Windows) | browser | browser |
36+
|Outlook integrated spam reporting feature | JavaScript-only</br>(classic Outlook on Windows)</br></br>browser</br>(new Outlook on Windows) | browser | browser |
3737
|task pane | browser | browser | browser |
3838
|dialog | browser | browser | browser |
3939
|function command | browser | browser | browser |

0 commit comments

Comments
 (0)