Customer story

WatchTeams

iPhone and Apple Watch companion for Microsoft Teams · signed on the Mac and in GitHub Actions

Product

WatchTeams is an iPhone and Apple Watch companion for Microsoft Teams.

Challenge

Release signing for TestFlight needs Apple identities, but parking private keys on developer Macs (or sharing a PKCS#12) spreads custody risk across the team.

Outcome

WatchTeams 2.1.0 was archived, signed in GitHub Actions through Liminal Keys CI & automation, and uploaded to TestFlight end to end on 25 Oct 2026. The key never left Key Vault.

The problem

Shipping iOS and watchOS builds means code signing with an Apple distribution identity. Keeping that private key on every laptop — or copying a PKCS#12 between machines — creates the custody problem Liminal Keys is built to remove: usable key material on endpoints that do not need it.

How Liminal Keys fit

WatchTeams release signing uses Liminal Keys on the Mac and in GitHub Actions:

What shipped

WatchTeams 2.1.0 is the first release signed end to end through Liminal Keys CI with an ephemeral CI device enrolled via GitHub OIDC — archive, sign, and TestFlight upload in one GitHub Actions workflow. The private key stayed in Key Vault; policy and audit covered the run like any Mac.

This is a working product reference, not a marketing claim about store rankings or enterprise logos. The point for prospects: real Apple app signing, keys off the laptop.

Why it matters for other teams

If you ship Mac, iOS, or watchOS builds and want Key Vault custody without abandoning native Apple tooling, WatchTeams is a concrete example of the same model: enroll, apply policy, sign with Xcode or codesign or GitHub Actions, keep private keys in Key Vault.

Independent app. Not affiliated with or endorsed by Microsoft.

Product overview Get started CI & pipelines