Exchange Online Tenants can Postpone Roaming Signatures

A new Exchange Online organization setting postpones the implementation of roaming signatures for Outlook clients in a tenant. The setting only allows a postponement because Microsoft really wants all Outlook clients to use the signature data stored in user mailboxes. The extra time allows tenants that use PowerShell to manage OWA signatures to work as they did before roaming signatures came along and screwed things up.

Microsoft’s Cloud Email Signatures Solve a Problem for Outlook

Microsoft says that the roaming (or cloud) email signatures feature is now fully deployed. The new approach solves an Outlook problem, but it’s not a universal panacea for the management of email signatures within large organizations where you want consistency in the signatures used by everyone. You’ll need an ISV solution to get that kind of functionality.

Outlook for Windows Stores Settings in Exchange Online Mailboxes

Outlook for Windows is being upgraded to store its setting, including signatures, in Exchange Online mailboxes for Office 365 accounts. Essentially, the bulk of the settings controlled through Outlook options are stored in mailboxes and available to Outlook on all Windows PCs that an Office 365 signs into.

Microsoft Introduces Roaming Signatures for Outlook for Windows

Outlook for Windows is soon to support roaming signatures, but only the click-to-run version when connected to an Exchange Online mailbox. Still, it’s progress, and it will make the task of using the same signature on different PCs much easier. Good-looking signatures must still be generated for corporate branding purposes, so the ISVs selling email signature products don’t need to fret.