Mapping email aliases from Okta to Google Workspace allows organizations to synchronize user email alias information seamlessly between the two services. This can be crucial for managing multiple email identities within a corporate environment. 

• Google Workspace
• Mappings
• Lifecycle Management

1. Define a Custom Attribute in Okta. If the custom attribute has not been set up, define a custom attribute on the Okta profile to store email aliases. This should be a string array type to accommodate multiple aliases per user.

2. Add the Email Aliases attribute from the Google Workspace Schema. Navigate to the Profile Editor in Okta and locate the Google Workspace App schema. From there, add the email aliases attribute. This attribute is critical as it will hold the alias data that needs to be synced with Google Workspace.

3. Map the Custom Attribute to Google Workspace. Now that both attributes are in place, go to the Okta directory and open the Google Workspace application mappings. Map the custom attribute defined in Step 1 to the email aliases attribute in the Google Workspace schema. This links the local data in Okta to the corresponding field in Google Workspace.

4. Preview and Save the Mappings.

Before finalizing the mappings, it is advisable to preview them to ensure the data appears as expected. This step is important to avoid syncing incorrect or malformed data. Once confirmed, save the changes to apply the mapping configuration.
 

5. Apply Updates Immediately.

Select the Apply now option to implement the new configuration immediately. This action triggers an update, syncing all current user data according to the new mapping settings without waiting for the next scheduled sync.