This document describes how a Planner customer can migrate their Outlook add-in to use the new Nested App authentication, providing better security and greater flexibility (https://learn.microsoft.com/en-gb/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens)
This removes the use of legacy Exchange Online tokens from the Planner Outlook add-in.
Pre-requisites
A Planner-site running at least version 12.1472
You need to be a Planner administrator
You need to be an Azure administrator Web - Chrome & Edge browsers
Supported platforms
Windows Outlook 2019 client and greater
Outlook Web - Chrome & Edge browsers
Mac - Safari (Follow the step-by-step guide and additionally read the Mac Safari Guide)
Mac - Outlook (Follow the step-by-step guide and additionally read the Mac Outlook Guide)
Step-by-step guide
1. In Planner, navigate to Administration » Integrations » Outlook add-in
2. Press Re-grant admin consent and follow the admin consent flow
3. Under Manifest, press Download manifest to download the updated Outlook add-in manifest
a. Make sure that you don’t press Download deprecated manifest
4. Go to the Microsoft 365 admin center, and find the Integrated apps page: https://admin.microsoft.com/Adminportal/Home?source=applauncher#/Settings/IntegratedApps
5. Click on the Planner entry, and in the details window that opens, press Update add-in and proceed to upload the new manifest that you just downloaded from Planner.
6. The updated Outlook add-in manifest will now be deployed automatically, and will use nested app authentication. You can verify that you are running the new add-in, by opening the add-in from Outlook Web, and checking the web console log for an entry saying Acquired token silently.
Mac Safari Guide
Two options are available to enable support for Safari browsers, both documented by Microsoft below:
Mac Outlook Guide
The following option is available to enable support for the Outlook application running on Apple Mac machines, documented by Microsoft below:
Notes
The technology that Microsoft uses to propagate Add-ins/Integrated Apps is notoriously slow, and provides zero feedback on time to complete. Microsoft cites 24 hours to deploy ( Centralized Deployment FAQ ) and our tests sometimes exhibit longer deployment times. If it does takes longer than 24 hours, it might be worth speaking with your Microsoft Support Representative.
If users are having trouble getting the add-in to work, ensure that they are not blocking pop-ups