Hi all, the support for NAA in the Jira Outlook add-in is now fully rolled out.

Re-iterating the expectations - 

1. Users may be asked to login again using Microsoft - This is normal. The add-in requires new NAA access tokens instead of the old cached identity tokens, so users may be asked to sign in again using their Microsoft login.
2. The add-in requires admin grant to run - This is non optional. Adoption of NAA requires Microsoft admins to approve the add-in. They can do so for the entire org by following the steps here. Refer to the "Grant tenant-wide admin consent in Enterprise apps" pane section.
3. Users may be asked to grant mailbox permissions or observe that shared mailbox attachments are not getting uploaded in the Create flow - Granting admin consent to the permissions to access shared mailboxes in step 2 will fix this.

Note: After the login and admin consent, if the add-on still does not work, please ask the users to re-install the add-in as there may be some Microsoft cache at play.

Thanks!

Hi all,

We have started rolling out support for NAA to our customers gradually. 
 
What can we expect?

1. Users may be asked to login again using Microsoft - This is normal. The add-in requires new NAA access tokens instead of the old cached identity tokens, so users may be asked to sign in again using their Microsoft login.
2. The add-in requires admin grant to run - This is non optional. Adoption of NAA requires Microsoft admins to approve the add-in. They can do so for the entire org by following the steps here. Refer to the "Grant tenant-wide admin consent in Enterprise apps" pane section.
3. Users may be asked to grant mailbox permissions - The add-in requires Graph API permissions to which the users may have to consent to continue uploading attachments to Jira.

Note: After the login and admin consent, if the add-on still does not work, please ask the users to re-install the add-in as there may be some Microsoft cache at play.

Thanks!

I am experiencing the same issue Carl P is as well

Hi there,

Unfortunately during this process, it has stopped working for us completely - it displays "Need admin approval" for each of our users who tries to use this add-in.

Any updates or progress on this would be greatly appreciated.

Due to limitations previously posed by Microsoft, the NAA approach was unable to fully replace the exchange of tokens, which temporarily halted our migration process. Microsoft has since acknowledged this and has released a new Graph API that enables us to retrieve the necessary information for migration.

To ensure uninterrupted Outlook integration, Microsoft has added our application to their exclusion list, so there will be no impact on functionality during this transition.

We are currently evaluating the new endpoint provided by Microsoft and are looking towards completing the migration. We will keep you updated on our progress and notify you once the migration is complete.

Thank you for your understanding and patience.

Best regards,
Volodymyr Hensorskyi

Will you be updating me when this is resolved?