I was asked today how I was able to do something for a previous project that involved executing a VBA script everytime an outlook rule ran, and it sparked the thought that I should include it on here to be able to share it with anyone else who may be interested.

BUT, the problem with running a script in Outlook is that most organizations have disabled outlook scripts from executing as a security threat. So the image above may not reflect what you see in your rules. The ‘run a script’ option, may not be listed at all.

The good news is, you can edit the registry to have that ‘run a script’ option show back up, and the direction on how to do this is below:

1. In the windows search bar, search ‘regedit’ and execute.

2. In the pop-up ‘User Account Control’ dialog box, click Yes.

3. In the Registry Editor window, open the Security key with below path:

4. Right click the Security key, and select New > DWORD (32-BIT Value) from the right-clicking menu, and then name the new DWORD as EnableUnsafeClientMailRules.

5. Double click the EnableUnsafeClientMailRules DWORD to open the Edit QWORD Value dialog box.

6. In the Edit QWORD (64-BIT) Value dialog box, type 1 in the Value data box, and click OK.

7. Restart your Microsoft Outlook.

And just like that, if you go to create a rule in Outlook, ‘run a script’ will once again be an option to you.