Artifact Signing organization validation – "Sorry, you do not meet requirements to create a Verified ID at this time" (US corporation, billing account possibly Individual type)

Your MCA billing account does not need an Account Type of Organization for Artifact Signing organization validation, so changing the billing account is not the appropriate fix; open an Azure Support case to have Microsoft inspect the failed Verified ID session and determine the specific rejection reason. Microsoft explicitly states that the Individual billing-account requirement applies only to individual developer validation, not to the individual representative verification performed as part of an organization request.^1^

Answers to the three questions

1. Can Microsoft confirm why the Verified ID was not issued? Not from the displayed message alone. It does not identify whether the failure involved the government ID, name extraction, face check, existing Verified ID state, or another eligibility check. Create an Azure support request from Azure portal → Help + support → Create a support request, selecting Artifact Signing as the affected service if available. Microsoft lists Azure Support as the support path for identity-validation problems.^2^ Ask support to:
   • Investigate the failed Verified ID/identity-proofing session.
   • Confirm whether the current organization validation can be reset or reopened.
   • Confirm whether the request must instead be deleted and recreated.
   • Provide a private upload or communication channel.
   Supply privately:
   • Identity validation ID and its current status.
   • Subscription and tenant IDs.
   • Artifact Signing account name and Azure region.
   • UTC date and time of the failure.
   • Screenshot and exact rejection text.
   • Primary email used on the request.
   • ID document type and issuing jurisdiction—but not an ID image or number unless support provides an approved secure-upload channel.
2. Is the billing account Individual, and must it be changed? That classification cannot be established from the information shown in the question. An MCA is the agreement type; the billing details page can separately show its type, legal entity, and sold-to information. The Microsoft 365 admin center exposes this under Billing → Billing accounts → select the account.^3^ However, the classification does not block the organization-validation flow under the current Artifact Signing requirements. Organization validation collects the organization name, website, business identifier, business address, and representative details directly. It does not require an Azure billing account whose Account Type is Organization.^1^ Therefore, do not change the sold-to party merely to retry this validation. Billing sold-to information identifies the person or organization legally responsible for the account, and some MCA changes require additional verification or Azure Support.^4^
3. Keep or delete the current validation request? Keep it until support has investigated it, particularly while its status is In Progress. Microsoft states that creating additional requests for the same entity while one is in progress does not help.^2^ Retry only under the matching condition:
   • Name mismatch, face-check error, or stale Verified ID: Delete the existing identity-validation request, remove its associated Verified ID from Microsoft Authenticator, and then create a new request and Verified ID. Ensure your first and last names exactly match the names extracted from the government-issued ID.^2^
   • Expired or missed email link: The link expires after seven days; create a new request because the link cannot be resent on the existing one.^2^
   • Status is Failed without either condition: Have support review it before deletion. The documented meaning is that the validation team could not determine eligibility from the submitted information.

If deletion is required, use Artifact Signing account → Objects → Identity Validation → select the request → Delete. Only requests that are not In Progress can be deleted. Deletion is irreversible, so first review the displayed linked accounts and certificate profiles.^5^

Before any supported retry, use the same monitored primary email throughout the flow and enter the representative’s first and last names exactly as shown on the government-issued ID. The organization request’s primary email must use a domain owned by the legal business entity, and its primary and secondary addresses must satisfy the documented organization-form requirements.^1^

References

1. Quickstart: Set up Artifact Signing
2. Artifact Signing FAQ
3. Understand your Microsoft business billing account
4. Change contact information for an Azure billing account
5. Renew or delete Artifact Signing Identity Validations