Outlook Add-In office 365 deployment > Add-In not visible

Question

I am trying to build my first Outlook Add-In (not VSTO) and followed the tutorial here. After setting up my Office 365 developer license/environment, I finally manage to compile/deploy the Add-In:

3>The manifest file "C:\Users\AAX\source\repos\MyProject\MyProject\bin\Debug\OfficeAppManifests\MyProject.xml" is being deployed to the Exchange server.
3>Successfully registered the mail app on the Exchange Server using service at https://outlook.office365.com/EWS/Exchange.asmx

The compile/deploy action ask me to sign to OWA which I can do but I do not see my Add-In. I try to a track of my Add-in

1. Search under the OWA > Settings > Manage Add-in --> Nothing
2. Search under Exchange Admin > Settings > Add-In --> Nothing
3. I tried to deploy it manually using OWA: All Ok

The workaround 3 does not help as I want to be able to develop build/deploy in a convenient manner. Any hint on why the Visual Studio deploy does not work?

Answer 1

Users can't see add-in? Try one of these:

Use the compatibility checker

• Outputs a status report for each user in your organization, whether they have a valid Office License, if they are set up correctly on Exchange, and if they are ready for centralized deployment. For more information, see deployment compatibility checker.

Check Office version requirements

• The user might be on an older, incompatible version of Office. For add-ins to be deployed the user must have Office ProPlus 2016. You can check this out for any member of your organization. To find out how, see Office 365 reports.
• Alternatively, you can check this manually by going to the application, such as Word, then choose File > Account. Under Product Information, you should see Office 365 ProPlus.

Check Exchange requirements

• Microsoft Exchange stores the add-in manifests within your organization's tenant. The admin deploying add-ins and the users receiving those add-ins must be on a version of Exchange Server that supports OAuth authentication. By default, Exchange Multi-Tenant and Dedicated VNext deployments support OAuth. Exchange Dedicated Legacy and hybrid on-premises deployments can be configured to support OAuth; however, it isn't the default configuration.

• Check with your organization's Exchange admin to find out which configuration is in use. OAuth connectivity per user can be verified by using the Test-OAuthConnectivity PowerShell cmdlet.

See regulations surrounding minors using add-ins

• Please see further information regarding minors using add-ins if applicable.

For more information, please see the following link:

Troubleshoot: User not seeing add-ins

Answer 2

Ok so the solution was to create a fresh account in the O365 developper subscription and to use that account in Visual Studio to deploy the manifest. After doing so the Add-In appears in Outlook and the OWA portal.