Skip to main content
MacroView branding and product names have changed. Learn more.

Search

How can we help?

Deploying MacroView Mail via Microsoft 365 Admin center

Colin Titmuss
  • Updated

The MacroView Mail App needs to be deployed to an organisation via the Microsoft 365 admin center. 

 

exclamationmark.png Important: To complete the steps in this article, you will need administrator rights to the Microsoft 365 tenant where MacroView Mail will be deployed

Deploy MacroView Mail add-in to M365

  • Open the Microsoft 365 admin center and expand ⚙️Settings in the sidebar. If you can't see ⚙️ Settings, press Show All to make it visible. Then open the Integrated apps section.


mceclip1.png

  • Select Add-ins IntegrateAppsAdd-ins.png

 

  • Select Deploy Add-ins and Next
  • Then Choose from the Store

DeployANewAdd-in.png

  • Enter MacroView into the search field and then initialise a search. 
  • For MacroView Mail select Add. 

SelectAnAdd-in.png

 

Deploy Mail add-in to Users

  • Within Integrated Apps > Add-ins select MacroView Mail. 
  • Once selected you have various options with respect to deploying to users. The two key settings relate to who to assign to while the is the default visibility of it to the respective users.  Choose wisely.  

MailDeployment.png

  • Note: It can take up to 6 hours to deploy the App to users.

 

 

Managing MacroView Mail as an integrated app

  • The add-in will now be visible in the list of Integrated apps page
  • Click on MacroView Mail in the Services & add-ins list to change who has access to the add-in or if you want to remove the add-in.

Sideloading the MacroView mail add-in

An alternative to deploying Office 365 admin center is to sideload the add-in by following these instructions from Microsoft.

https://docs.microsoft.com/en-us/outlook/add-ins/sideload-outlook-add-ins-for-testing

When you sideload an add-in for testing it appears immediately so you don’t have to wait up to 12 hours for it to appear.  The caveat is that the add-in is sideloaded and if your administrator later deploys the same add-in centrally, you will need to manually remove the side-loaded add-in.