The real problem with Microsoft Security is that it’s just shifting the blame. If you disable macros, it won’t work. If you enable them, it’s your fault when things fall apart.
I haven’t worked with Microsoft products for some years now, which is why my sanity is slowly returning to me.
When Microsoft first released VBA for their applications, they enabled the first cross-platform viruses (Mac & Windows running the same evil code). Their solution was not to fix the problem, but simply to ask your permission to run the code.
One thing Microsoft has never understood is the concept of sandboxing macros. The majority of VBA I have developed is solely to enhance functionality within the document, and has no need to gain access outside of it. With Microsoft security, if you write a macro to automate adding a new worksheet, you need to grant permissions to interact with the whole operating system.
I mean, what were these guys snorting when they implemented this and called it Security? The correct solution is to enable two levels of enabling macros: sandboxed and superuser.