Artifact Signing org identity validation - Verified ID "Share" fails with CosmosDB error

This request requires an Azure Support case because Microsoft Q&A participants cannot inspect backend logs or reset an Artifact Signing identity validation, and creating duplicate requests while the current one is in progress does not help.^1^

Submit the support request

1. In the Azure portal, open Help + support and select Create a support request.
2. Route the case to Azure → Security → Artifact Signing. If that exact routing choice is unavailable, select the nearest Artifact Signing option and identify the service in the case title.
3. Use a title such as: Artifact Signing organization validation – Verified ID Share fails with CosmosDB error
4. Include:
   • Identity Validation ID
   • Artifact Signing account and resource group
   • Region: East US
   • Current status: Action Required
   • UTC timestamp of the latest failure
   • Authenticator version and mobile OS/version
   • Exact CosmosDB error text and a screenshot
   • Confirmation that AU10TIX completed and the Verified ID was issued successfully
   • Confirmation that failure occurs specifically when selecting Share
   • Request to inspect the Verified ID presentation transaction and reset or re-trigger the existing organization validation

Provide the tenant ID and subscription ID only through the private support case, not in this public thread. Artifact Signing documentation explicitly directs identity-validation cases to Azure Support or Microsoft Q&A.^1^

Preserve the current request

Do not create additional identity-validation requests for the same organization while this one remains in progress. Microsoft states that duplicate in-progress requests do not help, and support is required when onboarding must continue with another validation or primary contact.^1^

Identity validation can be completed only through the Azure portal; there is no Azure CLI operation that can finish or repair this presentation step.^2^

Client-side checks before the next presentation

While preserving the request, apply only the documented technical-error checks:

1. Force-close all Microsoft Authenticator instances.
2. Update Authenticator to the latest Android or iOS version.
3. Clear the browser cache or open the validation link in another browser.
4. Use a stable connection without VPN or proxy.
5. If available, try the presentation from another supported phone.

These are Microsoft’s documented checks for technical errors during Verified ID completion.^1^ If Share still produces the same CosmosDB error, stop retrying and attach the latest timestamp and screenshot to the support case so the transaction can be correlated.

Do not delete the Verified ID or current validation unless support instructs you to do so. The documented delete-and-recreate procedure applies to specific individual-validation errors such as address mismatch, name mismatch, or FaceCheck failure—not to this organization credential-sharing error.^1^

References

1. Artifact Signing FAQ
2. Quickstart: Set up Artifact Signing | Microsoft Learn