Best Practices for Handling Email Changes in ISC Tenant

Identity Security Cloud (ISC) ISC Discussion and Questions
, ,
3

Hi @ama1 ,

For Technical Implementation:

  1. Use Business Process Rules (BPR) for email uniqueness validation rather than transforms. This allows real-time validation during provisioning.

  2. Configure Attribute Synchronization properly:

    • Go to Admin > Connections > Sources > [Your AD Source] > Account Management > Attribute Sync

    • Enable sync for mail, proxyAddresses, and userPrincipalName attributes

  3. Implement ProxyAddresses Strategy:

    • Always preserve old email as alias: smtp:old.email@domain.com

    • Set new email as primary: SMTP:new.email@domain.com

For Minimizing User Disruption:

  1. Maintain Email Aliases: Keep old email addresses active as aliases indefinitely for legacy application support

  2. Staged Rollout: Implement changes in phases rather than bulk updates

  3. Clear Communication: Notify users well in advance with impact timelines

For Non-ISC Connected Applications:

  • Create an application inventory to identify systems using email for authentication

  • Coordinate with application owners for manual updates where needed

  • Consider implementing a grace period where both emails remain active

Key Documentation References:

Hope this helps!