Artifact Signing: public identity validation failed with no reason given, EU sole proprietorship registered in 2026

Open an Azure Support request for backend review of the failed validation before submitting another request, and provide the validation ID and resource identifiers only through that private support case.

1. Obtain the failure reason privately

Microsoft Q&A participants generally cannot inspect tenant or validation backend data, so do not post the validation ID, subscription ID, tenant ID, or account details publicly.

1. In the Azure portal, open Help + support.
2. Select Create a support request.
3. Choose the affected subscription and route the request to Azure Artifact Signing / identity validation.
4. State that:
   • This was an Organization → Public identity validation.
   • The organization is a Polish CEIDG sole proprietorship.
   • Email verification completed.
   • No Action Required document request was issued.
   • The request changed from In Progress to Failed after five days.
   • The portal and notification email contain no rejection reason.
5. Supply privately:
   • Identity Validation ID
   • Artifact Signing account name and region
   • Subscription and tenant IDs
   • Submission and failure timestamps, including time zone
   • Legal entity name and CEIDG identifier
   • A screenshot of the failed status and the notification email
6. Ask support to identify the backend rejection category and confirm whether the entity is presently eligible before another request is created.

This is the documented support route for identity-validation assistance. A closely matching case—repeated unexplained failures despite completed verification—was resolved only after support passed the validation ID and account details to the internal team for backend investigation.^1^ The FAQ likewise directs identity-validation cases to Azure Support or Microsoft Q&A, but Q&A is unsuitable for exchanging private resource identifiers.^2^

Since email verification was completed, the FAQ’s missed-or-expired-email remedy does not match this case. It says that a non-email-related failure means the validation team could not make a determination from the submitted information; it does not expose the specific failed check.^2^

2. Three-year tax-history requirement

The currently published Microsoft documentation is inconsistent:

• The current Artifact Signing quickstart explicitly includes European Union organizations in Public Trust availability and gives the organization-validation fields and process, but it does not state a minimum three-year tax history in its published prerequisites.^3^
• The current MSIX signing overview explicitly says: “Organizations must have a verifiable tax history of three or more years.” Its wording is not restricted to US organizations, so as written it also applies to organizations in the European Union.^4^
• The Artifact Signing FAQ does not currently clarify or override that requirement.^2^

Therefore, the omission from the quickstart or FAQ is not sufficient evidence that the requirement was withdrawn. For an entity registered in October 2026, the cautious action is not to submit a second request until Azure Support confirms whether the three-year rule is currently enforced for CEIDG sole proprietorships. If support confirms that it is enforced, the business cannot presently satisfy it and another request should be deferred.

Request a written answer to these exact points in the support case:

1. Is the MSIX page’s three-year verifiable tax-history requirement still an active Artifact Signing Public Trust policy?
2. Does it apply to an EU sole proprietorship registered through Poland’s CEIDG?
3. Was this validation rejected for insufficient verifiable history, or for a different record-matching issue?
4. Would a second request count against any document-submission or appeal limit?

The FAQ’s three-attempt statement specifically concerns cases where extra documents were requested and all three attempts were exhausted.^2^ Because no document request was received here, the available documentation does not establish that this failure exhausted one of those three document attempts.

References

1. Artifact Signing ID validation fails repeatedly 9afac007-6e27-4e93-84b1-34ac87fcdc90 - Microsoft Q&A
2. Artifact Signing FAQ
3. Quickstart: Set up Artifact Signing | Microsoft Learn
4. Sign an MSIX package