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.
Agree critical to recording Actions. Please fix
I use this tool with every single donor email i sent to save time on entering Actions into their record. This is my lifeline!!
Agree completely, I'm looking at alternative solutions for this which will cost money, but we don't have a choice
Please keep this plug-in! Very valuable and extremely efficient tool.
From a fundraising perspective, this is a valuable tool and saves so much time and energy.
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.