mirror of
https://github.com/Set-OutlookSignatures/Set-OutlookSignatures.git
synced 2026-04-26 10:45:52 +03:00
[GH-ISSUE #133] Graph authentication fails with HTTP status code 417 in some regions #60
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Set-OutlookSignatures-Set-OutlookSignatures#60
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @GruberMarkus on GitHub (Feb 25, 2025).
Original GitHub issue: https://github.com/Set-OutlookSignatures/Set-OutlookSignatures/issues/133
Issue happens in the latest release
Previously solved issues and documentation
Code of Conduct
What happened?
This only happens in some regions and not consistently within these regions. We are currently only aware that this happens in some regions of Germany, but the problem seems to spread - if you are affected, let us know at set-outlooksignatures@explicitconsulting.at.
While authentication against Graph works fine, the separate authentication against Exchange Online (EXO) fails.
The root cause is not within Set-OutlookSignatures itself, but in Microsoft's infrastructure. Microsoft's servers suddenly randomly incorrectly interpret the HTTP 'Expect' header, returning HTTP error status code 417 instead of a 2xx success code.
Until a new version of Set-OutlookSignatures is released, you can implement the following workaround: In the file '
Set-OutlookSignatures.ps1', search for 'function GraphGetToken'.Replace the whole function (lines 7089..7584) with the following code:
The next release of Set-OutlookSignatures will include this fix or an updated version of it.
@GruberMarkus commented on GitHub (Feb 28, 2025):
See updated function in the first posting (https://github.com/Set-OutlookSignatures/Set-OutlookSignatures/issues/133#issue-2877725178).
@GruberMarkus commented on GitHub (Mar 6, 2025):
Resolved in release v4.18.0, closing issue.