diff --git a/docs/concepts/add-in-development-best-practices.md b/docs/concepts/add-in-development-best-practices.md index 1db227ce48..0674c288e7 100644 --- a/docs/concepts/add-in-development-best-practices.md +++ b/docs/concepts/add-in-development-best-practices.md @@ -1,4 +1,4 @@ ---- +--- title: Best practices for developing Office Add-ins description: Apply the best practices when developing Office Add-ins. ms.topic: best-practice @@ -23,11 +23,11 @@ Build add-ins that help users complete tasks quickly and efficiently. Focus on s Make sure users understand your add-in's value immediately by [creating an engaging first-run experience](#create-an-engaging-first-run-experience). -When you're ready to promote your add-in, learn how to create an [effective AppSource listing](/partner-center/marketplace-offers/create-effective-office-store-listings). +When you're ready to promote your add-in, learn how to create an [effective Microsoft Marketplace listing](/partner-center/marketplace-offers/create-effective-office-store-listings). - Make your add-in's benefits clear in the title and description. Don't rely only on your brand to communicate what your add-in does. - Ensure your add-in provides sufficient value to justify users' investment. It shouldn't be just a simple utility or have limited scope. -- [!INCLUDE [AppSource enterprise info](../includes/appsource-enterprise.md)] +- [!INCLUDE [Microsoft Marketplace enterprise info](../includes/appsource-enterprise.md)] ## Create an engaging first-run experience @@ -131,27 +131,27 @@ Performance directly impacts user satisfaction. Follow these guidelines to keep Ready to share your add-in with the world? Here's how to get started. -- **Create a Partner Center account.** This process can take time, so if you plan to publish to AppSource, start early. See [Partner Center account](/partner-center/marketplace-offers/open-a-developer-account). +- **Create a Partner Center account.** This process can take time, so if you plan to publish to Microsoft Marketplace, start early. See [Partner Center account](/partner-center/marketplace-offers/open-a-developer-account). -- **Create an effective AppSource listing.** Follow these tips: +- **Create an effective Microsoft Marketplace listing.** Follow these tips: - Use succinct, descriptive titles (128 characters or fewer). - Write short, compelling descriptions that answer "What problem does this add-in solve?" - Convey your add-in's value proposition clearly in the title and description. Don't rely only on your brand. - Learn more about [creating effective AppSource listings](/partner-center/marketplace-offers/create-effective-office-store-listings). + Learn more about [creating effective Microsoft Marketplace listings](/partner-center/marketplace-offers/create-effective-office-store-listings). -- **Publish to AppSource.** Follow the AppSource [prepublish checklist](/partner-center/marketplace-offers/checklist) and [submission guide](/partner-center/marketplace-offers/add-in-submission-guide). Make sure to: +- **Publish to Microsoft Marketplace.** Follow the Microsoft Marketplace [prepublish checklist](/partner-center/marketplace-offers/checklist) and [submission guide](/partner-center/marketplace-offers/add-in-submission-guide). Make sure to: - Test your add-in thoroughly on all supported operating systems, browsers, and devices. - Provide detailed testing instructions and resources for certification reviewers. -- **Create a website.** Help users discover your add-in outside of AppSource. +- **Create a website.** Help users discover your add-in outside of Microsoft Marketplace. - **Promote your add-in** from your website. See [how to promote your add-in](/partner-center/marketplace-offers/promote-your-office-store-solution). > [!IMPORTANT] -> [!INCLUDE [AppSource enterprise info](../includes/appsource-enterprise.md)] +> [!INCLUDE [Microsoft Marketplace enterprise info](../includes/appsource-enterprise.md)] ## Support older Microsoft webviews and Office versions (recommended but not required) diff --git a/docs/concepts/browsers-used-by-office-web-add-ins.md b/docs/concepts/browsers-used-by-office-web-add-ins.md index e540de41a4..16e6563a6e 100644 --- a/docs/concepts/browsers-used-by-office-web-add-ins.md +++ b/docs/concepts/browsers-used-by-office-web-add-ins.md @@ -23,8 +23,8 @@ Which webview is used depends on: > > We recommend (but don't require) that you continue to support these combinations, at least in a minimal way, by providing users of your add-in a graceful failure message when your add-in is launched in one of these webviews. Keep these additional points in mind: > -> - Office on the web no longer opens in Internet Explorer or Microsoft Edge Legacy. Consequently, [AppSource](/partner-center/marketplace-offers/submit-to-appsource-via-partner-center) doesn't test add-ins in Office on these web browsers. -> - AppSource still tests for combinations of platform and Office *desktop* versions that use Trident or EdgeHTML. However, it only issues a warning when the add-in doesn't support these webviews; the add-in isn't rejected by AppSource. +> - Office on the web no longer opens in Internet Explorer or Microsoft Edge Legacy. Consequently, [Microsoft Marketplace](/partner-center/marketplace-offers/submit-to-appsource-via-partner-center) doesn't test add-ins in Office on these web browsers. +> - Microsoft Marketplace still tests for combinations of platform and Office *desktop* versions that use Trident or EdgeHTML. However, it only issues a warning when the add-in doesn't support these webviews; the add-in isn't rejected by Microsoft Marketplace. > - The [Script Lab tool](../overview/explore-with-script-lab.md) no longer supports Trident. > > For more information about supporting Trident or EdgeHTML, including configuring a graceful failure message on your add-in, see [Support older Microsoft webviews and Office versions](../develop/support-ie-11.md). diff --git a/docs/concepts/duplicate-legacy-metaos-add-ins.md b/docs/concepts/duplicate-legacy-metaos-add-ins.md index fa7360d13c..4c61dc89da 100644 --- a/docs/concepts/duplicate-legacy-metaos-add-ins.md +++ b/docs/concepts/duplicate-legacy-metaos-add-ins.md @@ -25,11 +25,11 @@ Use the following steps. 1. Open the extension object in the [`"extensions"`](/microsoft-365/extensibility/schema/root#extensions) array. 1. Create an [`"alternates"`](/microsoft-365/extensibility/schema/element-extensions#alternates) array property, if there isn’t one already. 1. In the `"alternates"` array, create an alternate object that has a [`"hide"`](/microsoft-365/extensibility/schema/extension-alternate-versions-array#hide) property. -1. If the existing add-in is marketed through AppSource, give the `"hide"` object a [`"storeOfficeAddin"`](/microsoft-365/extensibility/schema/extension-alternate-versions-array-hide#storeofficeaddin) property. Otherwise, skip to step 6. +1. If the existing add-in is marketed through Microsoft Marketplace, give the `"hide"` object a [`"storeOfficeAddin"`](/microsoft-365/extensibility/schema/extension-alternate-versions-array-hide#storeofficeaddin) property. Otherwise, skip to step 6. 1. Give the `"storeOfficeAddin"` object two properties: - An `"officeAddinId"` with the GUID of the old add-in as its value. - - An `"assetId"` with the AppSource asset ID as its value. + - An `"assetId"` with the Microsoft Marketplace asset ID as its value. The following is an example: @@ -59,7 +59,7 @@ Use the following steps. > - The asset ID of the add-in in your unified manifest must match with an existing add-in that has been published by your seller account on Partner Center. If the asset ID of the add-in that you have linked in your unified manifest doesn't match an existing offer published by your seller account, the unified manifest submission will fail. You'll need to update the manifest to use the correct add-in asset ID and re-submit the unified manifest. > - An existing add-in can only be hidden by a single unified manifest. At this time, you may not use multiple unified manifests to hide the same add-in. If you try to hide an already linked add-in using a different unified manifest, the submission will fail. You'll need to remove the linking and re-submit the unified manifest. -1. If the old add-in isn't distributed through AppSource, then give the `"hide"` object a [`"customOfficeAddin"`](/microsoft-365/extensibility/schema/extension-alternate-versions-array-hide-custom-office-addin) property. +1. If the old add-in isn't distributed through Microsoft Marketplace, then give the `"hide"` object a [`"customOfficeAddin"`](/microsoft-365/extensibility/schema/extension-alternate-versions-array-hide-custom-office-addin) property. 1. Give the `"customOfficeAddin"` object an `"officeAddinId"` property with the GUID of the old add-in as its value. The following is an example. ```json @@ -82,7 +82,7 @@ Use the following steps. ] ``` -Don't remove the existing add-in from AppSource or the Microsoft 365 Admin Center, or earlier versions of Office will no longer be able to use your add-in. +Don't remove the existing add-in from Microsoft Marketplace or the Microsoft 365 Admin Center, or earlier versions of Office will no longer be able to use your add-in. ## Maintain both versions for the immediate future diff --git a/docs/concepts/privacy-and-security.md b/docs/concepts/privacy-and-security.md index 846b8f4cad..2dffde6f04 100644 --- a/docs/concepts/privacy-and-security.md +++ b/docs/concepts/privacy-and-security.md @@ -52,9 +52,9 @@ In supported web clients, Office Add-ins are hosted in an **iframe** that runs u ![Diagram of the infrastructure that supports Office Add-ins in Office on the web clients.](../images/dk2-agave-overview-03.png) -## Add-in integrity in AppSource +## Add-in integrity in Microsoft Marketplace -You can make your Office Add-ins available to the public by publishing them to AppSource. AppSource enforces the following measures to maintain the integrity of add-ins. +You can make your Office Add-ins available to the public by publishing them to Microsoft Marketplace. Microsoft Marketplace enforces the following measures to maintain the integrity of add-ins. - Requires the host server of an Office Add-in to always use Secure Sockets Layer (SSL) to communicate. @@ -85,7 +85,7 @@ This section describes the protection offered by the Office Add-ins platform fro ### End users' perspective -Office Add-ins are built using web technologies that run in a browser control or **iframe**. Because of this, using add-ins is similar to browsing to web sites on the Internet or intranet. Add-ins can be external to an organization (if you acquire the add-in from AppSource) or internal (if you acquire the add-in from an Exchange Server add-in catalog, SharePoint app catalog, or file share on an organization's network). Add-ins have limited access to the network and most add-ins can read or write to the active document or mail item. The add-in platform applies certain constraints before a user or administrator installs or starts an add-in. But as with any extensibility model, users should be cautious before starting an unknown add-in. +Office Add-ins are built using web technologies that run in a browser control or **iframe**. Because of this, using add-ins is similar to browsing to web sites on the Internet or intranet. Add-ins can be external to an organization (if you acquire the add-in from Microsoft Marketplace) or internal (if you acquire the add-in from an Exchange Server add-in catalog, SharePoint app catalog, or file share on an organization's network). Add-ins have limited access to the network and most add-ins can read or write to the active document or mail item. The add-in platform applies certain constraints before a user or administrator installs or starts an add-in. But as with any extensibility model, users should be cautious before starting an unknown add-in. > [!NOTE] > Users may see a security prompt to trust the domain the first time an add-in is loaded. This will happen if the add-in's domain host is outside of the domain of Exchange on-premise or Office Online Server. @@ -94,7 +94,7 @@ The add-in platform addresses end users' privacy concerns in the following ways. - Data communicated with the web server that hosts a content, Outlook or task pane add-in as well as communication between the add-in and any web services it uses must be encrypted using the Secure Socket Layer (SSL) protocol. -- Before a user installs an add-in from AppSource, the user can view the privacy policy and requirements of that add-in. In addition, Outlook add-ins that interact with users' mailboxes surface the specific permissions that they require; the user can review the terms of use, requested permissions and privacy policy before installing an Outlook add-in. +- Before a user installs an add-in from Microsoft Marketplace, the user can view the privacy policy and requirements of that add-in. In addition, Outlook add-ins that interact with users' mailboxes surface the specific permissions that they require; the user can review the terms of use, requested permissions and privacy policy before installing an Outlook add-in. - When sharing a document, users also share add-ins that have been inserted in or associated with that document. If a user opens a document that contains an add-in that the user hasn't used before, the Office client application prompts the user to grant permission for the add-in to run in the document. In an organizational environment, the Office client application also prompts the user if the document comes from an external source. @@ -106,11 +106,11 @@ The add-in platform addresses end users' privacy concerns in the following ways. A user's device capabilities include their camera, geolocation, and microphone. To learn more, see [View, manage, and install add-ins for Excel, PowerPoint, and Word](https://support.microsoft.com/office/16278816-1948-4028-91e5-76dca5380f8d). -- Users can enable or disable the access to AppSource. For content and task pane add-ins, users manage access to trusted add-ins and catalogs from the **Trust Center** on the host Office client (opened from **File** > **Options** > **Trust Center** > **Trust Center Settings** > **Trusted Add-in Catalogs**). +- Users can enable or disable the access to Microsoft Marketplace. For content and task pane add-ins, users manage access to trusted add-ins and catalogs from the **Trust Center** on the host Office client (opened from **File** > **Options** > **Trust Center** > **Trust Center Settings** > **Trusted Add-in Catalogs**). In Outlook, access to manage add-ins depends on the user's Outlook client. To learn more, see [Use add-ins in Outlook](https://support.microsoft.com/office/1ee261f9-49bf-4ba6-b3e2-2ba7bcab64c8). - Administrators can also manage access to AppSource [through the admin center](/microsoft-365/admin/manage/manage-addins-in-the-admin-center). + Administrators can also manage access to Microsoft Marketplace [through the admin center](/microsoft-365/admin/manage/manage-addins-in-the-admin-center). - The design of the add-in platform provides security and performance for end users in the following ways. @@ -152,9 +152,9 @@ The following lists some specific PII protection guidelines for you as a develop - Using some applications can reveal PII. Make sure that you securely store data for your users' identity, location, access times, and any other credentials so that data won't become available to other users of the add-in. -- If your add-in is available in AppSource, the AppSource requirement for HTTPS protects PII transmitted between your web server and the client computer or device. However, if you re-transmit that data to other servers, make sure you observe the same level of protection. +- If your add-in is available in Microsoft Marketplace, the requirement for HTTPS protects PII transmitted between your web server and the client computer or device. However, if you re-transmit that data to other servers, make sure you observe the same level of protection. -- If you store users' PII, make sure you reveal that fact, and provide a way for users to inspect and delete it. If you submit your add-in to AppSource, you can outline the data you collect and how it's used in the privacy statement. +- If you store users' PII, make sure you reveal that fact, and provide a way for users to inspect and delete it. If you submit your add-in to Microsoft Marketplace, you can outline the data you collect and how it's used in the privacy statement. ## Developers' permission choices and security practices @@ -315,7 +315,7 @@ Developers should also take note of the following security practices. - Developers shouldn't embed keys that they use to access APIs or services from Microsoft and others (such as Bing, Google, or Facebook) directly in the HTML pages of their add-in. Instead, they should create a custom web service or store the keys in some other form of secure web storage that they can then call to pass the key value to their add-in. -- Developers should do the following when submitting an add-in to AppSource. +- Developers should do the following when submitting an add-in to Microsoft Marketplace. - Host the add-in they are submitting on a web server that supports SSL. - Produce a statement outlining a compliant privacy policy. @@ -325,7 +325,7 @@ Other than resource usage rules, developers for Outlook add-ins should also make ## IT administrators' control -In a corporate setting, IT administrators have ultimate authority over enabling or disabling access to AppSource and any private catalogs. +In a corporate setting, IT administrators have ultimate authority over enabling or disabling access to Microsoft Marketplace and any private catalogs. The management and enforcement of Office settings is done with group policy settings. These are configurable through the [Office Deployment Tool](/deployoffice/overview-office-deployment-tool), in conjunction with the [Office Customization Tool](/deployoffice/admincenter/overview-office-customization-tool). @@ -333,7 +333,7 @@ The management and enforcement of Office settings is done with group policy sett |--------------|-------------| | Allow Unsecure web add-ins and Catalogs | Allows users to run non-secure Office Add-ins, which are Office Add-ins that have webpage or catalog locations that are not SSL-secured (https://) and are not in users' Internet zones. | | Block Web Add-ins | Allows you to prevent users from running Office Add-ins that use web technologies. | -| Block the Office Store | Allows you to prevent users from getting or running Office Add-ins that come from [AppSource](https://appsource.microsoft.com). | +| Block the Office Store | Allows you to prevent users from getting or running Office Add-ins that come from [Microsoft Marketplace](https://marketplace.microsoft.com). | To specify permissions to install and manage Outlook add-ins in an organization that uses Exchange Online, configure administrative and user roles in the Exchange admin center. For more information, see [Specify the administrators and users who can install and manage add-ins for Outlook in Exchange Online](/exchange/clients-and-mobile-in-exchange-online/add-ins-for-outlook/specify-who-can-install-and-manage-add-ins). diff --git a/docs/concepts/requirements-for-running-office-add-ins.md b/docs/concepts/requirements-for-running-office-add-ins.md index 6ddf46c993..29e361c8d3 100644 --- a/docs/concepts/requirements-for-running-office-add-ins.md +++ b/docs/concepts/requirements-for-running-office-add-ins.md @@ -1,4 +1,4 @@ ---- +--- title: Requirements for running Office Add-ins description: Learn about the client and server requirements that an end user needs to run Office Add-ins. ms.date: 08/13/2025 @@ -31,7 +31,7 @@ To test and run an Outlook add-in, the user's Outlook email account must reside - The server must be Exchange 2016 or later. - Exchange Web Services (EWS) must be enabled and must be exposed to the Internet. Many add-ins require EWS to function properly. - The server must have a valid authentication certificate in order for the server to issue valid identity tokens. New installations of Exchange Server include a default authentication certificate. For more information, see [Digital certificates and encryption in Exchange 2016](/Exchange/architecture/client-access/certificates) and [Set-AuthConfig](/powershell/module/exchangepowershell/set-authconfig). -- To access add-ins from [AppSource](https://appsource.microsoft.com/marketplace/apps?product=office), the client access servers must be able to communicate with AppSource. +- To access add-ins from [Microsoft Marketplace](https://marketplace.microsoft.com/marketplace/apps?product=office), the client access servers must be able to communicate with Microsoft Marketplace. > [!NOTE] > POP3 and IMAP email accounts in Outlook don't support Office Add-ins. diff --git a/docs/concepts/resource-limits-and-performance-optimization.md b/docs/concepts/resource-limits-and-performance-optimization.md index 984df00356..119b5a4239 100644 --- a/docs/concepts/resource-limits-and-performance-optimization.md +++ b/docs/concepts/resource-limits-and-performance-optimization.md @@ -1,4 +1,4 @@ ---- +--- title: Resource limits and performance optimization for Office Add-ins description: Learn about the resource limits of the Office Add-in platform, including CPU and memory. ms.date: 09/03/2025 @@ -81,7 +81,7 @@ The following table lists the events that the Telemetry Log tracks for Office Ad |Event ID|Title|Severity|Description| |:-----|:-----|:-----|:-----| |7|Add-in manifest downloaded successfully|*Not applicable*|The manifest of the Office Add-in was successfully loaded and read by the Office application.| -|8|Add-in manifest did not download|Critical|The Office application was unable to load the manifest file for the Office Add-in from the SharePoint catalog, corporate catalog, or AppSource.| +|8|Add-in manifest did not download|Critical|The Office application was unable to load the manifest file for the Office Add-in from the SharePoint catalog, corporate catalog, or Microsoft Marketplace.| |9|Add-in markup could not be parsed|Critical|The Office application loaded the Office Add-in manifest, but could not read the HTML markup of the app.| |10|Add-in used too much CPU|Critical|The Office Add-in used more than 90% of the CPU resources over a finite period of time.| |15|Add-in disabled due to string search time-out|*Not applicable*|Outlook add-ins search the subject line and message of an e-mail to determine whether they should be displayed by using a regular expression. The Outlook add-in listed in the **File** column was disabled by Outlook because it timed out repeatedly while trying to match a regular expression.| diff --git a/docs/design/add-in-commands.md b/docs/design/add-in-commands.md index 7b2a3fbf13..54bf73fca6 100644 --- a/docs/design/add-in-commands.md +++ b/docs/design/add-in-commands.md @@ -1,4 +1,4 @@ ---- +--- title: Basic concepts for add-in commands description: Learn how to add custom ribbon buttons and menu items to Excel, Outlook, PowerPoint, and Word as part of an Office Add-in. ms.date: 09/30/2025 @@ -12,7 +12,7 @@ Add-in commands are UI elements that extend the Office UI and start actions in y > [!NOTE] > -> - SharePoint catalogs don't support add-in commands. You can deploy add-in commands via the [integrated apps portal](/microsoft-365/admin/manage/test-and-deploy-microsoft-365-apps) or [AppSource](/partner-center/marketplace-offers/submit-to-appsource-via-partner-center), or use [sideloading](../testing/test-debug-non-local-server.md) to deploy your add-in command for testing. +> - SharePoint catalogs don't support add-in commands. You can deploy add-in commands via the [integrated apps portal](/microsoft-365/admin/manage/test-and-deploy-microsoft-365-apps) or [Microsoft Marketplace](/partner-center/marketplace-offers/submit-to-appsource-via-partner-center), or use [sideloading](../testing/test-debug-non-local-server.md) to deploy your add-in command for testing. > - Content add-ins don't currently support add-in commands. ## Types of add-in commands @@ -173,7 +173,7 @@ In addition to the recommended object limits, keep the following in mind when co - Implement a dialog to provide users with advanced options. This prevents your add-in from overloading the ribbon with rarely used commands. To learn how to implement a dialog, see [Use the Office dialog API in Office Add-ins](../develop/dialog-api-in-office-add-ins.md). > [!NOTE] -> Add-ins that take up too much space might not pass [AppSource validation](/legal/marketplace/certification-policies). +> Add-ins that take up too much space might not pass [Microsoft Marketplace validation](/legal/marketplace/certification-policies). ## Next steps diff --git a/docs/design/add-in-icons-fresh.md b/docs/design/add-in-icons-fresh.md index 2dc7ce291a..b8a7236be6 100644 --- a/docs/design/add-in-icons-fresh.md +++ b/docs/design/add-in-icons-fresh.md @@ -1,4 +1,4 @@ ---- +--- title: Fresh style icon guidelines for Office Add-ins description: Guidelines for using Fresh style icons in Office Add-ins. ms.date: 08/25/2025 @@ -42,7 +42,7 @@ Office desktop icons are bitmap images. Different sizes will render depending on - 80 px (Required) > [!IMPORTANT] -> For an image that is your add-in's representative icon, see [Create effective listings in AppSource and within Office](/partner-center/marketplace-offers/create-effective-office-store-listings#create-an-icon-for-your-add-in) for size and other requirements. +> For an image that is your add-in's representative icon, see [Create effective listings in Microsoft Marketplace and within Office](/partner-center/marketplace-offers/create-effective-office-store-listings#create-an-icon-for-your-add-in) for size and other requirements. Make sure to redraw your icons for each size rather than shrink them to fit. diff --git a/docs/design/add-in-icons-monoline.md b/docs/design/add-in-icons-monoline.md index ed9bbf56f3..586ed85f6a 100644 --- a/docs/design/add-in-icons-monoline.md +++ b/docs/design/add-in-icons-monoline.md @@ -1,4 +1,4 @@ ---- +--- title: Monoline style icon guidelines for Office Add-ins description: Guidelines for using Monoline style icons in Office Add-ins. ms.date: 02/12/2025 @@ -57,7 +57,7 @@ We recommend that you produce each icon in all these sizes to support high DPI d **16 px, 20 px, 24 px, 32 px, 40 px, 48 px, 64 px, 80 px, 96 px** > [!IMPORTANT] -> For an image that is your add-in's representative icon, see [Create effective listings in AppSource and within Office](/partner-center/marketplace-offers/create-effective-office-store-listings#create-an-icon-for-your-add-in) for size and other requirements. +> For an image that is your add-in's representative icon, see [Create effective listings in Microsoft Marketplace and within Office](/partner-center/marketplace-offers/create-effective-office-store-listings#create-an-icon-for-your-add-in) for size and other requirements. ### Layout diff --git a/docs/design/keyboard-shortcuts.md b/docs/design/keyboard-shortcuts.md index b4fdb7dce2..060934361a 100644 --- a/docs/design/keyboard-shortcuts.md +++ b/docs/design/keyboard-shortcuts.md @@ -120,7 +120,7 @@ If your add-in uses the unified app manifest for Microsoft 365, custom keyboard ``` > [!NOTE] -> If you've defined keyboard shortcuts for an add-in that uses the unified manifest and want to publish it to [AppSource](../publish/publish-office-add-ins-to-appsource.md), you must specify JSON resource files for the custom shortcuts and their localized strings (if applicable) in the manifest. These resource files are used for backward compatibility on platforms that don't directly support the unified manifest. To learn how to configure this in your manifest, see [Support backward compatibility for add-ins with a unified manifest in AppSource](#support-backward-compatibility-for-add-ins-with-a-unified-manifest-in-appsource). +> If you've defined keyboard shortcuts for an add-in that uses the unified manifest and want to publish it to [Microsoft Marketplace](../publish/publish-office-add-ins-to-appsource.md), you must specify JSON resource files for the custom shortcuts and their localized strings (if applicable) in the manifest. These resource files are used for backward compatibility on platforms that don't directly support the unified manifest. To learn how to configure this in your manifest, see [Support backward compatibility for add-ins with a unified manifest in Microsoft Marketplace](#support-backward-compatibility-for-add-ins-with-a-unified-manifest-in-microsoft-marketplace). # [Add-in only manifest](#tab/xmlmanifest) @@ -293,7 +293,7 @@ Guidance on how to localize your keyboard shortcuts varies depending on the type To learn how to localize your custom keyboard shortcuts with the unified app manifest for Microsoft 365, see [Localize strings in your app manifest](/microsoftteams/platform/concepts/build-and-test/apps-localization). > [!NOTE] -> If you've defined keyboard shortcuts for an add-in that uses the unified manifest and want to publish it to [AppSource](../publish/publish-office-add-ins-to-appsource.md), you must specify JSON resource files for the custom shortcuts and their localized strings (if applicable) in the manifest. These resource files are used for backward compatibility on platforms that don't directly support the unified manifest. To learn how to configure this in your manifest, see [Support backward compatibility for add-ins with a unified manifest in AppSource](#support-backward-compatibility-for-add-ins-with-a-unified-manifest-in-appsource). +> If you've defined keyboard shortcuts for an add-in that uses the unified manifest and want to publish it to [Microsoft Marketplace](../publish/publish-office-add-ins-to-appsource.md), you must specify JSON resource files for the custom shortcuts and their localized strings (if applicable) in the manifest. These resource files are used for backward compatibility on platforms that don't directly support the unified manifest. To learn how to configure this in your manifest, see [Support backward compatibility for add-ins with a unified manifest in Microsoft Marketplace](#support-backward-compatibility-for-add-ins-with-a-unified-manifest-in-microsoft-marketplace). # [Add-in only manifest](#tab/xmlmanifest) @@ -455,9 +455,9 @@ if (host === Office.HostType.Excel) { ... ``` -## Support backward compatibility for add-ins with a unified manifest in AppSource +## Support backward compatibility for add-ins with a unified manifest in Microsoft Marketplace -To publish an add-in that uses the unified manifest and implements custom keyboard shortcuts to AppSource, you must specify JSON resource files for the shortcuts and their localized strings (if applicable) in the manifest. This ensures your add-in's keyboard shortcuts and its localized resources work on platforms that don't directly support the unified manifest (for information on supported clients and platforms, see [Office Add-ins with the unified app manifest for Microsoft 365](../develop/unified-manifest-overview.md#client-and-platform-support)). +To publish an add-in that uses the unified manifest and implements custom keyboard shortcuts to Microsoft Marketplace, you must specify JSON resource files for the shortcuts and their localized strings (if applicable) in the manifest. This ensures your add-in's keyboard shortcuts and its localized resources work on platforms that don't directly support the unified manifest (for information on supported clients and platforms, see [Office Add-ins with the unified app manifest for Microsoft 365](../develop/unified-manifest-overview.md#client-and-platform-support)). ### Create JSON resource files diff --git a/docs/develop/add-in-manifests.md b/docs/develop/add-in-manifests.md index a0bd7bf347..2525bf28da 100644 --- a/docs/develop/add-in-manifests.md +++ b/docs/develop/add-in-manifests.md @@ -1,4 +1,4 @@ ---- +--- title: Office Add-ins manifest description: Get an overview of the Office Add-in manifest and its uses. ms.topic: overview @@ -45,11 +45,11 @@ All image URIs, such as those used for [add-in commands](../design/add-in-comman All URLs to code or content files in the add-in should be **SSL-secured (HTTPS)**. [!INCLUDE [HTTPS guidance](../includes/https-guidance.md)] -## Best practices for submitting to AppSource +## Best practices for submitting to Microsoft Marketplace Make sure that the add-in ID is a valid and unique GUID. Various GUID generator tools are available on the web that you can use to create a unique GUID. -Add-ins submitted to AppSource must also include a support URL in the manifest. For more information, see [Validation policies for apps and add-ins submitted to AppSource](/legal/marketplace/certification-policies). +Add-ins submitted to Microsoft Marketplace must also include a support URL in the manifest. For more information, see [Validation policies for apps and add-ins submitted to Microsoft Marketplace](/legal/marketplace/certification-policies). ## Specify domains you want to open in the add-in window diff --git a/docs/develop/authorize-to-microsoft-graph.md b/docs/develop/authorize-to-microsoft-graph.md index 48a0ca24c1..e800982b18 100644 --- a/docs/develop/authorize-to-microsoft-graph.md +++ b/docs/develop/authorize-to-microsoft-graph.md @@ -54,9 +54,9 @@ For examples of detailed walkthroughs and scenarios, see: * [Create an ASP.NET Office Add-in that uses single sign-on](create-sso-office-add-ins-aspnet.md) * [Scenario: Implement single sign-on to your service in an Outlook add-in](../outlook/implement-sso-in-outlook-add-in.md) -## Distributing SSO-enabled add-ins in Microsoft AppSource +## Distributing SSO-enabled add-ins in Microsoft Marketplace -When a Microsoft 365 admin acquires an add-in from [AppSource](https://appsource.microsoft.com), the admin can redistribute it through the [integrated apps portal](/microsoft-365/admin/manage/test-and-deploy-microsoft-365-apps) and grant admin consent to the add-in to access Microsoft Graph scopes. It's also possible, however, for the end user to acquire the add-in directly from AppSource, in which case the user must grant consent to the add-in. This can create a potential performance problem for which we've provided a solution. +When a Microsoft 365 admin acquires an add-in from [Microsoft Marketplace](https://marketplace.microsoft.com), the admin can redistribute it through the [integrated apps portal](/microsoft-365/admin/manage/test-and-deploy-microsoft-365-apps) and grant admin consent to the add-in to access Microsoft Graph scopes. It's also possible, however, for the end user to acquire the add-in directly from Microsoft Marketplace, in which case the user must grant consent to the add-in. This can create a potential performance problem for which we've provided a solution. If your code passes the `allowConsentPrompt` option in the call of `getAccessToken`, like `OfficeRuntime.auth.getAccessToken( { allowConsentPrompt: true } );`, then Office can prompt the user for consent if the Microsoft identity platform reports to Office that consent has not yet been granted to the add-in. However, for security reasons, Office can only prompt the user to consent to the Microsoft Graph `profile` scope. *Office cannot prompt for consent to other Microsoft Graph scopes*, not even `User.Read`. This means that if the user grants consent on the prompt, Office returns an access token. But the attempt to exchange the access token for a new access token with additional Microsoft Graph scopes fails with error AADSTS65001, which means consent (to Microsoft Graph scopes) has not been granted. @@ -65,7 +65,7 @@ If your code passes the `allowConsentPrompt` option in the call of `getAccessTok Your code can, and should, handle this error by falling back to an alternate system of authentication, which prompts the user for consent to Microsoft Graph scopes. For code examples, see [Create a Node.js Office Add-in that uses single sign-on](create-sso-office-add-ins-nodejs.md) and [Create an ASP.NET Office Add-in that uses single sign-on](create-sso-office-add-ins-aspnet.md) and the samples they link to. The entire process requires multiple round trips to the Microsoft identity platform. To avoid this performance penalty, include the `forMSGraphAccess` option in the call of `getAccessToken`; for example, `OfficeRuntime.auth.getAccessToken( { forMSGraphAccess: true } )`. This signals to Office that your add-in needs Microsoft Graph scopes. Office will ask the Microsoft identity platform to verify that consent to Microsoft Graph scopes has already been granted to the add-in. If it has, the access token is returned. If it hasn't, then the call of `getAccessToken` returns error 13012. Your code can handle this error by falling back to an alternate system of authentication immediately, without making a doomed attempt to exchange tokens with the Microsoft identity platform. -As a best practice, always pass `forMSGraphAccess` to `getAccessToken` when your add-in will be distributed in AppSource and needs Microsoft Graph scopes. +As a best practice, always pass `forMSGraphAccess` to `getAccessToken` when your add-in will be distributed in Microsoft Marketplace and needs Microsoft Graph scopes. ## Details on SSO with an Outlook add-in diff --git a/docs/develop/automatically-open-a-task-pane-with-a-document.md b/docs/develop/automatically-open-a-task-pane-with-a-document.md index ee5e2c989b..60180d248e 100644 --- a/docs/develop/automatically-open-a-task-pane-with-a-document.md +++ b/docs/develop/automatically-open-a-task-pane-with-a-document.md @@ -42,7 +42,7 @@ Apply the following best practices when you use the autoopen feature. - Don't use the autoopen feature to artificially increase usage of your add-in. If it doesn't make sense for your add-in to open automatically with certain documents, this feature can annoy users. > [!NOTE] - > If Microsoft detects abuse of the autoopen feature, your add-in might be rejected from AppSource. + > If Microsoft detects abuse of the autoopen feature, your add-in might be rejected from Microsoft Marketplace. - Don't use this feature to pin multiple task panes. You can only set one pane of your add-in to open automatically with a document. @@ -127,7 +127,7 @@ The following example shows how to add the `webextension` part. ```xml - + @@ -143,14 +143,14 @@ The `webextension` part also includes a reference to the store or catalog with a |`storeType` value|`id` value|`store` value|`version` value| |:---------------|:---------------|:---------------|:---------------| -|OMEX (AppSource)|The AppSource asset ID of the add-in (see Note).|The locale of AppSource; for example, "en-us".|The version in the AppSource catalog (see Note).| -|WOPICatalog (partner [WOPI](/microsoft-365/cloud-storage-partner-program/online/) hosts)| The AppSource asset ID of the add-in (see Note). | `"wopicatalog"`. Use this value for add-ins that are published in App Source and are installed in WOPI hosts. For more information, see [Integrating with Office Online](/microsoft-365/cloud-storage-partner-program/online/overview). | The version in the add-in manifest.| +|OMEX (Microsoft Marketplace)|The Microsoft Marketplace asset ID of the add-in (see Note).|The locale of Microsoft Marketplace; for example, "en-us".|The version in the Microsoft Marketplace catalog (see Note).| +|WOPICatalog (partner [WOPI](/microsoft-365/cloud-storage-partner-program/online/) hosts)| The Microsoft Marketplace asset ID of the add-in (see Note). | `"wopicatalog"`. Use this value for add-ins that are published in App Source and are installed in WOPI hosts. For more information, see [Integrating with Office Online](/microsoft-365/cloud-storage-partner-program/online/overview). | The version in the add-in manifest.| |FileSystem (a network share)|The GUID of the add-in in the add-in manifest.|The path of the network share; for example, "\\\\MyComputer\\MySharedFolder".|The version in the add-in manifest.| |EXCatalog (deployment via the Exchange server) |The GUID of the add-in in the add-in manifest.|`"EXCatalog"`. EXCatalog row is the row to use with add-ins that use Centralized Deployment in the Microsoft 365 admin center.|The version in the add-in manifest.| |Registry (System registry)|The GUID of the add-in in the add-in manifest.|`"developer"`|The version in the add-in manifest.| > [!NOTE] -> To find the asset ID and version of an add-in in AppSource, go to the AppSource landing page for the add-in. The asset ID appears in the address bar in the browser. The version is listed in the **Details** section of the page. +> To find the asset ID and version of an add-in in Microsoft Marketplace, go to the Microsoft Marketplace landing page for the add-in. The asset ID appears in the address bar in the browser. The version is listed in the **Details** section of the page. For more information about the webextension markup, see [[MS-OWEXML] 2.2.5. WebExtensionReference](/openspecs/office_standards/ms-owexml/d4081e0b-5711-45de-b708-1dfa1b943ad1). diff --git a/docs/develop/convert-xml-to-json-manifest.md b/docs/develop/convert-xml-to-json-manifest.md index a327e0327a..e554e9ee22 100644 --- a/docs/develop/convert-xml-to-json-manifest.md +++ b/docs/develop/convert-xml-to-json-manifest.md @@ -88,7 +88,7 @@ Review and change, as needed, manifest values in light of the following effects ### Ensure conformity of custom functions configuration -If your add-in has custom functions, then it includes a JSON configuration file. Some requirements for this file weren't always enforced by Office or AppSource in the past, but they are all enforced when the add-in has a unified manifest. Before you convert the manifest, ensure that this JSON file conforms to all requirements. For more information, see [Custom functions naming and localization](../excel/custom-functions-naming.md) and [Manually create JSON metadata for custom functions](../excel/custom-functions-json.md) +If your add-in has custom functions, then it includes a JSON configuration file. Some requirements for this file weren't always enforced by Office or Microsoft Marketplace in the past, but they are all enforced when the add-in has a unified manifest. Before you convert the manifest, ensure that this JSON file conforms to all requirements. For more information, see [Custom functions naming and localization](../excel/custom-functions-naming.md) and [Manually create JSON metadata for custom functions](../excel/custom-functions-json.md) In particualar, note that [all function names and function ids must have at least 3 characters](../excel/custom-functions-naming.md#custom-functions-naming-guidelines) and that [each function object must have a "result" property](../excel/custom-functions-json.md#metadata-reference). diff --git a/docs/develop/create-sso-office-add-ins-aspnet.md b/docs/develop/create-sso-office-add-ins-aspnet.md index 67841d1caa..430ab01237 100644 --- a/docs/develop/create-sso-office-add-ins-aspnet.md +++ b/docs/develop/create-sso-office-add-ins-aspnet.md @@ -69,7 +69,7 @@ Use the following values for placeholders for the subsequent app registration st 1. Replace the placeholder "Enter_client_ID_here" _in both places_ in the markup with the **Application ID** that you copied when you created the **Office-Add-in-ASPNET-SSO** app registration. This is the same ID you used for the application ID in the appsettings.json file. > [!NOTE] - > The `` value is the **Application ID URI** you set when you registered the add-in. The `` section is used only to generate a consent dialog box if the add-in is sold through AppSource. + > The `` value is the **Application ID URI** you set when you registered the add-in. The `` section is used only to generate a consent dialog box if the add-in is sold through Microsoft Marketplace. 1. Save and close the manifest file. diff --git a/docs/develop/create-sso-office-add-ins-nodejs.md b/docs/develop/create-sso-office-add-ins-nodejs.md index 555b14654b..a7e5ef528e 100644 --- a/docs/develop/create-sso-office-add-ins-nodejs.md +++ b/docs/develop/create-sso-office-add-ins-nodejs.md @@ -88,7 +88,7 @@ Use the following values for placeholders for the subsequent app registration st 1. Replace the placeholder "$app-id-guid$" _in both places_ in the markup with the **Application ID** that you copied when you created the **Office-Add-in-NodeJS-SSO** app registration. The "$" symbols are not part of the ID, so don't include them. This is the same ID you used for the CLIENT_ID in the .ENV file. > [!NOTE] - > The `` value is the **Application ID URI** you set when you registered the add-in. The `` section is used only to generate a consent dialog box if the add-in is sold through AppSource. + > The `` value is the **Application ID URI** you set when you registered the add-in. The `` section is used only to generate a consent dialog box if the add-in is sold through Microsoft Marketplace. 1. Open the `\public\javascripts\fallback-msal\authConfig.js` file. Replace the placeholder "$app-id-guid$" with the application ID that you saved from the **Office-Add-in-NodeJS-SSO** app registration you created previously. diff --git a/docs/develop/develop-office-add-ins-for-the-ipad.md b/docs/develop/develop-office-add-ins-for-the-ipad.md index 29e8c5ab91..975fc7c8f3 100644 --- a/docs/develop/develop-office-add-ins-for-the-ipad.md +++ b/docs/develop/develop-office-add-ins-for-the-ipad.md @@ -1,4 +1,4 @@ ---- +--- title: Special requirements for add-ins on the iPad description: Learn some requirements for creating an Office Add-in that runs on an iPad. ms.topic: best-practice @@ -8,20 +8,20 @@ ms.localizationpriority: medium # Special requirements for add-ins on the iPad -You'll need to make additional considerations if you want to make your add-in available on iPad. If your add-in uses only Office APIs that are supported on iPad, customers can install it on their devices. However, if you're publishing to [AppSource](https://appsource.microsoft.com), there are some additional requirements you'll need to meet. +You'll need to make additional considerations if you want to make your add-in available on iPad. If your add-in uses only Office APIs that are supported on iPad, customers can install it on their devices. However, if you're publishing to [Microsoft Marketplace](https://marketplace.microsoft.com), there are some additional requirements you'll need to meet. For details on API compatibility, see [Specify Office applications and API requirements](../develop/specify-office-hosts-and-api-requirements.md). -## iPad AppSource requirements +## iPad Microsoft Marketplace requirements -Here's what you need to know when submitting your add-in to AppSource for iPad users. +Here's what you need to know when submitting your add-in to Microsoft Marketplace for iPad users. |Task|Description|Resources| |:-----|:-----|:-----| |Apply iOS design best practices.|Make your add-in UI feel native to iOS by following Apple's design guidelines.|[Designing for iOS](https://developer.apple.com/design/human-interface-guidelines/designing-for-ios)| |Make your add-in free.|Your add-in must be free on iPad. Office on iPad is a great way to reach new users who might become customers on other platforms.|[Certification policy 1120.2](/legal/marketplace/certification-policies#11202-mobile-requirements)| |Remove commerce features on iPad.|When running on iPad, your add-in can't include in-app purchases, trial offers, upselling UI, or links to online stores. Your Privacy Policy and Terms of Use pages must also be commerce-free. You can still have commerce on other platforms. Check the [Office.context.commerceAllowed](/javascript/api/office/office.context#office-office-context-commerceallowed-member) property and hide commerce features when it returns `false`.|[Certification policy 1100.3](/legal/marketplace/certification-policies#11003-selling-additional-features)| -|Submit to AppSource correctly.|In Partner Center, go to the **Product setup** page and select **Make my product available on iOS and Android (if applicable)**. You'll also need to provide your Apple developer ID in Account settings. Don't forget to review the [Application Provider Agreement](https://go.microsoft.com/fwlink/?linkid=715691).|[Make your solutions available in AppSource and within Office](/partner-center/marketplace-offers/submit-to-appsource-via-partner-center)| +|Submit to Microsoft Marketplace correctly.|In Partner Center, go to the **Product setup** page and select **Make my product available on iOS and Android (if applicable)**. You'll also need to provide your Apple developer ID in Account settings. Don't forget to review the [Application Provider Agreement](https://go.microsoft.com/fwlink/?linkid=715691).|[Make your solutions available in Microsoft Marketplace and within Office](/partner-center/marketplace-offers/submit-to-appsource-via-partner-center)| ## Detecting iPad devices diff --git a/docs/develop/develop-overview.md b/docs/develop/develop-overview.md index df191a0e07..041822130b 100644 --- a/docs/develop/develop-overview.md +++ b/docs/develop/develop-overview.md @@ -1,4 +1,4 @@ ---- +--- title: Develop Office Add-ins description: An introduction to developing Office Add-ins. ms.topic: overview @@ -86,7 +86,7 @@ An Office Add-in can use the Office JavaScript APIs to interact with content in #### Explore APIs with Script Lab -Script Lab is an add-in that enables you to explore the Office JavaScript API and run code snippets while you're working in an Office program such as Excel or Word. It's available for free via AppSource and is a useful tool to include in your development toolkit as you prototype and verify the functionality you want in your add-in. In Script Lab, you can access a library of built-in samples to quickly try out APIs or even use a sample as the starting point for your own code. +Script Lab is an add-in that enables you to explore the Office JavaScript API and run code snippets while you're working in an Office program such as Excel or Word. It's available for free via Microsoft Marketplace and is a useful tool to include in your development toolkit as you prototype and verify the functionality you want in your add-in. In Script Lab, you can access a library of built-in samples to quickly try out APIs or even use a sample as the starting point for your own code. The following one-minute video shows Script Lab in action. diff --git a/docs/develop/event-based-activation.md b/docs/develop/event-based-activation.md index a09f5a4595..f706e15c56 100644 --- a/docs/develop/event-based-activation.md +++ b/docs/develop/event-based-activation.md @@ -76,7 +76,7 @@ Support for this feature in Outlook was introduced in [requirement set 1.10](/ja > [!NOTE] > 1 Event-based add-ins in classic Outlook on Windows require a minimum of Windows 10 Version 1903 (Build 18362) or Windows Server 2019 Version 1903 to run. > -> 2 Add-ins that use the unified manifest for Microsoft 365 aren't directly supported in Outlook on Mac and on mobile devices. To run this type of add-in on Mac and on mobile platforms, the add-in must first be published to [AppSource](https://appsource.microsoft.com/) then deployed in the [Microsoft 365 Admin Center](../publish/publish.md). For more information, see the "Client and platform support" section of [Office Add-ins with the unified app manifest for Microsoft 365](../develop/unified-manifest-overview.md#client-and-platform-support). +> 2 Add-ins that use the unified manifest for Microsoft 365 aren't directly supported in Outlook on Mac and on mobile devices. To run this type of add-in on Mac and on mobile platforms, the add-in must first be published to [Microsoft Marketplace](https://marketplace.microsoft.com/) then deployed in the [Microsoft 365 Admin Center](../publish/publish.md). For more information, see the "Client and platform support" section of [Office Add-ins with the unified app manifest for Microsoft 365](../develop/unified-manifest-overview.md#client-and-platform-support). > > 3 For more information, see [Implement event-based activation in Outlook mobile add-ins](../outlook/mobile-event-based.md). > @@ -92,7 +92,7 @@ Outlook on mobile supports APIs up to Mailbox requirement set 1.5. However, supp As you develop an event-based add-in, be mindful of the following feature behaviors and limitations. -- Event-based add-ins work only when deployed by an administrator. If users install them directly from AppSource or the Office Store, they will not automatically launch (for workarounds to the AppSource limitation, see [AppSource listing options for your event-based add-in](../publish/autolaunch-store-options.md)). Admin deployments are done by uploading the manifest to the Microsoft 365 admin center. +- Event-based add-ins work only when deployed by an administrator. If users install them directly from Microsoft Marketplace or the Office Store, they will not automatically launch (for workarounds to the Microsoft Marketplace limitation, see [Microsoft Marketplace listing options for your event-based add-in](../publish/autolaunch-store-options.md)). Admin deployments are done by uploading the manifest to the Microsoft 365 admin center. - APIs that interact with the UI or display UI elements are not supported for Word, PowerPoint, and Excel on Windows. This is because the event handler runs in a JavaScript-only runtime. For more information, see [Runtimes in Office Add-ins](../testing/runtimes.md). @@ -177,7 +177,7 @@ As you develop your event-based add-in, you may need to troubleshoot issues, suc ## Deploy your add-in -Event-based add-ins are restricted to admin-managed deployments only, even if they're acquired from AppSource. If users acquire the add-in from AppSource or the in-app Office Store, they won't be able to activate the event-based function of the add-in. To learn more about listing your event-based add-in in AppSource, see [AppSource listing options for your event-based add-in](../publish/autolaunch-store-options.md). +Event-based add-ins are restricted to admin-managed deployments only, even if they're acquired from Microsoft Marketplace. If users acquire the add-in from Microsoft Marketplace or the in-app Office Store, they won't be able to activate the event-based function of the add-in. To learn more about listing your event-based add-in in Microsoft Marketplace, see [Microsoft Marketplace listing options for your event-based add-in](../publish/autolaunch-store-options.md). Admin deployments are done by uploading the manifest to the Microsoft 365 admin center. To do so, follow these steps. @@ -198,5 +198,5 @@ Because event-based add-ins are deployed by admins, any change you make to the m - [Troubleshoot event-based and spam-reporting add-ins](../testing/troubleshoot-event-based-and-spam-reporting-add-ins.md) - [Debug event-based and spam-reporting add-ins](../testing/debug-autolaunch.md) -- [AppSource listing options for your event-based add-in](../publish/autolaunch-store-options.md) +- [Microsoft Marketplace listing options for your event-based add-in](../publish/autolaunch-store-options.md) - [Handle OnMessageSend and OnAppointmentSend events in your Outlook add-in with Smart Alerts](../outlook/onmessagesend-onappointmentsend-events.md) diff --git a/docs/develop/loading-the-dom-and-runtime-environment.md b/docs/develop/loading-the-dom-and-runtime-environment.md index 8239e1df1b..4f5102b64c 100644 --- a/docs/develop/loading-the-dom-and-runtime-environment.md +++ b/docs/develop/loading-the-dom-and-runtime-environment.md @@ -1,4 +1,4 @@ ---- +--- title: Loading the DOM and runtime environment description: Load the DOM and Office Add-ins runtime environment. ms.date: 05/20/2023 @@ -20,7 +20,7 @@ The following events occur when a content or task pane add-in starts. 1. The user opens a document that already contains an add-in or inserts an add-in in the document. -2. The Office client application reads the add-in's manifest from AppSource, an app catalog on SharePoint, or the shared folder catalog it originates from. +2. The Office client application reads the add-in's manifest from Microsoft Marketplace, an app catalog on SharePoint, or the shared folder catalog it originates from. 3. The Office client application opens the add-in's HTML page in a webview control. diff --git a/docs/develop/localization.md b/docs/develop/localization.md index 8b51796401..2a466a5f56 100644 --- a/docs/develop/localization.md +++ b/docs/develop/localization.md @@ -1,4 +1,4 @@ ---- +--- title: Localization for Office Add-ins description: Use the Office JavaScript API to determine a locale and display strings based on the locale of the Office application, or to interpret or display data based on the locale of the data. ms.date: 02/12/2025 @@ -84,8 +84,8 @@ Every Office Add-in specifies a [DefaultLocale] element and a locale in its mani |Element|Localization support| |:-----|:-----| -|[Description] |Users in each locale you specify can see a localized description for the add-in in AppSource (or private catalog).
For Outlook add-ins, users can see the description in the Exchange Admin Center (EAC) after installation.| -|[DisplayName] |Users in each locale you specify can see a localized description for the add-in in AppSource (or private catalog).
For Outlook add-ins, users can see the display name as a label for the Outlook add-in button and in the EAC after installation.
For content and task pane add-ins, users can see the display name on the ribbon after installing the add-in.| +|[Description] |Users in each locale you specify can see a localized description for the add-in in Microsoft Marketplace (or private catalog).
For Outlook add-ins, users can see the description in the Exchange Admin Center (EAC) after installation.| +|[DisplayName] |Users in each locale you specify can see a localized description for the add-in in Microsoft Marketplace (or private catalog).
For Outlook add-ins, users can see the display name as a label for the Outlook add-in button and in the EAC after installation.
For content and task pane add-ins, users can see the display name on the ribbon after installing the add-in.| |[IconUrl] |The icon image is optional. You can use the same override technique to specify a certain image for a specific culture. If you use and localize an icon, users in each locale you specify can see a localized icon image for the add-in.
For Outlook add-ins, users can see the icon in the EAC after installing the add-in.
For content and task pane add-ins, users can see the icon on the ribbon after installing the add-in.| |[HighResolutionIconUrl] **Important:** This element is available only when using add-in manifest version 1.1.|The high resolution icon image is optional but if it is specified, it must occur after the [IconUrl] element. When [HighResolutionIconUrl] is specified, and the add-in is installed on a device that supports high dpi resolution, the [HighResolutionIconUrl] value is used instead of the value for [IconUrl].
You can use the same override technique to specify a certain image for a specific culture. If you use and localize an icon, users in each locale you specify can see a localized icon image for the add-in.
For Outlook add-ins, users can see the icon in the EAC after installing the add-in.
For content and task pane add-ins, users can see the icon on the ribbon after installing the add-in.| |[Resources] **Important:** This element is available only when using add-in manifest version 1.1. |Users in each locale you specify can see string and icon resources that you specifically create for the add-in for that locale. | 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 ab27784b70..ebac7de3b0 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,4 +1,4 @@ ---- +--- 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: 07/21/2025 @@ -128,9 +128,9 @@ 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. -### AppSource acquisition of an Office Add-in +### Microsoft Marketplace acquisition of an Office Add-in -If a user acquires the Office Add-in from AppSource and the equivalent Windows-only add-in is already installed, then Office will: +If a user acquires the Office Add-in from Microsoft Marketplace and the equivalent Windows-only add-in is already installed, then Office will: 1. Install the Office Add-in. 2. Hide the Office Add-in UI on the ribbon. diff --git a/docs/develop/platform-specific-requirement-sets.md b/docs/develop/platform-specific-requirement-sets.md index a1f0ec7210..2cf891ec7a 100644 --- a/docs/develop/platform-specific-requirement-sets.md +++ b/docs/develop/platform-specific-requirement-sets.md @@ -1,4 +1,4 @@ ---- +--- title: Understanding platform-specific requirement sets description: Understand and learn how to use platform-specific requirement sets. ms.topic: how-to @@ -46,7 +46,7 @@ When you note a requirement set in the [Set element](/javascript/api/manifest/se When you declare a platform-specific requirement set, your add-in activates only when it's run in Office on that platform. For example, if you have the WordApiDesktop 1.1 requirement set in your manifest, your add-in will only activate in Word on Windows and on Mac. -Keep in mind that in the case where the APIs become supported cross-platform, you'll need to update your add-in manifest to add a cross-platform requirement set and remove the platform-specific requirement set. If your add-in is available in AppSource or the Office store, you'll need to resubmit it for validation. +Keep in mind that in the case where the APIs become supported cross-platform, you'll need to update your add-in manifest to add a cross-platform requirement set and remove the platform-specific requirement set. If your add-in is available in Microsoft Marketplace, you'll need to resubmit it for validation. ### Code @@ -72,13 +72,13 @@ if (Office.context.document.setSelectedDataAsync) } ``` -## Notify customers on AppSource +## Notify customers on Microsoft Marketplace -If your add-in is in AppSource or the Office store, be sure to notify customers about any platform-specific behavior. +If your add-in is in Microsoft Marketplace or the Office store, be sure to notify customers about any platform-specific behavior. -**Details + support** > **Products supported** on your add-in's AppSource page should automatically show the appropriate supported platforms based on the requirements you declared in the manifest. +**Details + support** > **Products supported** on your add-in's Microsoft Marketplace page should automatically show the appropriate supported platforms based on the requirements you declared in the manifest. -However, if your add-in is supported cross-platform but you also implemented platform-specific behaviors, you should point out those feature differences in the **Overview** section on your add-in's AppSource page. +However, if your add-in is supported cross-platform but you also implemented platform-specific behaviors, you should point out those feature differences in the **Overview** section on your add-in's Microsoft Marketplace page. ## Exceptions diff --git a/docs/develop/referencing-the-javascript-api-for-office-library-from-its-cdn.md b/docs/develop/referencing-the-javascript-api-for-office-library-from-its-cdn.md index 280d911d10..a6a88570fc 100644 --- a/docs/develop/referencing-the-javascript-api-for-office-library-from-its-cdn.md +++ b/docs/develop/referencing-the-javascript-api-for-office-library-from-its-cdn.md @@ -1,4 +1,4 @@ ---- +--- title: Referencing the Office JavaScript API library description: Learn how to reference the Office JavaScript API library and type definitions in your add-in. ms.date: 01/14/2025 @@ -50,7 +50,7 @@ Thank you to [@stepper and the Stack Overflow community](https://stackoverflow.c In the previous HTML snippet, the `/1/` in front of `office.js` in the CDN URL specifies the latest incremental release within version 1 of Office.js. Because the Office JavaScript API maintains backward compatibility, the latest release will continue to support API members that were introduced earlier in version 1. -If you plan to publish your Office Add-in from AppSource, you must use this CDN reference. Local references are only appropriate for internal, development, and debugging scenarios. +If you plan to publish your Office Add-in from Microsoft Marketplace, you must use this CDN reference. Local references are only appropriate for internal, development, and debugging scenarios. > [!NOTE] > To use preview APIs, reference the preview version of the Office JavaScript API library on the CDN: `https://appsforoffice.microsoft.com/lib/beta/hosted/office.js`. diff --git a/docs/develop/requirements-property-unified-manifest.md b/docs/develop/requirements-property-unified-manifest.md index a279b54f22..8cc5fe888d 100644 --- a/docs/develop/requirements-property-unified-manifest.md +++ b/docs/develop/requirements-property-unified-manifest.md @@ -1,4 +1,4 @@ ---- +--- title: Specify Office Add-in requirements in the unified manifest for Microsoft 365 description: Learn how to use requirements to configure on which host and platforms an add-in can be installed and which features are available. ms.date: 04/18/2025 @@ -48,7 +48,7 @@ You can have more than one capability object. The following example shows how to ## Filter features -The "requirements" properties in descendant objects of "extensions" are used to block some features of an add-in while still allowing the add-in to be installed. The implementation of this filtering is done at the source of installation, such as [AppSource](/partner-center/marketplace-offers/submit-to-appsource-via-partner-center) or [Microsoft 365 Admin Center](/office/dev/add-ins/publish/publish). If the version of Office doesn't support the requirements specified for the feature, then the JSON node for the feature is removed from the manifest before it is installed in the Office application. +The "requirements" properties in descendant objects of "extensions" are used to block some features of an add-in while still allowing the add-in to be installed. The implementation of this filtering is done at the source of installation, such as [Microsoft Marketplace](/partner-center/marketplace-offers/submit-to-appsource-via-partner-center) or [Microsoft 365 Admin Center](/office/dev/add-ins/publish/publish). If the version of Office doesn't support the requirements specified for the feature, then the JSON node for the feature is removed from the manifest before it is installed in the Office application. > [!TIP] > Don't include a capability, formFactor, or scope requirement in a descendant object of "extensions" that's *less* restrictive than the corresponding capability, formFactor, or scope requirement in the ancestor "extensions.requirements" property, if there is one. Since the add-in can't be installed on clients that don't meet the ancestor requirement, no feature filtering would occur anyway. For example, if an "extensions.requirements.capabilities" property requires **Mailbox 1.10**, there's no point in requiring **Mailbox 1.9** in any descendant objects. @@ -56,7 +56,7 @@ The "requirements" properties in descendant objects of "extensions" are used to > [!NOTE] > Office Add-ins that use the unified manifest for Microsoft 365 are *directly* supported in Office on the web, in [new Outlook on Windows](https://support.microsoft.com/office/656bb8d9-5a60-49b2-a98b-ba7822bc7627), and in Office on Windows connected to a Microsoft 365 subscription, Version 2304 (Build 16320.00000) or later. > -> When the app package that contains the unified manifest is deployed in [AppSource](https://appsource.microsoft.com/) or the [Microsoft 365 Admin Center](/office/dev/add-ins/publish/publish) then an add-in only manifest is generated from the unified manifest and stored. This add-in only manifest enables the add-in to be installed on platforms that don't directly support the unified manifest, including Office on Mac, Office on mobile, subscription versions of Office on Windows earlier than 2304 (Build 16320.00000), and perpetual versions of Office on Windows. +> When the app package that contains the unified manifest is deployed in [Microsoft Marketplace](https://marketplace.microsoft.com/) or the [Microsoft 365 Admin Center](/office/dev/add-ins/publish/publish) then an add-in only manifest is generated from the unified manifest and stored. This add-in only manifest enables the add-in to be installed on platforms that don't directly support the unified manifest, including Office on Mac, Office on mobile, subscription versions of Office on Windows earlier than 2304 (Build 16320.00000), and perpetual versions of Office on Windows. > > Feature filtering is less fine-grained in the add-in only manifest. As a result, on platforms that don't directly support the unified manifest, adding a "requirements" subproperty to *any* child of "extensions" is effectively the same as adding that same "requirements" subproperty to *all* the children of "extensions" with one possible exception. So, on these platforms *none* of the features that are configured in these child properties of "extensions" will be available on platform and version combinations that don't meet the specified requirements. The exception is the "extensions.alternates" property. If this property is present, the alternates feature will be filtered in or out based only on its own "requirements" subproperty (if any), not on the "requirements" subproperties of any other child properties of "extensions". diff --git a/docs/develop/sso-in-office-add-ins.md b/docs/develop/sso-in-office-add-ins.md index 04c99902d5..e627b43cef 100644 --- a/docs/develop/sso-in-office-add-ins.md +++ b/docs/develop/sso-in-office-add-ins.md @@ -114,7 +114,7 @@ The following is an example of the markup. > If your add-in is deployed by one or more admins to their organizations, adding new scopes to the manifest will require the admin to consent to the updates. Users will be blocked from the add-in until consent is granted. > [!NOTE] -> If you don't follow the format requirements in the manifest for SSO, your add-in will be rejected from AppSource until it meets the required format. +> If you don't follow the format requirements in the manifest for SSO, your add-in will be rejected from Microsoft Marketplace until it meets the required format. --- diff --git a/docs/develop/support-ie-11.md b/docs/develop/support-ie-11.md index 0030651127..fe1f8be134 100644 --- a/docs/develop/support-ie-11.md +++ b/docs/develop/support-ie-11.md @@ -1,4 +1,4 @@ ---- +--- title: Support older Microsoft webviews and Office versions description: Learn how to support support older Microsoft webviews and Office versions in your add-in. ms.date: 01/07/2025 @@ -16,8 +16,8 @@ Office Add-ins are web applications that are displayed inside iframes when runni > > We recommend (but don't require) that you support these combinations, at least in a minimal way, by providing users of your add-in a graceful failure message when your add-in is launched in these webviews. Keep these additional points in mind: > -> - Office on the web no longer opens in Internet Explorer or Microsoft Edge Legacy. Consequently, [AppSource](/partner-center/marketplace-offers/submit-to-appsource-via-partner-center) doesn't test add-ins in Office on the web on these browsers. -> - AppSource still tests for combinations of platform and Office *desktop* versions that use Trident or EdgeHTML. However, it only issues a warning when the add-in doesn't support these webviews; the add-in isn't rejected by AppSource. +> - Office on the web no longer opens in Internet Explorer or Microsoft Edge Legacy. Consequently, [Microsoft Marketplace](/partner-center/marketplace-offers/submit-to-appsource-via-partner-center) doesn't test add-ins in Office on the web on these browsers. +> - Microsoft Marketplace still tests for combinations of platform and Office *desktop* versions that use Trident or EdgeHTML. However, it only issues a warning when the add-in doesn't support these webviews; the add-in isn't rejected by Microsoft Marketplace. > - The [Script Lab tool](../overview/explore-with-script-lab.md) no longer supports Trident. If you plan to support older versions of Windows and Office, your add-in must work in the embeddable browser controls used by these versions. For example, browser controls based on Internet Explorer 11 (IE11) or Microsoft Edge Legacy (EdgeHTML-based). For information about which combinations of Windows and Office use these browser controls, see [Browsers and webview controls used by Office Add-ins](../concepts/browsers-used-by-office-web-add-ins.md). diff --git a/docs/develop/troubleshoot-sso-in-office-add-ins.md b/docs/develop/troubleshoot-sso-in-office-add-ins.md index f70d174820..621eeb4a4f 100644 --- a/docs/develop/troubleshoot-sso-in-office-add-ins.md +++ b/docs/develop/troubleshoot-sso-in-office-add-ins.md @@ -100,7 +100,7 @@ There are several possible causes. - The add-in is running on a platform that does not support the `getAccessToken` API. For example, it isn't supported on iPad. See also [Identity API requirement sets](/javascript/api/requirement-sets/common/identity-api-requirement-sets). - The Office document was opened from the **Files** tab of a Teams channel using the **Edit in Teams** option on the **Open** dropdown menu. The `getAccessToken` API isn't supported in this scenario. -- The `forMSGraphAccess` option was passed in the call to `getAccessToken` and the user obtained the add-in from AppSource. In this scenario, the tenant admin has not granted consent to the add-in for the Microsoft Graph scopes (permissions) that it needs. Recalling `getAccessToken` with the `allowConsentPrompt` will not solve the problem because Office is allowed to prompt the user for consent to only the Microsoft Entra ID `profile` scope. +- The `forMSGraphAccess` option was passed in the call to `getAccessToken` and the user obtained the add-in from Microsoft Marketplace. In this scenario, the tenant admin has not granted consent to the add-in for the Microsoft Graph scopes (permissions) that it needs. Recalling `getAccessToken` with the `allowConsentPrompt` will not solve the problem because Office is allowed to prompt the user for consent to only the Microsoft Entra ID `profile` scope. Your code should fall back to an alternate system of user authentication. diff --git a/docs/develop/unified-manifest-overview.md b/docs/develop/unified-manifest-overview.md index 6d4054be0c..b12b395ecf 100644 --- a/docs/develop/unified-manifest-overview.md +++ b/docs/develop/unified-manifest-overview.md @@ -1,4 +1,4 @@ ---- +--- title: Office Add-ins with the unified app manifest for Microsoft 365 description: Get an overview of the unified app manifest for Microsoft 365 for Office Add-ins and its uses. ms.topic: overview @@ -79,7 +79,7 @@ To override this behavior in desktop platforms, add each domain you want to open Add-ins that use the unified manifest can be installed if the Office platform *directly* supports it. -To run an add-in on platforms that don't directly support the unified manifest, you must publish the add-in to [AppSource](https://appsource.microsoft.com/). Then, deploy the add-in in the [Microsoft 365 admin center](../publish/publish.md). This way, an add-in only manifest is generated from the unified manifest and stored. The add-in only manifest is then used to install the add-in on platforms that don't directly support the unified manifest. +To run an add-in on platforms that don't directly support the unified manifest, you must publish the add-in to [Microsoft Marketplace](https://marketplace.microsoft.com/). Then, deploy the add-in in the [Microsoft 365 admin center](../publish/publish.md). This way, an add-in only manifest is generated from the unified manifest and stored. The add-in only manifest is then used to install the add-in on platforms that don't directly support the unified manifest. The following tables lists which Office platforms directly support add-ins that use the unified manifest. @@ -94,7 +94,7 @@ The following tables lists which Office platforms directly support add-ins that | Office on mobile | Not directly supported | > [!NOTE] -> If you're deploying an add-in in the [Microsoft 365 admin center](../publish/publish.md#integrated-apps-portal-in-the-microsoft-365-admin-center) and require it to run on platforms that don't directly support the unified manifest, the add-in must be a published AppSource add-in. Custom add-ins or line-of-business (LOB) add-ins that use the unified manifest can be deployed in the [Integrated apps portal](/microsoft-365/admin/manage/test-and-deploy-microsoft-365-apps) of the Microsoft 365 admin center, but they won't be installable on Office versions that don't directly support the unified manifest. +> If you're deploying an add-in in the [Microsoft 365 admin center](../publish/publish.md#integrated-apps-portal-in-the-microsoft-365-admin-center) and require it to run on platforms that don't directly support the unified manifest, the add-in must be a published Microsoft Marketplace add-in. Custom add-ins or line-of-business (LOB) add-ins that use the unified manifest can be deployed in the [Integrated apps portal](/microsoft-365/admin/manage/test-and-deploy-microsoft-365-apps) of the Microsoft 365 admin center, but they won't be installable on Office versions that don't directly support the unified manifest. ## Sample unified manifest diff --git a/docs/develop/usability-testing.md b/docs/develop/usability-testing.md index 196041397d..c613b3ca67 100644 --- a/docs/develop/usability-testing.md +++ b/docs/develop/usability-testing.md @@ -1,4 +1,4 @@ ---- +--- title: Usability testing for Office Add-ins description: Learn how to test your add-in design with real users. ms.date: 01/13/2025 @@ -20,7 +20,7 @@ These testing services help you to streamline test plan creation and remove the You need only five participants to uncover most usability issues in your design. Incorporate small tests regularly throughout your development cycle to ensure that your product is user-centered. > [!NOTE] -> We recommend that you test the usability of your add-in across multiple platforms. To [publish your add-in to AppSource](/partner-center/marketplace-offers/submit-to-appsource-via-partner-center), it must work on all [platforms that support the methods that you define](/javascript/api/requirement-sets). +> We recommend that you test the usability of your add-in across multiple platforms. To [publish your add-in to Microsoft Marketplace](/partner-center/marketplace-offers/submit-to-appsource-via-partner-center), it must work on all [platforms that support the methods that you define](/javascript/api/requirement-sets). ## 1. Sign up for a testing service @@ -45,7 +45,7 @@ Research questions define the objectives of your research and guide your test pl It's important to get data on the entire user journey – from discovering your add-in, to installing and using it. Consider research questions that address the following aspects of the add-in user experience. -- Finding your add-in in AppSource +- Finding your add-in in Microsoft Marketplace - Choosing to install your add-in - First-run experience - Ribbon commands diff --git a/docs/develop/xml-manifest-overview.md b/docs/develop/xml-manifest-overview.md index 9e3e2a8670..acdc9f5baf 100644 --- a/docs/develop/xml-manifest-overview.md +++ b/docs/develop/xml-manifest-overview.md @@ -66,7 +66,7 @@ The following table specifies the elements that are required for the three types _\*Added in the Office Add-in Manifest Schema version 1.1._ -_\*\* SupportUrl is only required for add-ins that are distributed through AppSource._ +_\*\* SupportUrl is only required for add-ins that are distributed through Microsoft Marketplace._ diff --git a/docs/excel/excel-add-ins-overview.md b/docs/excel/excel-add-ins-overview.md index f1390dbc19..10405467a8 100644 --- a/docs/excel/excel-add-ins-overview.md +++ b/docs/excel/excel-add-ins-overview.md @@ -1,4 +1,4 @@ ---- +--- title: Excel add-ins overview description: Excel add-in allow you to extend Excel application functionality across multiple platforms including Windows, Mac, iPad, and in a browser. ms.date: 03/21/2023 @@ -23,7 +23,7 @@ The Office Add-ins platform provides the framework and Office.js JavaScript APIs - **Cross-platform support**: Excel add-ins run in Office on the web, Windows, Mac, and iPad. - **Centralized deployment**: Admins can quickly and easily deploy Excel add-ins to users throughout an organization. - **Use of standard web technology**: Create your Excel add-in using familiar web technologies such as HTML, CSS, and JavaScript. -- **Distribution via AppSource**: Share your Excel add-in with a broad audience by publishing it to [AppSource](https://appsource.microsoft.com/marketplace/apps?product=office). +- **Distribution via Microsoft Marketplace**: Share your Excel add-in with a broad audience by publishing it to [Microsoft Marketplace](https://marketplace.microsoft.com/marketplace/apps?product=office). > [!NOTE] > Excel add-ins are different from COM and VSTO add-ins, which are earlier Office integration solutions that run only in Office on Windows. Unlike COM add-ins, Excel add-ins don't require you to install any code on a user's device, or within Excel. @@ -47,7 +47,7 @@ The [manifest](../develop/add-in-manifests.md) is a configuration file that defi - How the add-in integrates with Excel, including any custom UI that the add-in creates (ribbon buttons, context menus, and so on). - Permissions that the add-in requires, such as reading and writing to the document. -To enable end users to install and use an Excel add-in, you must publish its manifest either to AppSource or to an add-ins catalog. For details about publishing to AppSource, see [Make your solutions available in AppSource and within Office](/partner-center/marketplace-offers/submit-to-appsource-via-partner-center). +To enable end users to install and use an Excel add-in, you must publish its manifest either to Microsoft Marketplace or to an add-ins catalog. For details about publishing to Microsoft Marketplace, see [Make your solutions available in Microsoft Marketplace and within Office](/partner-center/marketplace-offers/submit-to-appsource-via-partner-center). ## Capabilities of an Excel add-in diff --git a/docs/excel/pnp-open-in-excel.md b/docs/excel/pnp-open-in-excel.md index 6d249e4373..65efe814f1 100644 --- a/docs/excel/pnp-open-in-excel.md +++ b/docs/excel/pnp-open-in-excel.md @@ -1,4 +1,4 @@ ---- +--- title: Create an Excel spreadsheet from your web page, populate it with data, and embed your Office Add-in description: Create an Excel spreadsheet from your web page, populate it with data, and embed your Office Add-in. ms.date: 01/23/2023 @@ -75,15 +75,15 @@ Much of the `SpreadsheetBuilder` class contains code that was generated by the O The `SpreadsheetBuilder` class also embeds the Script Lab add-in inside the spreadsheet and configures to display when the document is opened. -The **SpreadsheetBuilder.GenerateWebExtensionPart1Content** method in the **SpreadsheetBuilder.cs** file sets the reference to the ID of Script Lab in Microsoft AppSource: +The **SpreadsheetBuilder.GenerateWebExtensionPart1Content** method in the **SpreadsheetBuilder.cs** file sets the reference to the ID of Script Lab in Microsoft Marketplace: ```csharp We.WebExtensionStoreReference webExtensionStoreReference1 = new We.WebExtensionStoreReference() { Id = "wa104380862", Version = "1.1.0.0", Store = "en-US", StoreType = "OMEX" }; ``` -- The **StoreType** value is "OMEX", an alias for Microsoft AppSource. -- The **Store** value is "en-US" found in the Microsoft AppSource culture section for Script Lab. -- The **Id** value is the Microsoft AppSource asset ID for Script Lab. +- The **StoreType** value is "OMEX", an alias for Microsoft Marketplace. +- The **Store** value is "en-US" found in the Microsoft Marketplace culture section for Script Lab. +- The **Id** value is the Microsoft Marketplace asset ID for Script Lab. You can change these values to embed your own Office Add-in. This makes it discoverable to the user and increases engagement with your add-in and web services. If your add-in is deployed through central deployment, use the following values instead. diff --git a/docs/includes/appsource-enterprise.md b/docs/includes/appsource-enterprise.md index 827b439bd8..5ab5db3a77 100644 --- a/docs/includes/appsource-enterprise.md +++ b/docs/includes/appsource-enterprise.md @@ -1 +1 @@ -If your add-in targets larger organizations and enterprises, several AppSource requirements differ from those of a general commercial marketplace add-in. For more information, see the [submission FAQ](/partner-center/marketplace-offers/appsource-submission-faq#if-my-app-targets-enterprises--how-does-that-affect-my-submission-). \ No newline at end of file +If your add-in targets larger organizations and enterprises, several Microsoft Marketplace requirements differ from those of a general commercial marketplace add-in. For more information, see the [submission FAQ](/partner-center/marketplace-offers/appsource-submission-faq#if-my-app-targets-enterprises--how-does-that-affect-my-submission-). \ No newline at end of file diff --git a/docs/includes/grant-admin-consent-to-an-add-in-include.md b/docs/includes/grant-admin-consent-to-an-add-in-include.md index 30e75716a8..f640a9e5b9 100644 --- a/docs/includes/grant-admin-consent-to-an-add-in-include.md +++ b/docs/includes/grant-admin-consent-to-an-add-in-include.md @@ -1,6 +1,6 @@ - + > [!NOTE] -> This procedure is only needed when you're developing the add-in. When your production add-in is deployed to AppSource or the Microsoft 365 admin center, users will individually trust it or an admin will consent for the organization at installation. +> This procedure is only needed when you're developing the add-in. When your production add-in is deployed to Microsoft Marketplace or the Microsoft 365 admin center, users will individually trust it or an admin will consent for the organization at installation. Carry out this procedure *after* you have [registered the add-in](../develop/register-sso-add-in-aad-v2.md). (If you have just completed that procedure and the **API permissions** tab of the **$ADD-IN-NAME$** page is open in your browser, you can choose the **Grant admin consent for [tenant name]** button, and then select **Yes** for the confirmation that appears. Skip the rest of this procedure.) diff --git a/docs/includes/https-guidance.md b/docs/includes/https-guidance.md index e7213c0e1b..9c1bae4ad6 100644 --- a/docs/includes/https-guidance.md +++ b/docs/includes/https-guidance.md @@ -1,2 +1,2 @@ -While not strictly required in all add-in scenarios, using an HTTPS endpoint for your add-in is strongly recommended. Add-ins that are not SSL-secured (HTTPS) generate unsecure content warnings and errors during use. If you plan to run your add-in in Office on the web or publish your add-in to AppSource, it must be SSL-secured. If your add-in accesses external data and services, it should be SSL-secured to protect data in transit. Self-signed certificates can be used for development and testing, so long as the certificate is trusted on the local machine. +While not strictly required in all add-in scenarios, using an HTTPS endpoint for your add-in is strongly recommended. Add-ins that are not SSL-secured (HTTPS) generate unsecure content warnings and errors during use. If you plan to run your add-in in Office on the web or publish your add-in to Microsoft Marketplace, it must be SSL-secured. If your add-in accesses external data and services, it should be SSL-secured to protect data in transit. Self-signed certificates can be used for development and testing, so long as the certificate is trusted on the local machine. diff --git a/docs/includes/note-publish-policies.md b/docs/includes/note-publish-policies.md index 2b3370857a..2645ee30e4 100644 --- a/docs/includes/note-publish-policies.md +++ b/docs/includes/note-publish-policies.md @@ -1,2 +1,2 @@ -> [!NOTE] -> If you plan to [publish](../publish/publish.md) your add-in to AppSource and make it available within the Office experience, make sure that you conform to the [Commercial marketplace certification policies](/legal/marketplace/certification-policies). For example, to pass validation, your add-in must work across all platforms that support the methods that you define (for more information, see [section 1120.3](/legal/marketplace/certification-policies#11203-functionality) and the [Office Add-in application and availability page](/javascript/api/requirement-sets)). \ No newline at end of file +> [!NOTE] +> If you plan to [publish](../publish/publish.md) your add-in to Microsoft Marketplace and make it available within the Office experience, make sure that you conform to the [Commercial marketplace certification policies](/legal/marketplace/certification-policies). For example, to pass validation, your add-in must work across all platforms that support the methods that you define (for more information, see [section 1120.3](/legal/marketplace/certification-policies#11203-functionality) and the [Office Add-in application and availability page](/javascript/api/requirement-sets)). \ No newline at end of file diff --git a/docs/includes/outlook-smart-alerts-deployment.md b/docs/includes/outlook-smart-alerts-deployment.md index c48bae21a5..5f40fff467 100644 --- a/docs/includes/outlook-smart-alerts-deployment.md +++ b/docs/includes/outlook-smart-alerts-deployment.md @@ -1,2 +1,2 @@ -> [!IMPORTANT] -> Add-ins that use the [Smart Alerts feature](../outlook/onmessagesend-onappointmentsend-events.md) can only be published to AppSource if the manifest's send mode property is set to the **prompt user** or **soft block** option. If an add-in's send mode property is set to **block**, it can only be deployed by an organization's admin as it will fail AppSource validation. +> [!IMPORTANT] +> Add-ins that use the [Smart Alerts feature](../outlook/onmessagesend-onappointmentsend-events.md) can only be published to Microsoft Marketplace if the manifest's send mode property is set to the **prompt user** or **soft block** option. If an add-in's send mode property is set to **block**, it can only be deployed by an organization's admin as it will fail Microsoft Marketplace validation. diff --git a/docs/includes/outlook-unified-manifest-mac.md b/docs/includes/outlook-unified-manifest-mac.md index 564550218e..4e05d10645 100644 --- a/docs/includes/outlook-unified-manifest-mac.md +++ b/docs/includes/outlook-unified-manifest-mac.md @@ -1,2 +1,2 @@ -> [!NOTE] -> Add-ins that use the unified manifest for Microsoft 365 aren't directly supported in Outlook on Mac. To run this type of add-in on Mac, the add-in must first be published to [AppSource](https://appsource.microsoft.com/) then deployed in the [Microsoft 365 Admin Center](../publish/publish.md). For more information, see [Support for add-ins with the unified manifest for Microsoft 365](../outlook/compare-outlook-add-in-support-in-outlook-for-mac.md#support-for-add-ins-with-the-unified-manifest-for-microsoft-365). +> [!NOTE] +> Add-ins that use the unified manifest for Microsoft 365 aren't directly supported in Outlook on Mac. To run this type of add-in on Mac, the add-in must first be published to [Microsoft Marketplace](https://marketplace.microsoft.com/) then deployed in the [Microsoft 365 Admin Center](../publish/publish.md). For more information, see [Support for add-ins with the unified manifest for Microsoft 365](../outlook/compare-outlook-add-in-support-in-outlook-for-mac.md#support-for-add-ins-with-the-unified-manifest-for-microsoft-365). diff --git a/docs/includes/outlook-unified-manifest-mobile.md b/docs/includes/outlook-unified-manifest-mobile.md index 96f53fc113..20d2da4234 100644 --- a/docs/includes/outlook-unified-manifest-mobile.md +++ b/docs/includes/outlook-unified-manifest-mobile.md @@ -1,2 +1,2 @@ -> [!NOTE] -> Add-ins that use the unified manifest for Microsoft 365 aren't directly supported in Outlook on mobile devices. To run this type of add-in on mobile platforms, the add-in must first be published to [AppSource](https://appsource.microsoft.com/) then deployed in the [Microsoft 365 Admin Center](../publish/publish.md). For more information, see [Support for add-ins with the unified manifest for Microsoft 365](../outlook/outlook-mobile-addins.md#support-for-add-ins-with-the-unified-manifest-for-microsoft-365). +> [!NOTE] +> Add-ins that use the unified manifest for Microsoft 365 aren't directly supported in Outlook on mobile devices. To run this type of add-in on mobile platforms, the add-in must first be published to [Microsoft Marketplace](https://marketplace.microsoft.com/) then deployed in the [Microsoft 365 Admin Center](../publish/publish.md). For more information, see [Support for add-ins with the unified manifest for Microsoft 365](../outlook/outlook-mobile-addins.md#support-for-add-ins-with-the-unified-manifest-for-microsoft-365). diff --git a/docs/includes/outlook-unified-manifest-platforms.md b/docs/includes/outlook-unified-manifest-platforms.md index 1bdc751747..bc5e366576 100644 --- a/docs/includes/outlook-unified-manifest-platforms.md +++ b/docs/includes/outlook-unified-manifest-platforms.md @@ -1,2 +1,2 @@ -> [!NOTE] -> Add-ins that use the unified manifest for Microsoft 365 aren't directly supported in Outlook on Mac and on mobile devices. To run this type of add-in on Mac and on mobile platforms, the add-in must first be published to [AppSource](https://appsource.microsoft.com/) then deployed in the [Microsoft 365 Admin Center](../publish/publish.md). For more information, see the "Client and platform support" section of [Office Add-ins with the unified app manifest for Microsoft 365](../develop/unified-manifest-overview.md#client-and-platform-support). +> [!NOTE] +> Add-ins that use the unified manifest for Microsoft 365 aren't directly supported in Outlook on Mac and on mobile devices. To run this type of add-in on Mac and on mobile platforms, the add-in must first be published to [Microsoft Marketplace](https://marketplace.microsoft.com/) then deployed in the [Microsoft 365 Admin Center](../publish/publish.md). For more information, see the "Client and platform support" section of [Office Add-ins with the unified app manifest for Microsoft 365](../develop/unified-manifest-overview.md#client-and-platform-support). diff --git a/docs/index.yml b/docs/index.yml index 40a1c60fb3..b7935aa8d2 100644 --- a/docs/index.yml +++ b/docs/index.yml @@ -1,4 +1,4 @@ -### YamlMime:Hub +### YamlMime:Hub title: Office Add-ins documentation # < 60 chars summary: Use the Office Add-ins platform to build solutions that extend Office applications and interact with content in Office documents and in Outlook mail messages and calendar items. With Office Add-ins, you can use familiar web technologies such as HTML, CSS, and JavaScript to build solutions that can run in Office on the web, Windows, Mac, and mobile. # < 160 chars @@ -135,7 +135,7 @@ conceptualContent: links: - url: /partner-center/marketplace-offers/open-a-developer-account itemType: overview - text: Create a Partner Center account for AppSource + text: Create a Partner Center account for Microsoft Marketplace - url: /partner-center/marketplace-offers/checklist itemType: overview text: Validate your Office Add-in diff --git a/docs/outlook/apis.md b/docs/outlook/apis.md index a6f77e8ed1..184cbb300d 100644 --- a/docs/outlook/apis.md +++ b/docs/outlook/apis.md @@ -12,7 +12,7 @@ To use APIs in your Outlook add-in, you must specify the location of the Office. ## Office.js library -To interact with the [Outlook add-in API](/javascript/api/outlook), you need to use the JavaScript APIs in Office.js. The content delivery network (CDN) for the library is `https://appsforoffice.microsoft.com/lib/1/hosted/Office.js`. Add-ins submitted to AppSource must reference Office.js by this CDN; they can't use a local reference. +To interact with the [Outlook add-in API](/javascript/api/outlook), you need to use the JavaScript APIs in Office.js. The content delivery network (CDN) for the library is `https://appsforoffice.microsoft.com/lib/1/hosted/Office.js`. Add-ins submitted to Microsoft Marketplace must reference Office.js by this CDN; they can't use a local reference. Reference the CDN in a `