Please keep Plug-in with Outlook!

We really love the plug-in with Outlook. Various people in our org use it often.

  • Guest
  • Feb 5 2025
  • Attach files
      Drop here to upload
    • Denise Miller commented
      09 Apr 12:10

      We literally just migrated to NXT and THIS option was one of THE most important for us moving forward for saving invaluable time on other tasks than copying in action data from the 8 of our officers. PLEASE DO NOT GET RID OF IT!!!!

    • Hillary Cote commented
      07 Apr 15:36

      This is a critical tool for my fundraisers. They use this every day, it's probably the only way we get most of our contact reports entered.

    • Guest commented
      06 Mar 16:57

      Agree critical to recording Actions. Please fix

    • Guest commented
      06 Mar 16:01

      I use this tool with every single donor email i sent to save time on entering Actions into their record. This is my lifeline!!

    • Adam Branston commented
      24 Feb 09:27

      Agree completely, I'm looking at alternative solutions for this which will cost money, but we don't have a choice

    • Guest commented
      18 Feb 15:04

      Please keep this plug-in! Very valuable and extremely efficient tool.

    • Dennis Dillon commented
      17 Feb 17:01

      From a fundraising perspective, this is a valuable tool and saves so much time and energy.

    • Chris Hounsell commented
      14 Feb 19:08

      100% agree. The Blackbaud for Outlook add-in is an invaluable tool to our team that saves a lot of time. But the proposed solution to continue using it after June (that's how I read the email titled 'Potential Action Needed: Microsoft Exchange Online Token Depreciation' from Feb 4) by turning back on legacy exchange online tokens is not something our IT unit is willing to do and I know it's the same for many other organizations who use it.

      As our IT folks put it, in your suggested solution, you are asking us to reduce security for our entire university tenant for one application which is not something we can do. Microsoft has disabled this legacy feature for security concerns and advise against enabling legacy features as they cannot be contained to just one application or service.

      Again, this is a very important took to our organization but we can't sacrifice security. Please find a different fix that is acceptable and doesn't sacrifice security.

    • +3