Merge pull request #5790 from OfficeDev/main

[Admin] Publish to live

Author: Rick-Kirkham

docs/publish/publish-add-in-vs-code.md

@@ -1,32 +1,38 @@
 ---
-title: Publish an add-in using Visual Studio Code and Azure
-description: How to publish an add-in using Visual Studio Code and Microsoft Entra ID
-ms.date: 05/19/2025
+title: Publish an Office Add-in from Visual Studio Code to Azure
+description: Deploy an Office Add-in web app from Visual Studio Code to Azure, update your manifest, and publish for users.
+ms.date: 06/09/2026
 ms.custom: vscode-azure-extension-update-completed
 ms.localizationpriority: medium
 ---
 
-# Publish an add-in developed with Visual Studio Code
+# Publish an Office Add-in from Visual Studio Code to Azure
 
-This article describes how to publish an Office Add-in that you created using the Yeoman generator and developed with [Visual Studio Code (VS Code)](https://code.visualstudio.com) or any other editor.
+One way to publish your Office Add-in is by deploying its web app to Azure. This article shows the end-to-end flow for add-ins that use the add-in only manifest and that were created with the Yeoman Generator for Office Add-ins.
 
 > [!NOTE]
 >
 > - For information about publishing an Office Add-in that you created using Visual Studio, see [Publish your add-in using Visual Studio](package-your-add-in-using-visual-studio.md).
 > - The process described in this article doesn't apply to add-ins that use the [unified manifest for Microsoft 365](../develop/unified-manifest-overview.md). Add-ins created using Microsoft 365 Agents Toolkit use the unified manifest. For information about publishing an add-in that you created using Agents Toolkit, see [Deploy Teams app to the cloud](/microsoftteams/platform/toolkit/deploy?pivots=visual-studio-code) and [Deploy your first Teams app](/microsoftteams/platform/sbs-gs-javascript?tabs=vscode%2Cvsc%2Cviscode). The latter article is about Teams tab apps, but it is applicable to Office Add-ins created with Agents Toolkit.
 
-## Publishing an add-in for other users to access
+## Publish for other users
 
-The simplest Office Add-in is made up of a manifest file and an HTML page. The manifest file describes the add-in's characteristics, such as its name, what Office applications it can run in, and the URL for the add-in's HTML page. The HTML page is contained in a web app that users interact with when they install and run your add-in within an Office application. You can host the web app of an Office Add-in on any web hosting platform, including Azure.
+An Office Add-in includes a manifest file and a web app. The manifest defines key details, such as the Office apps that support your add-in and the web app URL.
 
-While you're developing, you can run the add-in on your local web server (`localhost`). When you're ready to publish it for other users to access, you'll need to deploy the web application and update the manifest to specify the URL of the deployed application.
+During development, you run the add-in on localhost. To publish it for other users, deploy the web app and update the manifest to use the deployed URL.
 
-When your add-in is working as desired, you can publish it directly through Visual Studio Code using the Azure Storage extension.
+You can complete this process directly in Visual Studio Code by using the Azure Storage extension.
+
+## Prerequisites
+
+- An Office Add-in project created with the Yeoman generator for Office Add-ins that uses the add-in only manifest.
+- [Visual Studio Code](https://code.visualstudio.com).
+- An Azure account and permission to create Azure Storage accounts.
 
 ## Using Visual Studio Code to publish
 
->[!NOTE]
-> These steps only work for projects created with the Yeoman generator, and that use the add-in only manifest. They don't apply if you created the add-in using Agents Toolkit or created it with the Yeoman generator and it uses the unified manifest for Microsoft 365.
+> [!NOTE]
+> These steps only work for projects created with the Yeoman generator for Office Add-ins, and that use the add-in only manifest. They don't apply if you created the add-in using Agents Toolkit or created it with the Yeoman generator and it uses the unified manifest for Microsoft 365.
 
 1. Open your project from its root folder in Visual Studio Code (VS Code).
 1. Select **View** > **Extensions** (<kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>X</kbd>) to open the Extensions view.
@@ -36,7 +42,7 @@ When your add-in is working as desired, you can publish it directly through Visu
 
     :::image type="content" source="../images/azure-extension-sign-in.png" alt-text="Sign in to Azure button selected in the Azure extension.":::
 
-1. Once you're signed in, you'll see your Azure storage accounts appear in the extension. If you don't already have a storage account, create one using the **Create Storage Account** option in the command palette. Name your storage account a globally unique name, using only 'a-z' and '0-9'. Note that by default, this creates a storage account and a resource group with the same name. It automatically puts the storage account in West US. This can be adjusted online through [your Azure account](https://portal.azure.com/).
+1. Once you're signed in, your Azure Storage accounts appear in the extension. If you don't already have one, create one by using the **Create Storage Account** command. Use a globally unique account name with only `a-z` and `0-9`. By default, this creates a storage account and a resource group with the same name in West US. You can change these settings in [Azure portal](https://portal.azure.com/).
 
     :::image type="content" source="../images/azure-extension-create-storage-account.png" alt-text="Selecting Storage accounts > Create Storage Account in the Azure extension.":::
 
@@ -45,7 +51,7 @@ When your add-in is working as desired, you can publish it directly through Visu
 1. Open your project's manifest file and change all references to your localhost URL (such as `https://localhost:3000`) to the URL you've copied. This endpoint is the static website URL for your newly created storage account. Save the changes to your manifest file.
 1. Open a command line prompt or terminal window and go to the root directory of your add-in project. Run the following command to prepare all files for production deployment.
 
-    ```command&nbsp;line
+    ```bash
     npm run build
     ```
 
@@ -55,9 +61,9 @@ When your add-in is working as desired, you can publish it directly through Visu
 
     :::image type="content" source="../images/deploy-to-static-website.png" alt-text="Select the dist folder, right-click (or select and hold), and select Deploy to Static Website via Azure Storage.":::
 
-1. When deployment is complete, right-click (or select and hold) the storage account that you created previously and select **Browse Static Website**. This opens the static web site and displays the task pane.
+1. When deployment is complete, right-click (or select and hold) the storage account that you created previously and select **Browse Static Website**. This opens the static website and displays the task pane.
 
-1. Finally, [sideload the manifest file](../testing/sideload-office-add-ins-for-testing.md) and the add-in will load from the static web site you just deployed.
+1. Finally, [sideload the manifest file](../testing/sideload-office-add-ins-for-testing.md). The add-in then loads from the static website you deployed.
 
 ## Deploy custom functions for Excel
 
@@ -67,13 +73,13 @@ If your add-in has custom functions, there are a few more steps to enable them o
 1. In the Settings group, select **Resource sharing (CORS)**. You can also use the search box to find this.
 1. Create a new CORS rule for the **Blob service** with the following settings.
 
-    |Property        |Value                        |
-    |----------------|-----------------------------|
-    |Allowed origins | \*                          |
-    |Allowed methods | GET                         |
-    |Allowed headers | \*                          |
-    |Exposed headers | Access-Control-Allow-Origin |
-    |Max age         | 200                         |
+    | Property | Value |
+    |--|--|
+    | Allowed origins | \* |
+    | Allowed methods | GET |
+    | Allowed headers | \* |
+    | Exposed headers | Access-Control-Allow-Origin |
+    | Max age | 200 |
 
 1. Select **Save**.
 
@@ -82,7 +88,7 @@ If your add-in has custom functions, there are a few more steps to enable them o
 
 Next, add a MIME type for JSON files.
 
-1. Create a new file in the /src folder named **web.config**.
+1. Create a new file in the `src` folder named **web.config**.
 1. Insert the following XML and save the file.
 
     ```xml
@@ -110,13 +116,13 @@ Next, add a MIME type for JSON files.
     }),
     ```
 
-1. Open a command line prompt and go to the root directory of your add-in project. Then, run the following command to prepare all files for deployment.
+1. Open a command line prompt and go to the root directory of your add-in project. Then run the following command to prepare all files for deployment.
 
-    ```command&nbsp;line
+    ```bash
     npm run build
     ```
 
-    When the build completes, the **dist** folder in the root directory of your add-in project will contain the files that you'll deploy.
+   When the build completes, the **dist** folder in the root directory of your add-in project will contain the files that you'll deploy.
 
 1. To deploy, in the VS Code **Explorer**, right-click (or select and hold) the **dist** folder and select **Deploy to Static Website via Azure Storage**. When prompted, select the storage account you created previously. If you already deployed the **dist** folder, you'll be prompted if you want to overwrite the files in the Azure storage with the latest changes.
 

docs/testing/clear-cache.md

@@ -1,7 +1,7 @@
 ---
 title: Clear the Office cache
 description: Learn how to clear the Office cache on your computer.
-ms.date: 12/02/2025
+ms.date: 06/12/2026
 ms.localizationpriority: high
 ---
 
@@ -36,21 +36,21 @@ The following table outlines which Office cache types can be cleared on differen
 
 | Platform | Types of caches to clear | Options to clear the cache |
 | ----- | ----- | ----- |
-| Windows | Both the web and Wef caches. There's currently no option to clear one cache without clearing the other. | <ul><li>[Automatically clear the cache](#automatically-clear-the-cache)</li><li>[Manually clear the cache](#manually-clear-the-cache)</li><li>[Use the Microsoft Edge developer tools on Windows 10](#use-the-microsoft-edge-developer-tools-on-windows-10)</li></ul> |
+| Windows | Both the web and Wef caches. There's currently no option to clear one cache without clearing the other. | <ul><li>[Automatically clear the cache](#automatically-clear-the-cache)</li><li>[Use the office-addin-cacche tool](#use-the-office-addin-cache-tool)</li><li>[Manually clear the cache](#manually-clear-the-cache)</li></ul> |
 | Mac | <ul><li>Web</li><li>Both web and Wef caches</li></ul> | <ul><li>**Web**: [Use the personality menu to clear the web cache](#clear-the-web-cache)</li><li>**Web and Wef**: [Clear the web and Wef caches on Mac](#clear-the-web-and-wef-caches)</li></ul> |
 | iOS | <ul><li>Web</li></ul> | <ul><li>[Use JavaScript to clear the cache on iOS](#clear-the-office-cache-on-ios)</li></ul> |
 
 ## Clear the Office cache on Windows
 
-Depending on your Office host and operating system, you can automatically or manually clear both the web and Wef caches on a Windows computer.
+Depending on the Office applications that your add-in supports, you may be able to configure Office on Windows to automatically clear both the web and Wef caches whenever it starts. Alternatively, clear the cache with the [office-addin-cache](https://www.npmjs.com/package/office-addin-cache) tool or manually.
 
 > [!IMPORTANT]
 > On Windows, the automatic and manual options clear both the web and Wef caches. There's currently no option to clear one cache without clearing the other.
 
 ### Automatically clear the cache
 
 > [!NOTE]
-> The automatic option is only supported for Excel, PowerPoint, and Word. Outlook only supports the [manual option](#manually-clear-the-cache-in-outlook).
+> The automatic option is only supported for Excel, PowerPoint, and Word. Outlook only supports the [tool](#use-the-office-addin-cache-tool) and [manual](#manually-clear-the-cache-in-outlook) options.
 
 This method is recommended for add-in development computers. If your Office on Windows version is 2108 or later, the following steps configure the Office cache to be cleared the next time Office is reopened.
 
@@ -59,6 +59,16 @@ This method is recommended for add-in development computers. If your Office on W
 1. Select **OK**.
 1. Restart Excel, PowerPoint, or Word.
 
+### Use the office-addin-cache tool
+
+To programmatically clear the cache, open a Command Prompt and run the following command. 
+
+```bash
+npx office-addin-cache clear
+```
+
+For information about options you can use with the command, see [office-addin-cache](https://www.npmjs.com/package/office-addin-cache).
+
 ### Manually clear the cache
 
 #### Manually clear the cache in Excel, Word, and PowerPoint
@@ -108,31 +118,6 @@ To clear the cache in [new Outlook on Windows](https://support.microsoft.com/off
 
   :::image type="content" source="../images/devtools-clear-cache.png" alt-text="The 'Clear browser cache' option is selected in Microsoft Edge DevTools.":::
 
-### Use the Microsoft Edge developer tools on Windows 10
-
-To clear the Office cache on Windows 10 when the add-in is running in Microsoft Edge, use the Microsoft Edge DevTools.
-
-> [!NOTE]
-> To clear the Office cache using the following steps, your add-in must have a task pane. If your add-in is a UI-less add-in -- for example, one that uses the [on-send](../outlook/outlook-on-send-addins.md) feature -- you'll need to add a task pane to your add-in that uses the same domain for [SourceLocation](/javascript/api/manifest/sourcelocation), before you can use the following steps to clear the cache.
-
-1. Install the [Microsoft Edge DevTools](https://apps.microsoft.com/detail/9mzbfrmz0mnj).
-
-2. Open your add-in in the Office client.
-
-3. Run the Microsoft Edge DevTools.
-
-4. In the Microsoft Edge DevTools, open the **Local** tab. Your add-in will be listed by its name.
-
-5. Select the add-in name to attach the debugger to your add-in. A new Microsoft Edge DevTools window will open when the debugger attaches to your add-in.
-
-6. On the **Network** tab of the new window, select **Clear cache**.
-
-    :::image type="content" source="../images/edge-devtools-clear-cache.png" alt-text="Microsoft Edge DevTools with the Clear cache button highlighted.":::
-
-7. If completing these steps doesn't produce the desired result, try selecting **Always refresh from server**.
-
-    :::image type="content" source="../images/edge-devtools-refresh-from-server.png" alt-text="Microsoft Edge DevTools with the Always refresh from server button highlighted.":::
-
 ## Clear the Office cache on Mac
 
 You can choose to clear the web or both the web and Wef caches on Mac.
@@ -154,6 +139,20 @@ From the add-in's task pane, choose the personality menu. Then, choose **Clear W
 
 ### Clear the web and Wef caches
 
+Clear both the caches either manually or by using the office-addin-cache tool.
+
+#### Clear the Office cache on Mac by using the office-addin-cache tool
+
+To programmatically clear the cache, open **Terminal** and run the following command. 
+
+```bash
+npx office-addin-cache clear
+```
+
+For information about options you can use with the command, see [office-addin-cache](https://www.npmjs.com/package/office-addin-cache).
+
+#### Clear the Office cache on Mac manually
+
 To clear both the web and Wef caches on Mac, delete the contents of the `~/Library/Containers/com.Microsoft.OsfWebHost/Data/` and `~/Library/Containers/com.microsoft.{host}/Data/Documents/wef` folders. Replace `{host}` with the Office application, such as `Excel`.
 
 > [!TIP]