A fully managed end-to-end service for digitally signing code, documents, and applications. (formerly Trusted Signing)
Hello @Zoltán Konkoly
Thank you for providing the detailed information, including the Correlation IDs and timestamps.
Since you've confirmed that:
- the issue occurs across multiple browsers, devices, and networks,
- VPN and proxy are not in use,
- the email itself is delivered successfully,
- and the verification link consistently returns "The request is blocked."
this doesn't appear to be a client-side browser or connectivity issue. Instead, it suggests the request is being blocked by the identity validation service or an upstream edge/WAF component before the verification request reaches the application.
At this point, I'd recommend that a Microsoft moderator escalate this to the Trusted Signing / Identity Validation team for investigation. The following information you've already provided should be sufficient to help correlate the failed requests:
- Trusted Signing account name
- Subscription ID
- Identity Validation ID
- Correlation IDs
- UTC timestamps of the failures
One additional question that may help narrow this down:
Has this verification link ever worked, or has it returned "The request is blocked." from the very first click?
Also, if possible, confirm whether the verification link is still within its validity period and hasn't expired. If the link has expired, regenerating a new verification email may resolve the issue; however, if a newly generated link exhibits the same behavior, that would further indicate a service-side issue.
Given that the request is blocked before the verification workflow completes and you've already ruled out browser, device, and network factors, this is likely something that requires investigation by the Trusted Signing service team rather than additional client-side troubleshooting.
Please "Accept the Answer" if this information helped you. This will help us and others in the community as well.