Outlook 5.2635.0 build 54733391 terminates at launch on Apple Vision Pro running xrOS 27.0 (24M362).

It looks like you’ve hit a genuine compatibility issue between Outlook’s current build and Apple’s Vision Pro runtime environment. The crash log you described — DYLD reporting a missing ContactProviderManager.init(domainIdentifier:) symbol in /System/Library/Frameworks/ContactProvider.framework — strongly suggests that Outlook is linking against a private or unavailable API on xrOS. Since the same binary fails on both xrOS 26.6.1 and 27.0, this isn’t just a regression in the OS; it points to Outlook’s packaging or linking configuration not being aligned with Apple’s Vision Pro app store requirements.

Here’s what this typically means in practice:

• Missing symbol at launch → Outlook is expecting a system framework entry point that doesn’t exist on xrOS. That’s usually a sign of either:
  • A build targeting iOS/iPadOS frameworks without proper xrOS adaptation.
  • A packaging mismatch where the App Store bundle includes references not valid on Vision Pro.
• Reality-device incompatibility → Even if the app runs fine on iPhone/iPad, Vision Pro requires explicit xrOS support. If Outlook hasn’t been rebuilt with xrOS SDK headers, you’ll see exactly this kind of launch termination.
• What you can do:
  • Check if Microsoft has released a newer Outlook build specifically flagged for Vision Pro compatibility. The build number you mentioned (54733391) may predate xrOS 27.0 support.
  • Report the crash through Apple’s Feedback Assistant and Microsoft’s Outlook support channels — they’ll need to recompile against the correct xrOS frameworks.
  • In the meantime, Outlook Web (via Safari) is the fallback until a patched binary is published.

This isn’t something you can fix locally — it requires Microsoft to adjust their build and packaging process for xrOS.