Commit Graph

4 Commits

Author SHA1 Message Date
duffyduck 33707bdb44 Simplify add-in registration to browser sideload only
Remove Exchange PowerShell option. Outlook add-ins are registered
per Microsoft 365 account via browser sideload. Each user must
add the add-in once - it then works on all their devices.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-04-03 10:13:56 +02:00
duffyduck 4bea737696 Fix Outlook add-in registration: use Exchange or manual sideload
The TrustedCatalogs registry approach only works for Word/Excel/
PowerPoint, NOT for Outlook. Outlook add-ins must be registered
via Exchange or manually through OWA.

Setup now offers two paths:
- Exchange Online PowerShell (New-App) for organizations
- Manual sideload via https://aka.ms/olksideload as fallback

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-04-03 10:11:31 +02:00
duffyduck 60b44788fd Fix installer scripts: private key export, encoding, description
- Fix PrivateKey null error by using GetRSAPrivateKey() instead of
  .PrivateKey which is null for certs created with -Signer
- Replace all Unicode characters (umlauts, arrows, emojis) with
  ASCII-safe alternatives so output renders correctly on any
  Windows console regardless of codepage
- Add explanation in setup why Starface URL is needed (CA import)

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-04-03 09:59:24 +02:00
Stefan Hacker 37ad745546 first commit 2026-04-03 09:38:48 +02:00