A rename policy is used to automatically detect when the underlying attributes that make up a username change, such as first name, last name, or ID, and ensure their account reflects the new information.
To enforce a rename policy, an active username policy must already be in place. Any usernames that are mapped from sources are not applicable in rename policies.
Configuring a custom rename policy allows you to set a delay for the change from occurring for a specific number of days, as well as notify the affected user of the impending change. These settings should be used in conjunction to inform and to give lead time prior to such a change.
If renames are allowed for an existing user, each time a potential rename event is detected, their current username is compared to their current username policy to determine if it's still valid. If it's no longer valid, a new username will be generated using the modified attributes for that user. Notifications will be sent and the change will be applied based on the additional settings of the policy. Additionally, there is a pending renames system delegation visible to tenant admins where the accounts that have been affected by a rename can be viewed.
A common rename policy allows a school district to include the last name of a staff member as part of their username and have it change automatically when the staff member's last name is changed in the system after a set processing time.