Artifact Signing organization validation failed after Verified ID success — New Zealand

Check whether the separate verification link sent to the request’s primary corporate email was completed within seven days: if it was not, create a new identity-validation request; if it was, preserve the failed request and seek review through Artifact Signing support before retrying.

1. Distinguish the two verification stages

The AU10TIX/Microsoft Authenticator “Verification successful” result confirms completion of the representative’s individual Verified ID interaction. It does not establish that the entire organization validation succeeded.

For organization validation, Artifact Signing separately:

1. Sends the Verified Credentials and email-verification communications to the primary email.
2. Continues organization validation after individual verification.
3. May request further documents.
4. Finally sets the request to Completed or Failed. ^1^

Therefore, establish whether the primary corporate mailbox received and completed a separate email-verification link:

• If the link was not clicked within seven days: the documented remediation is to create a new identity-validation request. The expired link cannot be resent for the existing request. ^2^
• If it was completed on time: keep the existing failed request available while requesting review. Do not repeat AU10TIX or create another request until advised, because the portal’s failure message does not identify which later organization check failed.
• If its completion is uncertain: check the primary mailbox, junk folder, mail-security logs, and the link-click audit if available before deciding which branch applies.

The FAQ states that a non-email-related organization failure can mean the validation team could not make a determination from the supplied information. In that situation, onboarding may not be possible; requesting review seeks the specific clarification and remediation available for this request, not a guaranteed reversal. ^2^

2. Request review without exposing identifiers publicly

Microsoft documents two Artifact Signing assistance routes:

• Create an Azure Support request.
• Post on Microsoft Q&A with the Artifact Signing tag. ^2^

A Basic Azure support plan does not include private technical support requests; technical support requires an eligible support plan. Subscription-management support is available without one, but this validation investigation is classified as technical support. ^3^

No official documentation supplied here identifies a guaranteed, no-cost private Artifact Signing intake channel for Basic-plan customers. In the existing Q&A thread, explicitly request moderator-assisted escalation for backend review. This is an observed escalation practice, not a guaranteed support entitlement.

Have the following ready for a private collection method if a moderator or support engineer offers one:

• Identity Validation ID
• Subscription ID
• Artifact Signing account and resource group
• UTC submission and failure timestamps
• Validation type: Organization / Public
• Country: New Zealand
• Confirmation of whether the separate primary-email link was completed and when
• Sanitized screenshots of the successful Verified ID result and failed Azure status
• Correlation IDs, if displayed

Do not publish subscription IDs, validation IDs, identity documents, email addresses, or unredacted screenshots in Q&A.

3. Representative account versus primary email

For an organization request, the documented primary email requirement is a monitored address on a domain owned by the legal entity. The organization’s representative name must exactly match the government-issued ID, and the individual-verification sequence instructs the representative to use the email supplied in the request. ^1^

The documentation does not conclusively say that the Azure operator account administering the resource must be the same underlying Microsoft/Entra account as the primary corporate mailbox in every organization-flow interaction. Consequently:

• Do not assume that using the Azure operator account caused this failure.
• On any supported retry, use the request’s primary corporate email wherever the verification flow asks for the primary email or credentials associated with the verification link.
• If changing the request’s primary email is required, contact support rather than creating competing requests; the FAQ directs organizations with an existing validation under another primary email to support. ^2^

4. New Zealand business identifier

New Zealand is supported for organization Public Trust onboarding, and the form requires a business identifier for the legal business entity. However, the available Microsoft documentation does not specify whether a New Zealand company must enter:

• the Companies Register company number, or
• the 13-digit NZBN. ^1^

Do not replace the identifier speculatively. Ask the reviewing team to confirm the accepted New Zealand identifier type and formatting against the existing request before resubmission. Include both numbers privately, clearly labelled, so the team can identify any registry-matching issue.

References

1. Quickstart: Set up Artifact Signing
2. Artifact Signing FAQ
3. Create an Azure support request