Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Doc Improvement] add note to combined add-in & app article #11883

Open
wants to merge 10 commits into
base: main
Choose a base branch
from
Original file line number Diff line number Diff line change
Expand Up @@ -47,6 +47,9 @@ Before you start work merging your two existing extensions, get a sense of how t
- How the single unified manifest is created.
- The differences in how the add-in and the Teams app are sideloaded and debugged.

> [!NOTE]
> Although the article uses an Outlook add-in, the general process of combining an add-in with a Teams app also applies to Excel, PowerPoint, and Word add-ins.

## Follow proper principles for combining Teams apps and add-ins

When you are ready to merge your existing add-in and Teams app, follow these principles:
Expand All @@ -56,7 +59,7 @@ When you are ready to merge your existing add-in and Teams app, follow these pri
- Keep configuration files that are applicable to both the add-in and Teams app in the root of the project.
- Move source files and configuration files that are only applicable to the Teams app into a subfolder off the root of the project. Similarly, copy source and configuration files that are only used by the add-in from the existing add-in to a different subfolder off the root of the combined project.
- Use the same base domain for the built files of both the add-in and Teams app; for example, contoso.com.
- Merge the two manifests into a single manifest. Use the process you went through in step 1 as a guide.
- Merge the two manifests into a single manifest. Use the process you went through in [add an Outlook Add-in to a Teams app](combine-office-add-in-and-teams-app.md) as a guide.
- The [id](../resources/schema/manifest-schema.md#id) property in the new manifest should be the same value as the "id" property in the original Teams app manifest.
- Raise the value of the [version](../resources/schema/manifest-schema.md#version) property; for example, raise "1.0.0" to "1.1.0".
- Add an [extensions.alternates](../resources/schema/manifest-schema.md#extensionsalternates) property to the manifest and configure it to hide the original Office add-in in versions of Office that support combining an add-in and a Teams app. For more information, see [Manage new and old versions of an add-in](/office/dev/add-ins/concepts/duplicate-legacy-metaos-add-ins).
Expand Down