A fully managed end-to-end service for digitally signing code, documents, and applications. (formerly Trusted Signing)
- Confirm the account has the Artifact Signing Identity Verifier role. If the role is missing, renewal actions can fail or be unavailable.
- Since a renewal request is already In Progress, do not create additional renewal requests for the same identity validation. Multiple in-progress requests do not help and cannot be expedited.
- For the Microsoft Authenticator technical failure, try the documented recovery steps in this order:
- Close all open instances of Microsoft Authenticator on the phone, then reopen it.
- Update Microsoft Authenticator to the latest iOS version.
- Clear the browser cache if the flow was launched from a browser, or retry with a different browser.
- Avoid weak Wi-Fi, VPN, or proxy connections.
- Try the renewal flow on a different device if possible.
- If the renewal flow still fails from the Renew button, and especially if the identity validation becomes Expired or renewal continues to return validation errors, create a new Identity Validation instead of renewing.
- If the existing in-progress renewal is stuck and blocks creating a new request, use Azure Support for Artifact Signing assistance. The guidance for identity validation issues is to contact Azure Support or Microsoft Q&A with the artifact-signing tag.
- If contacting support, include the Authenticator error details such as the timestamp, request ID, and correlation ID from the failure screen, plus the identity validation ID already shown in the portal.
Important details:
- Renewal can start 60 days before expiration.
- Identity validation renewal must be completed in the Azure portal; it cannot be completed with Azure CLI.
- If renewal is not completed before expiration, certificate renewal stops and signing associated with those certificate profiles stops.
References: