Failed organization validation for Québec sole proprietorship — how to provide registry evidence?

Email [Email] before creating another validation request, asking for diagnosis and an approved private channel for the registry evidence; the normal portal workflow does not document an upload control after a request reaches Failed.^1^

Include only the minimum necessary information initially:

• Artifact Signing account name and Azure subscription context.
• Validation ID.
• Exact failure text and current status.
• The original Gmail primary address and the proposed address on the business-owned domain.
• A sanitized description of the Québec enterprise-register statement and its date.
• A request to confirm:
  1. Whether the validation remains eligible for review.
  2. How the legal entity name must be represented for this sole proprietorship.
  3. Whether Microsoft authorizes a replacement request using the corrected email.
  4. Where confidential documents may be submitted securely.

Do not attach confidential registry evidence until Microsoft confirms that the mailbox or another supplied mechanism is approved for it.

Document-submission status

The documented document-upload flow applies while the request is Action Required:

1. Microsoft sends an email requesting more documents.
2. The request changes to Action Required.
3. The email directs the applicant to the Azure portal to supply the requested material.
4. Processing resumes after submission.^2^

There is no documented self-service upload or reopen operation once the status is Failed. More importantly, the current FAQ says that when additional documents were required, all three attempts have been exhausted and Microsoft cannot proceed further with onboarding. If that rule applies to this request, support can investigate whether it was classified correctly, but the documentation provides no further upload or reopening path.^3^

Organization Name for a Québec sole proprietorship

For Public organization validation, Organization Name must be the validated legal business entity; custom certificate CN or O values are not supported. The submitted business identifier, address, website, and public records should describe that same entity.^2^ ^3^

Microsoft’s published guidance does not specify whether a Québec sole proprietor must enter:

• The proprietor’s legal personal name;
• The registered operating name; or
• A combined form such as “Legal Name operating as Registered Name.”

Do not infer the format or create a custom combined name. Ask the validation team which exact registry field must populate Organization Name, and provide a text transcription of the relevant Québec register fields. Before any authorized resubmission, use Certificate subject preview to inspect the resulting certificate identity.^2^

Correcting the primary email

A Public organization request requires a monitored primary mailbox on a domain owned by the legal business entity; it must accept external messages containing links. The secondary address must be different but use the same domain.^2^

Because a validation already exists for this entity, do not independently create a duplicate with the new address. The FAQ specifically directs customers to contact support when another request for the same organization is needed with a different primary email. Support must determine how onboarding can continue; continuation of the existing record is not guaranteed.^3^

Assistance when Azure Basic blocks a technical case

Azure Basic does not include technical support; technical tickets require an eligible support plan.^4^ Therefore:

1. Use the Artifact Signing support email above first.
2. If necessary, post a sanitized question on Microsoft Q&A with the artifact-signing tag; Q&A is an official assistance option, but it is public and does not guarantee a private escalation channel.^3^
3. Do not post the validation ID, registry document, personal address, or other account identifiers publicly. Supply them only when a Microsoft representative provides an authorized private mechanism.

References

1. Identity validation failed - Microsoft Q&A
2. Quickstart: Set up Artifact Signing
3. Artifact Signing FAQ
4. Create an Azure support request