A fully managed end-to-end service for digitally signing code, documents, and applications. (formerly Trusted Signing)
Artifact Signing: Organization Identity Verification – Tenant / Access Issue
Issue
I am unable to complete Azure Artifact Signing (formerly Trusted Signing) Public Organization Identity Validation because the verification service authenticates against the wrong Microsoft tenant.
I created a new Azure subscription, Artifact Signing resource, and Public Organization identity validation on November 9, 2026, using my existing personal Microsoft account.
The verification page redirects to:
https://credentials.microsoft.com/verify/noPermission
The error states that I am authenticated in the Microsoft Accounts tenant and must authenticate as an authorized user of the Microsoft Entra tenant associated with the original enrollment.
Confirmed Configuration
The Azure subscription and Artifact Signing resource exist in the same company Entra tenant.
I can successfully sign into Azure Portal and access the correct tenant, subscription, and signing resource.
My account has the Azure subscription Owner role.
My account has the Artifact Signing Identity Verifier role.
Microsoft Entra lists my account as Member.
My User Principal Name contains #EXT#, indicating an externally authenticated identity.
The same Microsoft account was used to create the subscription and initiate the identity validation request.
I do not have a separate native Work or School account to select during authentication.
Problem
Although the account has the necessary Azure permissions, the separate identity-verification application authenticates against the Microsoft Accounts tenant instead of the Entra tenant containing the Artifact Signing resource.
This occurs before the organization identity validation process begins.
The issue appears to involve the relationship between:
The personal Microsoft account used to create the Azure subscription.
The external Member identity representing that account within the company's Entra tenant.
The tenant and authorized-user association used by the Artifact Signing identity-verification service.
Selecting the correct directory in Azure Portal does not change the Microsoft account's home authentication tenant.
Environment
Product: Trusted Signing - Preview; Validation scenario: Public Trust signing using a Public identity validation for an organization; Timing: created on November 9, 2026; Sign-in context: Microsoft Accounts tenant; Case details: no region, SKU/tier, or resource identifiers provided.
What I've already tried
I have created the Trusted Signing environment and initiated the organization identity verification flow on November 9, 2026. The first attempt resulted in the tenant/authorization error described, and no further troubleshooting steps or diagnostic outputs are documented beyond the initial issue description. I have reviewed guidance suggesting to verify sign-in tenant and role assignments, but no changes have resolved the issue.
Related Microsoft Issue
Microsoft previously acknowledged and reported resolving a substantially similar tenant-authentication issue in October 2026:
Artifact Signing organization verification: "You need permission" due to Entra tenant mismatch
The symptoms appear nearly identical, including the noPermission redirect and authentication against the Microsoft Accounts tenant despite the correct Azure role assignments.
Current status
I am seeking guidance on whether my personal Microsoft account, recognized as an external Member in the Azure tenant, can support organization identity validation. I need clarification on tenant and role configurations, and instructions on how to correct the tenant mismatch to proceed with verification. Additionally, I request escalation of this case to a support engineer specializing in Artifact Signing identity validation.