Users may be unable to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile.
- Status
- Eingeschränkt
- Funktion
- Access
- Region
- Nicht angegeben (alle Regionen)
- Beginn
- 06.10.2026, 13:45 Uhr
- Dauer
- 10 Tage 14 Std.
- Letztes Update
- 16.10.2026, 11:50 Uhr
- Nächstes Update
- 19.10.2026, 12:00 Uhr
Aktueller Stand
We’re validating an additional fix in our internal environment to confirm its effectiveness before deploying it to the affected infrastructure. We’ll provide the deployment timeline once it becomes available.
Mehr Informationen
Affected users may observe missing contacts, blank or grey placeholder entries, or Speed Dial entries that can't be re-added. This behavior may occur across Microsoft Teams desktop and web experiences, Outlook Mobile, and Outlook desktop.
More specifically, this issue impacts in-tenant contacts created in Microsoft Teams using the Notify when available presence notification option. Some older contacts may also be impacted under specific circumstances.
Betroffen
Some users attempting to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile may be impacted. This information may be updated as our investigation continues.
Ursache
A problem with a contact-processing component has incorrectly separated some PBCs from their associated profiles when specific contact information isn't explicitly stored, causing affected contacts to appear as blank.
Verlauf
Alle Updates von Microsoft zu dieser Meldung, das neuste zuoberst.
- 16.10.2026, 11:48 Uhr
We’re validating an additional fix in our internal environment to confirm its effectiveness before deploying it to the affected infrastructure. We’ll provide the deployment timeline once it becomes available.
- 14.10.2026, 11:56 Uhr
We've confirmed that the fix should now have reached most affected users, and we're working with a subset of users to confirm its effectiveness and validate recovery. We've identified some cases where the issue persists and are working to implement additional fix. We'll provide an update once a deployment timeline for the additional fix is available.
- 12.10.2026, 11:20 Uhr
We’re proceeding to monitor the deployment as it progresses and expect completion by Wednesday, October 14, 2026.
- 12.10.2026, 11:20 Uhr
We’re proceeding to monitor the deployment as it progresses and expect completion by Wednesday, October 14, 2026.
- 07.10.2026, 11:26 Uhr
We’ve completed validation of our fix in our internal testing environment and have begun deploying it across the affected environments. We’ve received confirmation from a subset of affected users that the fix successfully resolves the issue, and we’re continuing to monitor the broader deployment as it progresses. We expect the deployment to complete by Wednesday, October 14, 2026.
- 06.10.2026, 20:49 Uhr
We’ve begun deploying our fix to the internal environment to validate its effectiveness. Once this process has completed, we will provide a remediation timeline.
- 06.10.2026, 15:32 Uhr
We’ve developed a fix and are deploying it to our internal environment to validate its effectiveness before deploying it to the affected environment. We expect to provide a deployment timeline and rollout trajectory in our next communication update.
- 06.10.2026, 14:24 Uhr
We’ve validated that a problem with a contact-processing component has incorrectly separated some Profile Based Contacts (PBCs) from their associated profiles when specific contact information isn't explicitly stored, causing affected contacts to appear as blank. We’re developing a fix to re-merge the affected contacts with their associated profiles and expect to provide deployment timeline by our next scheduled update.
Störungen in LEXOJ abonnieren