A fully managed end-to-end service for digitally signing code, documents, and applications. (formerly Trusted Signing)
Can you confirm whether the primary email address is associated with the tenant ID used to create the Artifact Signing account?
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
An existing Azure Artifact Signing Public organization identity validation request was last shown as In Progress. The representative can sign in successfully with a Microsoft account matching the request's primary email, but a fresh retry of the original verification link still returns "You need permission". Personal representative verification is incomplete; the cause is unknown.
Could Microsoft investigate or direct us to the appropriate support team? We want to recover access while preserving the existing request. Please provide a private channel for request/account identifiers and diagnostic evidence.
A fully managed end-to-end service for digitally signing code, documents, and applications. (formerly Trusted Signing)
Can you confirm whether the primary email address is associated with the tenant ID used to create the Artifact Signing account?
AI answer
Open an Azure support request against the affected subscription and ask for escalation to the Artifact Signing identity-validation team without deleting or duplicating the existing in-progress request.
The documented cause of “You don't have permission to access this page” is a mismatch between the email in the individual identity-validation request and the account used to open the link. Since those addresses already match, that documented check is exhausted and the remaining issue requires account-specific investigation.^1^
Artifact Signing Public organization validation – representative link returns “You need permission” although sign-in email matches
Microsoft documents Azure Support and Microsoft Q&A as the support options for Artifact Signing identity validation. It also states that creating more requests for the same entity while one is in progress does not help.^1^
Do not post request, subscription, tenant, or account identifiers in this public Q&A thread. In the support case, provide:
The initial support form permits one uploaded file, such as a browser trace or compressed diagnostic bundle. After the case is created, open Help + support → All support requests → the case → Upload file; up to five files can be attached. Remove unnecessary personal information before uploading.^3^
Creating a subscription-scoped support request requires Owner, Contributor, Support Request Contributor, or equivalent Microsoft.Support/* permission at subscription scope.^2^
Do not delete the request while seeking recovery:
If the original link is more than seven days old, include that fact in the case. Verification links expire after seven days and cannot be resent on the same request; the general remedy is a new request.^1^ Because the stated goal is to preserve an existing organization request and the error persists despite an exact email match, obtain support’s decision before replacing it.
References