Keeping Teams Tidy: Handling Former Employee Accounts in AAD

Question:

Certainly, here’s a rephrased question: “In the context of Azure Active Directory, can email forwarding rules be maintained even if a user account is removed? Additionally, how can one ensure that a former employee’s account does not appear in Teams or the organizational chart?”

Answer:

In Azure Active Directory (AAD), managing user accounts and their associated functionalities, such as email forwarding rules, is a critical aspect of IT administration. A common concern arises when an employee leaves the company: how to retain their email forwarding rules while ensuring their account no longer appears in Microsoft Teams or the organizational chart.

When a user is removed from AAD, their associated email forwarding rules typically cease to function because these rules are tied to the user’s account. However, there are strategies to maintain email continuity:

1.

Shared Mailbox Conversion

: Before deleting the user, convert their mailbox into a shared mailbox. This retains the mailbox contents and any associated forwarding rules.

2.

Mail Flow Rules

: Create organization-wide mail flow rules in Exchange Online to handle emails sent to the former employee’s address.

Hiding Former Employees in Teams and Org Chart

To prevent a deleted user from appearing in Teams or the organizational chart, you should:

1.

Remove from AAD

: Ensure the user is fully removed from AAD. This action should automatically remove them from Teams and the org chart.

2.

Teams Clean-Up

: If the user still appears in Teams, manually remove them from any Teams and channels.

3.

Directory Synchronization

: If your organization uses directory synchronization, make sure to update the on-premises directory and perform a sync to reflect the changes in AAD.

By implementing these measures, you can maintain essential email functions while keeping your Teams and organizational chart up-to-date, reflecting the current state of your workforce.

Note: The above information is based on practices commonly used as of 2021. For the most current procedures, please refer to the latest Microsoft documentation or consult with an AAD expert.

Leave a Reply

Your email address will not be published. Required fields are marked *

Privacy Terms Contacts About Us