You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Install the latest version of Teams Toolkit into Visual Studio Code as described in [Install Teams Toolkit](/microsoftteams/platform/toolkit/install-teams-toolkit?tabs=vscode).
21
+
Install the latest version of Agents Toolkit into Visual Studio Code as described in [Install Microsoft 365 Agents Toolkit](/microsoftteams/platform/toolkit/install-teams-toolkit?tabs=vscode).
22
22
23
23
> [!IMPORTANT]
24
-
> You can create an Outlook add-in with the latest released version of Teams Toolkit. To create an add-in for Excel, PowerPoint, or Word, install the prerelease version as described in [Install a prerelease version](/microsoftteams/platform/toolkit/install-teams-toolkit?tabs=vscode#install-a-prerelease-version). The toolkit creates projects that use the [unified manifest for Microsoft 365](json-manifest-overview.md). Support for this manifest in Excel, PowerPoint, and Word is preview only.
24
+
> You can create an Outlook add-in with the latest released version of Agents Toolkit. To create an add-in for Excel, PowerPoint, or Word, install the prerelease version as described in [Install a prerelease version](/microsoftteams/platform/toolkit/install-teams-toolkit?tabs=vscode#install-a-prerelease-version). The toolkit creates projects that use the [unified manifest for Microsoft 365](json-manifest-overview.md). Support for this manifest in Excel, PowerPoint, and Word is preview only.
25
25
26
26
## Create an Office Add-in project
27
27
28
-
1. Open Visual Studio Code and select Teams Toolkit icon in the **Activity Bar**.
28
+
1. Open Visual Studio Code and select the Agents Toolkit icon in the **Activity Bar**.
1. The **New Project** dropdown menu opens. The options listed will vary depending on your version of Teams Toolkit. Select **Office Add-in**.
33
+
1. The **New Project** dropdown menu opens. The options listed will vary depending on your version of Agents Toolkit. Select **Office Add-in**.
34
34
35
-
:::image type="content" source="../images/teams-toolkit-create-office-add-in.png" alt-text="The options in New Project dropdown menu. The last option is called 'Office Add-in'.":::
35
+
:::image type="content" source="../images/atk-toolkit-new-project-list.png" alt-text="The options in New Project dropdown menu. One option is called 'Office Add-in'.":::
36
36
37
-
1. The **App Features Using an Office Add-in** dropdown menu opens. The options listed will vary depending on your version of Teams Toolkit. Select **Task pane**.
37
+
1. The **App Features Using an Office Add-in** dropdown menu opens. The options listed will vary depending on your version of Agents Toolkit. Select **Task pane**.
38
38
39
39
:::image type="content" source="../images/teams-toolkit-create-office-task-pane-capability.png" alt-text="The options in the App Features Using an Office Add-in dropdown menu. The option 'Task pane' is selected.":::
40
40
41
41
1. In the **Workspace Folder** dialog that opens, select the folder where you want to create the project.
42
-
1. Give a name to the project (with no spaces) when prompted. Teams Toolkit will create the project with basic files and scaffolding. It will then open the project *in a second Visual Studio Code window*. Close the original Visual Studio Code window.
42
+
1. Give a name to the project (with no spaces) when prompted. Agents Toolkit will create the project with basic files and scaffolding. It will then open the project *in a second Visual Studio Code window*. Close the original Visual Studio Code window.
43
43
44
44
> [!NOTE]
45
45
> The project that's generated is configured to be installable on Excel, Outlook, PowerPoint, and Word. You can edit the manifest and source files as needed to change which Office applications are supported.
@@ -76,11 +76,11 @@ Install the latest version of Teams Toolkit into Visual Studio Code as described
76
76
### Sideload in Outlook
77
77
78
78
> [!NOTE]
79
-
> If your development computer is Windows, be sure that your Outlook client is classic Outlook for Windows, not [new Outlook on Windows](https://support.microsoft.com/office/656bb8d9-5a60-49b2-a98b-ba7822bc7627). There is currently a bug that prevents add-ins created with the Teams Toolkit from properly sideloading in new Outlook for Windows or in Outlook on the web.
79
+
> If your development computer is Windows, be sure that your Outlook client is classic Outlook for Windows, not [new Outlook on Windows](https://support.microsoft.com/office/656bb8d9-5a60-49b2-a98b-ba7822bc7627). There is currently a bug that prevents add-ins created with Agents Toolkit from properly sideloading in new Outlook for Windows or in Outlook on the web.
80
80
81
81
1. Ensure that your account in your Microsoft 365 developer tenancy is also an email account in desktop Outlook. If it isn't, follow the guidance in [Add an email account to Outlook](https://support.microsoft.com/office/e9da47c4-9b89-4b49-b945-a204aeea6726).
82
82
1.**Close Outlook desktop**.
83
-
1. In Visual Studio Code, open Teams Toolkit.
83
+
1. In Visual Studio Code, open Agents Toolkit.
84
84
1. In the **ACCOUNTS** section, verify that you're signed into Microsoft 365.
85
85
1. Select **View** | **Run** in Visual Studio Code. In the **RUN AND DEBUG** dropdown menu, select the option, **Outlook Desktop (Edge Chromium)**, and then press F5. The project builds and a Node dev-server window opens. This process may take a couple of minutes and then Outlook desktop will open.
Copy file name to clipboardExpand all lines: docs/develop/convert-xml-to-json-manifest.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: Convert an add-in to use the unified manifest for Microsoft 365
3
3
description: Learn the various methods for converting an add-in with an add-in only manifest to the unified manifest for Microsoft 365 and sideload the add-in.
4
4
ms.topic: how-to
5
-
ms.date: 05/08/2025
5
+
ms.date: 05/19/2025
6
6
ms.localizationpriority: medium
7
7
---
8
8
@@ -24,7 +24,7 @@ There are three basic tasks to converting an add-in project from the add-in only
24
24
>
25
25
> - Add-ins that use the unified manifest can be sideloaded only on Office Version 2304 (Build 16320.20000) or later.
26
26
> - Projects created in Visual Studio, as distinct from Visual Studio Code, can't be converted at this time.
27
-
> - If you [created the project with Teams Toolkit](teams-toolkit-overview.md) or with the "unified manifest" option in the [Office Yeoman Generator](yeoman-generator-overview.md), it already uses the unified manifest.
27
+
> - If you [created the project with Teams Toolkit or Microsoft 365 Agents Toolkit](agents-toolkit-overview.md) or with the "unified manifest" option in the [Office Yeoman Generator](yeoman-generator-overview.md), it already uses the unified manifest.
28
28
29
29
## Ensure that your manifest is ready to convert
30
30
@@ -102,7 +102,7 @@ There are several ways to carry out the remaining tasks, depending on the IDE an
102
102
-[Convert NodeJS and npm projects that weren't created with the Yeoman generator for Office Add-ins (Yo Office)](#convert-nodejs-and-npm-projects-that-werent-created-with-the-yeoman-generator-for-office-add-ins-yo-office)
103
103
104
104
> [!NOTE]
105
-
> Conversion of the manifest is one of the effects of importing the add-in project into Teams Toolkit if you do so using the toolkit's importation feature. For details, see [Import an add-in project to Teams Toolkit](import-teams-toolkit.md)
105
+
> Conversion of the manifest is one of the effects of importing the add-in project into Agents Toolkit if you do so using the toolkit's importation feature. For details, see [Import an add-in project to Agents Toolkit](import-teams-toolkit.md)
106
106
107
107
### Convert projects created with the Yeoman generator for Office Add-ins (aka "Yo Office")
Copy file name to clipboardExpand all lines: docs/develop/create-addin-commands-unified-manifest.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: Create add-in commands with the unified manifest for Microsoft 365
3
3
description: Configure the unified manifest for Microsoft 365 to define add-in commands for Excel, Outlook, PowerPoint, and Word. Use add-in commands to create UI elements, add buttons or lists, and perform actions.
4
-
ms.date: 02/12/2025
4
+
ms.date: 05/19/2025
5
5
ms.localizationpriority: medium
6
6
---
7
7
@@ -20,7 +20,7 @@ This article describes how to configure the [Unified manifest for Microsoft 365]
20
20
21
21
## Starting point and major steps
22
22
23
-
Both of the tools that create add-in projects with a unified manifest — the [Office Yeoman generator](yeoman-generator-overview.md) and [Teams Toolkit](teams-toolkit-overview.md)— create projects with one or more add-in commands. The only time you won't already have an add-in command is if you are updating an add-in which previously didn't have one.
23
+
Both of the tools that create add-in projects with a unified manifest — the [Office Yeoman generator](yeoman-generator-overview.md) and [Microsoft 365 Agents Toolkit](agents-toolkit-overview.md)— create projects with one or more add-in commands. The only time you won't already have an add-in command is if you are updating an add-in which previously didn't have one.
Copy file name to clipboardExpand all lines: docs/develop/develop-overview.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: Develop Office Add-ins
3
3
description: An introduction to developing Office Add-ins.
4
4
ms.topic: overview
5
-
ms.date: 03/12/2025
5
+
ms.date: 05/19/2025
6
6
ms.localizationpriority: high
7
7
---
8
8
@@ -15,7 +15,7 @@ All Office Add-ins are built upon the Office Add-ins platform. For any add-in yo
15
15
16
16
## Create an Office Add-in
17
17
18
-
You can create an Office Add-in by using the [Yeoman generator for Office Add-ins](yeoman-generator-overview.md), Visual Studio, Teams Toolkit, or the [Office Add-ins Development Kit (preview)](development-kit-overview.md).
18
+
You can create an Office Add-in by using the [Yeoman generator for Office Add-ins](yeoman-generator-overview.md), Visual Studio, Microsoft 365 Agents Toolkit, or the [Office Add-ins Development Kit](development-kit-overview.md).
19
19
20
20
### Yeoman generator
21
21
@@ -35,9 +35,9 @@ Create your project using HTML, CSS and JavaScript (or TypeScript), or using Rea
35
35
36
36
Visual Studio can be used to create Office Add-ins for Excel, Outlook, Word, and PowerPoint. An Office Add-in project gets created as part of a Visual Studio solution and uses HTML, CSS, and JavaScript. For more information about creating add-ins with Visual Studio, see [Develop Office Add-ins with Visual Studio](../develop/develop-add-ins-visual-studio.md).
37
37
38
-
### Teams Toolkit
38
+
### Agents Toolkit
39
39
40
-
The Teams Toolkit can be used to create almost any kind of Teams App, a term which includes all extensions of Microsoft 365, including those that don't extend the Teams application. For details about creating an add-in, see [Create Office Add-in projects with Teams Toolkit](teams-toolkit-overview.md).
40
+
The Agents Toolkit can be used to create almost any kind of Microsoft 365 extension. For details about creating an add-in, see [Create Office Add-in projects with Microsoft 365 Agents Toolkit](agents-toolkit-overview.md).
0 commit comments