Nested App Authentication and the Blackbaud for Outlook Add-In

Seamlessly integrating software tools is crucial for maintaining productivity and efficiency. At Blackbaud, we understand the challenges you face and are dedicated to providing robust, secure applications.

What Is Nested App Authentication (NAA)?



Beginning in early 2025, Microsoft began deprecating legacy Exchange online tokens in favor of Nested App Authentication for applications nested inside of supported Microsoft applications, like the Blackbaud for Outlook Add-In. NAA provides single sign-on (SSO) for users with better security and greater flexibility in app architecture. With NAA, Blackbaud customers can now enjoy a more secure and reliable integration experience.



Do I Need to Take Any Action?



Our development team recognizes the importance of the tools you use. We've partnered closely with Microsoft to ensure that the introduction of Nested App Authentication integrates seamlessly into your workflow.

By utilizing an admin consent flow, a customer’s Microsoft 365 (M365) administrator will need to re-approve the Blackbaud for Outlook Add-In by June 2025.

If you haven't already done so, admins can follow the steps outlined in Knowledgebase Article “How do I re-authenticate my Blackbaud for Outlook Add-In?” to complete this task.

Note: If your organization uses M365 with an on-premise Microsoft Exchange server, no action is needed.

Our Ongoing Commitment



At Blackbaud, we deeply value the trust and collaboration of our customers. Our hope is that the transition to Nested App Authentication will boost the performance and security of the Blackbaud for Outlook Add-In, ensuring a seamless experience for our customers.