If an environment uses Universal Sync provisioning, the default Microsoft Office 365 mapping expression for the ProxyAddresses application attribute returns a null value for non-Active Directory (AD) sourced users. This causes the field attributes to populate based only on Microsoft predefined calculated field logic. Resolve this by creating a custom attribute in the Okta profile, populating it with the alias email, and mapping it to the Microsoft Office 365 ProxyAddresses attribute.

• Okta Identity Engine (OIE)
• Okta Classic Engine
• Microsoft Office 365 with Universal Sync provisioning
• Non-Active Directory Sourced Users
• Okta Integration Network (OIN)
• Profile Mappings

The default Microsoft Office 365 mapping expression for the ProxyAddresses application attribute always returns a null value for non-AD sourced users. Consequently, the field attributes populate based exclusively on Microsoft predefined calculated field logic.

Review the following image for the default mapping expression.

Review the following image for a mapping preview of a non-AD sourced Okta user.

What process creates a custom attribute in the Okta profile?

Add a new string array attribute to the default Okta user profile in the Okta Admin Console to store the Microsoft Office 365 proxy address.

1. In the Okta Admin Console, navigate to Directory > Profile Editor.
2. Select User (default) next to the Okta user object.
3. Select Add Attribute.
4. In the Data type dropdown menu, select string array.
5. In the Display name field, enter a friendly name for the attribute, such as Office365 Proxy Address.
6. In the Variable name field, enter a variable name, such as o365proxy.

Review the following image for the Add Attribute configuration window.

7. Select Save.

NOTE: Edit the newly created attribute and change the Source priority to Inherit from Okta to allow modifications to the attribute in a user profile.

Populate the new Okta attribute in the user profile.

Navigate to the user profile in the Okta Admin Console and enter the email alias using the required SMTP format.

1. In the Okta Admin Console, navigate to Directory > People.
2. Select the user.
3. Select the Profile tab.
4. Locate the newly created attribute.
5. Enter the value using the format smtp:<aliasemail@domain.com>.

Review the following image for the correct value format.

6. Select Save.

Map the custom Okta attribute to the Microsoft Office 365 ProxyAddresses attribute.

Update the Microsoft Office 365 application profile mappings in the Okta Admin Console to synchronize the new custom attribute to the application.

1. In the Okta Admin Console, navigate to Directory > Profile Editor.
2. Locate the Microsoft Office 365 application and select Mappings.
3. Select the Okta User to Office 365 tab.

Review the following image for the Okta User to Office 365 tab.

4. Locate the ProxyAddresses attribute in the right column.
5. Select the newly created Okta attribute from the dropdown menu in the left column.
6. Select Save Mappings.
7. Select Apply updates now.

Review the following image for the Apply updates now button.

NOTE: If Okta fails to push the attribute to Microsoft Office 365, perform a force synchronization from Okta to the application.

8. Verify that the expected address populates in the Azure Active Directory user profile.

Review the following image for the populated address in Azure Active Directory.

Related References

• Supported user profile attributes for Office 365 provisioning