When deploying AD FS for Office 365, the ideal deployment scenario is to have the userPrincipalName (UPN) value in Active Directory configured to match the user’s email address; at a minimum, your UPN suffix needs to be a publically routable domain. For many organizations, changing user UPNs is a fairly easily scriptable change with little to no impact. However, for some organizations, existing applications are using the current UPN values and making the recommended change would require significant effort.

A recent update to AD FS 3.0 (Windows Server 2012 R2) and updated guidance for Directory Sync now allow for using an “alternate login ID” with AD FS and Office 365. The end result is you can now use a value such as “mail” as the user’s login in Office 365 and avoid changes to the on-premises Active Directory objects.

The instructions for this configuration are somewhat buried in two links so I’ve consolidated them in the article below.

AD FS Configuration

Requires: AD FS 3.0 (Windows Server 2012 R2) + KB2919355

Once the required update is installed, you can modify the AD FS configuration to use an alternate login ID. To change set the alternate login ID to the “mail” attribute for the “” domain, you’d use the following:

Set-AdfsClaimsProviderTrust -TargetIdentifier "AD AUTHORITY" -AlternateLoginID mail -LookupForests

For Office 365, you now need to modify the AD FS Issuance Transform Claim Rules using the following process:

  1. Open up the “AD FS Management” console
  2. Expand “Trust Relationships” and select “Relying Party Trusts”
  3. Right-click “Microsoft Office 365 Identity Platform” and select “Edit Claim Rules…”
  4. Highlight claim rule #1 and select “Edit Rule…”
  5. Edit the rule as below (be sure to include the preceding semicolon) JPALARCHIO-ALTLOGIN1

After saving the claim rule changes, the AD FS configuration change is completed.

DirSync Configuration

For DirSync, the default rules will continue to try and sync the on-premises UPN to Azure Active Directory and if the UPN suffix is not valid, the user will be provisioned with a “” suffix. The configuration change below allows you to modify DirSync such that the on-premises “mail” attribute is used in Azure Active Directory.

DirSync can be modified with the following process:

  1. Open “miisclient.exe” on the DirSync server (Located in “C:Program FilesWindows Azure Active Directory SyncSYNCBUSSynchronization ServiceUIShell”)
  2. Select the “Management Agents” tab
  3. Right-click the “Active Directory Connector” and select “Properties”
  4. Select “Configure Attribute Flow”
  5. Expand “Object Type: user” and scroll until you find the “Data Source Attribute” of “,sAMAccountName,userPrincipalName”
  6. Change the “Mapping Type” from “Advanced” to “Direct”
  7. Select “mail” as the “Data source attribute” and confirm that the “Metaverse attribute” is set to “userPrincipalName”
  8. Click “Edit” and then “OK” to save the changes


Considerations Post-Sync

If you have previously run a synchronization job with DirSync, you may run into one of the following scenarios:

  • If the current UPN for the user is a federated domain, DirSync will not change the user’s UPN in Azure Active Directory
  • If the user has a license assigned, DirSync will not change the user’s UPN in Azure Active Directory

In the above situations, you will need to update the user’s UPN in Azure Active Directory using the process documented by my peer Erik Enger: Changing UPN for Office 365 account between two SSO domains

Additional Links

For additional information on the above configuration, please see the links below:


Published: 4/27/2014 15:13
Number of Likes: 1