Trust issues
Under certain circumstances, which probably are related to the deployment method used, the Office 365 (2016) applications lose the ability to either sign their VBA projects or validate existing signatures.
Microsoft’s Office 365 support begs off due to “request out of scope” and refers me to the paid support. Thanks.
I’m not sure yet what the actual cause of the problem is, but the workaround is embarassingly simple:
- Run any application once with elevation and go through the motions of signing something (no actual certificate required). Signing will then work again as LUA, too.
- If macros still do not work after that, open a macro-containing file, again running elevated. Validation will now work again, same as signing above.