What has always surprised me is that there is almost no (formal) support from the IT department for the standard functionality of the application that is provided to each employee.
I regularly hear phrases like “personal risk”, but this is simply not acceptable. Being an IT within the company, you will have virtually no responsibility anymore to prevent “things suddenly stop working for some reason”.
I’ve often seen in companies that the IT help desk simply dismisses people by declaring that Excel documents containing macros are essentially unsupported in terms of content, when there are just people who are busy all day with SQL or something and have more Than enough knowledge to analyze a simple VBA macro.
It often appears as if the IT department refuses to think along with the company.
The strange thing is that it is often recognized that there is a huge gap between IT, which is often concerned exclusively with the background, and employees who are usually only interested in front-end content, but rarely try to bridge this gap. .

If VBA is widely used by users, there is a reason for that. If, instead of simply saying that you don’t want anything to do with it, you visualize the use, you might be able to determine if there really is an app that can better facilitate users or perhaps structural improvements are needed.
For some activities, perhaps the easiest and/or cheapest way to do this is in Office with VBA and why wouldn’t you want to set up and support this in an organized way.

If there really is an IT club with probably a specialist in expensive enterprise systems that a company has, why not have a specialist, project engineer, or the like who can think along with the employees?
Just spending a day watching the work and taking stock of problems that are sometimes surprisingly easy to solve always makes something happen.
More often than not, I have encouraged entire departments by reorganizing the folder structure, explicit naming of network and document locations, agreements about layouts and formatting, and restructuring setup of old Excel documents, which means the chance of no macro functionality is longer due to invalid reference (which gives In my experience the most common error message) is decreasing exponentially.

I’ve heard the comment many times that these kinds of things are not part of the IT department’s job. If there is interest in it, it is often placed with a club-like improvement team or project person, always lacking either IT knowledge or insight into actual business operations and activities.
In the end, of course, it makes no difference what you fall under from a regulatory point of view, as long as this is admittedly an underrated area for many companies where profit can often be made.