In October, we shared how AMD and Microsoft are exploring independently verifiable hardware provenance through Artifact Signing with Signing Transparency. Now, we’re taking the next step with a controlled private preview, inviting a select group of customers to evaluate Signing Transparency in Artifact Signing against their own supported workflows.
The preview brings Microsoft's Signing Transparency (MST) into the Artifact Signing experience in Azure portal, with availability in limited regions. It gives selected customers an opportunity to evaluate supported signing and verification workflows with our team and help shape the experience. The opportunity extends beyond semiconductor provenance to software, firmware, and other supply chain evidence.
Have a signing or verification challenge to explore? Express interest in the private preview.
Why signing transparency matters
Digital signatures are foundational to software and supply chain security. They help establish who signed an artifact and whether the signed content has changed. Artifact Signing makes this practical at scale by simplifying how signatures are produced with validated identities for signing artifacts. But increasingly, enterprises also need durable evidence about the decisions, processes, and assurances associated with that artifact, evidence that can be independently verified across organizational and trust boundaries.
Microsoft's Signing Transparency extends signing with a standards-based transparency layer for that evidence. It creates tamper-evident, cryptographically verifiable records of signed statements, allowing customers, partners, and auditors to independently verify that evidence was registered and has not been altered. This provides a stronger foundation for security, compliance, release, and supply chain decisions without requiring every relying party to depend solely on assertions from the organization that produced the evidence.
Importantly, Signing Transparency is an implementation of the IETF Supply Chain Integrity, Transparency, and Trust (SCITT) architecture. SCITT defines a standards-based approach for registering and verifying signed statements about supply chain artifacts and processes. By implementing this architecture, Signing Transparency provides a foundation for interoperable evidence that can be independently verified across enterprise and ecosystem boundaries.
For enterprises, this can strengthen governance and provide more verifiable inputs into trust decisions. For software publishers, hardware manufacturers, security providers, and other ecosystem participants, it creates a common standards-based model for producing and consuming evidence that can travel with an artifact across its lifecycle.
Signing Transparency in action: strengthening semiconductor supply chain trust
AMD, an early design partner, helped us explore semiconductor provenance as a demanding test case: are manufacturing records authentic, and do they belong to the processor being evaluated? The proof of concept brought together AMD Device Provenance, Artifact Signing, and Signing Transparency to explore how manufacturer-issued evidence could be signed, recorded, and independently validated.
That work illustrates the value of connecting evidence creation with independent verification across organizational boundaries. The same need is relevant to software publishers, firmware suppliers, and teams assessing third-party artifacts. The AMD demonstration remains a proof of concept, not a product commitment or a statement of private preview scope.
“AMD Device Provenance is standards-aligned and designed to help customers independently verify the provenance of AMD hardware. Our collaboration with Microsoft shows how manufacturing evidence can connect with signing and transparency services to strengthen trust across the semiconductor supply chain.” – Ravi Kuppuswamy, SVP, Compute & Enterprise AI, AMD.
Read more about our collaboration, Strengthening Semiconductor Supply Chain Trust with Microsoft’s Artifact Signing and Transparency, and AMD’s Advancing Semiconductor Supply Chain Assurance.
How the private preview works
Figure 1. Enabling Signing Transparency in the Azure portal. Manage Signing Transparency for individual Private Trust certificate profiles and access the associated ledger from your Artifact Signing account.
Our first priority is to validate end-to-end functionality across each participant’s agreed supported scenarios. Participants can assess how transparency evidence fits their existing verification process and provide feedback on workflow and usability gaps. We also want to understand which new scenarios matter most, without treating them as capabilities already supported by the preview.
- Share your scenario. Describe your signing or verification challenge through the interest form.
- Confirm fit. Our team reviews submissions and contacts selected customers to confirm supported scenarios, regional availability, and prerequisites before onboarding.
- Evaluate. Work with our team on an agreed plan, using a representative artifact and supported workflows. Compare the evidence with your current verification process; a production release is not required.
- Share feedback. Tell us what worked, what did not, and whether the evidence helped a concrete release or verification decision. Identify any integration or usability gaps.
We welcome interest from software publishers, release and platform teams, and organizations evaluating supplier evidence. A concrete scenario and a technical contact who can collaborate and share feedback will help us assess fit.
Express your interest
Have a signing or verification challenge you would like to explore? Tell us about your scenario through the private preview interest form: Express interest in the Artifact Signing with Signing Transparency private preview. Onboarding will be staged and team-managed; submitting the form does not guarantee access.
Together, we can explore where independently verifiable signing evidence makes a practical difference to supply chain and security decisions.