Outlook VBA code is supposed to be for your personal use and, therefore,
Outlook provides no such deployment functionality. You can copy the
VBAProject.otm file to other machines, but doing that will overwrite any
existing macros they already have.
There are plenty of add-ins that do what you are trying to do. If you need
it Organization wide you should look into this. Generally add-ins are more
stable for large groups and easier to deploy and maintain.
I have built simple macros and hand distributed them to 20 or more machines.
Put them in a text file and just copy and paste. You can add startup code
to add buttons and menu items to save hand hooking the macros.
I don't have some offhand but there are numerous examples on outlook.com
put a call to your routine into the Outlook project "ThisOutlookSession" in
the Application_Startup routine.
You can insert the template for the routing by selecting "Application" from
the dropdown in the editor and then select "Startup" from the right hand
dropdown.
If you are hand installing forget the startup and just call the code from
the debugger window and it will add the button linked to the macro. If you
use startup code you will have to mask it so it doesn't repeatedly try to
add the button on each restart. Doing it with the debugger should be easier
and safer. You can also just use the Macro run dialog on the Macro menu and
select to run the macro that adds the button.