Alternate Address in Microsoft 365: Understanding Email Aliases and Secondary Email Addresses

When managing users in Microsoft 365 and SharePoint Online, you may encounter the term Alternate Address. Understanding how alternate addresses work is important for identity management, email delivery, user access, and collaboration across the Microsoft 365 ecosystem.

What is an Alternate Address?

An Alternate Address is any email address associated with a Microsoft 365 account that is not the user's primary email address.

In other words, a user can have one primary email address and multiple alternate addresses, commonly referred to as email aliases.

Example:

Primary email address:

kevin@contoso.com

Alternate addresses:

k.smith@contoso.com

kevin.smith@contoso.com

support@contoso.com

Messages sent to any of these alternate addresses are delivered to the same mailbox.

How Alternate Addresses Work

Microsoft 365 allows administrators to assign multiple email aliases to a single user account. These addresses can be used for:

Receiving email through multiple addresses

Supporting organizational naming conventions

Simplifying migrations from legacy email systems

Maintaining compatibility after domain changes

Supporting mergers and acquisitions

For example, a user may receive email sent to both:

john.doe@contoso.com

jdoe@contoso.com

Even though only one address is configured as the primary SMTP address.

The primary address serves as the user's main identity, while alternate addresses provide additional methods for communication.

SharePoint Online and Alternate Addresses

In SharePoint Online, alternate addresses play an important role behind the scenes.

Benefits include:

• Improved User Recognition
• Users may appear in SharePoint with their primary identity even when emails originate from an alternate address.
• Seamless Collaboration
• Documents shared with an alternate address still resolve to the correct Microsoft 365 user account.
• Simplified Tenant Migrations
• Organizations migrating domains can maintain legacy email addresses as alternate addresses, reducing user disruption.

Guest and Hybrid Scenarios

Alternate addresses can help organizations maintain consistent user identity mapping across multiple domains and environments.

Before:

jane@oldcompany.com

After migration:

jane@newcompany.com

Instead of removing the old address, administrators can add it as an alternate address:

Primary: jane@newcompany.com

Alias: jane@oldcompany.com

This ensures continued email delivery while users adopt the new branding.

Department Reorganization

A user moving from one department to another might require a new email address while maintaining access to messages sent to their previous address.

Corporate Rebranding

Organizations frequently retain older email domains as alternate addresses during branding transitions to avoid lost communications.

Managing Alternate Addresses

Microsoft 365 administrators can manage alternate addresses through:

• Microsoft 365 Admin Center
• Exchange Admin Center
• Microsoft Graph
• Exchange Online PowerShell

Example PowerShell command to view SMTP addresses:

Get-Mailbox -Identity "Kevin" | Select-Object -ExpandProperty EmailAddresses

Example output:

SMTP:kevin@contoso.com

smtp:k.smith@contoso.com

smtp:kevin.smith@contoso.com

Notice that:

Uppercase SMTP indicates the primary address.

Lowercase smtp entries represent alternate addresses (aliases).

Best Practices

To effectively manage alternate addresses:

• Use descriptive and consistent naming conventions.
• Retain previous addresses during migrations.
• Document alias assignments for administrative tracking.
• Regularly review unused aliases.
• Ensure alternate addresses align with organizational security policies.

Conclusion

An Alternate Address in Microsoft 365 is any email address associated with a user account that is not the primary email address. These additional addresses, often called aliases, allow organizations to support multiple domains, simplify migrations, maintain backward compatibility, and improve communication flexibility. Understanding alternate addresses can help SharePoint and Microsoft 365 administrators create a smoother user experience while maintaining efficient identity and email management across the organization.

SharePoint - Alternate Account

The following is a SharePoint dictionary word of the day: Alternate Account

Alternate Account in SharePoint: Understanding Secondary Identities in the Same Forest

In complex enterprise environments, it is common for users to have more than one Active Directory account. One of these may be designated as an alternate account, allowing organizations to support administrative tasks, migrations, security requirements, and resource access scenarios without creating entirely separate identities.

What Is an Alternate Account?

An alternate account is an additional user account that exists in a different domain but remains within the same Active Directory forest as a user's primary account.

This secondary account is typically linked to the same individual and may be used for:

• Administrative responsibilities
• Elevated privilege access
• Legacy application support
• Resource access across domains
• SharePoint migration scenarios
• Security separation of duties

For example:

User Primary Account Alternate Account

John Smith CORP\jsmith ADMIN\jsmith-admin

Both accounts belong to the same Active Directory forest but reside in different domains.

Why Alternate Accounts Matter in SharePoint

SharePoint environments often integrate closely with Active Directory for authentication and authorization. When organizations operate multiple domains within a single forest, SharePoint can recognize alternate accounts and map them to the same user identity under specific configurations.

Benefits include:

• Administrative Access
• 
  
• Many organizations require administrators to use separate privileged accounts.
• 
  
• Instead of granting elevated permissions to a user's everyday account:
• 
  
• Primary Account: Email, Teams, SharePoint collaboration
• Alternate Account: SharePoint Farm Administration, SQL Administration, Service Management

This helps reduce security risks associated with privilege escalation.

Cross-Domain Resource Access

Large enterprises frequently organize business units into separate domains while maintaining a common forest structure.

Example:

Forest: Contoso.com

 

Domain A:

user1@corp.contoso.com

 

Domain B:

user1@admin.contoso.com

SharePoint can authenticate users from both domains while maintaining consistent access control.

Migration and Consolidation Projects

During:

• Domain consolidations
• Active Directory restructures
• Mergers and acquisitions
• SharePoint migrations

Alternate accounts provide continuity while user identities are transitioned between domains.

SharePoint Authentication Considerations

When an alternate account is configured:

User Profile Service

The SharePoint User Profile Service can associate profile information with the correct individual even when multiple domain accounts exist.

Organizations should verify:

• Account mappings
• Profile synchronization settings
• Identity synchronization rules
• Active Directory trust relationships
• Permission Management

Permissions should be assigned carefully.

Best practice is to: Grant permissions through Active Directory security groups

Avoid: Assigning permissions directly to both primary and alternate accounts

Using groups simplifies administration and auditing.

Security Best Practices

Organizations using alternate accounts should follow several security recommendations:

1. Separate Administrative Activities

• Use:
• 
  
• Primary account for daily work
• Alternate account for administrative functions
• 
  
• This aligns with Microsoft's least-privilege security model.

2. Enforce Multi-Factor Authentication

• Apply MFA to both:
• 
  
• Primary identities
• Alternate identities
• 
  
• Administrative accounts should receive the strongest protection.

3. Enable Auditing

• Monitor:
• 
  
• SharePoint access
• Permission changes
• Administrative actions
• Login activity across domains

4. Follow Zero Trust Principles

• Treat each account independently:
• 
  
• Verify identity
• Validate device compliance
• Require conditional access policies
• Common SharePoint Scenarios

Scenario 1: SharePoint Farm Administrator

Primary: CORP\KevinB

 

Alternate: ADMIN\KevinB-ADM

The user accesses SharePoint sites using their primary account while performing farm administration tasks with the alternate account.

Scenario 2: Domain Migration

Old Domain:

NA\User1

 

New Domain:

CORP\User1

During migration, SharePoint can maintain access continuity until permissions and profiles are fully updated.

Scenario 3: Multi-Domain Enterprise

Sales.DomainA.com

IT.DomainB.com

HR.DomainC.com

A user's alternate account enables controlled access to resources located within another domain while remaining inside the same forest.

• Benefits of Alternate Accounts in SharePoint
• Improved security through privilege separation
• Easier administration across multiple domains
• Support for migration and consolidation projects
• Better compliance and auditing capabilities
• Flexible resource access within a shared forest

Conclusion

In SharePoint, an alternate account is an additional user account located in a different domain but within the same Active Directory forest as the user's primary account. These accounts are commonly used to separate administrative and standard user activities, facilitate cross-domain access, and support migration scenarios. When managed properly through Active Directory groups, MFA, and least-privilege principles, alternate accounts help organizations improve both security and operational efficiency while maintaining seamless SharePoint access.