Before you begin
- An Exchange Administrator or Global Administrator account in your Microsoft 365 tenant
- A Windows, macOS or Linux computer with PowerShell 7 or Windows PowerShell 5.1 (Azure Cloud Shell also works)
When you need this
Atlas Ink checks this setting for you on the Rollout tab once Exchange is connected:
- "Turn off Outlook roaming signatures in this tenant": roaming signatures are still on. Follow the steps below.
- "Couldn’t check whether Outlook roaming signatures are turned off": Atlas couldn't read the setting. Step 3 tells you whether it is already in place.
- "Outlook roaming signatures are turned off" (green): nothing to do.
Step 1: Install the Exchange Online PowerShell module
Skip this step if you have used Connect-ExchangeOnline on this computer before, or if you are in Azure Cloud Shell, where the module is already installed.
Install-Module -Name ExchangeOnlineManagement -Scope CurrentUserStep 2: Connect to Exchange Online
Sign in with your Exchange Administrator or Global Administrator account when prompted.
Connect-ExchangeOnlineStep 3: Check the current value
- True: roaming signatures are already off. Skip to step 5.
- False: continue with step 4.
Get-OrganizationConfig | Select-Object PostponeRoamingSignaturesUntilLaterStep 4: Turn off roaming signatures
Run this once. It applies to the whole tenant and returns no output when it succeeds.
Set-OrganizationConfig -PostponeRoamingSignaturesUntilLater $trueThis doesn't change anyone's mail flow. Classic Outlook for Windows and Mac keeps its local signatures either way; Atlas Ink's coverage table on the Rollout tab shows which Outlook apps a pushed signature reaches.
Step 5: Confirm the change
Run the check again. It should now report True. Then disconnect.
Get-OrganizationConfig | Select-Object PostponeRoamingSignaturesUntilLater
Disconnect-ExchangeOnline -Confirm:$falseStep 6: Recheck in Atlas Ink
In Atlas, open Ink, go to the Rollout tab and click Recheck on the roaming-signature card. When the card turns green, push signatures as usual.
If the card still says Atlas couldn’t check the setting after step 5 reported True, the setting is in place: Atlas only lacks permission to read your organization settings. Continue with your rollout, and confirm it by pushing a signature to one test user and composing a new message in Outlook on the web.
Turning roaming signatures back on
If you stop using Atlas Ink and want Outlook to manage roaming signatures again, an Exchange administrator can reverse the setting:
Set-OrganizationConfig -PostponeRoamingSignaturesUntilLater $false