npm - @types/office-js-preview - Versions diffs - 1.0.484 → 1.0.486 - Mend

@types/office-js-preview 1.0.484 → 1.0.486

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (3) hide show

office-js-preview/README.md CHANGED Viewed

@@ -8,7 +8,7 @@ This package contains type definitions for office-js-preview (https://github.com
 Files were exported from https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/office-js-preview.
 ### Additional Details
- * Last updated: Wed, 03 Jul 2024 21:07:51 GMT
+ * Last updated: Wed, 17 Jul 2024 22:36:40 GMT
  * Dependencies: none
 # Credits

office-js-preview/index.d.ts CHANGED Viewed

@@ -8014,7 +8014,7 @@ declare namespace Office {
          * </table>
          *
          * The `format:` property specifies values that correspond to a subset of the settings available in the Format Cells dialog box in Excel
-         * (Right-click then select **Format Cells**, or **Home** \> **Format** \> **Format Cells**).
+         * (Open the context menu (right-click or select and hold) then select **Format Cells**, or **Home** \> **Format** \> **Format Cells**).
          *
          * @param cellReference An object literal containing name-value pairs that specify the range of cells to get formatting from.
          * @param formats An array specifying the format properties to get.
@@ -8068,7 +8068,7 @@ declare namespace Office {
          * </table>
          *
          * The `format:` property specifies values that correspond to a subset of the settings available in the Format Cells dialog box in Excel
-         * (Right-click then select **Format Cells**, or **Home** \> **Format** \> **Format Cells**).
+         * (Open the context menu (right-click or select and hold) then select **Format Cells**, or **Home** \> **Format** \> **Format Cells**).
          *
          * @param cellReference An object literal containing name-value pairs that specify the range of cells to get formatting from.
          * @param formats An array specifying the format properties to get.
@@ -8125,7 +8125,7 @@ declare namespace Office {
          * </table>
          *
          * The `format:` property specifies values that correspond to a subset of the settings available in the Format Cells dialog box in Excel
-         * (Right-click then select **Format Cells**, or **Home** \> **Format** \> **Format Cells**).
+         * (Open the context menu (right-click or select and hold) then select **Format Cells**, or **Home** \> **Format** \> **Format Cells**).
          *
          * You specify the value of the `format:` property as a list of one or more property name - value pairs in a JavaScript object literal. The
          * property name specifies the name of the formatting property to set, and value specifies the property value.
@@ -8224,7 +8224,7 @@ declare namespace Office {
          * </table>
          *
          * The `format:` property specifies values that correspond to a subset of the settings available in the Format Cells dialog box in Excel
-         * (Right-click then select **Format Cells**, or **Home** \> **Format** \> **Format Cells**).
+         * (Open the context menu (right-click or select and hold) then select **Format Cells**, or **Home** \> **Format** \> **Format Cells**).
          *
          * You specify the value of the `format:` property as a list of one or more property name - value pairs in a JavaScript object literal. The
          * property name specifies the name of the formatting property to set, and value specifies the property value.
@@ -9097,31 +9097,16 @@ declare namespace Office {
         /**
          * Specifies an entity's type.
          *
-         * @remarks
-         *
-         * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-add-ins-overview#extension-points | Applicable Outlook mode}**: Compose or Read
-         *
-         * **Important**: Entity-based contextual Outlook add-ins will be retired in Q2 of 2024. The work to retire this feature will start in May and continue
-         * until the end of June. After June, contextual add-ins will no longer be able to detect entities in mail items to perform tasks on them.
-         * The following APIs will also be retired.
+         * **Warning**: Entity-based contextual Outlook add-ins are now retired. However, regular expression rules are still supported.
+         * We recommend updating your contextual add-in to use regular expression rules as an alternative solution.
+         * For guidance on how to implement these rules, see
+         * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | Contextual Outlook add-ins}.
          *
-         * - `Office.context.mailbox.item.getEntities`
-         * - `Office.context.mailbox.item.getEntitiesByType`
-         * - `Office.context.mailbox.item.getFilteredEntitiesByName`
-         * - `Office.context.mailbox.item.getSelectedEntities`
+         * @deprecated Use {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | regular expression rules} instead.
          *
-         * To help minimize potential disruptions, the following will still be supported after entity-based contextual add-ins are retired.
-         *
-         * - An alternative implementation of the **Join Meeting** button, which is activated by online meeting add-ins, is being developed. Once support for
-         * entity-based contextual add-ins ends, online meeting add-ins will automatically transition to the alternative implementation to activate the
-         * **Join Meeting** button.
-         *
-         * - Regular expression rules will continue to be supported after entity-based contextual add-ins are retired. We recommend updating your contextual add-in
-         * to use regular expression rules as an alternative solution. For guidance on how to implement these rules, see
-         * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/use-regular-expressions-to-show-an-outlook-add-in | Use regular expression activation rules to show an Outlook add-in}.
+         * @remarks
          *
-         * For more information, see
-         * {@link https://devblogs.microsoft.com/microsoft365dev/retirement-of-entity-based-contextual-outlook-add-ins | Retirement of entity-based contextual Outlook add-ins}.
+         * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-add-ins-overview#extension-points | Applicable Outlook mode}**: Compose or Read
          */
         enum EntityType {
             /**
@@ -12097,30 +12082,31 @@ declare namespace Office {
         /**
          * Gets the entities found in the selected item's body.
          *
+         * **Warning**: Entity-based contextual Outlook add-ins are now retired. However, regular expression rules are still supported.
+         * We recommend updating your contextual add-in to use regular expression rules as an alternative solution.
+         * For guidance on how to implement these rules, see
+         * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | Contextual Outlook add-ins}.
+         *
+         * @deprecated Use {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | regular expression rules} instead.
+         *
          * @remarks
          * [Api set: Mailbox 1.1]
          *
          * **{@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}**: Appointment Attendee
-         *
-         * **Important**:
-         *
-         * - Entity-based contextual Outlook add-ins, including the `getEntities` method, will be retired in Q2 of 2024. The work to retire this method will
-         * start in May and continue until the end of June. After June, contextual add-ins will no longer be able to detect entities in mail items to perform tasks on them.
-         * Regular expression rules will continue to be supported after entity-based contextual add-ins are retired. We recommend updating your contextual add-in
-         * to use regular expression rules as an alternative solution. For guidance on how to implement these rules, see
-         * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/use-regular-expressions-to-show-an-outlook-add-in | Use regular expression activation rules to show an Outlook add-in}.
-         * To learn more about the retirement of entity-based contextual Outlook add-ins, see
-         * {@link https://devblogs.microsoft.com/microsoft365dev/retirement-of-entity-based-contextual-outlook-add-ins | Retirement of entity-based contextual Outlook add-ins}.
-         *
-         * - This method isn't supported in Outlook on Android or on iOS. For more information on supported APIs in Outlook mobile, see
-         * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-mobile-apis | Outlook JavaScript APIs supported in Outlook on mobile devices}.
          */
         getEntities(): Entities;
         /**
          * Gets an array of all the entities of the specified entity type found in the selected item's body.
          *
+         * **Warning**: Entity-based contextual Outlook add-ins are now retired. However, regular expression rules are still supported.
+         * We recommend updating your contextual add-in to use regular expression rules as an alternative solution.
+         * For guidance on how to implement these rules, see
+         * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | Contextual Outlook add-ins}.
+         *
+         * @deprecated Use {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | regular expression rules} instead.
+         *
          * @returns
          * If the value passed in `entityType` is not a valid member of the `EntityType` enumeration, the method returns null.
          * If no entities of the specified type are present in the item's body, the method returns an empty array.
@@ -12132,71 +12118,20 @@ declare namespace Office {
          * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/understanding-outlook-add-in-permissions | Minimum permission level}**: **restricted**
          *
          * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-add-ins-overview#extension-points | Applicable Outlook mode}**: Appointment Attendee
-         *
-         * **Important**:
-         *
-         * - Entity-based contextual Outlook add-ins, including the `getEntitiesByType` method, will be retired in Q2 of 2024. The work to retire this method will
-         * start in May and continue until the end of June. After June, contextual add-ins will no longer be able to detect entities in mail items to perform tasks on them.
-         * Regular expression rules will continue to be supported after entity-based contextual add-ins are retired. We recommend updating your contextual add-in
-         * to use regular expression rules as an alternative solution. For guidance on how to implement these rules, see
-         * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/use-regular-expressions-to-show-an-outlook-add-in | Use regular expression activation rules to show an Outlook add-in}.
-         * To learn more about the retirement of entity-based contextual Outlook add-ins, see
-         * {@link https://devblogs.microsoft.com/microsoft365dev/retirement-of-entity-based-contextual-outlook-add-ins | Retirement of entity-based contextual Outlook add-ins}.
-         *
-         * - This method isn't supported in Outlook on Android or on iOS. For more information on supported APIs in Outlook mobile, see
-         * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-mobile-apis | Outlook JavaScript APIs supported in Outlook on mobile devices}.
          *
          * @param entityType - One of the `EntityType` enumeration values.
-         *
-         * While the minimum permission level to use this method is **restricted**, some entity types require **read item** to access, as specified in the following table.
-         *
-         * <table>
-         *   <tr>
-         *     <th>Value of entityType</th>
-         *     <th>Type of objects in returned array</th>
-         *     <th>Required permission level</th>
-         *   </tr>
-         *   <tr>
-         *     <td>Address</td>
-         *     <td>String</td>
-         *     <td>Restricted</td>
-         *   </tr>
-         *   <tr>
-         *     <td>Contact</td>
-         *     <td>Contact</td>
-         *     <td>ReadItem</td>
-         *   </tr>
-         *   <tr>
-         *     <td>EmailAddress</td>
-         *     <td>String</td>
-         *     <td>ReadItem</td>
-         *   </tr>
-         *   <tr>
-         *     <td>MeetingSuggestion</td>
-         *     <td>MeetingSuggestion</td>
-         *     <td>ReadItem</td>
-         *   </tr>
-         *   <tr>
-         *     <td>PhoneNumber</td>
-         *     <td>PhoneNumber</td>
-         *     <td>Restricted</td>
-         *   </tr>
-         *   <tr>
-         *     <td>TaskSuggestion</td>
-         *     <td>TaskSuggestion</td>
-         *     <td>ReadItem</td>
-         *   </tr>
-         *   <tr>
-         *     <td>URL</td>
-         *     <td>String</td>
-         *     <td>Restricted</td>
-         *   </tr>
-         * </table>
          */
         getEntitiesByType(entityType: MailboxEnums.EntityType | string): Array<string | Contact | MeetingSuggestion | PhoneNumber | TaskSuggestion>;
         /**
          * Returns well-known entities in the selected item that pass the named filter defined in an XML manifest file.
          *
+         * **Warning**: Entity-based contextual Outlook add-ins are now retired. However, regular expression rules are still supported.
+         * We recommend updating your contextual add-in to use regular expression rules as an alternative solution.
+         * For guidance on how to implement these rules, see
+         * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | Contextual Outlook add-ins}.
+         *
+         * @deprecated Use {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | regular expression rules} instead.
+         *
          * @returns
          * The entities that match the regular expression defined in the `ItemHasKnownEntity` rule element in the
          * manifest XML file with the specified `FilterName` element value. If there's no `ItemHasKnownEntity` element in the manifest with a
@@ -12210,22 +12145,6 @@ declare namespace Office {
          *
          * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-add-ins-overview#extension-points | Applicable Outlook mode}**: Appointment Attendee
          *
-         * **Important**:
-         *
-         * - Entity-based contextual Outlook add-ins, including the `getFilteredEntitiesByName` method, will be retired in Q2 of 2024. The work to retire this method will
-         * start in May and continue until the end of June. After June, contextual add-ins will no longer be able to detect entities in mail items to perform tasks on them.
-         * Regular expression rules will continue to be supported after entity-based contextual add-ins are retired. We recommend updating your contextual add-in
-         * to use regular expression rules as an alternative solution. For guidance on how to implement these rules, see
-         * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/use-regular-expressions-to-show-an-outlook-add-in | Use regular expression activation rules to show an Outlook add-in}.
-         * To learn more about the retirement of entity-based contextual Outlook add-ins, see
-         * {@link https://devblogs.microsoft.com/microsoft365dev/retirement-of-entity-based-contextual-outlook-add-ins | Retirement of entity-based contextual Outlook add-ins}.
-         *
-         * - This method is used with the {@link https://learn.microsoft.com/office/dev/add-ins/outlook/activation-rules | activation rules feature for Outlook add-ins},
-         * which isn't supported by the {@link https://learn.microsoft.com/office/dev/add-ins/develop/json-manifest-overview | unified manifest for Microsoft 365}.
-         *
-         * - This method isn't supported in Outlook on Android or on iOS. For more information on supported APIs in Outlook mobile, see
-         * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-mobile-apis | Outlook JavaScript APIs supported in Outlook on mobile devices}.
-         *
          * @param name - The name of the `ItemHasKnownEntity` rule element that defines the filter to match.
          */
         getFilteredEntitiesByName(name: string): Array<string | Contact | MeetingSuggestion | PhoneNumber | TaskSuggestion>;
@@ -12268,8 +12187,8 @@ declare namespace Office {
          *
          * @returns
          * An object that contains arrays of strings that match the regular expressions defined in the manifest XML file.
-         * The name of each array is equal to the corresponding value of the RegExName attribute of the matching `ItemHasRegularExpressionMatch` rule
-         * or the `FilterName` attribute of the matching `ItemHasKnownEntity` rule. For an `ItemHasRegularExpressionMatch` rule, a matching string has to occur in the property
+         * The name of each array is equal to the corresponding value of the RegExName attribute of the matching `ItemHasRegularExpressionMatch` rule.
+         * For an `ItemHasRegularExpressionMatch` rule, a matching string has to occur in the property
          * of the item that's specified by that rule. The `PropertyName` simple type defines the supported properties.
          *
          * @remarks
@@ -12281,12 +12200,10 @@ declare namespace Office {
          *
          * **Important**:
          *
-         * - Entity-based contextual Outlook add-ins will be retired in Q2 of 2024. Once retired, contextual add-ins will no longer be able to detect
-         * entities in mail items to perform tasks on them. Regular expression rules will continue to be supported after entity-based contextual add-ins are retired.
-         * We recommend updating your contextual add-in to use regular expression rules as an alternative solution. For guidance on how to implement these rules, see
-         * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/use-regular-expressions-to-show-an-outlook-add-in | Use regular expression activation rules to show an Outlook add-in}.
-         * To learn more about the retirement of entity-based contextual add-ins, see
-         * {@link https://devblogs.microsoft.com/microsoft365dev/retirement-of-entity-based-contextual-outlook-add-ins | Retirement of entity-based contextual Outlook add-ins}.
+         * - Entity-based contextual Outlook add-ins are now retired. However, regular expression rules are still supported.
+         * We recommend updating your contextual add-in to use regular expression rules as an alternative solution.
+         * For guidance on how to implement these rules, see
+         * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | Contextual Outlook add-ins}.
          *
          * - This method is used with the {@link https://learn.microsoft.com/office/dev/add-ins/outlook/activation-rules | activation rules feature for Outlook add-ins},
          * which isn't supported by the {@link https://learn.microsoft.com/office/dev/add-ins/develop/json-manifest-overview | unified manifest for Microsoft 365}.
@@ -12315,12 +12232,10 @@ declare namespace Office {
          *
          * **Important**:
          *
-         * - Entity-based contextual Outlook add-ins will be retired in Q2 of 2024. Once retired, contextual add-ins will no longer be able to detect
-         * entities in mail items to perform tasks on them. Regular expression rules will continue to be supported after entity-based contextual add-ins are retired.
-         * We recommend updating your contextual add-in to use regular expression rules as an alternative solution. For guidance on how to implement these rules, see
-         * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/use-regular-expressions-to-show-an-outlook-add-in | Use regular expression activation rules to show an Outlook add-in}.
-         * To learn more about the retirement of entity-based contextual add-ins, see
-         * {@link https://devblogs.microsoft.com/microsoft365dev/retirement-of-entity-based-contextual-outlook-add-ins | Retirement of entity-based contextual Outlook add-ins}.
+         * - Entity-based contextual Outlook add-ins are now retired. However, regular expression rules are still supported.
+         * We recommend updating your contextual add-in to use regular expression rules as an alternative solution.
+         * For guidance on how to implement these rules, see
+         * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | Contextual Outlook add-ins}.
          *
          * - This method is used with the {@link https://learn.microsoft.com/office/dev/add-ins/outlook/activation-rules | activation rules feature for Outlook add-ins},
          * which isn't supported by the {@link https://learn.microsoft.com/office/dev/add-ins/develop/json-manifest-overview | unified manifest for Microsoft 365}.
@@ -12338,6 +12253,13 @@ declare namespace Office {
         /**
          * Gets the entities found in a highlighted match a user has selected. Highlighted matches apply to contextual add-ins.
          *
+         * **Warning**: Entity-based contextual Outlook add-ins are now retired. However, regular expression rules are still supported.
+         * We recommend updating your contextual add-in to use regular expression rules as an alternative solution.
+         * For guidance on how to implement these rules, see
+         * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | Contextual Outlook add-ins}.
+         *
+         * @deprecated Use {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | regular expression rules} instead.
+         *
          * @remarks
          * [Api set: Mailbox 1.6]
          *
@@ -12345,22 +12267,6 @@ declare namespace Office {
          *
          * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-add-ins-overview#extension-points | Applicable Outlook mode}**: Appointment Attendee
          *
-         * **Important**:
-         *
-         * - Entity-based contextual Outlook add-ins, including the `getSelectedEntities` method, will be retired in Q2 of 2024. The work to retire this method will
-         * start in May and continue until the end of June. After June, contextual add-ins will no longer be able to detect entities in mail items to perform tasks on them.
-         * Regular expression rules will continue to be supported after entity-based contextual add-ins are retired. We recommend updating your contextual add-in
-         * to use regular expression rules as an alternative solution. For guidance on how to implement these rules, see
-         * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/use-regular-expressions-to-show-an-outlook-add-in | Use regular expression activation rules to show an Outlook add-in}.
-         * To learn more about the retirement of entity-based contextual Outlook add-ins, see
-         * {@link https://devblogs.microsoft.com/microsoft365dev/retirement-of-entity-based-contextual-outlook-add-ins | Retirement of entity-based contextual Outlook add-ins}.
-         *
-         * - This method is used with the {@link https://learn.microsoft.com/office/dev/add-ins/outlook/activation-rules | activation rules feature for Outlook add-ins},
-         * which isn't supported by the {@link https://learn.microsoft.com/office/dev/add-ins/develop/json-manifest-overview | unified manifest for Microsoft 365}.
-         *
-         * - This method isn't supported in Outlook on iOS or Android. For more information on supported APIs in Outlook mobile, see
-         * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-mobile-apis | Outlook JavaScript APIs supported in Outlook on mobile devices}.
-         *
          * @param name - The name of the `ItemHasRegularExpressionMatch` rule element that defines the filter to match.
          */
         getSelectedEntities(): Entities;
@@ -12370,9 +12276,9 @@ declare namespace Office {
          *
          * @returns
          * An object that contains arrays of strings that match the regular expressions defined in the manifest XML file.
-         * The name of each array is equal to the corresponding value of the `RegExName` attribute of the matching `ItemHasRegularExpressionMatch` rule or
-         * the `FilterName` attribute of the matching `ItemHasKnownEntity` rule. For an `ItemHasRegularExpressionMatch` rule, a matching string has to occur
-         * in the property of the item that is specified by that rule. The `PropertyName` simple type defines the supported properties.
+         * The name of each array is equal to the corresponding value of the `RegExName` attribute of the matching `ItemHasRegularExpressionMatch` rule.
+         * For an `ItemHasRegularExpressionMatch` rule, a matching string has to occur in the property of the item that's specified by that rule.
+         * The `PropertyName` simple type defines the supported properties.
          *
          * @remarks
          * [Api set: Mailbox 1.6]
@@ -12383,12 +12289,10 @@ declare namespace Office {
          *
          * **Important**:
          *
-         * - Entity-based contextual Outlook add-ins will be retired in Q2 of 2024. Once retired, contextual add-ins will no longer be able to detect
-         * entities in mail items to perform tasks on them. Regular expression rules will continue to be supported after entity-based contextual add-ins are retired.
-         * We recommend updating your contextual add-in to use regular expression rules as an alternative solution. For guidance on how to implement these rules, see
-         * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/use-regular-expressions-to-show-an-outlook-add-in | Use regular expression activation rules to show an Outlook add-in}.
-         * To learn more about the retirement of entity-based contextual add-ins, see
-         * {@link https://devblogs.microsoft.com/microsoft365dev/retirement-of-entity-based-contextual-outlook-add-ins | Retirement of entity-based contextual Outlook add-ins}.
+         * - Entity-based contextual Outlook add-ins are now retired. However, regular expression rules are still supported.
+         * We recommend updating your contextual add-in to use regular expression rules as an alternative solution.
+         * For guidance on how to implement these rules, see
+         * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | Contextual Outlook add-ins}.
          *
          * - This method is used with the {@link https://learn.microsoft.com/office/dev/add-ins/outlook/activation-rules | activation rules feature for Outlook add-ins},
          * which isn't supported by the {@link https://learn.microsoft.com/office/dev/add-ins/develop/json-manifest-overview | unified manifest for Microsoft 365}.
@@ -13425,57 +13329,84 @@ declare namespace Office {
      * The list of contacts extracted from the body of an email message or appointment is returned in the `contacts` property of the
      * {@link Office.Entities | Entities} object returned by the `getEntities` or `getEntitiesByType` method of the current item.
      *
+     * **Warning**: Entity-based contextual Outlook add-ins are now retired. However, regular expression rules are still supported.
+     * We recommend updating your contextual add-in to use regular expression rules as an alternative solution.
+     * For guidance on how to implement these rules, see
+     * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | Contextual Outlook add-ins}.
+     *
+     * @deprecated Use {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | regular expression rules} instead.
+     *
      * @remarks
      *
      * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/understanding-outlook-add-in-permissions | Minimum permission level}**: **restricted**
      *
      * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-add-ins-overview#extension-points | Applicable Outlook mode}**: Read
-     *
-     * **Important**: Entity-based contextual Outlook add-ins will be retired in Q2 of 2024. The work to retire this feature will start in May and continue
-     * until the end of June. After June, contextual add-ins will no longer be able to detect entities in mail items to perform tasks on them.
-     * The following APIs will also be retired.
-     *
-     * - `Office.context.mailbox.item.getEntities`
-     * - `Office.context.mailbox.item.getEntitiesByType`
-     * - `Office.context.mailbox.item.getFilteredEntitiesByName`
-     * - `Office.context.mailbox.item.getSelectedEntities`
-     *
-     * To help minimize potential disruptions, the following will still be supported after entity-based contextual add-ins are retired.
-     *
-     * - An alternative implementation of the **Join Meeting** button, which is activated by online meeting add-ins, is being developed. Once support for
-     * entity-based contextual add-ins ends, online meeting add-ins will automatically transition to the alternative implementation to activate the
-     * **Join Meeting** button.
-     *
-     * - Regular expression rules will continue to be supported after entity-based contextual add-ins are retired. We recommend updating your contextual add-in
-     * to use regular expression rules as an alternative solution. For guidance on how to implement these rules, see
-     * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/use-regular-expressions-to-show-an-outlook-add-in | Use regular expression activation rules to show an Outlook add-in}.
-     *
-     * For more information, see
-     * {@link https://devblogs.microsoft.com/microsoft365dev/retirement-of-entity-based-contextual-outlook-add-ins | Retirement of entity-based contextual Outlook add-ins}.
      */
     interface Contact {
         /**
          * An array of strings containing the mailing and street addresses associated with the contact. Nullable.
+         *
+         * **Warning**: Entity-based contextual Outlook add-ins are now retired. However, regular expression rules are still supported.
+         * We recommend updating your contextual add-in to use regular expression rules as an alternative solution.
+         * For guidance on how to implement these rules, see
+         * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | Contextual Outlook add-ins}.
+         *
+         * @deprecated Use {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | regular expression rules} instead.
          */
         addresses: string[];
         /**
          * A string containing the name of the business associated with the contact. Nullable.
+         *
+         * **Warning**: Entity-based contextual Outlook add-ins are now retired. However, regular expression rules are still supported.
+         * We recommend updating your contextual add-in to use regular expression rules as an alternative solution.
+         * For guidance on how to implement these rules, see
+         * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | Contextual Outlook add-ins}.
+         *
+         * @deprecated Use {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | regular expression rules} instead.
          */
         businessName: string;
         /**
          * An array of strings containing the SMTP email addresses associated with the contact. Nullable.
+         *
+         * **Warning**: Entity-based contextual Outlook add-ins are now retired. However, regular expression rules are still supported.
+         * We recommend updating your contextual add-in to use regular expression rules as an alternative solution.
+         * For guidance on how to implement these rules, see
+         * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | Contextual Outlook add-ins}.
+         *
+         * @deprecated Use {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | regular expression rules} instead.
          */
         emailAddresses: string[];
         /**
          * A string containing the name of the person associated with the contact. Nullable.
+         *
+         * **Warning**: Entity-based contextual Outlook add-ins are now retired. However, regular expression rules are still supported.
+         * We recommend updating your contextual add-in to use regular expression rules as an alternative solution.
+         * For guidance on how to implement these rules, see
+         * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | Contextual Outlook add-ins}.
+         *
+         * @deprecated Use {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | regular expression rules} instead.
          */
         personName: string;
         /**
          * An array containing a `PhoneNumber` object for each phone number associated with the contact. Nullable.
+         *
+         * **Warning**: Entity-based contextual Outlook add-ins are now retired. However, regular expression rules are still supported.
+         * We recommend updating your contextual add-in to use regular expression rules as an alternative solution.
+         * For guidance on how to implement these rules, see
+         * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | Contextual Outlook add-ins}.
+         *
+         * @deprecated Use {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | regular expression rules} instead.
          */
         phoneNumbers: PhoneNumber[];
         /**
          * An array of strings containing the Internet URLs associated with the contact. Nullable.
+         *
+         * **Warning**: Entity-based contextual Outlook add-ins are now retired. However, regular expression rules are still supported.
+         * We recommend updating your contextual add-in to use regular expression rules as an alternative solution.
+         * For guidance on how to implement these rules, see
+         * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | Contextual Outlook add-ins}.
+         *
+         * @deprecated Use {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | regular expression rules} instead.
          */
         urls: string[];
     }
@@ -14220,61 +14151,95 @@ declare namespace Office {
      * When the property arrays are returned by the `getEntitiesByType` method, only the property for the specified entity contains data;
      * all other properties are null.
      *
+     * **Warning**: Entity-based contextual Outlook add-ins are now retired. However, regular expression rules are still supported.
+     * We recommend updating your contextual add-in to use regular expression rules as an alternative solution.
+     * For guidance on how to implement these rules, see
+     * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | Contextual Outlook add-ins}.
+     *
+     * @deprecated Use {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | regular expression rules} instead.
+     *
      * @remarks
      *
      * **{@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}**: Read
-     *
-     * **Important**: Entity-based contextual Outlook add-ins will be retired in Q2 of 2024. The work to retire this feature will start in May and continue
-     * until the end of June. After June, contextual add-ins will no longer be able to detect entities in mail items to perform tasks on them.
-     * The following APIs will also be retired.
-     *
-     * - `Office.context.mailbox.item.getEntities`
-     * - `Office.context.mailbox.item.getEntitiesByType`
-     * - `Office.context.mailbox.item.getFilteredEntitiesByName`
-     * - `Office.context.mailbox.item.getSelectedEntities`
-     *
-     * To help minimize potential disruptions, the following will still be supported after entity-based contextual add-ins are retired.
-     *
-     * - An alternative implementation of the **Join Meeting** button, which is activated by online meeting add-ins, is being developed. Once support for
-     * entity-based contextual add-ins ends, online meeting add-ins will automatically transition to the alternative implementation to activate the
-     * **Join Meeting** button.
-     *
-     * - Regular expression rules will continue to be supported after entity-based contextual add-ins are retired. We recommend updating your contextual add-in
-     * to use regular expression rules as an alternative solution. For guidance on how to implement these rules, see
-     * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/use-regular-expressions-to-show-an-outlook-add-in | Use regular expression activation rules to show an Outlook add-in}.
-     *
-     * For more information, see
-     * {@link https://devblogs.microsoft.com/microsoft365dev/retirement-of-entity-based-contextual-outlook-add-ins | Retirement of entity-based contextual Outlook add-ins}.
      */
     interface Entities {
         /**
          * Gets the physical addresses (street or mailing addresses) found in an email message or appointment.
+         *
+         * **Warning**: Entity-based contextual Outlook add-ins are now retired. However, regular expression rules are still supported.
+         * We recommend updating your contextual add-in to use regular expression rules as an alternative solution.
+         * For guidance on how to implement these rules, see
+         * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | Contextual Outlook add-ins}.
+         *
+         * @deprecated Use {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | regular expression rules} instead.
          */
         addresses: string[];
         /**
          * Gets the contacts found in an email address or appointment.
+         *
+         * **Warning**: Entity-based contextual Outlook add-ins are now retired. However, regular expression rules are still supported.
+         * We recommend updating your contextual add-in to use regular expression rules as an alternative solution.
+         * For guidance on how to implement these rules, see
+         * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | Contextual Outlook add-ins}.
+         *
+         * @deprecated Use {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | regular expression rules} instead.
          */
         contacts: Contact[];
         /**
          * Gets the email addresses found in an email message or appointment.
+         *
+         * **Warning**: Entity-based contextual Outlook add-ins are now retired. However, regular expression rules are still supported.
+         * We recommend updating your contextual add-in to use regular expression rules as an alternative solution.
+         * For guidance on how to implement these rules, see
+         * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | Contextual Outlook add-ins}.
+         *
+         * @deprecated Use {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | regular expression rules} instead.
          */
         emailAddresses: string[];
         /**
          * Gets the meeting suggestions found in an email message.
+         *
+         * **Warning**: Entity-based contextual Outlook add-ins are now retired. However, regular expression rules are still supported.
+         * We recommend updating your contextual add-in to use regular expression rules as an alternative solution.
+         * For guidance on how to implement these rules, see
+         * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | Contextual Outlook add-ins}.
+         *
+         * @deprecated Use {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | regular expression rules} instead.
          */
         meetingSuggestions: MeetingSuggestion[];
         /**
          * Gets the phone numbers found in an email message or appointment.
+         *
+         * **Warning**: Entity-based contextual Outlook add-ins are now retired. However, regular expression rules are still supported.
+         * We recommend updating your contextual add-in to use regular expression rules as an alternative solution.
+         * For guidance on how to implement these rules, see
+         * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | Contextual Outlook add-ins}.
+         *
+         * @deprecated Use {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | regular expression rules} instead.
          */
         phoneNumbers: PhoneNumber[];
         /**
          * Gets the task suggestions found in an email message or appointment.
+         *
+         * **Warning**: Entity-based contextual Outlook add-ins are now retired. However, regular expression rules are still supported.
+         * We recommend updating your contextual add-in to use regular expression rules as an alternative solution.
+         * For guidance on how to implement these rules, see
+         * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | Contextual Outlook add-ins}.
+         *
+         * @deprecated Use {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | regular expression rules} instead.
          */
         taskSuggestions: string[];
         /**
          * Gets the Internet URLs present in an email message or appointment.
+         *
+         * **Warning**: Entity-based contextual Outlook add-ins are now retired. However, regular expression rules are still supported.
+         * We recommend updating your contextual add-in to use regular expression rules as an alternative solution.
+         * For guidance on how to implement these rules, see
+         * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | Contextual Outlook add-ins}.
+         *
+         * @deprecated Use {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | regular expression rules} instead.
          */
         urls: string[];
     }
@@ -15993,63 +15958,90 @@ declare namespace Office {
     /**
      * Represents a suggested meeting found in an item. Read mode only.
      *
-     * The list of meetings suggested in an email message is returned in the `meetingSuggestions` property of the `Entities` object that is returned when
+     * The list of meetings suggested in an email message is returned in the `meetingSuggestions` property of the `Entities` object that's returned when
      * the `getEntities` or `getEntitiesByType` method is called on the active item.
      *
      * The start and end values are string representations of a `Date` object that contains the date and time at which the suggested meeting is to
      * begin and end. The values are in the default time zone specified for the current user.
      *
+     * **Warning**: Entity-based contextual Outlook add-ins are now retired. However, regular expression rules are still supported.
+     * We recommend updating your contextual add-in to use regular expression rules as an alternative solution.
+     * For guidance on how to implement these rules, see
+     * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | Contextual Outlook add-ins}.
+     *
+     * @deprecated Use {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | regular expression rules} instead.
+     *
      * @remarks
      *
      * **{@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}**: Read
-     *
-     * **Important**: Entity-based contextual Outlook add-ins will be retired in Q2 of 2024. The work to retire this feature will start in May and continue
-     * until the end of June. After June, contextual add-ins will no longer be able to detect entities in mail items to perform tasks on them.
-     * The following APIs will also be retired.
-     *
-     * - `Office.context.mailbox.item.getEntities`
-     * - `Office.context.mailbox.item.getEntitiesByType`
-     * - `Office.context.mailbox.item.getFilteredEntitiesByName`
-     * - `Office.context.mailbox.item.getSelectedEntities`
-     *
-     * To help minimize potential disruptions, the following will still be supported after entity-based contextual add-ins are retired.
-     *
-     * - An alternative implementation of the **Join Meeting** button, which is activated by online meeting add-ins, is being developed. Once support for
-     * entity-based contextual add-ins ends, online meeting add-ins will automatically transition to the alternative implementation to activate the
-     * **Join Meeting** button.
-     *
-     * - Regular expression rules will continue to be supported after entity-based contextual add-ins are retired. We recommend updating your contextual add-in
-     * to use regular expression rules as an alternative solution. For guidance on how to implement these rules, see
-     * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/use-regular-expressions-to-show-an-outlook-add-in | Use regular expression activation rules to show an Outlook add-in}.
-     *
-     * For more information, see
-     * {@link https://devblogs.microsoft.com/microsoft365dev/retirement-of-entity-based-contextual-outlook-add-ins | Retirement of entity-based contextual Outlook add-ins}.
      */
     interface MeetingSuggestion {
         /**
          * Gets the attendees for a suggested meeting.
+         *
+         * **Warning**: Entity-based contextual Outlook add-ins are now retired. However, regular expression rules are still supported.
+         * We recommend updating your contextual add-in to use regular expression rules as an alternative solution.
+         * For guidance on how to implement these rules, see
+         * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | Contextual Outlook add-ins}.
+         *
+         * @deprecated Use {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | regular expression rules} instead.
          */
         attendees: EmailUser[];
         /**
          * Gets the date and time that a suggested meeting is to end.
+         *
+         * **Warning**: Entity-based contextual Outlook add-ins are now retired. However, regular expression rules are still supported.
+         * We recommend updating your contextual add-in to use regular expression rules as an alternative solution.
+         * For guidance on how to implement these rules, see
+         * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | Contextual Outlook add-ins}.
+         *
+         * @deprecated Use {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | regular expression rules} instead.
          */
         end: string;
         /**
          * Gets the location of a suggested meeting.
+         *
+         * **Warning**: Entity-based contextual Outlook add-ins are now retired. However, regular expression rules are still supported.
+         * We recommend updating your contextual add-in to use regular expression rules as an alternative solution.
+         * For guidance on how to implement these rules, see
+         * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | Contextual Outlook add-ins}.
+         *
+         * @deprecated Use {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | regular expression rules} instead.
          */
         location: string;
         /**
          * Gets a string that was identified as a meeting suggestion.
+         *
+         * **Warning**: Entity-based contextual Outlook add-ins are now retired. However, regular expression rules are still supported.
+         * We recommend updating your contextual add-in to use regular expression rules as an alternative solution.
+         * For guidance on how to implement these rules, see
+         * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | Contextual Outlook add-ins}.
+         *
+         * @deprecated Use {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | regular expression rules} instead.
          */
         meetingString: string;
         /**
          * Gets the date and time that a suggested meeting is to begin.
+         *
+         * **Warning**: Entity-based contextual Outlook add-ins are now retired. However, regular expression rules are still supported.
+         * We recommend updating your contextual add-in to use regular expression rules as an alternative solution.
+         * For guidance on how to implement these rules, see
+         * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | Contextual Outlook add-ins}.
+         *
+         * @deprecated Use {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | regular expression rules} instead.
          */
         start: string;
         /**
          * Gets the subject of a suggested meeting.
+         *
+         * **Warning**: Entity-based contextual Outlook add-ins are now retired. However, regular expression rules are still supported.
+         * We recommend updating your contextual add-in to use regular expression rules as an alternative solution.
+         * For guidance on how to implement these rules, see
+         * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | Contextual Outlook add-ins}.
+         *
+         * @deprecated Use {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | regular expression rules} instead.
          */
         subject: string;
     }
@@ -18261,30 +18253,31 @@ declare namespace Office {
         /**
          * Gets the entities found in the selected item's body.
          *
+         * **Warning**: Entity-based contextual Outlook add-ins are now retired. However, regular expression rules are still supported.
+         * We recommend updating your contextual add-in to use regular expression rules as an alternative solution.
+         * For guidance on how to implement these rules, see
+         * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | Contextual Outlook add-ins}.
+         *
+         * @deprecated Use {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | regular expression rules} instead.
+         *
          * @remarks
          * [Api set: Mailbox 1.1]
          *
          * **{@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}**: Appointment Attendee
-         *
-         * **Important**:
-         *
-         * - Entity-based contextual Outlook add-ins, including the `getEntities` method, will be retired in Q2 of 2024. The work to retire this method will
-         * start in May and continue until the end of June. After June, contextual add-ins will no longer be able to detect entities in mail items to perform tasks on them.
-         * Regular expression rules will continue to be supported after entity-based contextual add-ins are retired. We recommend updating your contextual add-in
-         * to use regular expression rules as an alternative solution. For guidance on how to implement these rules, see
-         * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/use-regular-expressions-to-show-an-outlook-add-in | Use regular expression activation rules to show an Outlook add-in}.
-         * To learn more about the retirement of entity-based contextual Outlook add-ins, see
-         * {@link https://devblogs.microsoft.com/microsoft365dev/retirement-of-entity-based-contextual-outlook-add-ins | Retirement of entity-based contextual Outlook add-ins}.
-         *
-         * - This method isn't supported in Outlook on Android or on iOS. For more information on supported APIs in Outlook mobile, see
-         * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-mobile-apis | Outlook JavaScript APIs supported in Outlook on mobile devices}.
          */
         getEntities(): Entities;
         /**
          * Gets an array of all the entities of the specified entity type found in the selected item's body.
          *
+         * **Warning**: Entity-based contextual Outlook add-ins are now retired. However, regular expression rules are still supported.
+         * We recommend updating your contextual add-in to use regular expression rules as an alternative solution.
+         * For guidance on how to implement these rules, see
+         * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | Contextual Outlook add-ins}.
+         *
+         * @deprecated Use {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | regular expression rules} instead.
+         *
          * @returns
          * If the value passed in `entityType` is not a valid member of the `EntityType` enumeration, the method returns `null`.
          * If no entities of the specified type are present in the item's body, the method returns an empty array.
@@ -18297,71 +18290,19 @@ declare namespace Office {
          *
          * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-add-ins-overview#extension-points | Applicable Outlook mode}**: Message Read
          *
-         * **Important**:
-         *
-         * - Entity-based contextual Outlook add-ins, including the `getEntitiesByType` method, will be retired in Q2 of 2024. The work to retire this method will
-         * start in May and continue until the end of June. After June, contextual add-ins will no longer be able to detect entities in mail items to perform tasks on them.
-         * Regular expression rules will continue to be supported after entity-based contextual add-ins are retired. We recommend updating your contextual add-in
-         * to use regular expression rules as an alternative solution. For guidance on how to implement these rules, see
-         * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/use-regular-expressions-to-show-an-outlook-add-in | Use regular expression activation rules to show an Outlook add-in}.
-         * To learn more about the retirement of entity-based contextual Outlook add-ins, see
-         * {@link https://devblogs.microsoft.com/microsoft365dev/retirement-of-entity-based-contextual-outlook-add-ins | Retirement of entity-based contextual Outlook add-ins}.
-         *
-         * - This method isn't supported in Outlook on Android or on iOS. For more information on supported APIs in Outlook mobile, see
-         * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-mobile-apis | Outlook JavaScript APIs supported in Outlook on mobile devices}.
-         *
          * @param entityType - One of the `EntityType` enumeration values.
-         *
-         * While the minimum permission level to use this method is **restricted**, some entity types require **read item** to access, as specified in the
-         * following table.
-         *
-         * <table>
-         *   <tr>
-         *     <th>Value of entityType</th>
-         *     <th>Type of objects in returned array</th>
-         *     <th>Required permission level</th>
-         *   </tr>
-         *   <tr>
-         *     <td>Address</td>
-         *     <td>String</td>
-         *     <td>Restricted</td>
-         *   </tr>
-         *   <tr>
-         *     <td>Contact</td>
-         *     <td>Contact</td>
-         *     <td>ReadItem</td>
-         *   </tr>
-         *   <tr>
-         *     <td>EmailAddress</td>
-         *     <td>String</td>
-         *     <td>ReadItem</td>
-         *   </tr>
-         *   <tr>
-         *     <td>MeetingSuggestion</td>
-         *     <td>MeetingSuggestion</td>
-         *     <td>ReadItem</td>
-         *   </tr>
-         *   <tr>
-         *     <td>PhoneNumber</td>
-         *     <td>PhoneNumber</td>
-         *     <td>Restricted</td>
-         *   </tr>
-         *   <tr>
-         *     <td>TaskSuggestion</td>
-         *     <td>TaskSuggestion</td>
-         *     <td>ReadItem</td>
-         *   </tr>
-         *   <tr>
-         *     <td>URL</td>
-         *     <td>String</td>
-         *     <td>Restricted</td>
-         *   </tr>
-         * </table>
          */
         getEntitiesByType(entityType: MailboxEnums.EntityType | string): Array<string | Contact | MeetingSuggestion | PhoneNumber | TaskSuggestion>;
         /**
          * Returns well-known entities in the selected item that pass the named filter defined in an XML manifest file.
          *
+         * **Warning**: Entity-based contextual Outlook add-ins are now retired. However, regular expression rules are still supported.
+         * We recommend updating your contextual add-in to use regular expression rules as an alternative solution.
+         * For guidance on how to implement these rules, see
+         * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | Contextual Outlook add-ins}.
+         *
+         * @deprecated Use {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | regular expression rules} instead.
+         *
          * @returns
          * The entities that match the regular expression defined in the `ItemHasKnownEntity` rule element in the
          * manifest XML file with the specified `FilterName` element value. If there's no `ItemHasKnownEntity` element in the manifest with a
@@ -18375,22 +18316,6 @@ declare namespace Office {
          *
          * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-add-ins-overview#extension-points | Applicable Outlook mode}**: Appointment Attendee
          *
-         * **Important**:
-         *
-         * - Entity-based contextual Outlook add-ins, including the `getFilteredEntitiesByName` method, will be retired in Q2 of 2024. The work to retire this method will
-         * start in May and continue until the end of June. After June, contextual add-ins will no longer be able to detect entities in mail items to perform tasks on them.
-         * Regular expression rules will continue to be supported after entity-based contextual add-ins are retired. We recommend updating your contextual add-in
-         * to use regular expression rules as an alternative solution. For guidance on how to implement these rules, see
-         * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/use-regular-expressions-to-show-an-outlook-add-in | Use regular expression activation rules to show an Outlook add-in}.
-         * To learn more about the retirement of entity-based contextual Outlook add-ins, see
-         * {@link https://devblogs.microsoft.com/microsoft365dev/retirement-of-entity-based-contextual-outlook-add-ins | Retirement of entity-based contextual Outlook add-ins}.
-         *
-         * - This method is used with the {@link https://learn.microsoft.com/office/dev/add-ins/outlook/activation-rules | activation rules feature for Outlook add-ins},
-         * which isn't supported by the {@link https://learn.microsoft.com/office/dev/add-ins/develop/json-manifest-overview | unified manifest for Microsoft 365}.
-         *
-         * - This method isn't supported in Outlook on Android or on iOS. For more information on supported APIs in Outlook mobile, see
-         * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-mobile-apis | Outlook JavaScript APIs supported in Outlook on mobile devices}.
-         *
          * @param name - The name of the `ItemHasKnownEntity` rule element that defines the filter to match.
          */
         getFilteredEntitiesByName(name: string): Array<string | Contact | MeetingSuggestion | PhoneNumber | TaskSuggestion>;
@@ -18433,9 +18358,9 @@ declare namespace Office {
          *
          * @returns
          * An object that contains arrays of strings that match the regular expressions defined in the manifest XML file.
-         * The name of each array is equal to the corresponding value of the RegExName attribute of the matching `ItemHasRegularExpressionMatch` rule
-         * or the `FilterName` attribute of the matching `ItemHasKnownEntity` rule. For an `ItemHasRegularExpressionMatch` rule, a matching string has to occur in the property
-         * of the item that is specified by that rule. The `PropertyName` simple type defines the supported properties.
+         * The name of each array is equal to the corresponding value of the RegExName attribute of the matching `ItemHasRegularExpressionMatch` rule.
+         * For an `ItemHasRegularExpressionMatch` rule, a matching string has to occur in the property
+         * of the item that's specified by that rule. The `PropertyName` simple type defines the supported properties.
          *
          * @remarks
          * [Api set: Mailbox 1.1]
@@ -18446,12 +18371,10 @@ declare namespace Office {
          *
          * **Important**:
          *
-         * - Entity-based contextual Outlook add-ins will be retired in Q2 of 2024. Once retired, contextual add-ins will no longer be able to detect
-         * entities in mail items to perform tasks on them. Regular expression rules will continue to be supported after entity-based contextual add-ins are retired.
-         * We recommend updating your contextual add-in to use regular expression rules as an alternative solution. For guidance on how to implement these rules, see
-         * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/use-regular-expressions-to-show-an-outlook-add-in | Use regular expression activation rules to show an Outlook add-in}.
-         * To learn more about the retirement of entity-based contextual add-ins, see
-         * {@link https://devblogs.microsoft.com/microsoft365dev/retirement-of-entity-based-contextual-outlook-add-ins | Retirement of entity-based contextual Outlook add-ins}.
+         * - Entity-based contextual Outlook add-ins are now retired. However, regular expression rules are still supported.
+         * We recommend updating your contextual add-in to use regular expression rules as an alternative solution.
+         * For guidance on how to implement these rules, see
+         * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | Contextual Outlook add-ins}.
          *
          * - This method is used with the {@link https://learn.microsoft.com/office/dev/add-ins/outlook/activation-rules | activation rules feature for Outlook add-ins},
          * which isn't supported by the {@link https://learn.microsoft.com/office/dev/add-ins/develop/json-manifest-overview | unified manifest for Microsoft 365}.
@@ -18480,12 +18403,10 @@ declare namespace Office {
          *
          * **Important**:
          *
-         * - Entity-based contextual Outlook add-ins will be retired in Q2 of 2024. Once retired, contextual add-ins will no longer be able to detect
-         * entities in mail items to perform tasks on them. Regular expression rules will continue to be supported after entity-based contextual add-ins are retired.
-         * We recommend updating your contextual add-in to use regular expression rules as an alternative solution. For guidance on how to implement these rules, see
-         * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/use-regular-expressions-to-show-an-outlook-add-in | Use regular expression activation rules to show an Outlook add-in}.
-         * To learn more about the retirement of entity-based contextual add-ins, see
-         * {@link https://devblogs.microsoft.com/microsoft365dev/retirement-of-entity-based-contextual-outlook-add-ins | Retirement of entity-based contextual Outlook add-ins}.
+         * - Entity-based contextual Outlook add-ins are now retired. However, regular expression rules are still supported.
+         * We recommend updating your contextual add-in to use regular expression rules as an alternative solution.
+         * For guidance on how to implement these rules, see
+         * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | Contextual Outlook add-ins}.
          *
          * - This method is used with the {@link https://learn.microsoft.com/office/dev/add-ins/outlook/activation-rules | activation rules feature for Outlook add-ins},
          * which isn't supported by the {@link https://learn.microsoft.com/office/dev/add-ins/develop/json-manifest-overview | unified manifest for Microsoft 365}.
@@ -18502,11 +18423,13 @@ declare namespace Office {
         getRegExMatchesByName(name: string): string[];
         /**
          * Gets the entities found in a highlighted match a user has selected. Highlighted matches apply to contextual add-ins.
-         *
-         * **Note**: This method is used with the {@link https://learn.microsoft.com/office/dev/add-ins/outlook/activation-rules | activation rules feature for Outlook add-ins}, which isn't supported by the
-         * {@link https://learn.microsoft.com/office/dev/add-ins/develop/unified-manifest-overview | unified manifest for Microsoft 365}.
          *
-         * **Note**: This method isn't supported in Outlook on iOS or on Android.
+         * **Warning**: Entity-based contextual Outlook add-ins are now retired. However, regular expression rules are still supported.
+         * We recommend updating your contextual add-in to use regular expression rules as an alternative solution.
+         * For guidance on how to implement these rules, see
+         * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | Contextual Outlook add-ins}.
+         *
+         * @deprecated Use {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | regular expression rules} instead.
          *
          * @remarks
          * [Api set: Mailbox 1.6]
@@ -18515,22 +18438,6 @@ declare namespace Office {
          *
          * **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-add-ins-overview#extension-points | Applicable Outlook mode}**: Message Read
          *
-         * **Important**:
-         *
-         * - Entity-based contextual Outlook add-ins, including the `getSelectedEntities` method, will be retired in Q2 of 2024. The work to retire this method will
-         * start in May and continue until the end of June. After June, contextual add-ins will no longer be able to detect entities in mail items to perform tasks on them.
-         * Regular expression rules will continue to be supported after entity-based contextual add-ins are retired. We recommend updating your contextual add-in
-         * to use regular expression rules as an alternative solution. For guidance on how to implement these rules, see
-         * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/use-regular-expressions-to-show-an-outlook-add-in | Use regular expression activation rules to show an Outlook add-in}.
-         * To learn more about the retirement of entity-based contextual Outlook add-ins, see
-         * {@link https://devblogs.microsoft.com/microsoft365dev/retirement-of-entity-based-contextual-outlook-add-ins | Retirement of entity-based contextual Outlook add-ins}.
-         *
-         * - This method is used with the {@link https://learn.microsoft.com/office/dev/add-ins/outlook/activation-rules | activation rules feature for Outlook add-ins},
-         * which isn't supported by the {@link https://learn.microsoft.com/office/dev/add-ins/develop/json-manifest-overview | unified manifest for Microsoft 365}.
-         *
-         * - This method isn't supported in Outlook on iOS or Android. For more information on supported APIs in Outlook mobile, see
-         * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-mobile-apis | Outlook JavaScript APIs supported in Outlook on mobile devices}.
-         *
          * @param name - The name of the `ItemHasRegularExpressionMatch` rule element that defines the filter to match.
          */
         getSelectedEntities(): Entities;
@@ -18540,9 +18447,9 @@ declare namespace Office {
          *
          * @returns
          * An object that contains arrays of strings that match the regular expressions defined in the manifest XML file.
-         * The name of each array is equal to the corresponding value of the `RegExName` attribute of the matching `ItemHasRegularExpressionMatch` rule or
-         * the `FilterName` attribute of the matching `ItemHasKnownEntity` rule. For an `ItemHasRegularExpressionMatch` rule, a matching string has to occur
-         * in the property of the item that is specified by that rule. The `PropertyName` simple type defines the supported properties.
+         * The name of each array is equal to the corresponding value of the `RegExName` attribute of the matching `ItemHasRegularExpressionMatch` rule.
+         * For an `ItemHasRegularExpressionMatch` rule, a matching string has to occur in the property of the item that's specified by that rule.
+         * The `PropertyName` simple type defines the supported properties.
          *
          * @remarks
          * [Api set: Mailbox 1.6]
@@ -18553,12 +18460,10 @@ declare namespace Office {
          *
          * **Important**:
          *
-         * - Entity-based contextual Outlook add-ins will be retired in Q2 of 2024. Once retired, contextual add-ins will no longer be able to detect
-         * entities in mail items to perform tasks on them. Regular expression rules will continue to be supported after entity-based contextual add-ins are retired.
-         * We recommend updating your contextual add-in to use regular expression rules as an alternative solution. For guidance on how to implement these rules, see
-         * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/use-regular-expressions-to-show-an-outlook-add-in | Use regular expression activation rules to show an Outlook add-in}.
-         * To learn more about the retirement of entity-based contextual add-ins, see
-         * {@link https://devblogs.microsoft.com/microsoft365dev/retirement-of-entity-based-contextual-outlook-add-ins | Retirement of entity-based contextual Outlook add-ins}.
+         * - Entity-based contextual Outlook add-ins are now retired. However, regular expression rules are still supported.
+         * We recommend updating your contextual add-in to use regular expression rules as an alternative solution.
+         * For guidance on how to implement these rules, see
+         * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | Contextual Outlook add-ins}.
          *
          * - This method is used with the {@link https://learn.microsoft.com/office/dev/add-ins/outlook/activation-rules | activation rules feature for Outlook add-ins},
          * which isn't supported by the {@link https://learn.microsoft.com/office/dev/add-ins/develop/json-manifest-overview | unified manifest for Microsoft 365}.
@@ -19122,48 +19027,54 @@ declare namespace Office {
      * Represents a phone number identified in an item. Read mode only.
      *
      * An array of `PhoneNumber` objects containing the phone numbers found in an email message is returned in the `phoneNumbers` property of the
-     * `Entities` object that is returned when you call the `getEntities` method on the selected item.
+     * `Entities` object that's returned when you call the `getEntities` method on the selected item.
+     *
+     * **Warning**: Entity-based contextual Outlook add-ins are now retired. However, regular expression rules are still supported.
+     * We recommend updating your contextual add-in to use regular expression rules as an alternative solution.
+     * For guidance on how to implement these rules, see
+     * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | Contextual Outlook add-ins}.
+     *
+     * @deprecated Use {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | regular expression rules} instead.
      *
      * @remarks
      *
      * **{@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}**: Read
-     *
-     * **Important**: Entity-based contextual Outlook add-ins will be retired in Q2 of 2024. The work to retire this feature will start in May and continue
-     * until the end of June. After June, contextual add-ins will no longer be able to detect entities in mail items to perform tasks on them.
-     * The following APIs will also be retired.
-     *
-     * - `Office.context.mailbox.item.getEntities`
-     * - `Office.context.mailbox.item.getEntitiesByType`
-     * - `Office.context.mailbox.item.getFilteredEntitiesByName`
-     * - `Office.context.mailbox.item.getSelectedEntities`
-     *
-     * To help minimize potential disruptions, the following will still be supported after entity-based contextual add-ins are retired.
-     *
-     * - An alternative implementation of the **Join Meeting** button, which is activated by online meeting add-ins, is being developed. Once support for
-     * entity-based contextual add-ins ends, online meeting add-ins will automatically transition to the alternative implementation to activate the
-     * **Join Meeting** button.
-     *
-     * - Regular expression rules will continue to be supported after entity-based contextual add-ins are retired. We recommend updating your contextual add-in
-     * to use regular expression rules as an alternative solution. For guidance on how to implement these rules, see
-     * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/use-regular-expressions-to-show-an-outlook-add-in | Use regular expression activation rules to show an Outlook add-in}.
-     *
-     * For more information, see
-     * {@link https://devblogs.microsoft.com/microsoft365dev/retirement-of-entity-based-contextual-outlook-add-ins | Retirement of entity-based contextual Outlook add-ins}.
      */
     interface PhoneNumber {
         /**
          * Gets a string containing a phone number. This string contains only the digits of the telephone number and excludes characters
          * like parentheses and hyphens, if they exist in the original item.
+         *
+         * **Warning**: Entity-based contextual Outlook add-ins are now retired. However, regular expression rules are still supported.
+         * We recommend updating your contextual add-in to use regular expression rules as an alternative solution.
+         * For guidance on how to implement these rules, see
+         * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | Contextual Outlook add-ins}.
+         *
+         * @deprecated Use {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | regular expression rules} instead.
          */
         phoneString: string;
         /**
          * Gets the text that was identified in an item as a phone number.
+         *
+         * **Warning**: Entity-based contextual Outlook add-ins are now retired. However, regular expression rules are still supported.
+         * We recommend updating your contextual add-in to use regular expression rules as an alternative solution.
+         * For guidance on how to implement these rules, see
+         * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | Contextual Outlook add-ins}.
+         *
+         * @deprecated Use {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | regular expression rules} instead.
          */
         originalPhoneString: string;
         /**
          * Gets a string that identifies the type of phone number: Home, Work, Mobile, Unspecified.
+         *
+         * **Warning**: Entity-based contextual Outlook add-ins are now retired. However, regular expression rules are still supported.
+         * We recommend updating your contextual add-in to use regular expression rules as an alternative solution.
+         * For guidance on how to implement these rules, see
+         * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | Contextual Outlook add-ins}.
+         *
+         * @deprecated Use {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | regular expression rules} instead.
          */
         type: string;
     }
@@ -21141,7 +21052,14 @@ declare namespace Office {
      * Represents a suggested task identified in an item. Read mode only.
      *
      * The list of tasks suggested in an email message is returned in the `taskSuggestions` property of the {@link Office.Entities | Entities} object
-     * that is returned when the `getEntities` or `getEntitiesByType` method is called on the active item.
+     * that's returned when the `getEntities` or `getEntitiesByType` method is called on the active item.
+     *
+     * **Warning**: Entity-based contextual Outlook add-ins are now retired. However, regular expression rules are still supported.
+     * We recommend updating your contextual add-in to use regular expression rules as an alternative solution.
+     * For guidance on how to implement these rules, see
+     * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | Contextual Outlook add-ins}.
+     *
+     * @deprecated Use {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | regular expression rules} instead.
      *
      * @remarks
      *
@@ -21152,10 +21070,24 @@ declare namespace Office {
     interface TaskSuggestion {
         /**
          * Gets the users that should be assigned a suggested task.
+         *
+         * **Warning**: Entity-based contextual Outlook add-ins are now retired. However, regular expression rules are still supported.
+         * We recommend updating your contextual add-in to use regular expression rules as an alternative solution.
+         * For guidance on how to implement these rules, see
+         * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | Contextual Outlook add-ins}.
+         *
+         * @deprecated Use {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | regular expression rules} instead.
          */
         assignees: EmailUser[];
         /**
          * Gets the text of an item that was identified as a task suggestion.
+         *
+         * **Warning**: Entity-based contextual Outlook add-ins are now retired. However, regular expression rules are still supported.
+         * We recommend updating your contextual add-in to use regular expression rules as an alternative solution.
+         * For guidance on how to implement these rules, see
+         * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | Contextual Outlook add-ins}.
+         *
+         * @deprecated Use {@link https://learn.microsoft.com/office/dev/add-ins/outlook/contextual-outlook-add-ins | regular expression rules} instead.
          */
         taskString: string;
     }

office-js-preview/package.json CHANGED Viewed

@@ -1,6 +1,6 @@
 {
     "name": "@types/office-js-preview",
-    "version": "1.0.484",
+    "version": "1.0.486",
     "description": "TypeScript definitions for office-js-preview",
     "homepage": "https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/office-js-preview",
     "license": "MIT",
@@ -45,7 +45,7 @@
     },
     "scripts": {},
     "dependencies": {},
-    "typesPublisherContentHash": "a16b5de40e6ef49014c9fbacf7076ebc3752efa0a1425f8a4a8b807f812978f6",
+    "typesPublisherContentHash": "fd6a9fdf302f93bb3ea5190802f0436fd3586db2768d8e91a2dd3648ea6414f3",
     "typeScriptVersion": "4.8",
     "nonNpm": true
 }