Repository navigation
Diagnose "Sign the MSIX" failure: missing Azure federated credential (no repo changes) - #7
Merged
Merged
Conversation
Copilot
AI
changed the title
[WIP] Fix failing GitHub Actions job Sign the MSIX
Diagnose "Sign the MSIX" failure: missing Azure federated credential (no repo changes)
Nov 6, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The "Sign the MSIX" job in the release workflow (run 42138867457) fails at
Azure/loginwithAADSTS700213: No matching federated identity record found for presented assertion subject 'repo:edwest19/SecretKey:environment:release'.This PR contains no file changes. The cause is Entra ID configuration, not repo code, and no workflow edit can fix it.
Root cause
environment: release(release.yml:166), so GitHub issues an OIDC token with subjectrepo:edwest19/SecretKey:environment:release.client-idsecret has no federated credential for that subject.Required fix (Azure, manual)
Add a federated credential to that app registration:
edwest19/SecretKeyreleasehttps://token.actions.githubusercontent.comapi://AzureADTokenExchangeCheck that the app has the Artifact Signing role on the signing account.
Re-run the failed job.
Notes
v2.0.0-rc.1, but the subject is determined by the job'senvironment, not the ref.