No. VBA macros remain fully supported. What’s changed is that macros from files marked as downloaded from the internet are now blocked by default, and ActiveX controls and VBScript are being phased out separately. Your existing VBA code is not affected by this change on its own.

ActiveX controls were disabled by default in Office 2024 from October 2024, and in Microsoft 365 apps from April 2025. It can still be re-enabled manually through Trust Center settings or Group Policy, but Microsoft actively discourages this for security reasons and it is not a long-term fix.

If ActiveX has been manually re-enabled in your environment, it will keep working for now. But that setting weakens a genuine security control, and it’s only a matter of time before a Windows or Office update, a new staff laptop, or a policy change breaks it without warning. Fixing it on your schedule is far cheaper than fixing it in a panic.

In most cases, native Content Controls (for Word) or standard Excel form controls and VBA UserForms give you the same interactivity, buttons, dropdowns, date pickers, without relying on a deprecated technology. For more complex cases, we sometimes recommend moving the functionality into a Power Apps or web-based solution instead.

PowerShell is the direct, supported replacement for most VBScript automation, file processing, and Windows task scheduling. Where the automation touches Office data specifically, Power Automate is often a better long-term fit, giving you monitoring and error handling that a standalone script never had.

Yes, and this protects you as much as us. We start with a compatibility check to identify exactly which files, forms or scripts rely on ActiveX or VBScript, then quote based on what we actually find rather than a guess.