Home › Microsoft Teams › PRESENCE_UNKNOWN

Microsoft Teams · PRESENCE_UNKNOWN · Windows 11 23H2

Teams Presence Unknown Error PRESENCE_UNKNOWN Windows 11 23H2

Error due to Exchange Online or Teams client issues; fix by verifying UPN and SMTP match, checking presence policy in admin center, clearing cache.

Error Details

FactValueSourceNote
Exact error stringPRESENCE_UNKNOWNTeams client logs->
Affected build rangeWindows 11 23H2OS version
Registry key involved%appdata%\Microsoft\TeamsLocal cache path->
Relevant service/endpoint URLhttps://webhook.office.com/, https://admin.teams.microsoft.com/Service endpoints
Log line signatureFailed to retrieve presence status from Exchange Online.Teams logs->

Log Files to Check

What This Error Actually Means

The error code PRESENCE_UNKNOWN is raised when Microsoft Teams fails to retrieve real-time presence status from Exchange Online or the user's local client cache. This issue typically occurs due to misconfigurations within the organization, such as mismatches in ProxyAddresses attributes between Entra ID and Exchange Online, or after a mailbox move operation that hasn't been properly synchronized with Teams settings. The error is logged by the Microsoft Teams application when it attempts to fetch presence information but encounters an issue connecting to the necessary services. This can be observed both on the client side within the Teams app and in server-side logs managed through Exchange Online PowerShell or the Teams admin center.

Affected Versions and Scope

The PRESENCE_UNKNOWN error is primarily encountered on Windows 11 build 23H2, although it may also appear on other recent versions of Windows. This issue does not affect users running older OS builds that do not support the latest Teams client features or those who have not yet migrated to Exchange Online hybrid configurations. The scope of this problem is limited to organizations that use Microsoft 365 with integrated Skype for Business and Teams services, particularly where there has been a recent migration from on-premises Exchange to Exchange Online. It does not impact standalone installations of Teams without an associated Exchange environment or users who have opted out of presence functionality within their organization's policies.

Where To Look First: Logs and Event IDs

To diagnose the PRESENCE_UNKNOWN error, start by examining the following log files: Within these logs, search for the exact string "Failed to retrieve presence status from Exchange Online." This line indicates that Teams has attempted to contact the Exchange Online service but was unable to do so due to a configuration issue or network problem. Additionally, check Event Viewer on affected client machines for events related to Microsoft Teams. Specifically, look for event ID 1024 and event ID 5768 which are commonly associated with presence status retrieval failures in the Windows Application log.

Root Causes

Mismatched ProxyAddresses Attributes

One common cause of PRESENCE_UNKNOWN is a mismatch between the ProxyAddresses attribute on an Entra ID user object and their Exchange Online mailbox. This can occur after a migration or when manually updating one side without synchronizing changes to the other. To detect this issue, run the following PowerShell cmdlet in Exchange Online: Get-Mailbox | fl PrimarySmtpAddress Compare the output with Entra ID attributes using: Get-AzureADUser -ObjectId [email protected] | Select-Object ProxyAddresses

Post-Migration Configuration Issues

After migrating from an on-premises Exchange environment to Exchange Online, presence settings may not be correctly configured. This can lead to the PRESENCE_UNKNOWN error if Teams is unable to retrieve necessary configuration details. To identify this issue, check for any outstanding tasks in the Teams admin center under "Teams & calling" > "Migration." Additionally, review recent changes made during migration using: Get-CsUser -Identity [email protected] | Select-Object MigrationPolicyName

Incomplete Cache Clearing or Re-sign In Process

Sometimes, a simple cache clearing and re-login process can resolve the PRESENCE_UNKNOWN error. However, if this step is not performed correctly, it may appear as though no progress has been made. To properly clear the Teams client cache: Remove-Item -Path "%appdata%\Microsoft\Teams" -Recurse Then instruct users to log out of Teams and re-sign in.

Fix Procedure

  1. Verify ProxyAddresses Attributes: Use the following cmdlet to ensure that the PrimarySmtpAddress matches across Entra ID and Exchange Online:
    Get-Mailbox | fl PrimarySmtpAddress
    Get-AzureADUser -ObjectId [email protected] | Select-Object ProxyAddresses
  2. Check Presence Policy Assignment: Navigate to Teams admin center > Users > [username] > Account, and verify that the presence policy is correctly assigned.
  3. Clean Local Cache: Delete the local cache folder:
    Remove-Item -Path "%appdata%\Microsoft\Teams" -Recurse
    Warning: Deleting this folder will remove all Teams settings and chat history for the user. Ensure users have backups before proceeding.
  4. Re-sign In: After cache clearing, instruct users to log out of Teams and re-login.
  5. Review Migration Status: If a recent migration occurred, check for any outstanding tasks in the Teams admin center under "Teams & calling" > "Migration."

Error Code Variants

Error Code Description Distinguishing Features
PRESENCE_UNAVAILABLE Presence service is not available. This error occurs when the presence service itself is down or unreachable, rather than a configuration issue within Teams.
POLICY_NOT_FOUND No matching policy found for user. This error indicates that no presence policy has been assigned to the user in the Teams admin center.

Verification

To verify that the PRESENCE_UNKNOWN issue is resolved, check the following:

Prevention

To prevent recurrence of the PRESENCE_UNKNOWN error, ensure that: By implementing these measures, organizations can minimize the likelihood of encountering the PRESENCE_UNKNOWN error and maintain a stable environment for Microsoft Teams communication.

Sources & References

Related Guides

Get new error code fixes by email

Product-specific solutions for Intune, Autopilot, SCCM and Entra ID — straight to your inbox. No spam.