This project simplifies the process of distributing Office add-ins by enabling direct installation from a website. We provide a convenient install link and a web widget to enhance user experience and streamline the add-in installation process for better acquisition conversion.

The webpage will show the add-in name, a few details about the add-in functionality for highlight, a dropdown button to install and use the add-in and an image to demo the add-in. This is what the UI looks like.

To better distribute your add-in, you can create an install link to provide your users with the "click and run" experience from your website or anywhere else after you submit your add-in to AppSource. The link will seamlessly bring users to their Web sersion WXP with your add-in automatically launched, so you can directly guide users to try your add-in instead of letting them find it themselves in the Add-in Store.

To create the link, you can reference the link below and configure the parameters in the query string.
{{appName}}:https://api.addins.store.office.com/addinstemplate/{{language}}/{{correlation}}/{{addinId}}/none/{{addinName}}.{{fileFormat}}?omexsrctype=1

1. appName
   This prarmeter controls which Office application would be opened when users click the link.
   · For Word: ms-word
   · For Excel: ms-excel
   · For PowerPoint: ms-powerpoint
   This approach currently supports WXP on Windows and Mac only.
   

2. language
   This is the language of Add-in instructions after opened on Word/Excel/PowerPoint on Windows or Mac.
   Please set as needed. For example: "de-DE", "fr-FR", "it-IT", "ja-JP", "zh-CN".
   

3. correlation
   A GUID for diagnostic purpose. For example, "7bf846ec-905a-5edd-b162-83498f9a8674".
   We strongly recommend you to runtime generate it and make it different per click.
   

4. addInId
   The ID of your add-in published in AppSource
   

5. addInName
   The full name of your add-in in percent encoding format. For example, "space" should be %20, and "-" should be %2D...etc.
   

6. fileFormat
   · For Word: docx
   · For Excel: xlsx
   · For PowerPoint: pptx
   

For example, if we want to create an install link so that users can click and launch Script Lab on Word on Windows, this link should be: ms-word:https://api.addins.store.office.com/addinstemplate/en-US/228a829b-69d7-45f4-a338-c6aba330ec7e/WA104380862/none/Script-Lab--a-Microsoft-Garage-project.docx?omexsrctype=1.

To better distribute your add-in, you can create an install link to provide your users with the "click and run" experience from your website or anywhere else after you submit your add-in to AppSource. The link will seamlessly bring users to their Web sersion WXP with your add-in automatically launched, so you can directly guide users to try your add-in instead of letting them find it themselves in the Add-in Store.

To create the link, you can reference the link below and configure the 3 parameters in the query string.
https://go.microsoft.com/fwlink/?linkid={{linkId}}&templateid={{addInId}}&templatetitle={{addInName}}

1. linkId
   This prarmeter controls which web endpoint would be opened when users click the link.
   · For Word Web: 2261098
   · For Excel Web: 2261819
   · For PowerPoint Web: 2261820
   This approach currently supports WXP Web only.
   

2. addInId
   The ID of your add-in published in AppSource
   

3. addInName
   The full name of your add-in in percent encoding format. For example, "space" should be %20, and "-" should be %2D...etc.
   

For example, for the add-in Script Lab, it supports all Word, Excel, PowerPoint. If we want to create an install link so that users can click and launch Script Lab, this link should be: https://go.microsoft.com/fwlink/?linkid=2261819&templateid=WA104380862&templatetitle=Script%20Lab,%20a%20Microsoft%20Garage%20project Where 2261819 is the Excel Web launch link ID, WA104380862 is Script Lab's add-in id, and "Script%20Lab,%20a%20Microsoft%20Garage%20project" is the full name in percent encoding format.

1. Download the WebWidget/Example-ScriptLab.html file and go to <script> at line 62.

2. Config the paramenters under "Paramenters that need to config" part.
   a. addinId
   This is the unique add-in ID. You can get the correct value by following below steps.
    1) Go to https://appsource.microsoft.com/en-US/ from your browser.
    2) Input your Office add-in name in the search bar on top center of AppSource homepage.
    3) Click your add-in in the seach results.
    4) The add-in information page will be automatically displayed in current tab.
    5) The add-in ID is in the URL.
   For example, if the URL is https://appsource.microsoft.com/en-US/product/office/WA104380862?tab=Overview, then "WA104380862" is the add-in ID that you should input for this parameter in sample code.

   b. addinName
   This is the add-in name. You can get the correct value by following below steps.
    1) Go to the webpage in 2.a.4).
    2) The add-in name is displayed as the title on right of the add-in icon.
   For example, if the webpage is https://appsource.microsoft.com/en-US/product/office/WA104380862?tab=Overview, then "Script Lab, a Microsoft Garage project" is the add-in ID that you should input for this parameter in sample code.

   c. wordOnlineSupported, excelOnlineSupported, powerpointOnlineSupported, wordDesktopSupported, excelDesktopSupported, powerpointDesktopSupported
   This is the Office products that this add-in supports. You can get the correct value by following below steps.
    1) Go to the webpage in 2.a.4).
    2) Click "details + support" tab on the webpage.
    3) Scroll down to "Products supported" section.
     - If "Word on the web" is in the list, then set wordOnlineSupported to true. Otherwise, set it to false.
     - If "Excel on the web" is in the list, then set excelOnlineSupported to true. Otherwise, set it to false.
     - If "PowerPoint on the web" is in the list, then set powerpointOnlineSupported to true. Otherwise, set it to false.
     - If "Word on Windows" or "Word on Mac" is in the list, then set wordDesktopSupported to true. Otherwise, set it to false.
     - If "Excel on Windows" or "Excel on Mac" is in the list, then set excelDesktopSupported to true. Otherwise, set it to false.
     - If "PowerPoint on Windows" or "PowerPoint on Mac" is in the list, then set powerpointDesktopSupported to true. Otherwise, set it to false.
   

   d. language
   The language of the Add-in instructions after opened on Word/Excel/PowerPoint on Windows or Mac. For example, "en-US", "de-DE", "fr-FR", "it-IT", "ja-JP", "zh-CN". Please leave this blank if your Add-in is only available on Office on the Web.

   e. linkAddInAppSource
   If you would like to show the link to Office AppSource, then set linkAddInAppSource to true. Otherwise, set it to false.

   f. addinDetails
   This is for descriptions about the add-in functionalities displayed on the webpage.

   g. demoImage
   This is the image for the add-in that display on the webpage.

3. Save the html file and open by browser. Verify the UI and dropdown links works for your scenario.

4. Make any additional changes to the sample code as you need, and integrete it into your website.

The deeplink can successfully open an Office document with your add-in and the end users can use your add-in for below scenarios only.

1. The add-in is public published, so that it can be found from Office AppSource https://appsource.microsoft.com/.

2. The Office store is enabled for the end user.

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.

When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.

This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party's policies.