Admins can now disable roaming signatures themselves for Outlook on the web

Originally posted by Microsoft Oct 26, 2023 Uncategorized 0 Comments

We are excited to announce that admins now have a self-serve way to disable roaming signatures themselves for their tenants for Outlook on the web (formerly known as Outlook Web App or OWA) and the new Outlook for Windows. Please note that for Windows, the registry setting to disable roaming signatures will continue to work and is the only way to disable it. For more information, see Outlook roaming signatures.

When this will happen:

When this will happen:

We will begin rolling it out mid-October 2023 and expect to complete it by early November 2023.

How this will affect your organization:

This change provides an option for admins to disable roaming signatures themselves. Previously, the only way to disable roaming signatures in Outlook on the web was to open a support ticket and ask to have Outlook roaming signatures disabled in your organization. Going forward, this support ticket process will be discontinued as admins can now disable roaming signatures themselves.

How to disable roaming signature

Set-OrganizationConfig -PostponeRoamingSignaturesUntilLater $true

OR

Set-OrganizationConfig -PostponeRoamingSignaturesUntilLater 1

Details can be found Set-OrganizationConfig documentation page

The PostponeRoamingSignaturesUntilLater parameter controls whether roaming signatures are enabled or disabled in Outlook on the web (formerly known as Outlook Web App or OWA) and the new Outlook for Windows. Valid values are:

• $true: Roaming signatures are temporarily disabled for Outlook on the web and the new Outlook for Windows. When roaming signatures are disabled, admins can use signature-specific parameters like SignatureHtml, AutoAddSignature, AutoAddSignatureOnReply, etc. on the Set-MailboxMessageConfiguration cmdlet to configure email signatures. For Windows, the registry setting to disable roaming signatures will continue to work.
  

  We’re also working on providing API support to roaming signatures in the future so admins and ISVs can get access to setting and defining User roaming signatures, and tenants no longer need to disable roaming signatures. When the new API is available (and after plenty of warning), this new parameter will be deprecated.

• $false: This is the default value.

FAQ

1. I have already disabled the Roaming signature in Outlook on the web (OWA) by raising a support ticket and setting the registry value in Win32 in my tenant. Do I need to do anything again?
   • No, you don’t need to make any changes again, as the roaming signature is already disabled.
2. Do I need to disable both GPO registries for roaming signature in win32 and set OrganizationConfig –PostponeRoamingSignaturesUntilLater as True for Outlook on the web for roaming signature?
   • The cmdlet set OrganizationConfig –PostponeRoamingSignaturesUntilLater works only for Outlook on the web and the new Outlook for Windows.
   • For Windows, the registry setting to disable roaming signatures will continue to work. For more information, see Outlook roaming signatures.
3. I had earlier disabled the Roaming signature both in Outlook on the web (OWA) and Win32. How do I enable it back?
   • For win32, you can revert the registry value yourself. For Outlook on the web, if you had earlier disabled the roaming signature by raising a ticket, please open a support ticket again to get it enabled.
   • If you have disabled it by setting the cmdlet Set-OrganizationConfig -PostponeRoamingSignaturesUntilLater as True, please run the cmdlet again by changing the parameter to $false.

Message ID: MC684213