Merge pull request #4956 from OfficeDev/main

[Admin] Publish

Author: davidchesnut

docs/develop/development-kit-overview.md

@@ -1,11 +1,11 @@
 ---
-title: Create Office Add-in projects using Office Add-ins Development Kit for Visual Studio Code (preview)
+title: Create Office Add-in projects using Office Add-ins Development Kit for Visual Studio Code
 description: Learn how to create Office Add-in projects using Office Add-ins Development Kit extension.
-ms.date: 09/09/2024
+ms.date: 12/19/2024
 ms.localizationpriority: high
 ---
 
-# Create Office Add-in projects using Office Add-ins Development Kit for Visual Studio Code (preview)
+# Create Office Add-in projects using Office Add-ins Development Kit for Visual Studio Code
 
 The Office Add-ins Development Kit helps set up your environment, create Office Add-ins, and debug your code in a streamlined experience.
 

docs/develop/enable-nested-app-authentication-in-your-add-in.md

@@ -1,7 +1,7 @@
 ---
 title: Enable SSO in an Office Add-in using nested app authentication
 description: Learn how to enable SSO in an Office Add-in using nested app authentication.
-ms.date: 11/22/2024
+ms.date: 12/18/2024
 ms.topic: how-to
 ms.localizationpriority: high
 ---
@@ -45,7 +45,11 @@ To enable NAA, your app registration must include a specific redirect URI to ind
 
 `brk-multihub://your-add-in-domain`
 
-For example if you were testing your add-in on port 3000 on the localhost server, you would use `brk-multihub://localhost:3000` as the redirect value.
+Your domain must include only the origin and not its subpaths. For example:
+
+✔️ brk-multihub://localhost:3000<br>
+✔️ brk-multihub://www.contoso.com<br>
+❌ brk-multihub://www.contoso.com/go
 
 Trusted broker groups are dynamic by design and can be updated in the future to include additional hosts where your add-in may use NAA flows. Currently the brk-multihub group includes Office Word, Excel, PowerPoint, Outlook, and Teams (for when Office is activated inside).
 

docs/includes/outlook-bundle-js.md

@@ -1,5 +1,5 @@
 > [!TIP]
-> If the **bundle.js** file doesn't appear in the **Wef** folder, try the following:
 >
-> - If your add-in is installed or sideloaded, restart Outlook.
-> - [Remove your add-in](../outlook/sideload-outlook-add-ins-for-testing.md#remove-a-sideloaded-add-in) from Outlook, then [sideload](../outlook/sideload-outlook-add-ins-for-testing.md) it again.
+> - There's no direct method to determine the Outlook profile GUID and mail account encoding used in the **bundle.js** file path. The most effective approach to locate your add-in's **bundle.js** file is to manually inspect each folder until you locate the **Javascript** folder that contains your add-in's ID.
+>
+> - If the **bundle.js** file doesn't appear in the **Wef** folder and your add-in is installed or sideloaded, restart Outlook. Alternatively, [remove your add-in](../outlook/sideload-outlook-add-ins-for-testing.md#remove-a-sideloaded-add-in) from Outlook, then [sideload](../outlook/sideload-outlook-add-ins-for-testing.md) it again.

docs/outlook/debug-autolaunch.md

@@ -1,7 +1,7 @@
 ---
 title: Debug your event-based or spam-reporting Outlook add-in
 description: Learn how to debug your Outlook add-in that implements event-based activation or integrated spam reporting.
-ms.date: 07/09/2024
+ms.date: 12/19/2024
 ms.topic: how-to
 ms.localizationpriority: medium
 ---
@@ -28,7 +28,7 @@ For more information, see the "Debug your add-in" section of [Develop Outlook ad
 
 # [Windows (classic)](#tab/windows)
 
-If you used the [Yeoman generator for Office Add-ins](../develop/yeoman-generator-overview.md) to create your add-in project (for example, by completing an [event-based activation walkthrough](on-new-compose-events-walkthrough.md)), follow the **Created with Yeoman generator** option throughout this article. Otherwise, follow the **Other** steps. Visual Studio Code should be at least version 1.56.1.
+If you used the [Yeoman generator for Office Add-ins](../develop/yeoman-generator-overview.md) to create your add-in project (for example, by completing an [event-based activation walkthrough](on-new-compose-events-walkthrough.md)), follow the **Created with Yeoman generator** option throughout this article. Otherwise, follow the **Other** steps.
 
 ## Mark your add-in for debugging and set the debugger port
 
@@ -37,19 +37,19 @@ If you used the [Yeoman generator for Office Add-ins](../develop/yeoman-generato
     - **Add-in only manifest**: Use the value of the **\<Id\>** element child of the root **\<OfficeApp\>** element.
     - **Unified manifest for Microsoft 365**: Use the value of the "id" property of the root anonymous `{ ... }` object.
 
-1. Create a registry `DWORD` value named `UseDirectDebugger` in `HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\16.0\Wef\Developer\[Add-in ID]`. Replace `[Add-in ID]` with your add-in's ID from the manifest.
+1. In the registry, mark your add-in for debugging.
 
-    [!include[Developer registry key](../includes/developer-registry-key.md)]
+    - **Created with Yeoman generator**: In a command line window, navigate to the root of your add-in folder then run the following command.
 
-    **Created with Yeoman generator**: In a command line window, navigate to the root of your add-in folder then run the following command.
+        ```command&nbsp;line
+        npm start
+        ```
 
-    ```command&nbsp;line
-    npm start
-    ```
+        In addition to building the code and starting the local server, this command sets the data of the `HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\16.0\WEF\Developer\[Add-in ID]\UseDirectDebugger` registry DWORD value for this add-in to `1`. `[Add-in ID]` is your add-in's ID from the manifest.
 
-    In addition to building the code and starting the local server, this command sets the `UseDirectDebugger` registry DWORD value data for this add-in to `1`.
+    - **Other**: In the `HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\16.0\WEF\Developer\[Add-in ID]\UseDirectDebugger` registry DWORD value, where `[Add-in ID]` is your add-in's ID from the manifest, set its data to `1`.
 
-    **Other**: In the `HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\16.0\WEF\Developer\[Add-in ID]\UseDirectDebugger` registry DWORD value, where `[Add-in ID]` is your add-in's ID from the manifest, set the value data to `1`.
+        [!include[Developer registry key](../includes/developer-registry-key.md)]
 
 1. In the registry key `HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\16.0\Wef\Developer\[Add-in ID]`, where `[Add-in ID]` is your add-in's ID from the manifest, create a new `DWORD` value with the following configuration.
 
@@ -63,11 +63,39 @@ If you used the [Yeoman generator for Office Add-ins](../develop/yeoman-generato
 
     ![The Debug Event-based handler dialog in Windows.](../images/outlook-win-autolaunch-debug-dialog.png)
 
-## Configure Visual Studio Code
+## Configure and attach the debugger
+
+You can debug your add-in using the Microsoft Edge Inspect tool or Visual Studio Code.
+
+### Debug with Microsoft Edge
+
+1. Open Microsoft Edge and go to **edge://inspect/#devices**.
+1. In the **Remote Target** section, look for your add-in using its ID from the manifest. Then, select **Inspect**.
+
+    The DevTools window appears.
+
+    > [!NOTE]
+    > It may take some time for your add-in to appear in the **Remote Target** section. You may need to refresh the page for the add-in to appear.
+
+1. In the **Sources** tab, go to **file://** > **Users/[User]/AppData/Microsoft/Office/16.0/Wef/{[Outlook profile GUID]}/[Outlook mail account encoding]/Javascript/[Add-in ID]\_[Add-in Version]_[locale]** > **bundle.js**.
+
+    > [!TIP]
+    > There's no direct method to determine the Outlook profile GUID or mail account encoding used in the **bundle.js** file path. If you're debugging multiple add-ins simultaneously, the easiest way to access an add-in's **bundle.js** file from the DevTools window is to locate the add-in's ID in the file path.
+
+1. In the **bundle.js** file, place breakpoints where you want the debugger to stop.
+1. [Run the debugger](#run-the-debugger).
+
+### Debug with Visual Studio Code
+
+To debug your add-in in Visual Studio Code, you must have at least version 1.56.1 installed.
+
+#### Configure the debugger
+
+Configure the debugger in Visual Studio Code. Follow the steps applicable to your add-in project.
 
-### Created with Yeoman generator
+##### Created with Yeoman generator
 
-1. Back in the command line window, run the following to open your add-in project in Visual Studio Code.
+1. In the command line, run the following to open your add-in project in Visual Studio Code.
 
     ```command&nbsp;line
     code .
@@ -86,7 +114,7 @@ If you used the [Yeoman generator for Office Add-ins](../develop/yeoman-generato
     }
     ```
 
-### Other
+##### Other
 
 1. Create a new folder called **Debugging** (perhaps in your **Desktop** folder).
 1. Open Visual Studio Code.
@@ -113,11 +141,11 @@ If you used the [Yeoman generator for Office Add-ins](../develop/yeoman-generato
     }
     ```
 
-## Attach the debugger
+#### Attach the debugger
 
 The **bundle.js** file of an add-in contains the JavaScript code of your add-in. It's created when classic Outlook on Windows is opened. When Outlook starts, the **bundle.js** file of each installed add-in is cached in the **Wef** folder of your machine.
 
-1. To find the add-in's **bundle.js** file, navigate to the following folder in File Explorer. Replace text enclosed in `[]` with your applicable Outlook and add-in information.
+1. To find the add-in's **bundle.js** file, navigate to the following folder in File Explorer. The text enclosed in `[]` represents your applicable Outlook and add-in information.
 
     ```text
     %LOCALAPPDATA%\Microsoft\Office\16.0\Wef\{[Outlook profile GUID]}\[Outlook mail account encoding]\Javascript\[Add-in ID]_[Add-in Version]_[locale]
@@ -133,9 +161,9 @@ The **bundle.js** file of an add-in contains the JavaScript code of your add-in.
 
 ## Run the debugger
 
-1. After confirming that the debugger is attached, return to Outlook, and in the **Debug Event-based handler** dialog, choose **OK** .
+After confirming that the debugger is attached, return to Outlook. In the **Debug Event-based handler** dialog, choose **OK** .
 
-1. You can now hit your breakpoints in Visual Studio Code, enabling you to debug your event-based activation or spam-reporting code.
+You can now hit your breakpoints to debug your event-based activation or spam-reporting code.
 
 ## Stop the debugger
 

docs/outlook/faq-nested-app-auth-outlook-legacy-tokens.md

@@ -4,7 +4,7 @@ description: Nested app authentication and Outlook legacy tokens deprecation FAQ
 ms.service: microsoft-365
 ms.subservice: add-ins
 ms.topic: faq
-ms.date: 12/12/2024
+ms.date: 12/18/2024
 ---
 
 # Nested app authentication and Outlook legacy tokens deprecation FAQ
@@ -38,11 +38,15 @@ The general availability (GA) date for NAA depends on which channel you are usin
 | Jan 2025 | NAA will GA in Semi-Annual Channel. |
 | Jun 2025 | NAA will GA in Semi-Annual Extended Channel. |
 
+### Are COM Add-ins affected by the deprecation of legacy Exchange Online tokens?
+
+It's very unlikely any COM add-ins are affected by the deprecation of legacy Exchange Online tokens. Outlook web add-ins are primarily affected because they can use Office.js APIs that rely on Exchange tokens. For more information, see[How do i know if my outlook add in relies on legacy tokens](#how-do-i-know-if-my-outlook-add-in-relies-on-legacy-tokens). The Exchange tokens are used to access Exchange Web Services (EWS) or Outlook REST APIs, both of which are also deprecated. If you suspect a COM add-in might be affected, you can test it by using it on a tenant with Exchange tokens turned off. For more information, see [Turn legacy Exchange Online tokens on or off](turn-exchange-tokens-on-off.md).
+
 ## Microsoft 365 administrator questions
 
 ### Can I turn Exchange Online legacy tokens back on?
 
-Yes, there are PowerShell commands you can use to turn legacy tokens on or off in any tenant. For more information on how to turn legacy tokens on or off, see [Turn legacy Exchange Online tokens on or off](turn-exchange-tokens-on-off.md).
+Yes, there are PowerShell commands you can use to turn legacy tokens on or off in any tenant. For more information on how to turn legacy tokens on or off, see [Turn legacy Exchange Online tokens on or off](turn-exchange-tokens-on-off.md). If you use the commands to enable legacy Exchange Online tokens, they will not be turned off in February 2025. They will remain on until June 2025, or until you use the tooling to turn them off.
 
 In June 2025, legacy tokens will be turned off and you won't be able to turn them back on without a specific exception granted by Microsoft. In October 2025, it won't be possible to turn on legacy tokens and they'll be disabled for all tenants. We'll update this FAQ with additional information once the tool is available.
 

docs/outlook/onmessagesend-onappointmentsend-events.md

@@ -1,7 +1,7 @@
 ---
 title: Handle OnMessageSend and OnAppointmentSend events in your Outlook add-in with Smart Alerts
 description: Learn about the Smart Alerts implementation and how it handles the OnMessageSend and OnAppointmentSend events in your event-based Outlook add-in.
-ms.date: 12/03/2024
+ms.date: 12/19/2024
 ms.topic: concept-article
 ms.localizationpriority: medium
 ---
@@ -234,10 +234,14 @@ You can customize the **Don't Send** button in the dialog to open a task pane or
 > [!NOTE]
 > Support to customize the **Don't Send** button was introduced in [Mailbox requirement set 1.14](/javascript/api/requirement-sets/outlook/requirement-set-1.14/outlook-requirement-set-1.14).
 
-In Outlook on the web and in new Outlook on Windows:
+### Limitations in Outlook on the web and new Outlook on Windows
+
+When developing a Smart Alerts add-in for Outlook on the web and new Outlook on Windows, you must be mindful of the following limitations.
 
 - The `OnAppointmentSend` event only occurs when the meeting being sent was created through the **New Event** option. If the meeting being sent was created by selecting a date and time directly from the calendar, the `OnAppointmentSend` event doesn't occur.
 - When forwarding a meeting, the `OnAppointmentSend` event only occurs if the organizer forwards the meeting. It doesn't occur if an attendee forwards the meeting to which they're invited.
+- When an attendee responds to a meeting invite using the **Accept**, **Decline**, **Tentative**, or **Follow** option, the `OnMessageSend` event doesn't occur. This behavior applies even if the attendee includes a personalized message in their response.
+- When the organizer cancels a meeting and includes a cancellation message, the `OnMessageSend` event doesn't occur.
 
 ### Limitations to formatting the dialog message using Markdown
 

docs/outlook/troubleshoot-event-based-and-spam-reporting-add-ins.md

@@ -61,7 +61,7 @@ As you develop your [event-based](autolaunch.md) or [spam-reporting](spam-report
 
     :::image type="content" source="../images/outlook-event-based-logs.png" alt-text="A sample of Event Viewer's Filter Current Log settings configured to only show Outlook errors with event ID 63 that occurred in the last hour.":::
 
-  - Verify that the **bundle.js** file is downloaded to the following folder in File Explorer. Replace text enclosed in `[]` with your applicable information.
+  - Verify that the **bundle.js** file is downloaded to the following folder in File Explorer. The text enclosed in `[]` represents your applicable Outlook and add-in information.
 
     ```text
     %LOCALAPPDATA%\Microsoft\Office\16.0\Wef\{[Outlook profile GUID]}\[Outlook mail account encoding]\Javascript\[Add-in ID]_[Add-in Version]_[locale]

docs/outlook/turn-exchange-tokens-on-off.md

@@ -4,7 +4,7 @@ description: Turn legacy Exchange Online tokens on or off
 ms.service: microsoft-365
 ms.subservice: add-ins
 ms.topic: how-to
-ms.date: 12/12/2024
+ms.date: 12/18/2024
 ---
 
 # Turn legacy Exchange Online tokens on or off
@@ -22,7 +22,7 @@ To run the commands you need to connect to Exchange Online PowerShell.
 1. To be sure you are on the latest version of the module, run the command `Update-Module -Name ExchangeOnlineManagement`.
 1. Run the command `Connect-ExchangeOnline`. Sign in with your Microsoft 365 administrator credentials.
 
-## Turn off legacy Exchange Online tokens in a test tenant
+## Turn off legacy Exchange Online tokens
 
 The `Set-AuthenticationPolicy` command controls the issuance of legacy Exchange Online tokens. When issuance is turned off, add-ins can no longer request user identity tokens or callback tokens. Existing tokens already issued will continue to work until they expire. It can take up to 24 hours before all request from Outlook add-ins for legacy Exchange Online tokens are blocked.
 
@@ -32,7 +32,10 @@ To turn legacy tokens off, run the following command.
 
 The command turns off legacy tokens for the entire tenant. If an Outlook add-in requests a legacy token, it won’t be issued a token.
 
-## Turn on legacy Exchange Online tokens in a test tenant
+> [!NOTE]
+> If you've confirmed that your tenant is not using any add-ins that require legacy Exchange Online tokens, we recommend you turn off legacy Exchange Online tokens as a security best practice. For more information on how to determine if you tenant has add-ins using legacy tokens, see the [Nested app authentication and Outlook legacy tokens deprecation FAQ](faq-nested-app-auth-outlook-legacy-tokens.md).
+
+## Turn on legacy Exchange Online tokens
 
 To turn legacy tokens on, run the following command. It can take up to 24 hours before all requests from Outlook add-ins for legacy tokens are allowed.