I'm curious to learn how different people take care of managing signatures in both OWA and New Outlook. We have a good number of users on Linux who rely on OWA for their email. Currently, we're using a Powershell script to generate signatures for all Windows PCs. However, users of OWA and New Outlook are managing their own signatures, which leads to inconsistencies. Our management isn't willing to invest in a solution like CodeTwo or Exclaimer, and the Set-MailboxMessageConfiguration CMDlet doesn't seem to provide a viable option for setting OWA signatures.
5 Answers
You really need to speak up to management about needing a paid solution like CodeTwo if they expect to control signatures effectively. Free alternatives just don’t cut it.
From what I recall, you have two options: either create a guide and a template for users to add their own signatures, or pay for a managed service like Signitic. Anything else is really unsupported. If consistency and professionalism matter, a managed solution is definitely the best way to go. CodeTwo has worked really well for us!
If your management isn't open to paying for a proper solution, it might be tough to get the signatures under control. Microsoft 365 has a method to create signatures and disclaimers, but it comes with its own set of limitations. For example, if a user already has their own signature, it ends up appending an additional one instead of just using the company's standard signature. You can set things individually for each user, but that means resetting parts of their account, which can really complicate things—best to do it when they’re first onboarded.
Yeah, those limitations can be frustrating. It’s not ideal to have multiple signatures stacking up. Getting users set up right from the start makes a huge difference.
I found out that I wasn’t using Set-MailboxMessageConfiguration correctly! It turns out you need to include SignatureName and DefaultSignature along with the SignatureHTML flag. My setup now looks like this:
```
Set-OrganizationConfig -PostponeRoamingSignaturesUntilLater $true
Set-MailboxMessageconfiguration -Identity [email protected] -SignatureName someName -SignatureHtml $SignatureHTML -SignatureText $SignatureTXT -SignatureTextOnMobile $SignatureTXT -DefaultSignature $true -DefaultSignatureOnReply $true -UseDefaultSignatureOnMobile $true -AutoAddSignature $true -AutoAddSignatureOnReply $true -AutoAddSignatureOnMobile $true
``` This actually worked!
Does it apply to already established mailboxes? I found it only worked for new users who didn’t have any signatures set up.
Spending time creating a workaround that may or may not work isn’t a good use of resources. That cash could easily cover a useful product like CodeTwo, which delivers exactly what you need without the fuss.
Totally agree! Investing in a good solution like CodeTwo is worth it if you want a polished look for your emails.