Macro check-up for IT teams and MSPs

Last updated 25 October 2026. Run by Obegi Software LLC. Contact: [email protected].

We read every VBA macro in a folder of Excel, Word and PowerPoint files and tell you which ones will break, or need testing, as Microsoft and Windows change: why, where, and what to do first. The first 10 files are free.

Ask for a check-up See a sample report (PDF)

Who it is for

• IT teams at firms whose shares are full of macro workbooks: finance, engineering, logistics and manufacturing, where macros run month-end, quoting and reporting.
• Managed service providers who run Microsoft 365 for client firms and take the tickets when macros break. Resell it inside a project at 25% off.

Why now

• Windows is switching VBScript off. Microsoft expects it to be off by default around 2026 to 2027, offers no tool to find the macros that depend on it, and advises testing VBA projects with VBScript turned off (Microsoft 365 Developer Blog, 9 September 2025).
• ActiveX controls have been off by default in Microsoft 365 since April 2025, so buttons and boxes on sheets stop working (Microsoft 365 message center, MC884011).
• Office blocks macros in files that came from the internet, with no button to enable them (Microsoft Learn).
• In 64-bit Office, the default install since 2019, a Windows API declaration without PtrSafe stops every macro in the file.
• The free Readiness Toolkit that used to inventory macros was retired on 31 March 2024 (MC705356).

Sources read on 19 October 2026.

What you get

A report your team can act on, as checkup.pdf and checkup.html, plus three files for your own tools:

• An executive summary first: how many files need fixing, testing or a security review, and roughly how many hours of work that is.
• Risk tiers: every file in exactly one, its most urgent finding.
• What to do first: the findings grouped into actions in priority order, each with the files it touches, who usually does it, the first step and an hours range.
• What only you can tell us: the questions about your setup (Office build, 32- or 64-bit, VBScript, ActiveX policy, Defender rules) whose answers settle the findings marked "needs testing".
• Every file, most urgent first: the module, procedure and line, the exact code, why it matters and what to do.
• tickets.csv: one row per file and action, with priority, risk tier, hours and a description, ready to import into Jira, ServiceNow, Freshservice or a spreadsheet.
• inventory.csv: one row per finding, for filtering and assigning in Excel. summary.json: the same data for your own tooling.

The hours are planning ranges from typical times for each kind of change, not a quote or a promise.

A sample report

Download the sample report (PDF, 23 pages). It is one run on 26 public workbooks from GitHub, picked so each kind of finding appears at least once, dated 23 October 2026 and anonymised: file names, user folders, server names and email addresses are masked, and so is every password or key found in the code. Result: 4 Fix, 9 Test, 3 Review, 6 Plan, 3 No action, 1 No macros, and 18.5 to 59.5 hours of work. The first two pages are the executive summary.

What it checks

It reads the code; it never runs it. A word in a comment or in a message to the user is not counted as a dependency, and each module is read the way 64-bit Office compiles it. When the outcome depends on something the file cannot show (the Office build, a policy, a value only known at run time) the finding says "needs testing", never "safe". Findings are grouped as: Breaks now; Will break when VBScript is disabled; Breaks on 64-bit Office; Unsupported, may stop working; Security-relevant; Maintenance risk.

• Excel: .xlsm .xltm .xlsb .xlam .xls .xlt .xla
• Word: .docm .dotm
• PowerPoint: .pptm .potm .ppsm .ppam

Legacy Word .doc and PowerPoint .ppt files are not read.

What it does not do

• Run the macros, or judge whether they do the right thing for your business.
• Test on your PCs, or read your Office build and policies: the questions in the report ask for those.
• Check macros kept outside the files you send: each user's Personal.xlsb, add-ins installed on PCs, Word's Normal.dotm.
• Read a locked project whose code cannot be read. It is reported as not checked.
• Check whether a signature is trusted, or whether a password found in the code is still in use.

How your files are handled

• Nothing is uploaded on this page. The form below takes no files.
• We agree how the check runs before you share anything. The way we suggest first: it runs on your own PC or server in a screen-sharing session, so the files never leave your network.
• If you would rather send copies, we agree in writing, before you send anything, how they travel and when our copy is deleted.
• The check only reads the files. It never changes them and never runs their macros.
• Passwords and keys found in the code are masked in every output. The report still quotes the lines of code it is about, so keep it as carefully as the files.
• For a report you want to pass around, file names, user-folder names, server names and email addresses can be masked too, as in the sample.

Prices

For example, 5,000 files: $3,600.

• Up to 10 files: The report: a sample check, to see whether it is useful before anyone pays.
• Up to 100 files: The report, a review of every finding that breaks or needs testing, a short cover note, and a 30-minute call to walk through it.
• Up to 1,000 files: The same, plus a review of the patterns repeated across files.
• Over 1,000 files: The same, plus a review of the patterns repeated across files.

US dollars. The price is fixed for the size you choose and agreed in writing before any work; it is paid by invoice. An MSP that resells the check-up to its clients pays 25% less; the report carries Obegi Software LLC's name, and there is no white-label version.

Fixing what it finds is separate and optional: $75 an hour, or a fixed price quoted from the report (Small $300 (up to 4 hours of work), Medium $750 (up to 10), Large $1,500 (up to 20); larger jobs at $75 an hour, still a fixed price).

Ask for a check-up