diff --git a/docs/develop/make-office-add-in-compatible-with-existing-com-add-in.md b/docs/develop/make-office-add-in-compatible-with-existing-com-add-in.md index 5489db95a..502179420 100644 --- a/docs/develop/make-office-add-in-compatible-with-existing-com-add-in.md +++ b/docs/develop/make-office-add-in-compatible-with-existing-com-add-in.md @@ -1,48 +1,52 @@ --- title: Make your Office Add-in compatible with an existing COM add-in -description: Enable compatibility between your Office Add-in and equivalent COM add-in. -ms.date: 10/28/2025 +description: Enable compatibility between your Office Add-in and similar COM or VSTO add-in. +ms.date: 11/04/2025 ms.localizationpriority: medium --- # Make your Office Add-in compatible with an existing COM or VSTO add-in -If you have an existing COM add-in or VSTO add-in, you can build equivalent functionality in your Office Add-in, thereby enabling your solution to run on other platforms such as Office on the web or Mac. In some cases, your Office Add-in may not be able to provide all of the functionality that's available in the corresponding COM or VSTO add-in. In these situations, your COM or VSTO add-in may provide a better user experience on Windows than the corresponding Office Add-in can provide. +If you have an existing COM add-in or VSTO add-in, you can build nearly equivalent functionality in your Office Web Add-in, thereby enabling your solution to run on other platforms such as in Office on the web or on Mac. In this scenario, the two add-ins are called "equivalent" and you can use the manifest of the Office Web Add-in to control which add-in is available to users on Windows computers (or give users the choice). > [!NOTE] > Because COM and VSTO add-ins can only be installed on Windows, this article refers to COM and VSTO add-ins collectively as "Windows-only" add-ins. -[!INCLUDE [new-outlook-vsto-com-support](../includes/new-outlook-vsto-com-support.md)] - -You can configure your Office Add-in so that when the equivalent Windows-only add-in is already installed on a user's computer, Office on Windows runs the Windows-only add-in instead of the Office Add-in. The Windows-only add-in is called "equivalent" because Office will seamlessly transition between the Windows-only add-in and the Office Add-in according to which one is installed on a user's computer. For more information, see [Equivalent behavior for users](#equivalent-behavior-for-users). As a general rule, add-ins should be treated as equivalent only when the following conditions are met, but there may be exceptional scenarios where add-ins are that don't meet these conditions can be treated as equivalent. + As a general rule, add-ins should be treated as equivalent only when the following conditions are met, but there may be exceptional scenarios where add-ins are that don't meet these conditions can be treated as equivalent. - They're both created by the same developer, typically the entity specified in the [`"developer"`](/microsoft-365/extensibility/schema/root-developer) property of the unified manifest or the [ProviderName](/javascript/api/manifest/providername) element in the add-in only manifest. - They both are designed to be installed on the same Office application or applications, and they address the same workload with mainly overlapping functionality. - They have identical, or highly similar, public names, and user interfaces including control names and icons. -If the Windows-only add-in is ever uninstalled, Office will automatically activate the Office Add-in the next time the host Office application is started. [!INCLUDE [Support note for equivalent add-ins feature](../includes/equivalent-add-in-support-note.md)] -> [!TIP] -> Currently, the Windows-only add-in is always given preference to the Office Add-in. But there's an enhancement to this feature in preview that provides you with a way to reverse this preference or to give the user a choice between the Windows-only add-in and Office Add-in. For more information, see [Option to disable the Windows-only add-in instead (preview)](#option-to-disable-the-windows-only-add-in-instead-preview). +[!INCLUDE [new-outlook-vsto-com-support](../includes/new-outlook-vsto-com-support.md)] + +Because the Windows-only add-in and the Office Add-in may not have exactly the same features, there are three scenarios you need to consider. -## Specify an equivalent Windows-only add-in +- Your Office Add-in does not provide all of the functionality that's available in the corresponding Windows-only add-in. In this scenario, you should [configure the Office add-in to be hidden](#hide-the-office-add-in) on any Windows computer on which the Windows-only add-in is installed. +- Your Office Add-in provides more and better functionality than the corresponding Windows-only add-in. In this scenario, you should [configure the Office Add-in so that it detects the presence of the Windows-only add-in and hides it](#hide-the-windows-only-add-in). +- Neither add-in would be regarded as better than the other by all your users. In this scenario, you should configure the Office Add-in to [give each user on a Windows computer the choice of which add-in is hidden](#give-the-user-the-choice-of-which-add-in-to-use). -### Obtain the ID of the Windows-only add-in +## Obtain the name of the Windows-only add-in -Before you can specify an equivalent Windows-only add-in, you must first identify its name with these steps: +Before you can configure the Office Add-in's manifest, you must first identify the name of the Windows-only add-in in the Windows Registry with these steps: 1. Open Windows Registry Editor on any computer where the Windows-only add-in is installed. 1. Go to **HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\\**\Addins** or **HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\\**\Addins**, where *\* is Excel, Outlook, PowerPoint, or Word. For example, **HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\Excel\Addins**. 1. Copy the name of the registry key associated with the Windows-only add-in you need. Note that the names are case-sensitive. +## Hide the Office Add-in + +You can configure your Office Add-in so that when the equivalent Windows-only add-in is already installed on a user's computer, Office on Windows runs the Windows-only add-in instead of the Office Add-in. If the Windows-only add-in is ever uninstalled, Office will automatically activate the Office Add-in the next time the host Office application is started. If the Windows-only add-in is installed *after* the Office Add-in, then when the Office application is restarted, the Office Add-in will be hidden. For more information, see [Behavior for users when the Office Add-in is hidden](#behavior-for-users-when-the-office-add-in-is-hidden). + ### Configure the manifest > [!IMPORTANT] > Applies to Excel, Outlook, PowerPoint, and Word. -To enable compatibility between your Office Add-in and the Windows-only add-in, identify the equivalent Windows-only add-in in the [manifest](add-in-manifests.md) of your Office Add-in using the name that you obtained in the section [Obtain the ID of the Windows-only add-in](#obtain-the-id-of-the-windows-only-add-in). Then, Office on Windows will use the Windows-only add-in instead of the Office Add-in, if they're both installed. The configuration depends on the type of manifest that is being used. +To enable compatibility between your Office Add-in and the Windows-only add-in, identify the equivalent Windows-only add-in in the [manifest](add-in-manifests.md) of your Office Add-in using the name that you obtained in the section [Obtain the name of the Windows-only add-in](#obtain-the-name-of-the-windows-only-add-in). Then, Office on Windows will use the Windows-only add-in instead of the Office Add-in, if they're both installed. The configuration depends on the type of manifest that is being used. # [Unified manifest for Microsoft 365](#tab/jsonmanifest) @@ -67,9 +71,7 @@ The following example shows the portion of the manifest that specifies a Windows ``` > [!TIP] -> -> - For information about COM add-in and XLL UDF compatibility, see [Make your custom functions compatible with XLL user-defined functions](../excel/make-custom-functions-compatible-with-xll-udf.md). Not applicable for Outlook. -> - If you're unable to specify the `alternates.prefer` property in the manifest of your Outlook web add-in, you must configure Group Policy instead. This only applies to Outlook. For guidance, see [Configure the Group Policy setting for Outlook add-ins](#configure-the-group-policy-setting-for-outlook-add-ins). +> If you're unable to specify the `alternates.prefer` property in the manifest of your Outlook web add-in, you must configure Group Policy instead. This only applies to Outlook. For guidance, see [Configure the Group Policy setting for Outlook add-ins](#configure-the-group-policy-setting-for-outlook-add-ins). # [Add-in only manifest](#tab/xmlmanifest) @@ -100,7 +102,7 @@ The following example shows the portion of the manifest that specifies a Windows > - For information about XLL UDF compatibility with an Excel add-in that contains custom functions, see [Make your custom functions compatible with XLL user-defined functions](../excel/make-custom-functions-compatible-with-xll-udf.md). > - For Outlook only, an admin of a computer can specify an equivalent Windows-only add-in by using a Group Policy. For guidance, see [Configure the Group Policy setting for Outlook add-ins](#configure-the-group-policy-setting-for-outlook-add-ins). -## Configure the Group Policy setting for Outlook add-ins +### Configure the Group Policy setting for Outlook add-ins A user with administrator powers on their computer can configure a Windows-only add-in to be the equivalent of an *Outlook* add-in by using the **Deactivate Outlook web add-ins whose equivalent COM or VSTO add-in is installed** Group Policy setting on the computer. This can be achieved even when the manifest of the Outlook add-in doesn't have the equivalent add-in markup. Then, classic Outlook on Windows uses the Windows-only add-in instead of the Outlook add-in if they're both installed. The following are the steps to configure the policy. @@ -111,12 +113,12 @@ A user with administrator powers on their computer can configure a Windows-only 1. Open the link to edit the policy setting. 1. In the dialog **Outlook web add-ins to deactivate**: 1. Set **Value name** to the ID of the Outlook add-in's manifest. In the add-in only manifest, use the value of the `` element. In the unified manifest, use the value of the `id` property in the root of the manifest. Do *not* add curly braces `{}` around the entry. - 1. Set **Value** to the name of the equivalent Windows-only add-in. See the section [Obtain the ID of the Windows-only add-in](#obtain-the-id-of-the-windows-only-add-in). + 1. Set **Value** to the name of the equivalent Windows-only add-in. See the section [Obtain the name of the Windows-only add-in](#obtain-the-name-of-the-windows-only-add-in). 1. Select **OK** to put the update into effect. ![The "Outlook web add-ins to deactivate" dialog.](../images/outlook-deactivate-gpo-dialog.png) -## Equivalent behavior for users +### Behavior for users when the Office Add-in is hidden When an equivalent Windows-only add-in is specified, Office on Windows won't display your Office Add-in's user interface (UI) if the equivalent Windows-only add-in is installed. But Office only hides the ribbon buttons of the Office Add-in and doesn't prevent installation. Therefore, your Office Add-in will still appear in the following locations within the UI. @@ -128,7 +130,7 @@ When an equivalent Windows-only add-in is specified, Office on Windows won't dis The following scenarios describe what happens depending on how the user acquires the Office Add-in. -### Microsoft Marketplace acquisition of an Office Add-in +#### Microsoft Marketplace acquisition of the Office Add-in If a user acquires the Office Add-in from Microsoft Marketplace and the equivalent Windows-only add-in is already installed, then Office will: @@ -136,7 +138,7 @@ If a user acquires the Office Add-in from Microsoft Marketplace and the equivale 2. Hide the Office Add-in UI on the ribbon. 3. Display a call-out for the user that points out the Windows-only add-in ribbon button. -### Centralized deployment of Office Add-in +#### Centralized deployment of the Office Add-in If an admin deploys the Office Add-in to their tenant using centralized deployment, and the equivalent Windows-only add-in is already installed, the user must restart Office before they'll see any changes. After Office restarts, it will: @@ -144,7 +146,7 @@ If an admin deploys the Office Add-in to their tenant using centralized deployme 2. Hide the Office Add-in UI on the ribbon. 3. Display a call-out for the user that points out the Windows-only add-in ribbon button. -### Document shared with embedded Office Add-in +#### Document shared with the Office Add-in embedded If a user has the Windows-only add-in installed, and then gets a shared document with the embedded Office Add-in, then when they open the document, Office will: @@ -152,58 +154,123 @@ If a user has the Windows-only add-in installed, and then gets a shared document 2. If trusted, the Office Add-in will install. 3. Hide the Office Add-in UI on the ribbon. -## Other Windows-only add-in behavior +### Other Windows-only add-in behavior -### Excel, PowerPoint, Word +#### Excel, PowerPoint, Word If a user uninstalls the equivalent Windows-only add-in, then Office on Windows restores the Office Add-in UI. After you specify an equivalent Windows-only add-in for your Office Add-in, Office stops processing updates for your Office Add-in. To acquire the latest updates for the Office Add-in, the user must first uninstall the Windows-only add-in. -### Outlook +#### Outlook The Windows-only add-in must be connected when Outlook is started in order for the corresponding Outlook add-in to be disabled. If the Windows-only add-in is then disconnected during a subsequent Outlook session, the Outlook add-in will likely remain disabled until Outlook is restarted. -## Option to disable the Windows-only add-in instead (preview) +## Hide the Windows-only add-in + +[!INCLUDE [Support limits on the equivalent add-ins feature](../includes/equivalent-add-ins-limitations.md)] + +### Configure the manifest + +The details to configure this feature depend on which type of manifest is being used by the Office Add-in. + +# [Unified manifest for Microsoft 365](#tab/jsonmanifest) + +To disable the Windows-only add-in, take the following steps. + +1. If it doesn't already exist, create an [`"extensions.alternates.hide.windowsExtensions"`](/microsoft-365/extensibility/schema/extension-alternate-versions-array-hide-windows-extensions) property. +1. Add a child `effect` property to the `windowsExtensions` property and set its value to **disableWithNotification**. +1. Add a child [`"comAddin"`](/microsoft-365/extensibility/schema/extension-alternate-versions-array-hide-windows-extensions-com-addin) property to the `windowsExtensions` property. +1. Add a child `progIds` array property to the `comAddin` property. +1. Add the names of all the Windows-only add-ins that you want to hide to the `progIds` array. For information about how to obtain these names, see [Obtain the name of the Windows-only add-in](#obtain-the-name-of-the-windows-only-add-in). > [!NOTE] -> The feature described in this section is in preview and shouldn't be used in a production add-in. It has the following limitations. -> -> - It's supported only for Excel, PowerPoint, and Word. -> - The minimum Office version that supports the feature is ubscription Office on Windows Version 2506 (Build 19029.20004) +> The string "com" is in the name `comAddin` for historical reasons. In the manifest, the property refers to either COM or VSTO add-ins. Similarly, the term "progIds" is usually associated with only COM add-ins, but names of VSTO add-ins can also be included in the `progIds` array. -Use manifest markup to specify whether the Windows-only add-in or the Office Add-in should be disabled and hidden on a Windows computer when they conflict, or give the user that is installing the Office Add-in the choice of which to use. +The following example shows how the JSON should look. -If you configure the manifest to give the user the choice, then the user sees a dialog similar to the following when they install the Office Add-in. The **Learn more** link in the dialog points to the following help page that provides information to help the user make the decision: [Resolve version conflicts for Office Add-ins](https://support.microsoft.com/office/1632ec51-82ed-4f8e-90b4-a246cbccccde). +```json +"extensions" [ + { + ... + "alternates": [ + { + "hide": { + "windowsExtensions": { + "effect": "disableWithNotification", + "comAddin": { + "progIds": [ + "ContosoAddin" + ] + } + } + } + } + ] + } +] +``` -:::image type="content" source="../images/com-preference-prompt.png" alt-text="A dialog titled 'Contoso JS Add-in Installer'. The first paragraph says 'Contoso JS Add-in has identified the following older versions of the add-in that may cause conflicts:'. Below this paragraph is a single bulleted paragraph that says 'COM Add-in name: Contoso'. Below this is a paragraph that says 'Do you want to disable the older add-in versions? (If you choose No, you will still get the new version if you open Office on Mac or Office on the web.)'. Below this is a link labelled 'Learn more'. Below this are two buttons labelled Yes and No."::: +# [Add-in only manifest](#tab/xmlmanifest) -If the user chooses **Yes** and Office successfully disables and hides the Windows-only add-in, then a dialog similar to the following opens that advises the user to restart the Office application. +To disable the Windows-only add-in, take the following steps. -:::image type="content" source="../images/com-preference-disable-success.png" alt-text="A dialog titled 'The Older Version Add-in Disabled'. The first paragraph says 'The older version of the add-in has been successfully disabled.' Below this a paragraph says 'To ensure the changes take effect, we recommend restarting this Office application. You can continue without restarting, but some updates may not be applied until the next launch.' Below this is an OK button."::: +1. Create an [EquivalentAddins](/javascript/api/manifest/equivalentaddins) as the very last child of the **\** element. +1. Add an **\** child for every Windows-only add-in that you want to hide. +1. For each **\** element, add a **\** and **\** child, *in that order*. +1. Set the **\** element to the name of a Windows-only add-in that you want to hide. For information about how to obtain these names, see [Obtain the name of the Windows-only add-in](#obtain-the-name-of-the-windows-only-add-in). +1. Set the **\** element to "COM". -If the user chooses **Yes** but Office can't disable the Windows-only add-in for any reason, then a dialog similar to the following opens that advises the user to manually disable the Windows-only add-in. + > [!NOTE] + > The **\** value is "COM" for historical reasons, but it refers to either a COM or a VSTO add-in. Similarly, the **\** value can be either the progId of a COM add-in or the name of a VSTO add-in. + +1. Add an **\** element *as the very last* child of the **\** element, and set its value to **DisableWithNotification**. + +The following is an example. + +```xml + + ... + + + ContosoAddin + COM + + DisableWithNotification + + +``` + +--- + +### Behavior for users when the Windows-only add-in is hidden -:::image type="content" source="../images/com-preference-disable-failure.png" alt-text="A dialog titled 'Please Disable Add-in Manually'. The first paragraph says 'The older version of the add-in could not be fully disabled. To complete the process, please manually disable the COM add-in in the Office application where it was installed.' Below this are instructions labelled 'Here's how'. The instructions read as follows '1. Go to File, Options, Add-ins. 2. In the Manage dropdown at the bottom, choose the add-in type and click Go. 3. In the dialog, uncheck the add-in to disable it. 4. Restart the app to apply changes (optional but recommended). Below this is an OK button."::: +When a Windows-only add-in is hidden, Office on Windows won't display its user interface (UI) if the equivalent Office Add-in is installed. A popup dialog notifies the user that this is happening. But Office only hides the Windows-only add-in and doesn't prevent installation. + +## Give the user the choice of which add-in to use + +[!INCLUDE [Support limits on the equivalent add-ins feature](../includes/equivalent-add-ins-limitations.md)] + +### Configure the manifest The details to configure this feature depend on which type of manifest is being used by the Office Add-in. # [Unified manifest for Microsoft 365](#tab/jsonmanifest) -To disable the Windows-only add-in instead of the Office Add-in (or to give the user the choice), use the `alternates.hide.windowsExtensions` and `alternates.hide.windowsExtensions.effect` properties. The two possible values of the `effect` property and their effects are as follows: +To give the user a choice of which add-in to hide, take the following steps. -- **disableWithNotification**: All of the Windows-only add-ins specified in the child `comAddin.progIds` array of the `windowsExtensions` property are disabled and hidden. A popup dialog notifies the user that this is happening. -- **userOptionToDisable**: The user is prompted to choose whether to disable and hide the Windows-only add-ins specified in the child `comAddin.progIds` array of the `windowsExtensions` property or to disable and hide the Office Add-in. +1. If it doesn't already exist, create an [`"extensions.alternates.hide.windowsExtensions"`](/microsoft-365/extensibility/schema/extension-alternate-versions-array-hide-windows-extensions) property. +1. Add a child `effect` property to the `windowsExtensions` property and set its value to **userOptionToDisable**. +1. Add a child [`"comAddin"`](/microsoft-365/extensibility/schema/extension-alternate-versions-array-hide-windows-extensions-com-addin) property to the `windowsExtensions` property. +1. Add a child `progIds` array property to the `comAddin` property. +1. Add the names of all the equivalent Windows-only add-ins to the `progIds` array. For information about how to obtain these names, see [Obtain the name of the Windows-only add-in](#obtain-the-name-of-the-windows-only-add-in). > [!NOTE] > The string "com" is in the name `comAddin` for historical reasons. In the manifest, the property refers to either COM or VSTO add-ins. Similarly, the term "progIds" is usually associated with only COM add-ins, but names of VSTO add-ins can also be included in the `progIds` array. -> [!TIP] -> To force the Windows-only add-in to be enabled and the Office Add-in to be disabled and hidden on the Windows computer, use the `alternates.prefer` property as described in [Configure the manifest](?tabs=jsonmanifest#configure-the-manifest). - -In the following example, the user will be prompted whether to disable the Windows-only add-in "ContosoAddin" or to disable the Office Add-in. +The following example shows how the JSON should look. ```json "extensions" [ @@ -229,15 +296,20 @@ In the following example, the user will be prompted whether to disable the Windo # [Add-in only manifest](#tab/xmlmanifest) -To configure which add-in is used (or give the user the choice), there is an optional **\** child of the **\** element that has one of the following effects when the Office Add-in is installed, depending on which of two possible values it's set to. +To disable the Windows-only add-in, take the following steps. -- **DisableWithNotification**: All of the Windows-only add-ins specified in the child **\** elements will be disabled and hidden. A popup dialog notifies the user that this happening. -- **UserOptionToDisable**: The user is prompted to choose whether to disable and hide the Windows-only add-ins specified in the child **\** elements or to disable and hide the Office Add-in. +1. Create an [EquivalentAddins](/javascript/api/manifest/equivalentaddins) as the very last child of the **\** element. +1. Add an **\** child for every Windows-only add-in that you want to hide. +1. For each **\** element, add a **\** and **\** child, *in that order*. +1. Set the **\** element to the name of a Windows-only add-in whose hidden/visible status you want the user to decide. For information about how to obtain these names, see [Obtain the name of the Windows-only add-in](#obtain-the-name-of-the-windows-only-add-in). +1. Set the **\** element to "COM". -> [!NOTE] -> If the **\** element isn't present, the Windows-only add-in is enabled and the Office Add-in is disabled and hidden on the Windows computer. + > [!NOTE] + > The **\** value is "COM" for historical reasons, but it refers to either a COM or a VSTO add-in. Similarly, the **\** value can be either the progId of a COM add-in or the name of a VSTO add-in. + +1. Add an **\** element *as the very last* child of the **\** element, and set its value to **UserOptionToDisable**. -The following is an example. The **\** element must be after all the **\** elements. +The following is an example. ```xml @@ -252,10 +324,22 @@ The following is an example. The **\** element must be after all the ** ``` -> [!NOTE] -> The **\** value is "COM" for historical reasons, but it refers to either a COM or a VSTO add-in. Similarly, the **\** value can be either the progId of a COM add-in or the name of a VSTO add-in. --- +### Behavior for users when they have the choice of which add-in is hidden + +If you configure the manifest to give the user the choice, then the user sees a dialog similar to the following when they install the Office Add-in. The **Learn more** link in the dialog points to the following help page that provides information to help the user make the decision: [Resolve version conflicts for Office Add-ins](https://support.microsoft.com/office/1632ec51-82ed-4f8e-90b4-a246cbccccde). + +:::image type="content" source="../images/com-preference-prompt.png" alt-text="A dialog titled 'Contoso JS Add-in Installer'. The first paragraph says, 'Contoso JS Add-in has identified the following older versions of the add-in that may cause conflicts:'. Below this paragraph is a single bulleted paragraph that says 'COM Add-in name: Contoso'. Below this is a paragraph that says, 'Do you want to disable the older add-in versions? (If you choose No, you will still get the new version if you open Office on Mac or Office on the web.)'. Below this is a link labelled 'Learn more'. Below this are two buttons labelled Yes and No."::: + +If the user chooses **Yes** and Office successfully disables and hides the Windows-only add-in, then a dialog similar to the following opens that advises the user to restart the Office application. + +:::image type="content" source="../images/com-preference-disable-success.png" alt-text="A dialog titled 'The Older Version Add-in Disabled'. The first paragraph says, 'The older version of the add-in has been successfully disabled.' Below this, a paragraph says, 'To ensure the changes take effect, we recommend restarting this Office application. You can continue without restarting, but some updates may not be applied until the next launch.' Below this is an OK button."::: + +If the user chooses **Yes** but Office can't disable the Windows-only add-in for any reason, then a dialog similar to the following opens that advises the user to manually disable the Windows-only add-in. + +:::image type="content" source="../images/com-preference-disable-failure.png" alt-text="A dialog titled 'Please Disable Add-in Manually'. The first paragraph says, 'The older version of the add-in could not be fully disabled. To complete the process, please manually disable the COM add-in in the Office application where it was installed.' Below this are instructions labelled 'Here's how'. The instructions read as follows: '1. Go to File, Options, Add-ins. 2. In the Manage dropdown at the bottom, choose the add-in type and click Go. 3. In the dialog, uncheck the add-in to disable it. 4. Restart the app to apply changes (optional but recommended).' Below this is an OK button."::: + ## See also - [Make your Custom Functions compatible with XLL User Defined Functions](../excel/make-custom-functions-compatible-with-xll-udf.md) diff --git a/docs/includes/equivalent-add-ins-limitations.md b/docs/includes/equivalent-add-ins-limitations.md new file mode 100644 index 000000000..2f40669f8 --- /dev/null +++ b/docs/includes/equivalent-add-ins-limitations.md @@ -0,0 +1,6 @@ + +> [!NOTE] +> The option described in this section has the following limitations. +> +> - It's supported only for Excel, PowerPoint, and Word. +> - The minimum Office version that supports the feature is subscription Office on Windows Version 2506 (Build 19029.20004).