Artifact Signing: what domain evidence is accepted when the domain predates the company?

win 11 0 Reputation points
2026-10-17T03:25:37.3+00:00

We are validating a UK limited company for Azure Artifact Signing. Our getvalo.dev domain was purchased through Namecheap before the company existed, and the unchanged paid receipt has historical purchaser details that do not match the company. Vetting requested the original receipt showing domain, owner, registration date, duration, registrar and expiry at least two months ahead. We supplied the receipt with an explanation. It still showed Action Required. We resubmitted on October 16; Azure confirmed successful upload and now shows In Progress. What additional evidence establishes company association with a domain purchased before incorporation? Is the original receipt plus current registrar ownership confirmation or assignment acceptable? Is a company website with legal name, registered address, contact details and domain acceptable supporting evidence? Please explain what evidence is missing rather than requesting the same receipt again. Please provide a private channel if our validation identifiers are needed; payment and identity documents are not included in this public question.

Artifact Signing
Artifact Signing

A fully managed end-to-end service for digitally signing code, documents, and applications. (formerly Trusted Signing)

0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. kagiyama yutaka 5,655 Reputation points
    2026-10-17T07:40:03.1233333+00:00

    I think the old Namecheap receipt shows who bought the domain, but doesn't show how it's linked to the UK company today. Artifact Signing asks for domain registration or renewal evidence with the company name, contact and domain. A company website isn't the same as a registrar record. And since vetting specifically asked for the original receipt, the 12-month document rule needs clearing up too.

    Ur Oct 16 submission is still In Progress. Contact Azure Support privately with the validation ID. Ask whether a current registrar record or assignment letter would work alongside the old receipt, and how the 12-month rule applies. Better to get that clear before uploading anything else.

    Was this answer helpful?

    0 comments

  2. AI answer

    2026-10-17T03:25:54.86+00:00

    For Artifact Signing organization identity validation, the documented domain-related evidence is:

    • A domain registration or domain invoice from registration or renewal that lists the entity and contact name and all domains included in the request.
    • If more documentation is requested, uploaded documents must be current, issued within the previous 12 months, and have an expiration date at least two months in the future.
    • For employment/domain ownership verification guidance in Microsoft company verification, accepted proof can include domain ownership records such as whois, domain purchase invoices, or registry confirmation records.
    • A screenshot of the company website showing the organization name, address, contact information, and domain is suggested as verification proof.

    Applied to the scenario described, the strongest supporting package is:

    1. The original receipt already requested by vetting.
    2. Current registrar ownership confirmation or registry confirmation records showing the company now owns or controls the domain.
    3. If the domain was originally purchased by an individual before incorporation, documentation confirming the domain is under the ownership of the employer/company, such as an assignment letter from an authorized representative.
    4. A company website screenshot showing the legal name, registered address, contact details, and the same domain.

    What appears to be missing is current proof that links the historical domain purchase to the present legal entity. The original receipt alone shows the registration history, but the documented supporting evidence for verification also includes current domain ownership records and, when the domain/email relationship is not straightforward, documentation confirming the domain is under the ownership of the company.

    For Artifact Signing specifically, if identity validation remains in Action Required or fails, the process is:

    1. Check the email associated with the request for any documentation request.
    2. Upload the requested documents in the Azure portal.
    3. Ensure the documents are current and match the legal business entity details used in the validation request.
    4. If another identity validation is needed for the same organization with a different primary email address, contact support to continue onboarding.
    5. If the request is stuck or unclear, create a support ticket in the Azure portal.

    Artifact Signing documentation also states that public records for the legal business entity should be up to date for quicker onboarding.

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.