diff --git a/docs/develop/develop-overview.md b/docs/develop/develop-overview.md index 22d30ca287..97bdb684ce 100644 --- a/docs/develop/develop-overview.md +++ b/docs/develop/develop-overview.md @@ -2,7 +2,7 @@ title: Develop Office Add-ins description: An introduction to developing Office Add-ins. ms.topic: overview -ms.date: 10/08/2025 +ms.date: 12/10/2025 ms.localizationpriority: high --- @@ -52,9 +52,12 @@ The Office Add-ins Development Kit is an extension for Visual Studio Code. It le An Office Add-in consists of two parts. -- The add-in manifest that defines the settings and capabilities of the add-in. +- An app package whose main constituent is an add-in manifest that defines the settings and capabilities of the add-in. The package is the unit of publishing and sideloading. -- The web application that defines the UI and functionality of add-in components such as task panes, content add-ins, and dialog boxes. + > [!NOTE] + > An add-in can have either of two types of manifests: the unified manifest for Microsoft 365 or the add-in only manifest. Everything said in this article about the manifest applies to both types. But note that if the add-in only manifest is used, then there is no app package: the manifest file is the unit of publishing and sideloading. For more information about the two types, see [Office Add-ins manifest](../develop/add-in-manifests.md). + +- The web application that defines the UI and functionality of add-in components such as task panes, content add-ins, dialog boxes, or Copilot agents. The web application uses the Office JavaScript API to interact with content in the Office document where the add-in is running. Your add-in can also do other things that web applications typically do, like call external web services, facilitate user authentication, and more. @@ -68,7 +71,6 @@ An Office Add-in's manifest defines the settings and capabilities of the add-in. - How the add-in integrates with Office, including any custom UI that the add-in creates (for example, a custom tab or custom ribbon buttons). - Location of images that the add-in uses for branding and command iconography. - Dimensions of the add-in (for example, dimensions for content add-ins, requested height for Outlook add-ins). -- Rules that specify when the add-in activates in the context of a message or appointment (for Outlook add-ins only). - Keyboard shortcuts (for Excel and Word add-ins only). For detailed information about the manifest, see [Office Add-ins manifest](add-in-manifests.md). @@ -113,6 +115,9 @@ The following image shows an add-in command on the ribbon, a task pane to the ri For more information about extending the Office UI and designing the add-in's UX, see [Office UI elements for Office Add-ins](../design/interface-elements.md). +> [!NOTE] +> It isn't necessary for an add-in to have any custom UI. An add-in can consist of only a custom Copilot agent that interacts with an Office document in response to natural language instructions given in Copilot chat. + ## Next steps This article has outlined the different ways to create Office Add-ins, introduced the ways that an add-in can extend the Office UI, described the API sets, and introduced Script Lab as a valuable tool for exploring Office JavaScript APIs and prototyping add-in functionality. Now that you've explored this introductory information, consider continuing your Office Add-ins journey along the following paths. diff --git a/docs/images/app-package.png b/docs/images/app-package.png new file mode 100644 index 0000000000..9fc6f3ff91 Binary files /dev/null and b/docs/images/app-package.png differ diff --git a/docs/images/office-programmability-diagram.png b/docs/images/office-programmability-diagram.png index 4f89fc1e4e..00c9030cc4 100644 Binary files a/docs/images/office-programmability-diagram.png and b/docs/images/office-programmability-diagram.png differ diff --git a/docs/images/office-programmability-diagram.pptx b/docs/images/office-programmability-diagram.pptx index ec8426990b..103968c8b8 100644 Binary files a/docs/images/office-programmability-diagram.pptx and b/docs/images/office-programmability-diagram.pptx differ diff --git a/docs/images/why.png b/docs/images/why.png deleted file mode 100644 index a0d25da478..0000000000 Binary files a/docs/images/why.png and /dev/null differ diff --git a/docs/overview/app-package-for-microsoft-365.md b/docs/overview/app-package-for-microsoft-365.md new file mode 100644 index 0000000000..a006dbc29b --- /dev/null +++ b/docs/overview/app-package-for-microsoft-365.md @@ -0,0 +1,96 @@ +--- +title: App package for Microsoft 365 +description: Learn how add-ins use the app package for Microsoft 365, for packaging, publishing, and management. +ms.date: 12/10/2025 +ms.topic: concept-article +ms.custom: scenarios:getting-started +ms.localizationpriority: high +--- + +# App package for Microsoft 365 + +The app package of an app for Microsoft 365 is a zip file that contains a manifest file, two app icons, and possibly additional configuration or localization files. Your app logic and data storage are hosted elsewhere and accessed by the Microsoft 365 host application via HTTPS. You'll submit the app package to your admin to publish to your organization or to Partner Center to publish to Microsoft Marketplace. + +At minimum, an app package contains: + +- The **app manifest** (`manifest.json`), which describes app configuration, capabilities, required resources, and important attributes. +- A **large full-color icon** (`color.png`), 192 x 192 pixels, to display your agent in the Microsoft 365 Copilot UI and store. +- A **small outline icon** (`outline.png`), 32 x 32 pixels, with a transparent background (not currently used in Copilot, but required to pass validation). + +The app package can also contain declarative agent and API plugin definitions, as well as localization files for other supported languages. + +:::image type="content" source="../images/app-package.png" alt-text="Diagram showing the anatomy of a Microsoft 365 app package: app manifest (.json file) + icons (color and outline .png files) wrapped in a .zip file." border="false"::: + +## App manifest + +The unified app manifest for Microsoft 365 is a JSON file that describes the functionality and characteristics of your add-in, such as: + +- The add-in's display name, description, ID, version, and default locale. + +- How the add-in integrates with Office.   + +- How the add-in integrates with Copilot (preview). + +- The permission level and data access requirements for the add-in. + +For a detailed overview of the manifest, see [Office Add-ins with the unified app manifest for Microsoft 365](../develop/unified-manifest-overview.md). For reference documentation, see [Microsoft 365 app manifest schema reference](/microsoft-365/extensibility/schema). + +## App icons + +Your app package must include both a color and outline version of your app icon, as .png files. These icons have specific size requirements in order to pass store validation. For detailed design guidance for color and outline icons for the Microsoft 365 app package, see [Design icons for add-in acquisition and management](../design/microsoft-365-extension-management-icons.md). + +## Other configuration and localization files + +In addition to the manifest and the two icon files, the app package may also contain some of the following files. + +- Localization files that are referenced in the `"localizationInfo"` property of the manifest. +- Copilot declarative agent files that are referenced in the `"copilotAgents"` property. +- Any second-level supplementary files. For example, Copilot declarative agent configuration files sometimes reference second-level supplementary files, such as Copilot plugin configuration files. + +## Manually create the app package file + +This app package file is usually created for you by the tools you use to create and test your app for Microsoft 365, but there are scenarios in which you create it manually. To do so, use any zip utility to create a zip file that contains the following files. + +- The unified manifest, which goes in the root of the zip file. +- The two image files referenced in the `"icons"` property of the manifest. +- Any localization files that are referenced in the `"localizationInfo"` property of the manifest. +- Any declarative agent files that are referenced in the `"copilotAgents"` property. +- Any second-level supplementary files. For example, Copilot declarative agent configuration files sometimes reference second-level supplementary files, such as Copilot plugin configuration files. These should be included too. + +> [!IMPORTANT] +> *All of these files must have the same relative path in the zip file as specified in the manifest.* For example, if the path of the two image files is **assets/color.png** and **assets/outline.png**, then you must include an **assets** folder with the two files in the zip package. Second-level files, such as plugin configuration files for declarative agents, must have the same relative path in the zip file as they do in the first-level file that references them. For example, if the relative path of a declarative agent file specified in the manifest is **agents/myAgent.json**, then you must include an **agents** folder in the zip package and put the **myAgent.json** file in it. If the declarative agent file, in turn, gives the relative path of **plugins/myPlugin.json** for a plugin configuration file, then you must include a **plugins** subfolder under the **agents** folder and put the **myPlugin.json** file in it. + +To maximize compatibility with Microsoft 365 development tools, we recommend that you keep the files that will be included in the package in a folder called **appPackage** in the root of your project, and that you put the package file in a subfolder named **build** in the **appPackage** folder. + +The following are examples of the recommended structure. The structure inside the **\build\appPackage.zip** file must mirror the structure of the **appPackage** folder, except for the **build** folder itself. + +```console +\appPackage + \assets + color.png + outline.png + \build + appPackage.zip + manifest.json +``` + +```console +\appPackage + \agents + myAgent.json + \plugins + myPlugin.json + \assets + color.png + outline.png + \build + appPackage.zip + \languages + fr-FR.json + es-MX.json + manifest.json +``` + +> [!NOTE] +> The JSON files that are referenced in the manifest's `"extensions.keyboardShortcuts.keyMappingFiles"` property are *not* included in the app package. They are deployed with the add-in's web application files. For more information, see [Support backward compatibility for add-ins with a unified manifest in Microsoft Marketplace](../design/keyboard-shortcuts.md#support-backward-compatibility-for-add-ins-with-a-unified-manifest-in-microsoft-marketplace). + diff --git a/docs/overview/office-add-ins.md b/docs/overview/office-add-ins.md index 9dba7f68e1..ed27388205 100644 --- a/docs/overview/office-add-ins.md +++ b/docs/overview/office-add-ins.md @@ -1,7 +1,7 @@ --- title: Office Add-ins platform overview description: Use familiar web technologies such as HTML, CSS, and JavaScript to extend and interact with Word, Excel, PowerPoint, OneNote, Project, and Outlook. -ms.date: 02/19/2025 +ms.date: 12/10/2025 ms.topic: overview ms.custom: scenarios:getting-started ms.localizationpriority: high @@ -9,41 +9,32 @@ ms.localizationpriority: high # Office Add-ins platform overview -You can use the Office Add-ins platform to build solutions that extend Office applications and interact with content in Office documents. With Office Add-ins, you can use familiar web technologies such as HTML, CSS, and JavaScript to extend and interact with Outlook, Excel, Word, PowerPoint, OneNote, and Project. Your solution can run in Office across multiple platforms, including Windows, Mac, iPad, and in a browser. +Use the Office Add-ins platform to build apps and agents that extend Office applications and interact with content in Office documents. With Office Add-ins, you can use familiar web technologies such as HTML, CSS, and JavaScript to extend and interact with Outlook, Excel, Word, PowerPoint, OneNote, and Project. Your solution can run in Office across multiple platforms, including Windows, Mac, iPad, and in a browser. When you build an add-in, you're also building an app for Microsoft 365, that is, an extensions of Microsoft 365. Apps for Microsoft 365 share a common manifest schema and packaging format, and unified distribution and management processes and tools. This system enables add-ins to be combined with other kinds of apps for Microsoft 365 in a single package that's installable as a unit. -![Office application plus an embedded website (add-in) make endless extensibility possibilities.](../images/addins-overview.png) +> [!IMPORTANT] +> An add-in can have either of two types of manifests. This article is written on the assumption that the add-in is using the type that's recommended for most scenarios: the unified manifest for Microsoft 365. For more information about the two types, see [Office Add-ins manifest](../develop/add-in-manifests.md). -Office Add-ins can do almost anything a webpage can do inside a browser. Use the Office Add-ins platform to: +![Office application plus an embedded website (add-in) make endless extensibility possibilities.](../images/addins-overview.png) -- **Add new functionality to Office clients** - Bring external data into Office, automate Office documents, expose functionality from Microsoft and others in Office clients, and more. For example, use Microsoft Graph API to connect to data that drives productivity. - -- **Create new rich, interactive objects that can be embedded in Office documents** - Embed maps, charts, and interactive visualizations that users can add to their own Excel spreadsheets and PowerPoint presentations. +Use the Office Add-ins platform to: -## How are Office Add-ins different from COM and VSTO add-ins? - -COM and VSTO add-ins are earlier Office integration solutions that run only in Office on Windows. Unlike COM and VSTO add-ins, Office Add-ins are web add-ins: the application (for example, Excel), reads the add-in manifest and connects the add-in's custom ribbon buttons and menu commands in the UI. When needed, it loads the add-in's JavaScript and HTML code, which runs in the context of a browser or webview control in a sandbox. - -![A four-quadrant diagram showing the focus areas for different Office extensibility solutions. Office Web Add-ins along with COM and VSTO add-ins target professional developers, while VBA targets end users. Office Web Add-ins are focused on cross-platform experiences and collaboration while COM and VSTO add-ins and VBA cater to the individual's experience on Windows.](../images/office-programmability-diagram.png) - -Office Add-ins provide the following advantages over add-ins built using VBA, COM, or VSTO. - -- Cross-platform support: Office Add-ins run in Office on the web, Windows, Mac, and iPad. +- **Add new functionality to Office clients** - Bring external data into Office, automate Office documents, expose functionality from Microsoft and others in Office clients, and more. For example, use Microsoft Graph API to connect to data that drives productivity. -- Centralized deployment and distribution: Admins can deploy Office Add-ins centrally across an organization. +- **Create custom Copilot agents that read and write to documents open in Office applications (preview)** - Enable your users to use natural language to access your add-in's functionality. -- Easy access via Microsoft Marketplace: You can make your solution available to a broad audience by submitting it to Microsoft Marketplace. +- **Create new rich, interactive objects that can be embedded in Office documents** - Embed maps, charts, and interactive visualizations that users can add to their own Excel spreadsheets and PowerPoint presentations. -- Based on standard web technology: You can use any library you like to build Office Add-ins. +## Components of an Office Add-in -![The reasons to use Office Add-ins: cross-platform, centralized deployment, easy access via Microsoft Marketplace, and built on standard web technologies.](../images/why.png) +An Office Add-in includes two basic components: an app package and your own web application. The package includes a manifest that defines various settings, including how your add-in integrates with Office clients. Your web application needs to be hosted on a web server, or web hosting service, such as Microsoft Azure. -[!INCLUDE [new-outlook-vsto-com-support](../includes/new-outlook-vsto-com-support.md)] +### App package -## Components of an Office Add-in +The app package of an app for Microsoft 365 is a zip file that contains a manifest file, two app icons, and possibly additional configuration or localization files. Your app logic and data storage are hosted elsewhere and accessed by the Microsoft 365 host application via HTTPS. You'll submit the app package to your admin to publish to your organization or to Partner Center to publish to Microsoft Marketplace. -An Office Add-in includes two basic components: a manifest file and your own web application. The manifest defines various settings, including how your add-in integrates with Office clients. Your web application needs to be hosted on a web server, or web hosting service, such as Microsoft Azure. +For a detailed overview of the app package, see [App package for Microsoft 365](app-package-for-microsoft-365.md). -### Manifest +#### Manifest The manifest specifies settings and capabilities of the add-in, such as: @@ -51,8 +42,12 @@ The manifest specifies settings and capabilities of the add-in, such as: - How the add-in integrates with Office.   +- How the add-in integrates with Copilot (preview). + - The permission level and data access requirements for the add-in. +For a detailed overview of the manifest, see [Office Add-ins with the unified app manifest for Microsoft 365](../develop/unified-manifest-overview.md). + ### Web app The most basic Office Add-in consists of a static HTML page that is displayed inside an Office application, but that doesn't interact with either the Office document or any other Internet resource. However, to create an experience that interacts with Office documents or allows the user to interact with online resources from an Office client application, you can use any technologies, both client and server side, that your hosting provider supports (such as ASP.NET, PHP, or Node.js). To interact with Office clients and documents, you use the Office.js JavaScript APIs. @@ -63,9 +58,11 @@ The most basic Office Add-in consists of a static HTML page that is displayed in Office Add-ins can do the following within an Office client application. -- Extend functionality (any Office application) +- Extend functionality + +- Carry out natural language instructions from Copilot (preview) -- Create new objects (Excel or PowerPoint) +- Create new objects (Excel or PowerPoint only) ### Extend Office functionality @@ -73,9 +70,11 @@ You can add new functionality to Office applications via the following:   - Custom ribbon buttons and menu commands (collectively called "add-in commands"). -- Insertable task panes. +- Insertable task panes with a webview control that can do almost anything a webpage can do inside a browser. -Custom UI and task panes are specified in the add-in manifest.   +- Event handlers that respond to events in the Office document or Office application. + +Custom UI, task panes, and event handlers are specified in the add-in manifest.   #### Custom buttons and menu commands   @@ -85,7 +84,7 @@ You can add custom ribbon buttons and menu items to the ribbon in Office on the #### Task panes   -You can use task panes in addition to add-in commands to enable users to interact with your solution. Clients that don't support add-in commands (Office on iPad) run your add-in as a task pane. In Excel, Word, and PowerPoint, users launch task pane add-ins via the **Home** > **Add-ins** button. In Outlook, users launch task pane add-ins via the add-in button or via the **All Apps** button on the ribbon. +You can use task panes in addition to add-in commands to enable users to interact with your solution. In Excel, Word, and PowerPoint, users launch task pane add-ins via the **Home** > **Add-ins** button. In Outlook, users launch task pane add-ins via the add-in button or via the **All Apps** button on the ribbon. ![Use task panes in addition to add-in commands.](../images/about-addins-taskpane.png) @@ -102,9 +101,13 @@ Users can run Outlook add-ins when they view, reply, or create emails, meeting r For an overview of Outlook add-ins, see [Outlook add-ins overview](../outlook/outlook-add-ins-overview.md). +### Carry out Copilot instructions (preview) + +You can create custom Copilot agents that enable your users to read and write to Office documents with natural language instructions entered in Copilot chat. For more information, see [Combine Copilot Agents with Office Add-ins (preview)](../design/agent-and-add-in-overview.md). + ### Create new objects in Office documents -You can embed web-based objects called content add-ins within Excel and PowerPoint documents. With content add-ins, you can integrate rich, web-based data visualizations, media (such as a YouTube video player or a picture gallery), and other external content. +You can embed web-based objects, called content add-ins, within Excel and PowerPoint documents. With content add-ins, you can integrate rich, web-based data visualizations, media (such as a YouTube video player or a picture gallery), and other external content. ![Embed web-based objects called content add-ins.](../images/about-addins-contentaddin.png) @@ -120,6 +123,27 @@ Learn how to build the simplest Office Add-in with only a manifest, HTML web pag - [Outlook "Hello world" add-in](https://github.com/OfficeDev/Office-Add-in-samples/tree/main/Samples/hello-world/outlook-hello-world) - [PowerPoint "Hello world" add-in](https://github.com/OfficeDev/Office-Add-in-samples/tree/main/Samples/hello-world/powerpoint-hello-world) - [Word "Hello world" add-in](https://github.com/OfficeDev/Office-Add-in-samples/tree/main/Samples/hello-world/word-hello-world) +- [Create data analysis charts in Excel with a Copilot agent](https://github.com/OfficeDev/Office-Add-in-samples/tree/main/Samples/excel-copilot-agent) + +## How are Office Add-ins different from COM and VSTO add-ins? + +COM and VSTO add-ins are earlier Office integration solutions that run only in Office on Windows. Unlike COM and VSTO add-ins, Office Add-ins are web add-ins: the application (for example, Excel), reads the add-in manifest and connects the add-in's custom ribbon buttons and menu commands in the UI. When needed, it loads the add-in's JavaScript and HTML code, which runs in the context of a browser or webview control in a sandbox. + +![A four-quadrant diagram showing the focus areas for different Office extensibility solutions. Office Web Add-ins along with COM and VSTO add-ins target professional developers, while VBA and Office Scripts target end users. Office Web Add-ins are focused on cross-platform experiences while COM and VSTO add-ins and VBA are applicable only in Windows.](../images/office-programmability-diagram.png) + +Office Add-ins provide the following advantages over add-ins built using VBA, COM, or VSTO. + +- Cross-platform support: Office Add-ins run in Office on the web, Windows, Mac, and iPad. + +- Apps for Microsoft 365 support: Office Add-ins can be packaged with other Microsoft 365 extensions, such as Teams apps and Copilot agents for deployment as a single unit. + +- Centralized deployment and distribution: Admins can deploy Office Add-ins centrally across an organization. + +- Easy access via Microsoft Marketplace: You can make your solution available to a broad audience by submitting it to Microsoft Marketplace. + +- Based on standard web technology: You can use any library you like to build Office Add-ins. + +[!INCLUDE [new-outlook-vsto-com-support](../includes/new-outlook-vsto-com-support.md)] ## Next steps diff --git a/docs/testing/sideload-add-in-with-unified-manifest.md b/docs/testing/sideload-add-in-with-unified-manifest.md index 44c81afda2..824ca4dc30 100644 --- a/docs/testing/sideload-add-in-with-unified-manifest.md +++ b/docs/testing/sideload-add-in-with-unified-manifest.md @@ -1,7 +1,7 @@ --- title: Sideload Office Add-ins that use the unified manifest for Microsoft 365 description: Test your Office Add-in on Windows by sideloading. -ms.date: 08/13/2025 +ms.date: 12/10/2025 ms.localizationpriority: medium --- @@ -63,7 +63,7 @@ There are two tools you can use to sideload. ### Sideload with Microsoft 365 Agents Toolkit CLI (command-line interface) -1. Create a zip package. See [Manually create the add-in package file](#manually-create-the-add-in-package-file). +1. Create a zip package. See [Manually create the app package file](../overview/app-package-for-microsoft-365.md#manually-create-the-app-package-file). 1. In the root of the project, open a command prompt or bash shell and run the following command to install the Agents Toolkit CLI. @@ -103,7 +103,7 @@ There are two tools you can use to sideload. Add-ins that use the unified manifest can be manually sideloaded through the Teams app store, even if they have no Teams-related functionality. The steps are as follows. -1. Create an app package manually if it hasn't already been created by a tool. See [Manually create the add-in package file](#manually-create-the-add-in-package-file). +1. Create an app package manually if it hasn't already been created by a tool. See [Manually create the app package file](../overview/app-package-for-microsoft-365.md#manually-create-the-app-package-file). 1. Close all Office applications, and then clear the Office cache following the instructions at [Manually clear the cache](../testing/clear-cache.md#manually-clear-the-cache). 1. Open Teams and select **Apps** from the app bar, then select **Manage your apps** at the bottom of the **Apps** pane. 1. Select **Upload an app** in the **Apps** dialog, and then in the dialog that opens, select **Upload a custom app**. @@ -135,49 +135,3 @@ Add-ins that use the unified manifest can be manually sideloaded through the Tea > > Make your changes and then sideload the add-in again. -## Manually create the add-in package file - -When the unified manifest is used, the unit of installation and sideloading is a zip-formatted package file. This file is usually created for you by the tools you use to create and test your add-in, but there are scenarios in which you create it manually. To do so, use any zip utility to create a zip file that contains the following files. - -- The unified manifest, which goes in the root of the zip file. -- The two image files referenced in the `"icons"` property of the manifest. -- Any localization files that are referenced in the `"localizationInfo"` property of the manifest. -- Any declarative agent files that are referenced in the `"copilotAgents"` property. -- Any second-level supplementary files. For example, declarative agent configuration files sometimes reference second-level supplementary files, such as plugin configuration files. These should be included too. - -> [!IMPORTANT] -> *All of these files must have the same relative path in the zip file as specified in the manifest.* For example, if the path of the two image files is **assets/icon-64.png** and **assets/icon-128.png**, then you must include an **assets** folder with the two files in the zip package. Second-level files, such as plugin configuration files for declarative agents, must have the same relative path in the zip file as they do in the first-level file that references them. For example, if the relative path of a declarative agent file specified in the manifest is **agents/myAgent.json**, then you must include an **agents** folder in the zip package and put the **myAgent.json** file in it. If the declarative agent file, in turn, gives the relative path of **plugins/myPlugin.json** for a plugin configuration file, then you must include a **plugins** subfolder under the **agents** folder and put the **myPlugin.json** file in it. - -To maximize compatibility with Microsoft 365 development tools, we recommend that you keep the files that will be included in the package in a folder called **appPackage** in the root of your project, and that you put the package file in a subfolder named **build** in the **appPackage** folder. - -The following are examples of the recommended structure. The structure inside the **\build\appPackage.zip** file must mirror the structure of the **appPackage** folder, except for the **build** folder itself. - -```console -\appPackage - \assets - color.png - outline.png - \build - appPackage.zip - manifest.json -``` - -```console -\appPackage - \agents - myAgent.json - \plugins - myPlugin.json - \assets - color.png - outline.png - \build - appPackage.zip - \languages - fr-FR.json - es-MX.json - manifest.json -``` - -> [!NOTE] -> The JSON files that are referenced in the `"extensions.keyboardShortcuts.keyMappingFiles"` property are *not* included in the app package. They are deployed with the add-in's web application files. For more information, see [Support backward compatibility for add-ins with a unified manifest in Microsoft Marketplace](../design/keyboard-shortcuts.md#support-backward-compatibility-for-add-ins-with-a-unified-manifest-in-microsoft-marketplace). \ No newline at end of file diff --git a/docs/toc.yml b/docs/toc.yml index 98231fc44e..cabe4a59bf 100644 --- a/docs/toc.yml +++ b/docs/toc.yml @@ -122,9 +122,11 @@ displayName: event-based activation - name: Run code on document open href: develop/run-code-on-document-open.md - - name: Manifest + - name: App package and manifest items: - - name: Overview + - name: App package for Microsoft 365 + href: overview/app-package-for-microsoft-365.md + - name: Manifest overview href: develop/add-in-manifests.md - name: Unified manifest for Microsoft 365 items: