Deleted , you mentioned three product languages and you're already using proofing languages.
I recommend to maintain only one product language - en_US recommended - and do the rest with language packs / proofing tools.
install.xml
<Configuration>
<Add ForceUpgrade="TRUE">
<Product ID="LanguagePack">
<Language ID="pt-br" />
</Product>
<Product ID="ProofingTools">
<Language ID="pt-br" />
</Product>
</Add>
<Updates Enabled="TRUE" />
<Display Level="Full" AcceptEULA="TRUE" />
<Logging Level="Standard" Path="C:\Windows\Debug\O365_LP_pt-br" />
</Configuration>
uninstall.xml
<Configuration>
<Remove All="FALSE">
<Product ID="LanguagePack" >
<Language ID="pt-br" />
</Product>
<Product ID="ProofingTools">
<Language ID="pt-br" />
</Product>
</Remove>
<Logging Level="Standard" Path="C:\Windows\Debug\O365_LP_pt-br" />
</Configuration>
In SCCM it is just three files to offer as available application in software center.
- setup.exe
- install.xml
- uninstall.xml
Everything is pulled from CDN.
Adding more configs like above for other languages brings user interface and proofing to your global users and makes them happy.
e.g. we're offering 15 languages but having only one product language.
Even you device to install another product later, e.g. Viso, the language pack is directly applied.