Skip Navigation LinksALVAO 11.1Extension modulesALVAO for OutlookDeployment Skip Navigation Links.


Technical requirements

  • ALVAO Service Desk
  • For the AppSource add-in:
    • ALVAO SaaS subscription
    • Microsoft 365 or Exchange Online service
    • Microsoft Outlook web or desktop application
  • For the desktop add-in:
    • Microsoft Outlook desktop application
    • Microsoft .NET Framework 4.8
    • Microsoft Edge WebView2 Runtime
    • Azure Active Directory or Active Directory authentication

Volume-licensed Outlook 2016 and 2019 is not supported. See if you are using the volume-licensed product.

Unless otherwise noted, these are versions of products with valid extended support within the Microsoft product lifecycle at the time the Alvao version was released.

AppSource add-in deployment

Deployment to single user

  1. On the ALVAO Service Desk for Outlook page, click on the Get it now button and follow the instructions. The add-in will deploy to your Microsoft 365 user account.
  2. Setup the add-in in Outlook:
    1. In the case of the Outlook web application, select any e-mail. In the e-mail pane, open the "..." menu and select the ALVAO command.
      In the case of the Outlook desktop application, go to the "..." menu and select the Related request command.
    2. Sign in and enter your ALVAO REST API url.

Deployment across organization

  1. In the Microsoft 365 admin center, login as a user with the Global administrator role.
  2. In Settings - Integrated apps, click on the Get apps command, search for ALVAO and choose the ALVAO Service Desk for Outlook application.
  3. Click on the Get it now button and follow the instructions.
  4. All users must set up the add-in in Outlook the same way as for the single-user deployment.

For more information, see Deploy add-ins in the Microsoft 365 admin center.

Desktop add-in deployment

Deployment on single computer

  1. On your computer, run the installation package AlvaoOutlookAddIn.msi and follow the instructions in the wizard.
  2. Start or restart Outlook.
  3. In Outlook - File - ALVAO Add-in settings enter the Alvao domain name and choose an authentication method.

Deployment accross organization

The add-in can be installed in bulk on multiple computers using Active Directory - Group Policy or another method that allows you to distribute MSI installation packages in bulk. The package must be distributed per user, not per computer.

In order to avoid having to manually set the path to the Alvao REST API on each computer after installing the package, we recommend following the following procedure to first create an installation package transformation and apply it to the original installation package when distributing it.

  1. Install Orca, which is part of e.g. the Windows SDK (C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\bin\Orca.Msi), or you can also find it separately on the Internet.
  2. In Orca, open the original add-in installation package.
  3. From the main menu, use the Transform - New Transform command.
  4. In the table view on the left side, select Property.
  5. In the property overview, use the local menu command Add Row, or use the keyboard shortcut Ctrl+R.
  6. In the Property name, type the name of the property you want to set (e.g. APIURL), see the following table:
    Property name Description
    APIURL Path to REST API. E.g., "".
    UseAadAuth Use Azure Active Directory authentication to access the REST API.
    Values: 1 = use, 0 = do not use.
    The use of this property is mutually exclusive with the use of the UseIntegratedAuth property.
    UseIntegratedAuth Use integrated Windows authentication to access REST API.
    Values: 1 = use, 0 = do not use.
    The use of this property is mutually exclusive with the use of the UseAadAuth property.
    AutoHideTaskPane Show and hide the taskbar automatically.
    Values: 1 = on, 0 = off.
  7. Enter a value for the Value property.
  8. From the main menu, use the Transform - Generate Transform command.
  9. Save the file with the name "AlvaoOutlookAddIn.mst".


Did not find what you were looking for? Ask our technical support team.