Share via


Best Practices to have in mind before submitting a script to MS for analysis

These are some tips I have had to give to customers that will help us go through the code and overall help you as well :)

- Naming standardization of variables & constants should be respected throughout the script.
- Exhaustive documentation of your script by using inline comments.
- Error and exception handling: trapping error codes and logging exhaustively operations performed by the script (in case of script malfunction, you will have exhaustive data to troubleshoot and correct issues in a minimum of time and without having to adapt your code).
- Planning environment’s evolutions by separating Exchange servers declarations and the core script so the guys not developing will be able to add/remove/modify servers without any script knowledge and without having to modify the core script => usage of a parameter file is strongly recommended in that case.