Secondary mailboxes and FSLogix Roam Identity

Try this to address and fix your issue:

1. Use FSLogix Profile Containers Without Roam Identity
- Configure FSLogix to persist tokens via profile containers rather than Roam Identity.
- This avoids the registry-level roaming and keeps the device compliant with Intune.
- You may need to tweak registry settings or use Nerdio Manager to automate token persistence without enabling Roam Identity.
2. Enable Seamless SSO for Primary Tenant
- Microsoft recommends configuring Entra seamless single sign-on instead of roaming tokens.
- This won’t help with the secondary tenant directly, but it reduces friction for the primary account.
3. Use Outlook Web Access (OWA) for Secondary Mailbox
- If signatures are the only reason for using Outlook desktop, consider shifting secondary mailbox access to OWA.
- You can still apply signatures via transport rules or third-party tools.
4. Explore Third-Party Signature Management
- Tools like CodeTwo or Exclaimer can centralize signature management across tenants, potentially removing the need for dual Outlook profiles.