diff --git a/types/office-js-preview/index.d.ts b/types/office-js-preview/index.d.ts index 7da13628f6d3ef..2abeb0afd159da 100644 --- a/types/office-js-preview/index.d.ts +++ b/types/office-js-preview/index.d.ts @@ -10822,7 +10822,7 @@ declare namespace Office { * Specifies the status of Exchange Web Services (EWS) callback tokens or REST API tokens in an organization. * * @remarks - * [Api set: Mailbox preview] + * [Api set: Mailbox 1.16] * * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-add-ins-overview#extension-points | Applicable Outlook mode}**: Compose or Read * @@ -10830,8 +10830,6 @@ declare namespace Office { * If an Outlook add-in requires delegated user access or user identity, we recommend using MSAL (Microsoft Authentication Library) and nested app authentication (NAA). * Exchange user identity tokens are still supported for Exchange on-premises. For more information, see * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | Nested app authentication FAQ}. - * - * @beta */ enum TokenStatus { /** @@ -11151,7 +11149,8 @@ declare namespace Office { /** * Manages the {@link Office.SessionData | SessionData} of an item in Compose mode. * - * **Important**: The entire SessionData object is limited to 50,000 characters per add-in. + * **Important**: In Outlook clients that support Mailbox 1.15 or earlier, the entire SessionData object for each mail item is limited to 50,000 characters per add-in. + * In clients that support Mailbox 1.16 or later, the character limit per add-in is 2,621,440 characters. * * @remarks * [Api set: Mailbox 1.11] @@ -12564,13 +12563,13 @@ declare namespace Office { * The `optionalAttendees` property returns an array that contains an {@link Office.EmailAddressDetails | EmailAddressDetails} object for * each optional attendee to the meeting. The maximum number of attendees returned varies per Outlook client. * - * - Windows (new and classic): 500 attendees + * - Windows (classic - Mailbox 1.15 and earlier): 500 attendees * - * - Windows (classic - in preview starting in Version 2511 (Build 19426.20000)): 1,000 attendees + * - Web, Windows (new, classic - Mailbox 1.16 and later): 1,000 recipients * * - Android, classic Mac UI, iOS: 100 attendees * - * - New Mac UI, web browser: No limit + * - New Mac UI: No limit * * @remarks * @@ -12614,13 +12613,13 @@ declare namespace Office { * The `requiredAttendees` property returns an array that contains an {@link Office.EmailAddressDetails | EmailAddressDetails} object for * each required attendee to the meeting. The maximum number of attendees returned varies per Outlook client. * - * - Windows (new and classic): 500 attendees + * - Windows (classic - Mailbox 1.15 and earlier): 500 attendees * - * - Windows (classic - in preview starting in Version 2511 (Build 19426.20000)): 1,000 recipients + * - Web, Windows (new, classic - Mailbox 1.16 and later): 1,000 recipients * * - Android, classic Mac UI, iOS: 100 attendees * - * - New Mac UI, web browser: No limit + * - New Mac UI: No limit * * @remarks * @@ -13414,18 +13413,15 @@ declare namespace Office { * Gets the content identifier of an inline attachment. * * @remarks + * [Api set: Mailbox 1.16] * - * **Important**: - * - * - The `contentId` property is only supported in Outlook on the web, the new Outlook on Windows, and classic Outlook on Windows (preview). - * To preview the `contentId` property in classic Outlook on Windows, your Outlook client must run Version 2510 (Build 19312.20000) - * or later and must be on the Beta Channel. For more information, see {@link https://aka.ms/Msft365InsiderProgram | Microsoft 365 Insider Program}. - * - * - Changes to how inline images are represented in the HTML body of Outlook emails in Outlook on the web and the new Outlook on Windows released on November 15, 2025. + * **Important**: Changes to how inline images are represented in the HTML body of Outlook emails in + * Outlook on the web and the new Outlook on Windows released on November 15, 2025. * Previously, the attachment ID of the image appeared in the `src` attribute of the applicable `` element. * Now, the image is represented by a content ID (`cid`) in the `src` attribute instead. - * If you parse the attachment ID from the HTML editor or get the Base64-encoded value of the image from the URL in the `src` attribute, you must update your add-in's parsing logic. - * For more information, see {@link https://devblogs.microsoft.com/microsoft365dev/changes-to-inline-images-in-outlook | Changes to inline image representation in Outlook on the web and new Outlook for Windows}. + * If you parse the attachment ID from the HTML editor or get the Base64-encoded value of the image from the URL in the + * `src` attribute, you must update your add-in's parsing logic. For more information, see + * {@link https://devblogs.microsoft.com/microsoft365dev/changes-to-inline-images-in-outlook | Changes to inline image representation in Outlook on the web and new Outlook for Windows}. */ contentId: string; /** @@ -13517,18 +13513,15 @@ declare namespace Office { * Gets the content identifier of an inline attachment. * * @remarks + * [Api set: Mailbox 1.16] * - * **Important**: - * - * - The `contentId` property is only supported in Outlook on the web, the new Outlook on Windows, and classic Outlook on Windows (preview). - * To preview the `contentId` property in classic Outlook on Windows, your Outlook client must run Version 2510 (Build 19312.20000) - * or later and must be on the Beta Channel. For more information, see {@link https://aka.ms/Msft365InsiderProgram | Microsoft 365 Insider Program}. - * - * - Changes to how inline images are represented in the HTML body of Outlook emails in Outlook on the web and the new Outlook on Windows released on November 15, 2025. + * **Important**: Changes to how inline images are represented in the HTML body of Outlook emails in + * Outlook on the web and the new Outlook on Windows released on November 15, 2025. * Previously, the attachment ID of the image appeared in the `src` attribute of the applicable `` element. * Now, the image is represented by a content ID (`cid`) in the `src` attribute instead. - * If you parse the attachment ID from the HTML editor or get the Base64-encoded value of the image from the URL in the `src` attribute, you must update your add-in's parsing logic. - * For more information, see {@link https://devblogs.microsoft.com/microsoft365dev/changes-to-inline-images-in-outlook | Changes to inline image representation in Outlook on the web and new Outlook for Windows}. + * If you parse the attachment ID from the HTML editor or get the Base64-encoded value of the image from the URL in the + * `src` attribute, you must update your add-in's parsing logic. For more information, see + * {@link https://devblogs.microsoft.com/microsoft365dev/changes-to-inline-images-in-outlook | Changes to inline image representation in Outlook on the web and new Outlook for Windows}. */ contentId: string; /** @@ -14748,15 +14741,13 @@ declare namespace Office { * * @remarks * - * [Api set: Mailbox preview] + * [Api set: Mailbox 1.16] * * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/understanding-outlook-add-in-permissions | Minimum permission level}**: **read/write item** * * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-add-ins-overview#extension-points | Applicable Outlook mode}**: Message Read * * To learn how to develop an encryption add-in in Outlook, see {@link https://learn.microsoft.com/office/dev/add-ins/outlook/encryption-decryption | Create an encryption Outlook add-in}. - * - * @beta */ interface DecryptedMessageAttachment { /** @@ -14764,15 +14755,13 @@ declare namespace Office { * * @remarks * - * [Api set: Mailbox preview] + * [Api set: Mailbox 1.16] * * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/understanding-outlook-add-in-permissions | Minimum permission level}**: **read/write item** * * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-add-ins-overview#extension-points | Applicable Outlook mode}**: Message Read * * **Important**: Attachments of type `MailboxEnums.AttachmentType.Item` aren't currently supported. - * - * @beta */ attachmentType: MailboxEnums.AttachmentType; /** @@ -14780,15 +14769,13 @@ declare namespace Office { * * @remarks * - * [Api set: Mailbox preview] + * [Api set: Mailbox 1.16] * * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/understanding-outlook-add-in-permissions | Minimum permission level}**: **read/write item** * * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-add-ins-overview#extension-points | Applicable Outlook mode}**: Message Read * * **Important**: The `content` property isn't supported by attachments of type `MailboxEnums.AttachmentType.Cloud`. - * - * @beta */ content: string; /** @@ -14798,7 +14785,7 @@ declare namespace Office { * * @remarks * - * [Api set: Mailbox preview] + * [Api set: Mailbox 1.16] * * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/understanding-outlook-add-in-permissions | Minimum permission level}**: **read/write item** * @@ -14808,8 +14795,6 @@ declare namespace Office { * specified in the `src` attribute of the `` element (for example, ``). * To easily identify and provide these inline attachments during decryption, we recommend saving the content IDs of inline attachments to the message header during encryption. * Call `Office.context.mailbox.item.getAttachmentsAsync` to get the content ID of an inline attachment. Then, call `Office.context.mailbox.item.internetHeaders.setAsync` to save the ID to the header of the message. - * - * @beta */ contentId?: string; /** @@ -14818,13 +14803,11 @@ declare namespace Office { * * @remarks * - * [Api set: Mailbox preview] + * [Api set: Mailbox 1.16] * * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/understanding-outlook-add-in-permissions | Minimum permission level}**: **read/write item** * * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-add-ins-overview#extension-points | Applicable Outlook mode}**: Message Read - * - * @beta */ isInline?: boolean; /** @@ -14832,13 +14815,11 @@ declare namespace Office { * * @remarks * - * [Api set: Mailbox preview] + * [Api set: Mailbox 1.16] * * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/understanding-outlook-add-in-permissions | Minimum permission level}**: **read/write item** * * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-add-ins-overview#extension-points | Applicable Outlook mode}**: Message Read - * - * @beta */ name: string; /** @@ -14847,13 +14828,11 @@ declare namespace Office { * * @remarks * - * [Api set: Mailbox preview] + * [Api set: Mailbox 1.16] * * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/understanding-outlook-add-in-permissions | Minimum permission level}**: **read/write item** * * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-add-ins-overview#extension-points | Applicable Outlook mode}**: Message Read - * - * @beta */ path?: string; } @@ -14862,15 +14841,13 @@ declare namespace Office { * * @remarks * - * [Api set: Mailbox preview] + * [Api set: Mailbox 1.16] * * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/understanding-outlook-add-in-permissions | Minimum permission level}**: **read/write item** * * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-add-ins-overview#extension-points | Applicable Outlook mode}**: Message Read * * To learn how to develop an encryption add-in in Outlook, see {@link https://learn.microsoft.com/office/dev/add-ins/outlook/encryption-decryption | Create an encryption Outlook add-in}. - * - * @beta */ interface DecryptedMessageBody { /** @@ -14879,13 +14856,11 @@ declare namespace Office { * * @remarks * - * [Api set: Mailbox preview] + * [Api set: Mailbox 1.16] * * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/understanding-outlook-add-in-permissions | Minimum permission level}**: **read/write item** * * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-add-ins-overview#extension-points | Applicable Outlook mode}**: Message Read - * - * @beta */ coercionType: Office.CoercionType; /** @@ -14893,13 +14868,11 @@ declare namespace Office { * * @remarks * - * [Api set: Mailbox preview] + * [Api set: Mailbox 1.16] * * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/understanding-outlook-add-in-permissions | Minimum permission level}**: **read/write item** * * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-add-ins-overview#extension-points | Applicable Outlook mode}**: Message Read - * - * @beta */ content: string; } @@ -15034,22 +15007,16 @@ declare namespace Office { * * @remarks * - * [Api set: Mailbox preview] + * [Api set: Mailbox 1.16] * * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/understanding-outlook-add-in-permissions | Minimum permission level}**: **read item** * * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-add-ins-overview#extension-points | Applicable Outlook mode}**: Compose or Read * - * **Important**: - * - * - The `ews` property is available for preview in Outlook on the web and on Windows (new and classic (Version 2510, Build 19328.20000 and later)). - * - * - Legacy Exchange Online user identity tokens and callback tokens are no longer supported and are turned off across all Microsoft 365 tenants. + * **Important**: Legacy Exchange Online user identity tokens and callback tokens are no longer supported and are turned off across all Microsoft 365 tenants. * If an Outlook add-in requires delegated user access or user identity, we recommend using MSAL (Microsoft Authentication Library) and nested app authentication (NAA). * Exchange user identity tokens are still supported for Exchange on-premises. For more information, see * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | Nested app authentication FAQ}. - * - * @beta */ ews: Ews; /** @@ -15854,7 +15821,7 @@ declare namespace Office { * * @remarks * - * [Api set: Mailbox preview] + * [Api set: Mailbox 1.16] * * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/understanding-outlook-add-in-permissions | Minimum permission level}**: **read item** * @@ -15864,8 +15831,6 @@ declare namespace Office { * If an Outlook add-in requires delegated user access or user identity, we recommend using MSAL (Microsoft Authentication Library) and nested app authentication (NAA). * Exchange user identity tokens are still supported for Exchange on-premises. For more information, see * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | Nested app authentication FAQ}. - * - * @beta */ interface Ews { /** @@ -15873,7 +15838,7 @@ declare namespace Office { * * @remarks * - * [Api set: Mailbox preview] + * [Api set: Mailbox 1.16] * * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/understanding-outlook-add-in-permissions | Minimum permission level}**: **read item** * @@ -15881,8 +15846,6 @@ declare namespace Office { * * **Important**: * - * - The `getTokenStatusAsync` method is available for preview in Outlook on the web and on Windows (new and classic (Version 2510, Build 19328.20000 and later)). - * * - The `getTokenStatusAsync` method isn't supported if you load an add-in in an Outlook.com or Gmail mailbox. * * - Calling the `getTokenStatusAsync` method in compose mode requires you to have saved the item. The `saveAsync` method requires a minimum permission level of **read/write item**. @@ -15893,8 +15856,6 @@ declare namespace Office { * The `asyncResult.value` property returns the token status, which can be `Office.MailboxEnums.TokenStatus.Enabled`, `Office.MailboxEnums.TokenStatus.Disabled`, or * `Office.MailboxEnums.TokenStatus.Removed`. A `Office.MailboxEnums.TokenStatus.Removed` status indicates that the mailbox is hosted in an Exchange Online environment * where legacy Exchange tokens are turned off and are no longer supported. - * - * @beta */ getTokenStatusAsync(options: Office.AsyncContextOptions & { isRest?: boolean }, callback: (asyncResult: Office.AsyncResult) => void): void; /** @@ -15902,7 +15863,7 @@ declare namespace Office { * * @remarks * - * [Api set: Mailbox preview] + * [Api set: Mailbox 1.16] * * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/understanding-outlook-add-in-permissions | Minimum permission level}**: **read item** * @@ -15910,8 +15871,6 @@ declare namespace Office { * * **Important**: * - * - The `getTokenStatusAsync` method is available for preview in Outlook on the web and on Windows (new and classic (Version 2510, Build 19328.20000 and later)). - * * - The `getTokenStatusAsync` method isn't supported if you load an add-in in an Outlook.com or Gmail mailbox. * * - Calling the `getTokenStatusAsync` method in compose mode requires you to have saved the item. The `saveAsync` method requires a minimum permission level of **read/write item**. @@ -15920,8 +15879,6 @@ declare namespace Office { * The `asyncResult.value` property returns the token status, which can be `Office.MailboxEnums.TokenStatus.Enabled`, `Office.MailboxEnums.TokenStatus.Disabled`, or * `Office.MailboxEnums.TokenStatus.Removed`. A `Office.MailboxEnums.TokenStatus.Removed` status indicates that the mailbox is hosted in an Exchange Online environment * where legacy Exchange tokens are turned off and are no longer supported. - * - * @beta */ getTokenStatusAsync(callback: (asyncResult: Office.AsyncResult) => void): void; } @@ -18425,24 +18382,7 @@ declare namespace Office { /** * Provides diagnostic information to an Outlook add-in. * - * Contains the following members. - * - * - `hostName` (string): A string that represents the name of the Office application. - * It should be one of the following values: `Outlook`, `newOutlookWindows`, `OutlookWebApp`, `OutlookIOS`, or `OutlookAndroid`. - * **Note**: The "Outlook" value is returned for Outlook on Windows (classic) and on Mac. - * - * - `hostVersion` (string): A string that represents the version of either the Office application or the Exchange Server (e.g., "15.0.468.0"). - * If the mail add-in is running in Outlook on Windows (classic), on Mac, or on mobile devices, the `hostVersion` property returns the version of the - * Outlook client. In Outlook on the web and {@link https://support.microsoft.com/office/656bb8d9-5a60-49b2-a98b-ba7822bc7627 | new Outlook on Windows}, - * the property returns the version of the Exchange Server. - * - * - `OWAView` (`MailboxEnums.OWAView` or string): An enum (or string literal) that represents the current view of Outlook on the web. - * If the application is not Outlook on the web, then accessing this property results in undefined. - * Outlook on the web has three views (`OneColumn` - displayed when the screen is narrow, `TwoColumns` - displayed when the screen is wider, - * and `ThreeColumns` - displayed when the screen is wide) that correspond to the width of the screen and the window, and the number of columns - * that can be displayed. - * - * More information is under {@link Office.Diagnostics}. + * For information about the diagnostic properties you can access, see {@link Office.Diagnostics}. * * @remarks * @@ -19531,7 +19471,7 @@ declare namespace Office { * {@link https://learn.microsoft.com/office/dev/add-ins/develop/event-based-activation | event-based activation}, including * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/onmessagesend-onappointmentsend-events | Smart Alerts}, the * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/spam-reporting | integrated spam-reporting feature}, or - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/encryption-decryption | decryption} (preview). + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/encryption-decryption | decryption}. * It allows the add-in to signify to the Outlook client that it has completed processing an event. * * @remarks @@ -19545,6 +19485,8 @@ declare namespace Office { * * - Support for the integrated spam-reporting feature was introduced in Mailbox 1.14. * + * - Support for the decryption feature was introduced in Mailbox 1.16. + * * - For information about the Event object used by the {@link https://learn.microsoft.com/office/dev/add-ins/design/add-in-commands | function command button}, * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-on-send-addins | on-send add-in}, * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/online-meeting | online-meeting provider add-in}, and @@ -19553,7 +19495,7 @@ declare namespace Office { */ interface MailboxEvent { /** - * Indicates that the event-based, spam-reporting, or decryption (preview) add-in has completed processing an event. + * Indicates that the event-based, spam-reporting, or decryption add-in has completed processing an event. * * @remarks * [Api set: Mailbox 1.10] @@ -19568,6 +19510,8 @@ declare namespace Office { * * - Support to assign a `SmartAlertsEventCompletedOptions` object to the `options` parameter was introduced in Mailbox 1.12. * + * - Support for the decryption feature was introduced in Mailbox 1.16. + * * @param options - Optional. An object that specifies the behavior of an event-based, spam-reporting, or decryption add-in when it completes processing an event. */ completed(options?: SmartAlertsEventCompletedOptions | SpamReportingEventCompletedOptions | MessageDecryptEventCompletedOptions): void; @@ -20034,7 +19978,8 @@ declare namespace Office { /** * Manages the {@link Office.SessionData | SessionData} of an item in Compose mode. * - * **Important**: The entire SessionData object is limited to 50,000 characters per add-in. + * **Important**: In Outlook clients that support Mailbox 1.15 or earlier, the entire SessionData object for each mail item is limited to 50,000 characters per add-in. + * In clients that support Mailbox 1.16 or later, the character limit per add-in is 2,621,440 characters. * * @remarks * [Api set: Mailbox 1.11] @@ -21521,13 +21466,11 @@ declare namespace Office { * * @remarks * - * [Api set: Mailbox preview] + * [Api set: Mailbox 1.16] * * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/understanding-outlook-add-in-permissions | Minimum permission level}**: **read/write item** * * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-add-ins-overview#extension-points | Applicable Outlook mode}**: Message Read - * - * @beta */ interface MessageDecryptEventCompletedOptions { /** @@ -21536,13 +21479,11 @@ declare namespace Office { * * @remarks * - * [Api set: Mailbox preview] + * [Api set: Mailbox 1.16] * * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/understanding-outlook-add-in-permissions | Minimum permission level}**: **read/write item** * * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-add-ins-overview#extension-points | Applicable Outlook mode}**: Message Read - * - * @beta */ allowEvent: boolean; /** @@ -21551,13 +21492,11 @@ declare namespace Office { * * @remarks * - * [Api set: Mailbox preview] + * [Api set: Mailbox 1.16] * * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/understanding-outlook-add-in-permissions | Minimum permission level}**: **read/write item** * * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-add-ins-overview#extension-points | Applicable Outlook mode}**: Message Read - * - * @beta */ attachments?: DecryptedMessageAttachment[]; /** @@ -21566,7 +21505,7 @@ declare namespace Office { * * @remarks * - * [Api set: Mailbox preview] + * [Api set: Mailbox 1.16] * * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/understanding-outlook-add-in-permissions | Minimum permission level}**: **read/write item** * @@ -21578,8 +21517,6 @@ declare namespace Office { * If you create a JSON string using `JSON.stringify()` and assign it to the `contextData` property, you must parse the string using `JSON.parse()` once you retrieve it. * * - You can use the `contextData` property to store custom internet headers to decrypt messages in reply and forward scenarios. - * - * @beta */ contextData?: any; /** @@ -21588,15 +21525,13 @@ declare namespace Office { * * @remarks * - * [Api set: Mailbox preview] + * [Api set: Mailbox 1.16] * * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/understanding-outlook-add-in-permissions | Minimum permission level}**: **read/write item** * * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-add-ins-overview#extension-points | Applicable Outlook mode}**: Message Read * * **Important**: If the `emailBody` property isn't specified, an empty body is returned. - * - * @beta */ emailBody?: DecryptedMessageBody; } @@ -21843,13 +21778,13 @@ declare namespace Office { * The `cc` property returns an array that contains an {@link Office.EmailAddressDetails | EmailAddressDetails} object for * each recipient listed on the **Cc** line of the message. The maximum number of recipients returned varies per Outlook client. * - * - Windows (classic): 500 recipients + * - Windows (classic - Mailbox 1.15 and earlier): 500 recipients * - * - Windows (classic - in preview starting in Version 2511 (Build 19426.20000)): 1,000 recipients + * - Windows (classic - Mailbox 1.16 and later): 1,000 recipients * * - Android, classic Mac UI, iOS: 100 recipients * - * - Web browser, Windows (new): 20 recipients (collapsed view), 500 recipients (expanded view) + * - Web browser, Windows (new): 20 recipients (collapsed view), 1,000 recipients (expanded view) * * - New Mac UI: No limit * @@ -22186,13 +22121,13 @@ declare namespace Office { * The `to` property returns an array that contains an {@link Office.EmailAddressDetails | EmailAddressDetails} object for * each recipient listed on the **To** line of the message. The maximum number of recipients returned varies per Outlook client. * - * - Windows (classic): 500 recipients + * - Windows (classic - Mailbox 1.15 and earlier): 500 recipients * - * - Windows (classic - in preview starting in Version 2511 (Build 19426.20000)): 1,000 recipients + * - Windows (classic - Mailbox 1.16 and later): 1,000 recipients * * - Android, classic Mac UI, iOS: 100 recipients * - * - Web browser, Windows (new): 20 recipients (collapsed view), 500 recipients (expanded view) + * - Web browser, Windows (new): 20 recipients (collapsed view), 1,000 recipients (expanded view) * * - New Mac UI: No limit * @@ -23482,16 +23417,14 @@ declare namespace Office { * * **Important**: * - * With the `addAsync` method, you can add a maximum of 100 recipients to a mail item in Outlook on the web, on Windows + * With the `addAsync` method, you can add a maximum of 100 recipients to a mail item at a time in Outlook on the web, on Windows * ({@link https://support.microsoft.com/office/656bb8d9-5a60-49b2-a98b-ba7822bc7627 | new} and classic), on Mac (classic UI), on Android, and on iOS. * However, take note of the following: * - * - In Outlook on the web, on Windows (new and classic), and on Mac (classic UI), you can have a maximum of 500 recipients in a target field. - * If you need to add more than 100 recipients to a mail item, you can call `addAsync` repeatedly, but be mindful of the recipient limit of the field. - * - * - In classic Outlook on Windows, a maximum of 1,000 recipients in a target field is available for preview. To test this increased limit, you must install Version 2511 (Build 19426.20000) or later. - * Then, join the {@link https://techcommunity.microsoft.com/kb/microsoft-365-insider-kb/join-the-microsoft-365-insider-program-on-windows/4401748 | Microsoft 365 Insider program} and select the - * **Beta Channel** option to access Office beta builds. + * - In classic Outlook on Windows (Mailbox 1.15 and earlier) and on Mac (classic UI), you can have a maximum of 500 recipients in a target field. + * In classic Outlook on Windows, clients that support Mailbox 1.16 and later can have a maximum of 1,000 recipients. Target fields in Outlook on the web and the + * new Outlook on Windows have no recipient limits. If you need to add more than 100 recipients to a mail item, you can call `addAsync` repeatedly, + * but be mindful of the recipient limit of the field. * * - In Outlook on Android and on iOS, the `addAsync` method is supported starting in Version 4.2530.0. On these mobile clients, the `addAsync` method isn't * supported when a user replies from the the reply field at the bottom of a message. @@ -23525,15 +23458,14 @@ declare namespace Office { * * **Important**: * - * With the `addAsync` method, you can add a maximum of 100 recipients to a mail item in Outlook on the web, on Windows, - * on Mac (classic UI), on Android, and on iOS. However, take note of the following: - * - * - In Outlook on the web, on Windows, and on Mac (classic UI), you can have a maximum of 500 recipients in a target field. - * If you need to add more than 100 recipients to a mail item, you can call `addAsync` repeatedly, but be mindful of the recipient limit of the field. + * With the `addAsync` method, you can add a maximum of 100 recipients to a mail item at a time in Outlook on the web, on Windows + * ({@link https://support.microsoft.com/office/656bb8d9-5a60-49b2-a98b-ba7822bc7627 | new} and classic), on Mac (classic UI), on Android, and on iOS. + * However, take note of the following: * - * - In classic Outlook on Windows, a maximum of 1,000 recipients in a target field is available for preview. To test this increased limit, you must install Version 2511 (Build 19426.20000) or later. - * Then, join the {@link https://techcommunity.microsoft.com/kb/microsoft-365-insider-kb/join-the-microsoft-365-insider-program-on-windows/4401748 | Microsoft 365 Insider program} and select the - * **Beta Channel** option to access Office beta builds. + * - In classic Outlook on Windows (Mailbox 1.15 and earlier) and on Mac (classic UI), you can have a maximum of 500 recipients in a target field. + * In classic Outlook on Windows, clients that support Mailbox 1.16 and later can have a maximum of 1,000 recipients. Target fields in Outlook on the web and the + * new Outlook on Windows have no recipient limits. If you need to add more than 100 recipients to a mail item, you can call `addAsync` repeatedly, + * but be mindful of the recipient limit of the field. * * - In Outlook on Android and on iOS, the `addAsync` method is supported starting in Version 4.2530.0. On these mobile clients, the `addAsync` method isn't * supported when a user replies from the the reply field at the bottom of a message. @@ -23567,9 +23499,9 @@ declare namespace Office { * * The maximum number of recipients returned by this method varies per Outlook client. * - * - Windows ({@link https://support.microsoft.com/office/656bb8d9-5a60-49b2-a98b-ba7822bc7627 | new} and classic), web browser, Mac (classic UI): 500 recipients + * - Windows (classic - Mailbox 1.15 and earlier), Mac (classic UI): 500 recipients * - * - Windows (classic - in preview starting in Version 2511 (Build 19426.20000)): 1,000 recipients + * - Web, Windows ({@link https://support.microsoft.com/office/656bb8d9-5a60-49b2-a98b-ba7822bc7627 | new}, classic - Mailbox 1.16 and later): 1,000 recipients * * - Android, iOS: 100 recipients * @@ -23623,9 +23555,9 @@ declare namespace Office { * * The maximum number of recipients returned by this method varies per Outlook client. * - * - Windows ({@link https://support.microsoft.com/office/656bb8d9-5a60-49b2-a98b-ba7822bc7627 | new} and classic), web browser, Mac (classic UI): 500 recipients + * - Windows (classic - Mailbox 1.15 and earlier), Mac (classic UI): 500 recipients * - * - Windows (classic - in preview starting in Version 2511 (Build 19426.20000)): 1,000 recipients + * - Web, Windows ({@link https://support.microsoft.com/office/656bb8d9-5a60-49b2-a98b-ba7822bc7627 | new}, classic - Mailbox 1.16 and later): 1,000 recipients * * - Android, iOS: 100 recipients * @@ -23674,16 +23606,14 @@ declare namespace Office { * * **Important**: * - * With the `setAsync` method, you can set a maximum of 100 recipients in Outlook on the web, on Windows + * With the `setAsync` method, you can set a maximum of 100 recipients at a time in Outlook on the web, on Windows * ({@link https://support.microsoft.com/office/656bb8d9-5a60-49b2-a98b-ba7822bc7627 | new} and classic), on Mac (classic UI), on Android, and on iOS. * However, take note of the following: * - * - In Outlook on the web, on Windows (new and classic), and on Mac (classic UI), you can have a maximum of 500 recipients in a target field. - * If you need to add more recipients after setting 100 recipients, you can call `addAsync` repeatedly, but be mindful of the recipient limit of the field. - * - * - In classic Outlook on Windows, a maximum of 1,000 recipients in a target field is available for preview. To test this increased limit, you must install Version 2511 (Build 19426.20000) or later. - * Then, join the {@link https://techcommunity.microsoft.com/kb/microsoft-365-insider-kb/join-the-microsoft-365-insider-program-on-windows/4401748 | Microsoft 365 Insider program} and select the - * **Beta Channel** option to access Office beta builds. + * - In classic Outlook on Windows (Mailbox 1.15 and earlier) and on Mac (classic UI), you can have a maximum of 500 recipients in a target field. + * In classic Outlook on Windows, clients that support Mailbox 1.16 and later can have a maximum of 1,000 recipients. Target fields in Outlook on the web and the + * new Outlook on Windows have no recipient limits. If you need to add more than 100 recipients to a mail item, you can call `addAsync` repeatedly, + * but be mindful of the recipient limit of the field. * * - In Outlook on Android and on iOS, the `setAsync` method is supported starting in Version 4.2530.0. On these mobile clients, the `setAsync` method isn't * supported when a user replies from the the reply field at the bottom of a message. @@ -23720,16 +23650,14 @@ declare namespace Office { * * **Important**: * - * With the `setAsync` method, you can set a maximum of 100 recipients in Outlook on the web, on Windows + * With the `setAsync` method, you can set a maximum of 100 recipients at a time in Outlook on the web, on Windows * ({@link https://support.microsoft.com/office/656bb8d9-5a60-49b2-a98b-ba7822bc7627 | new} and classic), on Mac (classic UI), on Android, and on iOS. * However, take note of the following: * - * - In Outlook on the web, on Windows (new and classic), and on Mac (classic UI), you can have a maximum of 500 recipients in a target field. - * If you need to add more recipients after setting 100 recipients, you can call `addAsync` repeatedly, but be mindful of the recipient limit of the field. - * - * - In classic Outlook on Windows, a maximum of 1,000 recipients in a target field is available for preview. To test this increased limit, you must install Version 2511 (Build 19426.20000) or later. - * Then, join the {@link https://techcommunity.microsoft.com/kb/microsoft-365-insider-kb/join-the-microsoft-365-insider-program-on-windows/4401748 | Microsoft 365 Insider program} and select the - * **Beta Channel** option to access Office beta builds. + * - In classic Outlook on Windows (Mailbox 1.15 and earlier) and on Mac (classic UI), you can have a maximum of 500 recipients in a target field. + * In classic Outlook on Windows, clients that support Mailbox 1.16 and later can have a maximum of 1,000 recipients. Target fields in Outlook on the web and the + * new Outlook on Windows have no recipient limits. If you need to add more than 100 recipients to a mail item, you can call `addAsync` repeatedly, + * but be mindful of the recipient limit of the field. * * - In Outlook on Android and on iOS, the `setAsync` method is supported starting in Version 4.2530.0. On these mobile clients, the `setAsync` method isn't * supported when a user replies from the the reply field at the bottom of a message. @@ -25016,7 +24944,8 @@ declare namespace Office { * * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-add-ins-overview#extension-points | Applicable Outlook mode}**: Compose * - * **Important**: For each mail item, the entire SessionData object is limited to 50,000 characters per add-in. + * **Important**: In Outlook clients that support Mailbox 1.15 or earlier, the entire SessionData object for each mail item is limited to 50,000 characters per add-in. + * In clients that support Mailbox 1.16 or later, the character limit per add-in is 2,621,440 characters. */ interface SessionData { /** @@ -25121,9 +25050,7 @@ declare namespace Office { * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-add-ins-overview#extension-points | Applicable Outlook mode}**: Compose * * **Important**: In Outlook clients that support Mailbox 1.15 or earlier, the entire SessionData object for each mail item is limited to 50,000 characters per add-in. - * In classic Outlook on Windows, you can preview an increased character limit of up to 2,621,440 characters per add-in. To test the updated limit, join the - * {@link https://aka.ms/MSFT365InsiderProgram | Microsoft 365 Insider program}, then choose the Beta Channel in the classic Outlook on Windows client. - * Your client must be on Version 2510 (Build 19317.20000) or later. + * In clients that support Mailbox 1.16 or later, the character limit per add-in is 2,621,440 characters. * * @param name - The session data key. * @param value - The session data value as a string. @@ -25144,9 +25071,7 @@ declare namespace Office { * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-add-ins-overview#extension-points | Applicable Outlook mode}**: Compose * * **Important**: In Outlook clients that support Mailbox 1.15 or earlier, the entire SessionData object for each mail item is limited to 50,000 characters per add-in. - * In classic Outlook on Windows, you can preview an increased character limit of up to 2,621,440 characters per add-in. To test the updated limit, join the - * {@link https://aka.ms/MSFT365InsiderProgram | Microsoft 365 Insider program}, then choose the Beta Channel in the classic Outlook on Windows client. - * Your client must be on Version 2510 (Build 19317.20000) or later. + * In clients that support Mailbox 1.16 or later, the character limit per add-in is 2,621,440 characters. * * @param name - The session data key. * @param value - The session data value as a string. diff --git a/types/office-js/index.d.ts b/types/office-js/index.d.ts index 611cd1edbdb55f..9798fa4d830743 100644 --- a/types/office-js/index.d.ts +++ b/types/office-js/index.d.ts @@ -10806,6 +10806,33 @@ declare namespace Office { */ Subject = "subject" } + /** + * Specifies the status of Exchange Web Services (EWS) callback tokens or REST API tokens in an organization. + * + * @remarks + * [Api set: Mailbox 1.16] + * + * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-add-ins-overview#extension-points | Applicable Outlook mode}**: Compose or Read + * + * **Important**: Legacy Exchange Online user identity tokens and callback tokens are no longer supported and are turned off across all Microsoft 365 tenants. + * If an Outlook add-in requires delegated user access or user identity, we recommend using MSAL (Microsoft Authentication Library) and nested app authentication (NAA). + * Exchange user identity tokens are still supported for Exchange on-premises. For more information, see + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | Nested app authentication FAQ}. + */ + enum TokenStatus { + /** + * EWS callback tokens or REST API tokens are turned off in the organization. + */ + Disabled = 0, + /** + * EWS callback tokens or REST API tokens are supported in the organization. + */ + Enabled = 1, + /** + * The mailbox is hosted in an Exchange Online environment where EWS tokens are turned off and are no longer supported. + */ + Removed = 2 + } /** * Specifies the week of the month. * @@ -11097,7 +11124,8 @@ declare namespace Office { /** * Manages the {@link Office.SessionData | SessionData} of an item in Compose mode. * - * **Important**: The entire SessionData object is limited to 50,000 characters per add-in. + * **Important**: In Outlook clients that support Mailbox 1.15 or earlier, the entire SessionData object for each mail item is limited to 50,000 characters per add-in. + * In clients that support Mailbox 1.16 or later, the character limit per add-in is 2,621,440 characters. * * @remarks * [Api set: Mailbox 1.11] @@ -12501,11 +12529,13 @@ declare namespace Office { * The `optionalAttendees` property returns an array that contains an {@link Office.EmailAddressDetails | EmailAddressDetails} object for * each optional attendee to the meeting. The maximum number of attendees returned varies per Outlook client. * - * - Windows: 500 attendees + * - Windows (classic - Mailbox 1.15 and earlier): 500 attendees + * + * - Web, Windows (new, classic - Mailbox 1.16 and later): 1,000 recipients * * - Android, classic Mac UI, iOS: 100 attendees * - * - New Mac UI, web browser: No limit + * - New Mac UI: No limit * * @remarks * @@ -12549,11 +12579,13 @@ declare namespace Office { * The `requiredAttendees` property returns an array that contains an {@link Office.EmailAddressDetails | EmailAddressDetails} object for * each required attendee to the meeting. The maximum number of attendees returned varies per Outlook client. * - * - Windows: 500 attendees + * - Windows (classic - Mailbox 1.15 and earlier): 500 attendees + * + * - Web, Windows (new, classic - Mailbox 1.16 and later): 1,000 recipients * * - Android, classic Mac UI, iOS: 100 attendees * - * - New Mac UI, web browser: No limit + * - New Mac UI: No limit * * @remarks * @@ -13332,17 +13364,16 @@ declare namespace Office { /** * Gets the content identifier of an inline attachment. * - * **Important**: - * - * - The `contentId` property is only supported in Outlook on the web, the new Outlook on Windows, and classic Outlook on Windows (preview). - * To preview the `contentId` property in classic Outlook on Windows, your Outlook client must run Version 2510 (Build 19312.20000) - * or later and must be on the Beta Channel. For more information, see {@link https://aka.ms/Msft365InsiderProgram | Microsoft 365 Insider Program}. + * @remarks + * [Api set: Mailbox 1.16] * - * - Changes to how inline images are represented in the HTML body of Outlook emails in Outlook on the web and the new Outlook on Windows released on November 15, 2025. + * **Important**: Changes to how inline images are represented in the HTML body of Outlook emails in + * Outlook on the web and the new Outlook on Windows released on November 15, 2025. * Previously, the attachment ID of the image appeared in the `src` attribute of the applicable `` element. * Now, the image is represented by a content ID (`cid`) in the `src` attribute instead. - * If you parse the attachment ID from the HTML editor or get the Base64-encoded value of the image from the URL in the `src` attribute, you must update your add-in's parsing logic. - * For more information, see {@link https://devblogs.microsoft.com/microsoft365dev/changes-to-inline-images-in-outlook | Changes to inline image representation in Outlook on the web and new Outlook for Windows}. + * If you parse the attachment ID from the HTML editor or get the Base64-encoded value of the image from the URL in the + * `src` attribute, you must update your add-in's parsing logic. For more information, see + * {@link https://devblogs.microsoft.com/microsoft365dev/changes-to-inline-images-in-outlook | Changes to inline image representation in Outlook on the web and new Outlook for Windows}. */ contentId: string; /** @@ -13435,18 +13466,15 @@ declare namespace Office { * Gets the content identifier of an inline attachment. * * @remarks + * [Api set: Mailbox 1.16] * - * **Important**: - * - * - The `contentId` property is only supported in Outlook on the web, the new Outlook on Windows, and classic Outlook on Windows (preview). - * To preview the `contentId` property in classic Outlook on Windows, your Outlook client must run Version 2510 (Build 19312.20000) - * or later and must be on the Beta Channel. For more information, see {@link https://aka.ms/Msft365InsiderProgram | Microsoft 365 Insider Program}. - * - * - Changes to how inline images are represented in the HTML body of Outlook emails in Outlook on the web and the new Outlook on Windows released on November 15, 2025. + * **Important**: Changes to how inline images are represented in the HTML body of Outlook emails in + * Outlook on the web and the new Outlook on Windows released on November 15, 2025. * Previously, the attachment ID of the image appeared in the `src` attribute of the applicable `` element. * Now, the image is represented by a content ID (`cid`) in the `src` attribute instead. - * If you parse the attachment ID from the HTML editor or get the Base64-encoded value of the image from the URL in the `src` attribute, you must update your add-in's parsing logic. - * For more information, see {@link https://devblogs.microsoft.com/microsoft365dev/changes-to-inline-images-in-outlook | Changes to inline image representation in Outlook on the web and new Outlook for Windows}. + * If you parse the attachment ID from the HTML editor or get the Base64-encoded value of the image from the URL in the + * `src` attribute, you must update your add-in's parsing logic. For more information, see + * {@link https://devblogs.microsoft.com/microsoft365dev/changes-to-inline-images-in-outlook | Changes to inline image representation in Outlook on the web and new Outlook for Windows}. */ contentId: string; /** @@ -14681,6 +14709,146 @@ declare namespace Office { */ set(name: string, value: string): void; } + /** + * Represents an attachment in a decrypted message. + * + * @remarks + * + * [Api set: Mailbox 1.16] + * + * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/understanding-outlook-add-in-permissions | Minimum permission level}**: **read/write item** + * + * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-add-ins-overview#extension-points | Applicable Outlook mode}**: Message Read + * + * To learn how to develop an encryption add-in in Outlook, see {@link https://learn.microsoft.com/office/dev/add-ins/outlook/encryption-decryption | Create an encryption Outlook add-in}. + */ + interface DecryptedMessageAttachment { + /** + * Specifies the type of attachment. + * + * @remarks + * + * [Api set: Mailbox 1.16] + * + * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/understanding-outlook-add-in-permissions | Minimum permission level}**: **read/write item** + * + * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-add-ins-overview#extension-points | Applicable Outlook mode}**: Message Read + * + * **Important**: Attachments of type `MailboxEnums.AttachmentType.Item` aren't currently supported. + */ + attachmentType: MailboxEnums.AttachmentType; + /** + * Specifies the Base64-encoded content of the attachment. + * + * @remarks + * + * [Api set: Mailbox 1.16] + * + * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/understanding-outlook-add-in-permissions | Minimum permission level}**: **read/write item** + * + * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-add-ins-overview#extension-points | Applicable Outlook mode}**: Message Read + * + * **Important**: The `content` property isn't supported by attachments of type `MailboxEnums.AttachmentType.Cloud`. + */ + content: string; + /** + * Specifies the content identifier of an inline attachment. + * + * The `contentId` property must be specified if `isInline` is set to `true`. + * + * @remarks + * + * [Api set: Mailbox 1.16] + * + * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/understanding-outlook-add-in-permissions | Minimum permission level}**: **read/write item** + * + * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-add-ins-overview#extension-points | Applicable Outlook mode}**: Message Read + * + * **Important**: When images are added to a message as inline attachments, they're automatically assigned a content ID. In the body of a message, the content ID of an inline attachment is + * specified in the `src` attribute of the `` element (for example, ``). + * To easily identify and provide these inline attachments during decryption, we recommend saving the content IDs of inline attachments to the message header during encryption. + * Call `Office.context.mailbox.item.getAttachmentsAsync` to get the content ID of an inline attachment. Then, call `Office.context.mailbox.item.internetHeaders.setAsync` to save the ID to the header of the message. + */ + contentId?: string; + /** + * If true, specifies that the decrypted attachment appears as an image in the body of the message instead of in the attachment list. + * If the `isInline` property isn't specified, its value is set to false. + * + * @remarks + * + * [Api set: Mailbox 1.16] + * + * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/understanding-outlook-add-in-permissions | Minimum permission level}**: **read/write item** + * + * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-add-ins-overview#extension-points | Applicable Outlook mode}**: Message Read + */ + isInline?: boolean; + /** + * Specifies the name of the attachment. + * + * @remarks + * + * [Api set: Mailbox 1.16] + * + * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/understanding-outlook-add-in-permissions | Minimum permission level}**: **read/write item** + * + * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-add-ins-overview#extension-points | Applicable Outlook mode}**: Message Read + */ + name: string; + /** + * Specifies the URL reference path of the attachment if its type is `MailboxEnums.AttachmentType.Cloud`. + * The `path` property must be specified for attachments of type `MailboxEnums.AttachmentType.Cloud`. + * + * @remarks + * + * [Api set: Mailbox 1.16] + * + * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/understanding-outlook-add-in-permissions | Minimum permission level}**: **read/write item** + * + * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-add-ins-overview#extension-points | Applicable Outlook mode}**: Message Read + */ + path?: string; + } + /** + * Represents the body of a decrypted message. + * + * @remarks + * + * [Api set: Mailbox 1.16] + * + * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/understanding-outlook-add-in-permissions | Minimum permission level}**: **read/write item** + * + * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-add-ins-overview#extension-points | Applicable Outlook mode}**: Message Read + * + * To learn how to develop an encryption add-in in Outlook, see {@link https://learn.microsoft.com/office/dev/add-ins/outlook/encryption-decryption | Create an encryption Outlook add-in}. + */ + interface DecryptedMessageBody { + /** + * Specifies the format of the body of a message. + * The body of a message can be formatted as `Office.CoercionType.Html` or `Office.CoercionType.Text`. + * + * @remarks + * + * [Api set: Mailbox 1.16] + * + * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/understanding-outlook-add-in-permissions | Minimum permission level}**: **read/write item** + * + * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-add-ins-overview#extension-points | Applicable Outlook mode}**: Message Read + */ + coercionType: Office.CoercionType; + /** + * Specifies the content displayed in the body of the message. + * + * @remarks + * + * [Api set: Mailbox 1.16] + * + * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/understanding-outlook-add-in-permissions | Minimum permission level}**: **read/write item** + * + * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-add-ins-overview#extension-points | Applicable Outlook mode}**: Message Read + */ + content: string; + } /** * The `DelayDeliveryTime` object enables you to manage the delayed delivery date and time of a message. * @@ -14807,6 +14975,23 @@ declare namespace Office { * property to get similar information. */ interface Diagnostics { + /** + * Gets an object to identify whether Exchange Web Services (EWS) callback tokens are supported in an organization. + * + * @remarks + * + * [Api set: Mailbox 1.16] + * + * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/understanding-outlook-add-in-permissions | Minimum permission level}**: **read item** + * + * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-add-ins-overview#extension-points | Applicable Outlook mode}**: Compose or Read + * + * **Important**: Legacy Exchange Online user identity tokens and callback tokens are no longer supported and are turned off across all Microsoft 365 tenants. + * If an Outlook add-in requires delegated user access or user identity, we recommend using MSAL (Microsoft Authentication Library) and nested app authentication (NAA). + * Exchange user identity tokens are still supported for Exchange on-premises. For more information, see + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | Nested app authentication FAQ}. + */ + ews: Ews; /** * Gets a string that represents the type of Outlook client. * @@ -15409,6 +15594,72 @@ declare namespace Office { */ urls: string[]; } + /** + * Provides methods to determine if Exchange Web Services (EWS) callback tokens are supported in an organization. + * + * @remarks + * + * [Api set: Mailbox 1.16] + * + * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/understanding-outlook-add-in-permissions | Minimum permission level}**: **read item** + * + * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-add-ins-overview#extension-points | Applicable Outlook mode}**: Compose or Read + * + * **Important**: Legacy Exchange Online user identity tokens and callback tokens are no longer supported and are turned off across all Microsoft 365 tenants. + * If an Outlook add-in requires delegated user access or user identity, we recommend using MSAL (Microsoft Authentication Library) and nested app authentication (NAA). + * Exchange user identity tokens are still supported for Exchange on-premises. For more information, see + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | Nested app authentication FAQ}. + */ + interface Ews { + /** + * Gets the status of EWS callback tokens in an organization. + * + * @remarks + * + * [Api set: Mailbox 1.16] + * + * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/understanding-outlook-add-in-permissions | Minimum permission level}**: **read item** + * + * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-add-ins-overview#extension-points | Applicable Outlook mode}**: Compose or Read + * + * **Important**: + * + * - The `getTokenStatusAsync` method isn't supported if you load an add-in in an Outlook.com or Gmail mailbox. + * + * - Calling the `getTokenStatusAsync` method in compose mode requires you to have saved the item. The `saveAsync` method requires a minimum permission level of **read/write item**. + * + * @param options - An object literal that contains one or more of the following properties. `asyncContext`: Any data you want to access in the callback function. + * `isRest`: Identifies whether the token needed is for EWS or Outlook REST APIs. By default, the `isRest` property is set to `false`. + * @param callback - When the method completes, the function passed in the `callback` parameter is called with a single parameter of type Office.AsyncResult. + * The `asyncResult.value` property returns the token status, which can be `Office.MailboxEnums.TokenStatus.Enabled`, `Office.MailboxEnums.TokenStatus.Disabled`, or + * `Office.MailboxEnums.TokenStatus.Removed`. A `Office.MailboxEnums.TokenStatus.Removed` status indicates that the mailbox is hosted in an Exchange Online environment + * where legacy Exchange tokens are turned off and are no longer supported. + */ + getTokenStatusAsync(options: Office.AsyncContextOptions & { isRest?: boolean }, callback: (asyncResult: Office.AsyncResult) => void): void; + /** + * Gets the status of EWS callback tokens in an organization. + * + * @remarks + * + * [Api set: Mailbox 1.16] + * + * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/understanding-outlook-add-in-permissions | Minimum permission level}**: **read item** + * + * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-add-ins-overview#extension-points | Applicable Outlook mode}**: Compose or Read + * + * **Important**: + * + * - The `getTokenStatusAsync` method isn't supported if you load an add-in in an Outlook.com or Gmail mailbox. + * + * - Calling the `getTokenStatusAsync` method in compose mode requires you to have saved the item. The `saveAsync` method requires a minimum permission level of **read/write item**. + * + * @param callback - When the method completes, the function passed in the `callback` parameter is called with a single parameter of type Office.AsyncResult. + * The `asyncResult.value` property returns the token status, which can be `Office.MailboxEnums.TokenStatus.Enabled`, `Office.MailboxEnums.TokenStatus.Disabled`, or + * `Office.MailboxEnums.TokenStatus.Removed`. A `Office.MailboxEnums.TokenStatus.Removed` status indicates that the mailbox is hosted in an Exchange Online environment + * where legacy Exchange tokens are turned off and are no longer supported. + */ + getTokenStatusAsync(callback: (asyncResult: Office.AsyncResult) => void): void; + } /** * Provides a method to get the from value of a message in an Outlook add-in. * @@ -17888,24 +18139,7 @@ declare namespace Office { /** * Provides diagnostic information to an Outlook add-in. * - * Contains the following members. - * - * - `hostName` (string): A string that represents the name of the Office application. - * It should be one of the following values: `Outlook`, `newOutlookWindows`, `OutlookWebApp`, `OutlookIOS`, or `OutlookAndroid`. - * **Note**: The "Outlook" value is returned for Outlook on Windows (classic) and on Mac. - * - * - `hostVersion` (string): A string that represents the version of either the Office application or the Exchange Server (e.g., "15.0.468.0"). - * If the mail add-in is running in Outlook on Windows (classic), on Mac, or on mobile devices, the `hostVersion` property returns the version of the - * Outlook client. In Outlook on the web and {@link https://support.microsoft.com/office/656bb8d9-5a60-49b2-a98b-ba7822bc7627 | new Outlook on Windows}, - * the property returns the version of the Exchange Server. - * - * - `OWAView` (`MailboxEnums.OWAView` or string): An enum (or string literal) that represents the current view of Outlook on the web. - * If the application is not Outlook on the web, then accessing this property results in undefined. - * Outlook on the web has three views (`OneColumn` - displayed when the screen is narrow, `TwoColumns` - displayed when the screen is wider, - * and `ThreeColumns` - displayed when the screen is wide) that correspond to the width of the screen and the window, and the number of columns - * that can be displayed. - * - * More information is under {@link Office.Diagnostics}. + * For information about the diagnostic properties you can access, see {@link Office.Diagnostics}. * * @remarks * @@ -18987,8 +19221,9 @@ declare namespace Office { /** * The `MailboxEvent` object is passed as an argument to the event handler of an add-in that implements * {@link https://learn.microsoft.com/office/dev/add-ins/develop/event-based-activation | event-based activation}, including - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/onmessagesend-onappointmentsend-events | Smart Alerts}, - * or the {@link https://learn.microsoft.com/office/dev/add-ins/outlook/spam-reporting | integrated spam-reporting feature}. + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/onmessagesend-onappointmentsend-events | Smart Alerts}, the + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/spam-reporting | integrated spam-reporting feature}, or + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/encryption-decryption | decryption}. * It allows the add-in to signify to the Outlook client that it has completed processing an event. * * @remarks @@ -19002,6 +19237,8 @@ declare namespace Office { * * - Support for the integrated spam-reporting feature was introduced in Mailbox 1.14. * + * - Support for the decryption feature was introduced in Mailbox 1.16. + * * - For information about the Event object used by the {@link https://learn.microsoft.com/office/dev/add-ins/design/add-in-commands | function command button}, * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-on-send-addins | on-send add-in}, * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/online-meeting | online-meeting provider add-in}, and @@ -19010,7 +19247,7 @@ declare namespace Office { */ interface MailboxEvent { /** - * Indicates that the event-based or spam-reporting add-in has completed processing an event. + * Indicates that the event-based, spam-reporting, or decryption add-in has completed processing an event. * * @remarks * [Api set: Mailbox 1.10] @@ -19025,9 +19262,11 @@ declare namespace Office { * * - Support to assign a `SmartAlertsEventCompletedOptions` object to the `options` parameter was introduced in Mailbox 1.12. * - * @param options - Optional. An object that specifies the behavior of an event-based or spam-reporting add-in when it completes processing an event. + * - Support for the decryption feature was introduced in Mailbox 1.16. + * + * @param options - Optional. An object that specifies the behavior of an event-based, spam-reporting, or decryption add-in when it completes processing an event. */ - completed(options?: SmartAlertsEventCompletedOptions | SpamReportingEventCompletedOptions): void; + completed(options?: SmartAlertsEventCompletedOptions | SpamReportingEventCompletedOptions | MessageDecryptEventCompletedOptions): void; } /** * Represents the categories master list on the mailbox. @@ -19491,7 +19730,8 @@ declare namespace Office { /** * Manages the {@link Office.SessionData | SessionData} of an item in Compose mode. * - * **Important**: The entire SessionData object is limited to 50,000 characters per add-in. + * **Important**: In Outlook clients that support Mailbox 1.15 or earlier, the entire SessionData object for each mail item is limited to 50,000 characters per add-in. + * In clients that support Mailbox 1.16 or later, the character limit per add-in is 2,621,440 characters. * * @remarks * [Api set: Mailbox 1.11] @@ -20965,6 +21205,81 @@ declare namespace Office { */ setSelectedDataAsync(data: string, callback?: (asyncResult: Office.AsyncResult) => void): void; } + /** + * Specifies the behavior of an {@link https://learn.microsoft.com/office/dev/add-ins/outlook/encryption-decryption | encryption add-in} after it completes processing an + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/event-based-activation#outlook-events | OnMessageDecrypt} event. + * + * @remarks + * + * [Api set: Mailbox 1.16] + * + * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/understanding-outlook-add-in-permissions | Minimum permission level}**: **read/write item** + * + * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-add-ins-overview#extension-points | Applicable Outlook mode}**: Message Read + */ + interface MessageDecryptEventCompletedOptions { + /** + * When you use the {@link https://learn.microsoft.com/javascript/api/outlook/office.mailboxevent#outlook-office-mailboxevent-completed-member(1) | completed method} to signal completion of an event handler, + * this value indicates if the `OnMessageDecrypt` event should continue to run or be canceled. If the `allowEvent` property is set to `true`, the decrypted contents of the message is displayed. + * + * @remarks + * + * [Api set: Mailbox 1.16] + * + * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/understanding-outlook-add-in-permissions | Minimum permission level}**: **read/write item** + * + * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-add-ins-overview#extension-points | Applicable Outlook mode}**: Message Read + */ + allowEvent: boolean; + /** + * When you use the {@link https://learn.microsoft.com/javascript/api/outlook/office.mailboxevent#outlook-office-mailboxevent-completed-member(1) | completed method} to signal completion of an event handler + * and set its `allowEvent` property to `true`, this property sets the decrypted attachments of the message. + * + * @remarks + * + * [Api set: Mailbox 1.16] + * + * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/understanding-outlook-add-in-permissions | Minimum permission level}**: **read/write item** + * + * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-add-ins-overview#extension-points | Applicable Outlook mode}**: Message Read + */ + attachments?: DecryptedMessageAttachment[]; + /** + * When you use the {@link https://learn.microsoft.com/javascript/api/outlook/office.mailboxevent#outlook-office-mailboxevent-completed-member(1) | completed method} to signal completion of an event handler + * and set its `allowEvent` property to `true`, this property specifies any JSON data passed to the add-in for processing. + * + * @remarks + * + * [Api set: Mailbox 1.16] + * + * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/understanding-outlook-add-in-permissions | Minimum permission level}**: **read/write item** + * + * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-add-ins-overview#extension-points | Applicable Outlook mode}**: Message Read + * + * **Important**: + * + * - To retrieve the value of the `contextData` property, you must call `Office.context.mailbox.item.getInitializationContextAsync`. + * If you create a JSON string using `JSON.stringify()` and assign it to the `contextData` property, you must parse the string using `JSON.parse()` once you retrieve it. + * + * - You can use the `contextData` property to store custom internet headers to decrypt messages in reply and forward scenarios. + */ + contextData?: any; + /** + * When you use the {@link https://learn.microsoft.com/javascript/api/outlook/office.mailboxevent#outlook-office-mailboxevent-completed-member(1) | completed method} to signal completion of an event handler + * and set its `allowEvent` property to `true`, this property sets the decrypted contents of the body of the message. + * + * @remarks + * + * [Api set: Mailbox 1.16] + * + * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/understanding-outlook-add-in-permissions | Minimum permission level}**: **read/write item** + * + * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-add-ins-overview#extension-points | Applicable Outlook mode}**: Message Read + * + * **Important**: If the `emailBody` property isn't specified, an empty body is returned. + */ + emailBody?: DecryptedMessageBody; + } /** * Represents the details of the form for composing a new message. * @@ -21208,11 +21523,13 @@ declare namespace Office { * The `cc` property returns an array that contains an {@link Office.EmailAddressDetails | EmailAddressDetails} object for * each recipient listed on the **Cc** line of the message. The maximum number of recipients returned varies per Outlook client. * - * - classic Windows: 500 recipients + * - Windows (classic - Mailbox 1.15 and earlier): 500 recipients + * + * - Windows (classic - Mailbox 1.16 and later): 1,000 recipients * * - Android, classic Mac UI, iOS: 100 recipients * - * - Web browser, new Outlook: 20 recipients (collapsed view), 500 recipients (expanded view) + * - Web browser, Windows (new): 20 recipients (collapsed view), 1,000 recipients (expanded view) * * - New Mac UI: No limit * @@ -21537,11 +21854,13 @@ declare namespace Office { * The `to` property returns an array that contains an {@link Office.EmailAddressDetails | EmailAddressDetails} object for * each recipient listed on the **To** line of the message. The maximum number of recipients returned varies per Outlook client. * - * - classic Windows: 500 recipients + * - Windows (classic - Mailbox 1.15 and earlier): 500 recipients + * + * - Windows (classic - Mailbox 1.16 and later): 1,000 recipients * * - Android, classic Mac UI, iOS: 100 recipients * - * - Web browser, new Outlook: 20 recipients (collapsed view), 500 recipients (expanded view) + * - Web browser, Windows (new): 20 recipients (collapsed view), 1,000 recipients (expanded view) * * - New Mac UI: No limit * @@ -22741,12 +23060,14 @@ declare namespace Office { * * **Important**: * - * With the `addAsync` method, you can add a maximum of 100 recipients to a mail item in Outlook on the web, on Windows + * With the `addAsync` method, you can add a maximum of 100 recipients to a mail item at a time in Outlook on the web, on Windows * ({@link https://support.microsoft.com/office/656bb8d9-5a60-49b2-a98b-ba7822bc7627 | new} and classic), on Mac (classic UI), on Android, and on iOS. * However, take note of the following: * - * - In Outlook on the web, on Windows (new and classic), and on Mac (classic UI), you can have a maximum of 500 recipients in a target field. - * If you need to add more than 100 recipients to a mail item, you can call `addAsync` repeatedly, but be mindful of the recipient limit of the field. + * - In classic Outlook on Windows (Mailbox 1.15 and earlier) and on Mac (classic UI), you can have a maximum of 500 recipients in a target field. + * In classic Outlook on Windows, clients that support Mailbox 1.16 and later can have a maximum of 1,000 recipients. Target fields in Outlook on the web and the + * new Outlook on Windows have no recipient limits. If you need to add more than 100 recipients to a mail item, you can call `addAsync` repeatedly, + * but be mindful of the recipient limit of the field. * * - In Outlook on Android and on iOS, the `addAsync` method is supported starting in Version 4.2530.0. On these mobile clients, the `addAsync` method isn't * supported when a user replies from the the reply field at the bottom of a message. @@ -22780,12 +23101,14 @@ declare namespace Office { * * **Important**: * - * With the `addAsync` method, you can add a maximum of 100 recipients to a mail item in Outlook on the web, on Windows + * With the `addAsync` method, you can add a maximum of 100 recipients to a mail item at a time in Outlook on the web, on Windows * ({@link https://support.microsoft.com/office/656bb8d9-5a60-49b2-a98b-ba7822bc7627 | new} and classic), on Mac (classic UI), on Android, and on iOS. * However, take note of the following: * - * - In Outlook on the web, on Windows (new and classic), and on Mac (classic UI), you can have a maximum of 500 recipients in a target field. - * If you need to add more than 100 recipients to a mail item, you can call `addAsync` repeatedly, but be mindful of the recipient limit of the field. + * - In classic Outlook on Windows (Mailbox 1.15 and earlier) and on Mac (classic UI), you can have a maximum of 500 recipients in a target field. + * In classic Outlook on Windows, clients that support Mailbox 1.16 and later can have a maximum of 1,000 recipients. Target fields in Outlook on the web and the + * new Outlook on Windows have no recipient limits. If you need to add more than 100 recipients to a mail item, you can call `addAsync` repeatedly, + * but be mindful of the recipient limit of the field. * * - In Outlook on Android and on iOS, the `addAsync` method is supported starting in Version 4.2530.0. On these mobile clients, the `addAsync` method isn't * supported when a user replies from the the reply field at the bottom of a message. @@ -22819,7 +23142,9 @@ declare namespace Office { * * The maximum number of recipients returned by this method varies per Outlook client. * - * - Windows ({@link https://support.microsoft.com/office/656bb8d9-5a60-49b2-a98b-ba7822bc7627 | new} and classic), web browser, Mac (classic UI): 500 recipients + * - Windows (classic - Mailbox 1.15 and earlier), Mac (classic UI): 500 recipients + * + * - Web, Windows ({@link https://support.microsoft.com/office/656bb8d9-5a60-49b2-a98b-ba7822bc7627 | new}, classic - Mailbox 1.16 and later): 1,000 recipients * * - Android, iOS: 100 recipients * @@ -22873,7 +23198,9 @@ declare namespace Office { * * The maximum number of recipients returned by this method varies per Outlook client. * - * - Windows ({@link https://support.microsoft.com/office/656bb8d9-5a60-49b2-a98b-ba7822bc7627 | new} and classic), web browser, Mac (classic UI): 500 recipients + * - Windows (classic - Mailbox 1.15 and earlier), Mac (classic UI): 500 recipients + * + * - Web, Windows ({@link https://support.microsoft.com/office/656bb8d9-5a60-49b2-a98b-ba7822bc7627 | new}, classic - Mailbox 1.16 and later): 1,000 recipients * * - Android, iOS: 100 recipients * @@ -22922,12 +23249,14 @@ declare namespace Office { * * **Important**: * - * With the `setAsync` method, you can set a maximum of 100 recipients in Outlook on the web, on Windows + * With the `setAsync` method, you can set a maximum of 100 recipients at a time in Outlook on the web, on Windows * ({@link https://support.microsoft.com/office/656bb8d9-5a60-49b2-a98b-ba7822bc7627 | new} and classic), on Mac (classic UI), on Android, and on iOS. * However, take note of the following: * - * - In Outlook on the web, on Windows (new and classic), and on Mac (classic UI), you can have a maximum of 500 recipients in a target field. - * If you need to add more recipients after setting 100 recipients, you can call `addAsync` repeatedly, but be mindful of the recipient limit of the field. + * - In classic Outlook on Windows (Mailbox 1.15 and earlier) and on Mac (classic UI), you can have a maximum of 500 recipients in a target field. + * In classic Outlook on Windows, clients that support Mailbox 1.16 and later can have a maximum of 1,000 recipients. Target fields in Outlook on the web and the + * new Outlook on Windows have no recipient limits. If you need to add more than 100 recipients to a mail item, you can call `addAsync` repeatedly, + * but be mindful of the recipient limit of the field. * * - In Outlook on Android and on iOS, the `setAsync` method is supported starting in Version 4.2530.0. On these mobile clients, the `setAsync` method isn't * supported when a user replies from the the reply field at the bottom of a message. @@ -22964,12 +23293,14 @@ declare namespace Office { * * **Important**: * - * With the `setAsync` method, you can set a maximum of 100 recipients in Outlook on the web, on Windows + * With the `setAsync` method, you can set a maximum of 100 recipients at a time in Outlook on the web, on Windows * ({@link https://support.microsoft.com/office/656bb8d9-5a60-49b2-a98b-ba7822bc7627 | new} and classic), on Mac (classic UI), on Android, and on iOS. * However, take note of the following: * - * - In Outlook on the web, on Windows (new and classic), and on Mac (classic UI), you can have a maximum of 500 recipients in a target field. - * If you need to add more recipients after setting 100 recipients, you can call `addAsync` repeatedly, but be mindful of the recipient limit of the field. + * - In classic Outlook on Windows (Mailbox 1.15 and earlier) and on Mac (classic UI), you can have a maximum of 500 recipients in a target field. + * In classic Outlook on Windows, clients that support Mailbox 1.16 and later can have a maximum of 1,000 recipients. Target fields in Outlook on the web and the + * new Outlook on Windows have no recipient limits. If you need to add more than 100 recipients to a mail item, you can call `addAsync` repeatedly, + * but be mindful of the recipient limit of the field. * * - In Outlook on Android and on iOS, the `setAsync` method is supported starting in Version 4.2530.0. On these mobile clients, the `setAsync` method isn't * supported when a user replies from the the reply field at the bottom of a message. @@ -24256,7 +24587,8 @@ declare namespace Office { * * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-add-ins-overview#extension-points | Applicable Outlook mode}**: Compose * - * **Important**: For each mail item, the entire SessionData object is limited to 50,000 characters per add-in. + * **Important**: In Outlook clients that support Mailbox 1.15 or earlier, the entire SessionData object for each mail item is limited to 50,000 characters per add-in. + * In clients that support Mailbox 1.16 or later, the character limit per add-in is 2,621,440 characters. */ interface SessionData { /** @@ -24360,7 +24692,8 @@ declare namespace Office { * * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-add-ins-overview#extension-points | Applicable Outlook mode}**: Compose * - * **Important**: For each mail item, the entire SessionData object is limited to 50,000 characters per add-in. + * **Important**: In Outlook clients that support Mailbox 1.15 or earlier, the entire SessionData object for each mail item is limited to 50,000 characters per add-in. + * In clients that support Mailbox 1.16 or later, the character limit per add-in is 2,621,440 characters. * * @param name - The session data key. * @param value - The session data value as a string. @@ -24380,7 +24713,8 @@ declare namespace Office { * * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-add-ins-overview#extension-points | Applicable Outlook mode}**: Compose * - * **Important**: For each mail item, the entire SessionData object is limited to 50,000 characters per add-in. + * **Important**: In Outlook clients that support Mailbox 1.15 or earlier, the entire SessionData object for each mail item is limited to 50,000 characters per add-in. + * In clients that support Mailbox 1.16 or later, the character limit per add-in is 2,621,440 characters. * * @param name - The session data key. * @param value - The session data value as a string.