A fully managed end-to-end service for digitally signing code, documents, and applications. (formerly Trusted Signing)
Hi @A17PROJECT
Welcome to Microsoft Q&A.
Please find the answers to your queries.
Location/IP Address:
• Your current location in Greece or use of a Greek IP address is unlikely to be the direct cause of validation failure.
• Artifact Signing validation primarily checks identity attributes and compliance requirements, not geographic IP. However, some services may flag unusual sign-in patterns, so using a VPN or non‑US IP could contribute indirectly.
Failure Reason Visibility:
• At present, Azure does not expose detailed failure reasons for Artifact Signing validation in the portal or notification email.
• To obtain the exact failure reason, you’ll need to open a support request in the Azure portal → Help + Support (portal.azure.com). This ensures the backend team can review logs tied to your Activity ID.
Reusing Verified ID:
• The Verified ID issued in Microsoft Authenticator is bound to the original validation attempt.
• If validation fails, you typically need to retry with a new issuance rather than reusing the existing Verified ID.
• Reuse is not supported because each validation run requires a fresh attestation.
Next Steps:
- Confirm you are using the latest Microsoft Authenticator app and that your Verified ID issuance completed successfully.
- Retry Artifact Signing validation with a fresh Verified ID issuance.
- If the issue persists, open a support case and provide:
- Your Activity ID (from the error message)
- Verified ID issuance details
- Confirmation of your citizenship/residency status (Greek citizen, US permanent resident)
Help make this community better for everyone: if this answer resolved your issue, please accept it or leave an upvote. If not, share more details in a comment so we can continue the discussion and find the right solution.