A fully managed end-to-end service for digitally signing code, documents, and applications. (formerly Trusted Signing)
An approved Artifact Signing identity validation is valid for one year and remains available at the subscription level if only the Artifact Signing account is deleted; however, Microsoft’s public documentation does not definitively preapprove the two proposed documents or state that organization verification requires a landline.
1. Validation duration and account deletion
- Identity validation is valid for one year. Its expiration date appears under Artifact Signing account → Objects → Identity validations.
- Renewal becomes available 60 days before expiration and can take 1–20 business days because Microsoft performs a full validation again and might request updated documents. If it expires, certificate renewal and associated signing stop.^1^
- Deleting an Artifact Signing account deletes its certificate profiles, immediately stopping signing through those profiles. The identity-validation request remains because it is scoped to the Azure subscription, not solely to that account.^2^
Therefore, the proposed annual workflow is supported:
- Complete validation and sign the annual release.
- Delete the Artifact Signing account—but do not delete the identity validation.
- Retain the same Azure subscription and tenant.
- Before the next release, create another Artifact Signing account in that subscription.
- Check whether the retained validation is still unexpired; if necessary, renew it beginning 60 days before expiration.
Deleting the identity validation itself is different: it cannot be recovered and stops renewal for every linked certificate profile across the subscription.^1^
2. Bank statement and TELUS bill
Microsoft does not publish a document matrix guaranteeing that either item will be accepted for Canadian organization validation. The organization workflow initially asks for the legal organization name, business identifier, business address, website, and organization-domain email addresses. If additional evidence is needed, the validation team changes the request to Action Required and sends upload instructions.^3^
A current business bank statement identifying both Davis Software and its proprietor is stronger evidence than a utility bill showing only the proprietor’s personal name. Supporting documents should be recent and clearly establish the connection between the person and organization; related Artifact Signing guidance specifies official business documents dated within the preceding 12 months.^4^
Prepare these items before applying:
- Current British Columbia registration or government registry extract showing the registered business name and proprietor.
- Business bank statement showing the same business/proprietor relationship and current address.
- TELUS bill as supplementary proof of address.
- Matching names and addresses across the application, public registry, bank statement, and identification.
The TELUS bill alone may not establish association with Davis Software if it contains only the personal name. Final acceptance remains a case-specific decision by Microsoft’s validation team; submitting extra requests while one is in progress does not expedite the review.^5^
3. Mobile telephone versus landline
The published Artifact Signing setup procedure instructs the individual representing the organization to enter a phone number during the identity-verification process. It does not state that the number must be a landline.^3^
Accordingly:
- A landline is not listed as a published prerequisite.
- Enter the mobile number when the verification provider prompts for a phone number.
- The number should be one that the proprietor controls and can use during verification.
- The documentation does not guarantee that every mobile number or carrier will be accepted, so only Microsoft’s validation team can confirm acceptance for a particular request.
For a definitive pre-enrollment determination on the two documents and mobile number, use an Azure support request or post under the Artifact Signing tag; those are Microsoft’s documented identity-validation support channels.^5^
References