- User John Doe is assigned the UPN and email address JDoe@contoso.com.
- John Doe leaves the company, but his Active Directory user account isn't deleted.
- JDoe@contoso.com is removed from the Active Directory group that's used to synchronize users to Project Web App (PWA).
- The UPN and email address JDoe@contoso.com is later reassigned to user Jane Doe.
In this scenario, the Active Directory group will successfully synchronize to Project Web App. However, Jane Doe will see the historical data for John Doe in Project Web App (PWA).
For example: John Doe is an employee at Contoso. His UPN or email address is JDoe@contoso.com. His account is added to an AD group that's used to synchronize users to PWA security groups. John Doe then leaves the company, his account is deleted from the AD group, and on the next synchronization with PWA, his account is marked as inactive.
Later, a new employee by the name of Jane Doe joins the company. At Contoso, they reuse UPNs that are available. Jane is given the UPN or email address JDoe@contoso.com. Jane is added to an AD group that synchronizes with PWA security groups. When the sync occurs, PWA matches the UPN only. PWA sees that UPN as already assigned to an inactive resource and links up the new AD user with the old PWA user, which isn't the desired behavior. Historic data will be incorrect.
Article ID: 3174771 - Last Review: Oct 11, 2016 - Revision: 1