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

[All Hosts] (manifest) reorg the manifest part of the TOC #4727

Open
wants to merge 9 commits into
base: main
Choose a base branch
from
5 changes: 2 additions & 3 deletions docs/develop/json-manifest-overview.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,16 +2,15 @@
title: Compare the add-in only manifest with the unified manifest for Microsoft 365
description: Get a comparison of the add-in only manifest with the unified manifest for Microsoft 365.
ms.topic: overview
ms.date: 09/09/2024
ms.date: 12/11/2024
ms.localizationpriority: high
---

# Compare the add-in only manifest with the unified manifest for Microsoft 365

This article is intended to help readers who are familiar with the add-in only manifest understand the unified manifest by comparing the two. Readers should also see [Office Add-ins with the unified manifest for Microsoft 365](unified-manifest-overview.md).

> [!NOTE]
> The unified manifest currently only supports Outlook add-ins and only in Office linked to a Microsoft 365 subscription and installed on Windows, on a mobile device, or in Outlook on the web. We're working on extending support to Excel, PowerPoint, and Word, as well as to Outlook on Mac, and to perpetual versions of Office.
[!include[Unified manifest host application support note](../includes/unified-manifest-support-note.md)]

## Schemas and general points

Expand Down
7 changes: 2 additions & 5 deletions docs/develop/unified-manifest-overview.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
title: Office Add-ins with the unified app manifest for Microsoft 365
description: Get an overview of the unified app manifest for Microsoft 365 for Office Add-ins and its uses.
ms.topic: overview
ms.date: 09/26/2024
ms.date: 12/11/2024
ms.localizationpriority: high
---

Expand All @@ -21,10 +21,7 @@ One important improvement is the ability to create a single unit of distribution

We've taken an important first step toward these goals by making it possible for you to create Outlook add-ins with a unified manifest for Microsoft 365.

> [!NOTE]
>
> - The unified manifest currently only supports Outlook add-ins and only in Office linked to a Microsoft 365 subscription and installed on Windows, on a mobile device, or in Outlook on the web. We're working on extending support to Excel, PowerPoint, and Word, as well as to Outlook on Mac, and to perpetual versions of Office.
> - The unified manifest requires Office Version 2304 (Build 16320.00000) or later.
[!include[Unified manifest host application support note](../includes/unified-manifest-support-note.md)]

> [!TIP]
> Ready to get started with the unified manifest? Begin with [Build an Outlook add-in with the unified manifest for Microsoft 365](../quickstarts/outlook-quickstart-json-manifest.md).
Expand Down
7 changes: 6 additions & 1 deletion docs/includes/manifest-guidance.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,12 @@
> [!TIP]
> If you'll be testing your add-in across multiple environments (for example, in development, staging, demo, etc.), we recommend that you maintain a different manifest file for each environment. In each manifest file, you can:
>
> - Specify the URLs that correspond to the environment.
> - Customize metadata values like `DisplayName` and labels within `Resources` to indicate the environment, so that end users will be able to identify a sideloaded add-in's corresponding environment.
> - Customize metadata values so that end users are able to identify a sideloaded add-in's corresponding environment. For example:
>
> - In the unified manifest for Microsoft 365, customize the "name" property of the add-in and the "label" properties for various UI controls to indicate the environment.
> - In the add-in only manifest, customize the `DisplayName` element and and labels within the `Resources` element to indicate the environment.
>
> - Customize the custom functions `namespace` to indicate the environment, if your add-in defines custom functions.
>
> By following this guidance, you'll streamline the testing process and avoid issues that would otherwise occur when an add-in is simultaneously sideloaded for multiple environments.
3 changes: 2 additions & 1 deletion docs/includes/unified-manifest-support-note.md
Original file line number Diff line number Diff line change
@@ -1,2 +1,3 @@
> [!NOTE]
> The [unified manifest for Microsoft 365](../develop/unified-manifest-overview.md) can be used in production Outlook add-ins. It is available only as a preview for Excel, PowerPoint, and Word add-ins.
> The [unified manifest for Microsoft 365](../develop/unified-manifest-overview.md) can be used in production Outlook add-ins. It's available only as a preview for Excel, PowerPoint, and Word add-ins.