Live status of all services Advisory

Users may be unable to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile

Microsoft 365 suite MO1489432

Users may be unable to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile.

Status
Service degradation
Feature
Access
Region
Not specified (all regions)
Started
Oct 6, 2026, 13:45 CEST
Duration
10 days 14 h
Last update
Oct 16, 2026, 11:50 CEST
Next update
Oct 19, 2026, 12:00 CEST

Current status

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.

More info

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.

Scope of impact

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.

Root cause

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.

Timeline

Every update Microsoft posted for this issue, newest first.

  1. Oct 16, 2026, 11:48 CEST

    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.

  2. Oct 14, 2026, 11:56 CEST

    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.

  3. Oct 12, 2026, 11:20 CEST

    We’re proceeding to monitor the deployment as it progresses and expect completion by Wednesday, October 14, 2026.

  4. Oct 12, 2026, 11:20 CEST

    We’re proceeding to monitor the deployment as it progresses and expect completion by Wednesday, October 14, 2026.

  5. Oct 7, 2026, 11:26 CEST

    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.

  6. Oct 6, 2026, 20:49 CEST

    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.

  7. Oct 6, 2026, 15:32 CEST

    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.

  8. Oct 6, 2026, 14:24 CEST

    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.

When Microsoft 365 goes down

The live overview shows the current state of every Microsoft 365 service, refreshed every minute from Microsoft Graph.

Live status of all services Subscribe to incidents in LEXOJ

To see whether your own tenant is affected, check Service health in the Microsoft 365 admin center. Only a backup outside Microsoft protects against data loss, and only a tested break-glass account against locked-out admins. We set up both in fixed-scope sprints.

Source: Microsoft Graph, Service Communications API. This is the view of a Swiss Microsoft 365 tenant: services not licensed there are missing, and individual issues may affect your tenant differently. Microsoft names the region only in the issue text. The Switzerland view shows issues for Switzerland, for Europe in general and those without a region, but not issues that only name other countries such as Germany or the UK. This page is not provided by Microsoft.