Should Word VSTO Add-ins be able to run with Visual Basic for Applications (VBA) disabled?
My understanding from reading the following Office VSTO documentation on Microsoft Learn/Microsoft Support is that VSTO Add-ins should continue to work when Visual Basic for Applications (VBA) is disabled (via group policy or in the registry).
How to turn off Visual Basic for Applications when you deploy Office - Office | Microsoft Learn
Considerations for disabling VBA in Office - Microsoft Support
When setting the VBAOFF registry key VSTO add-ins in Excel and PowerPoint continue to work fine but Word brings up the following warning message as the add-in starts up.
Here is a GitHub repo that minimally reproduces the issue using a new blank VSTO Word Add-in created with Visual Studio 2022. Even if you add no code to a new Word VSTO add-in it will cause this error message to show in Word at startup.
GitHub - Coianiz/WordAddInDisableMacros
Can I get clarification on whether this is an unintentional bug or if I've missed something whereby we should be able to run Word VSTO add-ins with VBA disabled.
The Australian Government (Australian Cyber Security Center) has started publishing advice regarding disabling VBA and this is leading to the VSTO Add-ins not functioning for Government customers in Australia who are implementing this advice.
Microsoft Office Macro Security | Cyber.gov.au
I am attempting to implement the advice as part of the Essential 8 and am also running into this issue at the moment.
Sign in to comment