[GH-ISSUE #115] Set-OutlookSignatures.ps1 unable to complete successfully for standard users (works perfectly for those with admin rights) #47

New issue

Closed

opened 2026-02-27 20:30:59 +03:00 by kerem · 0 comments

kerem commented

2026-02-27 20:30:59 +03:00

Owner

Originally created by @GruberMarkus on GitHub (May 29, 2024).
Original GitHub issue: https://github.com/Set-OutlookSignatures/Set-OutlookSignatures/issues/115

Discussed in https://github.com/Set-OutlookSignatures/Set-OutlookSignatures/discussions/114

^{Originally posted by CarlInLV May 29, 2024}
Hello,
Thank you for creating and sharing this very helpful utility!
I ran the Set-OutlookSignatures.ps1 while logged in with an account that has Domain Administrator permissions and encountered no issues.
I created custom _Signatures.ini, replacement variable config file, and graph config file.
When I launch this from my own PC, it works great and I can immediately see and use the signature based on the template (we're only standardizing one signature for now).
powershell.exe -noexit -file "X:\Redacted\Set-OutlookSignatures\Set-OutlookSignatures.ps1" -GraphOnly true -SignatureTemplatePath 'X:\Redacted\Set-OutlookSignatures\Redacted Templates\Signatures DOCX' -SignatureIniPath 'X:\Redacted\Set-OutlookSignatures\Redacted Templates\Signatures DOCX_RedactedSignatures.ini' -ReplacementVariableConfigFile "X:\Redacted\Set-OutlookSignatures\Redactedconfig\Redacted replacement variables.ps1" -GraphConfigFile "X:\Redacted\Set-OutlookSignatures\Redactedconfig\Redacted graph config.ps1"

Now when I launch that same script while logged in as a help desk user with slightly elevated permissions (local admin on the local workstation) or if the script launches as per the scheduled task (which runs the script at any user logon), the end result is a window pops up that says "You started Set-OutlookSignatures, or an Administrator configured it to run for you to update your Outlook signatures and out-of-office replies. A required security token for access to Microsoft 365 is not yet available..."

The last paragraph says to login to Micrososft 365 with my account in the new browser tab that will open after I close this message, but the browser never opens after I close that message so I can't figure out how to work through this.

This is a Windows environment (clients are on Windows 10 Enterprise and servers are 2016/2019/2022 Standard/Enterprise) with on-prem A.D. which syncs to M365/Azure (we're hybrid configured). We do not have a local MS Exchange server. All of our mailboxes are in Microsoft's Cloud. edit 3 - All of our workstations are equipped with Microsoft Office 2019 Professional Plus.

My intent is to use Set-OutlookSignatures to apply one standardized email signature to all users (all of whom have a mailbox with Microsoft 365).

Please let me know what else to try, or what other pieces of information I may provide to assist. Thanks again!

edit - I have manually set the execution policy within PowerShell to bypass on the PC I am testing with. I do plan on setting this back to Restricted once successful testing occurs. I have also used Group Policy to allow Google Chrome (it's our default browser) to "allow insecure content on these sites" = localhost

edit 2 - the only text that appears in red when I launch the script as a standard user (or as the help desk user) is "Problem connecting to Microsoft Graph. Exit." - This didn't happen to me, I assume because I have Global Administrator rights within our M365 tenant.

Originally created by @GruberMarkus on GitHub (May 29, 2024). Original GitHub issue: https://github.com/Set-OutlookSignatures/Set-OutlookSignatures/issues/115 ### Discussed in https://github.com/Set-OutlookSignatures/Set-OutlookSignatures/discussions/114 <div type='discussions-op-text'> <sup>Originally posted by **CarlInLV** May 29, 2024</sup> Hello, Thank you for creating and sharing this very helpful utility! I ran the Set-OutlookSignatures.ps1 while logged in with an account that has Domain Administrator permissions and encountered no issues. I created custom _Signatures.ini, replacement variable config file, and graph config file. When I launch this from my own PC, it works great and I can immediately see and use the signature based on the template (we're only standardizing one signature for now). powershell.exe -noexit -file "X:\Redacted\Set-OutlookSignatures\Set-OutlookSignatures.ps1" -GraphOnly true -SignatureTemplatePath 'X:\Redacted\Set-OutlookSignatures\Redacted Templates\Signatures DOCX' -SignatureIniPath 'X:\Redacted\Set-OutlookSignatures\Redacted Templates\Signatures DOCX\_RedactedSignatures.ini' -ReplacementVariableConfigFile "X:\Redacted\Set-OutlookSignatures\Redactedconfig\Redacted replacement variables.ps1" -GraphConfigFile "X:\Redacted\Set-OutlookSignatures\Redactedconfig\Redacted graph config.ps1" Now when I launch that same script while logged in as a help desk user with slightly elevated permissions (local admin on the local workstation) or if the script launches as per the scheduled task (which runs the script at any user logon), the end result is a window pops up that says "You started Set-OutlookSignatures, or an Administrator configured it to run for you to update your Outlook signatures and out-of-office replies. A required security token for access to Microsoft 365 is not yet available..." The last paragraph says to login to Micrososft 365 with my account in the new browser tab that will open after I close this message, but the browser never opens after I close that message so I can't figure out how to work through this. This is a Windows environment (clients are on Windows 10 Enterprise and servers are 2016/2019/2022 Standard/Enterprise) with on-prem A.D. which syncs to M365/Azure (we're hybrid configured). We do not have a local MS Exchange server. All of our mailboxes are in Microsoft's Cloud. *edit 3* - All of our workstations are equipped with Microsoft Office 2019 Professional Plus. My intent is to use Set-OutlookSignatures to apply one standardized email signature to all users (all of whom have a mailbox with Microsoft 365). Please let me know what else to try, or what other pieces of information I may provide to assist. Thanks again! *edit* - I have manually set the execution policy within PowerShell to bypass on the PC I am testing with. I do plan on setting this back to Restricted once successful testing occurs. I have also used Group Policy to allow Google Chrome (it's our default browser) to "allow insecure content on these sites" = localhost *edit 2* - the only text that appears in red when I launch the script as a standard user (or as the help desk user) is "Problem connecting to Microsoft Graph. Exit." - This didn't happen to me, I assume because I have Global Administrator rights within our M365 tenant.</div>