How to delete existing signatures from Microsoft Outlook (Windows)

To delete signatures manually:

1. In Outlook, open the File menu, then select Options from the menu pane.
   
   
   _{The FIle menu in Outlook.}
   
   
2. Select Mail, then select Signatures.
   
   
   _{Select Mail from the menu sidebar, then Signatures from the Mail screen.}
   
   
3. Select a signature and select Delete.
   
   
   _{Select a signature to delete, then select the Delete button.}
   
   
4. Select Yes to confirm. 

This option is suitable for organizations that have enabled client-side signatures and installed the Exclaimer Signature Update Agent on the users' machines.

To use the Exclaimer Signature Update Agent to delete the signatures:

1. Log into the Exclaimer portal.
   
   
2. From the Outlook Signatures screen under Configuration, enable the option Remove all existing signatures in Outlook. For more information, see Outlook Signatures - Options. 
   The manually-created signatures will be removed from all machines where the Exclaimer Signature Update Agent is installed. This may take up to one hour.

This option is suitable for Azure AD-joined machines, where users sign in with their Azure AD accounts.

A Powershell script to delete signatures is necessary for this option.

1.  Save the following basic Powershell script, which will back up and then delete the signature files, as a Powershell file (.ps1):
   
   
   # 
   .SYNOPSIS 
   Script to backup and then delete all signature files from the signatures folder used by Microsoft Outlook on Windows. 
   .DESCRIPTION 
   This script is designed to be deployed by Microsoft Endpoint Manager or by Group Policy to delete signature files from a machine for the logged in user. 
   .NOTES 
   Date: 23rd January 2023. 
   .PRODUCTS 
   Exclaimer - Signatures for Office 365. 
   .USAGE 
   Check that the variables $SignaturesFolder and $SignaturesBackupFolder are set to the best values for your organisation. 
   The backup of the signature files is optional can can be removed if desired. 
   #> 
   #Declaring Signatures folder location 
   $SignaturesFolder = "$env:APPDATA\Microsoft\Signatures" 
   #Declaring Signature backup folder location 
   $SignaturesBackupFolder = "$env:APPDATA\Microsoft\SignaturesBackup" 
   #Backup Existing signature files 
   If (! (Test-Path -path "$SignaturesBackupFolder")){ 
   Copy-Item -Path "$SignaturesFolder" -Destination "$SignaturesBackupFolder" -Recurse 
   } 
   #Delete original signature files 
   Get-ChildItem -Path "$SignaturesFolder" -Include *.* -Recurse | foreach
   { $_.Delete()}
2. Sign in to the Microsoft Endpoint Manager.
   
   
3. Select Devices from the menu sidebar. From the Devices screen, select Scripts from the menu, then select Add.
   
   
   _{Select Devices, then from the Devices menu bar, select Scripts. Select Add from the Scripts screen.}
   
   
4. This opens the Add Powershell script window. Select Windows 10 or later.
   
   
5. Enter a name for the script, then select Next.
   
   
6. For Script location, select the folder icon. Locate your Powershell script file from where you saved it, then select Open.
   
   
7. Set the Run this script using the logged-on credentials toggle to Yes.
   
   
   _{In the Script settings section, choose your file and set the toggle to Yes.}
   
   
8. Select Next.
   
   
9. Choose the users for this script by selecting Add groups and specifying a group in Azure, or selecting Add all users.
   
   
10. Review the settings, then select Add. The script will run the next time the user logs into the machine.

A Powershell script to delete signatures is necessary for this option.

1. Save the following basic Powershell script, which will back up then delete the signature files, as a Powershell file (.ps1):
   
   
   <#
   .SYNOPSIS
   Script to backup and then delete all signature files from the signatures folder used by Microsoft Outlook on Windows.
   .DESCRIPTION
   This script is designed to be deployed by Microsoft Endpoint Manager or by Group Policy to delete signature files from a machine for the logged in user.
   .NOTES
   Date: 23rd January 2023.
   .PRODUCTS
   Exclaimer - Signatures for Office 365.
   .USAGE
   Check that the variables $SignaturesFolder and $SignaturesBackupFolder are set to the best values for your organisation.
   The backup of the signature files is optional can can be removed if desired.
   #>
   #Declaring Signatures folder location
   $SignaturesFolder = "$env:APPDATA\Microsoft\Signatures"
   #Declaring Signature backup folder location
   $SignaturesBackupFolder = "$env:APPDATA\Microsoft\SignaturesBackup"
   #Backup Existing signature files
   If (! (Test-Path -path "$SignaturesBackupFolder")){
   Copy-Item -Path "$SignaturesFolder" -Destination "$SignaturesBackupFolder" -Recurse
   }
   #Delete original signature files
   Get-ChildItem -Path "$SignaturesFolder" -Include *.* -Recurse | foreach { $_.Delete()}
2. Open the Group Policy Management console, either by entering gpedit or gpedit .msc in the Run command console (Windows key+R), or by locating Edit Group Policy in the Control Panel.
   
   
3. Select the required domain.
   
   
4. Either open the Action menu and select Create a GPO in this domain>Link it here… or right-click the required domain and select Create a GPO in this domain, and Link it here…
   
   
   _{The Create a GPO option in the right-click menu.}
   
   This opens the New GPO window.
   
   
5. Enter a name for the new Group Policy Object (GPO) and select OK.
   
   
   _{The New GPO window.}
   
   
6. Right-click the newly-created GPO and select Edit.
   
   
7. Expand User Configuration > Policies > Windows Settings.
   
   
8. Select Scripts (Logon/Logoff).
   
   
9. Double-click Logon. This opens the Logon Properties window.
   
   
   _{Open Scripts (Logon/Logoff) from the Windows Settings folder, then open Logon.}
   
   
10. Open the Powershell Scripts tab and select Add...
    
    
    _{The Add button is found in the Powershell Scripts tab.}
    
    
11. Select Browse... and select the script from the NETLOGON folder.
    
    
12. Select OK. The script will run the next time the user logs into the machine.