As many of you know, I have long advocated for the power of Visual Basic for Applications in automating tasks within Microsoft Outlook. From streamlining email workflows to integrating with other applications, VBA has been a trusty tool in our arsenal. However, the technological landscape is ever-evolving, and with progress comes change, sometimes unwelcome.
Microsoft has announced that the New Outlook will no longer support VBA or COM Add-ins. This shift is part of a broader move to enhance security and modernize the platform. While these goals are commendable, the decision leaves many of us who rely on custom scripts and macros facing significant challenges.
The transition to the New Outlook began in early 2025. New installations of Microsoft 365 now include only the New Outlook by default, omitting the classic version. This change has caught many users off guard, especially those who depend on VBA for their workflows.
For those of us deeply embedded in the VBA ecosystem, this means our existing solutions will become obsolete unless we adapt. I have been working on a solution that will allow you to connect directly with mail servers to retrieve your email. Sending email is already possible, and I will be releasing more information on this soon.
In the meantime, if you need to install Classic Outlook on a Microsoft 365 machine, see this article from Office Watch.
How long until Microsoft says, for "security reasons", you can no longer use VBA in Access or Excel?
That question shows the stupidity behind New Outlook.
They couldn't have expanded the concept of Trusted Locations to Outlook?
What's the point of an Office suite of applications, if they aren't going to work together to do what each does best?
If you are a Visitor, go ahead and post your reply as a
new comment, and we'll move it here for you
once it's approved. Be sure to use the same name and email address.
This thread is now CLOSED. If you wish to comment, start a NEW discussion in
Captain's Log.
