Outlook macro aren't made to be disitributed such as in Excel. You should build an add-in in .NET Framework using Office tools.
Here's an introduction : https://learn.microsoft.com/en-us/outlook/add-ins/quick-start?tabs=visual-studio
If you still want to export your macro, there are some workaround :
Solution 1
You can export modules as .bas, .cls, frx, and .frm files.Other users will have to reverse the process by importing them.
With this method no user will lose any code.
BUT
When importing the ThisOutlookSession module, it will be renamed ThisOutlookSession1. You'll have to copy the code from here and paste it in ThisOutlookSession or it won't run.
Solution 2
If the users don't have any macro project in their Outlook, you can copy (assuming there is only this macro on your Outlook) the VBAProject.OTM that you can find in %AppData%\Microsoft\Outlook and overwrite the user's one with it.
The last method is the one I used when I had to share a macro. But if I knew it would be such a ****** I would have use VB.NET immediately. There are other solutions but I never experimented them.