MicrosoftHello Gargy, thank you for inviting feedback on the People hub updates. I appreciate the intent behind improving contact management; however, my experience to date warrants a very direct response. In my tenant, the “new improved contacts” architecture has introduced severe functional regressions rather than improvements. Exchange Online repeatedly creates duplicate contact objects instead of reconciling existing ones, duplicates appear in real time while viewing People without any user interaction, categories are applied yet multiple GUID-backed contact objects exist per individual, there is no tenant- or mailbox-level control to disable or reset self-updating contacts, and the behavior strongly indicates contact store corruption or reconciliation failure rather than user error. To be clear, this is not a browser issue, client issue, sync partner issue, or configuration issue; it is a server-side Exchange Online contact object integrity problem introduced or exposed by this update. By contrast, my prior system enforced a strict one-contact, one-object model with a single authoritative source of truth, and the reliability gap is significant.
I have been in the Microsoft ecosystem for less than eight months and have encountered repeated inconsistencies across core services including Exchange, Outlook, identity, and contact management, and I am actively evaluating whether remaining on this platform is viable for a production business environment. I respectfully request escalation to Exchange engineering for mailbox-level contact store repair, a supported way to disable or reset self-updating contact behavior at the mailbox or tenant level, transparency into how GUID reconciliation is intended to function under the new architecture, and acknowledgment that contact duplication at this scale is a data integrity issue rather than merely feedback. I am offering this feedback because I want the platform to succeed, but reliability must precede innovation; contact data is foundational, and when it cannot be trusted, everything built on top of it is compromised. Thank you for your time and attention, and I would welcome confirmation that this feedback has reached the appropriate engineering team.
