Meeting requests are re-triggered as updates from Outlook mobile without user intervention

Priya Jayaraman 466 Reputation points
2026-03-25T17:37:37.9866667+00:00

Hi

Meeting requests are re-triggered as updates from Outlook mobile without user intervention.

Android -15.0 +

Mobile Outlook version-5.2610.1 (72610114)

No suspicious authentication activity as verified through Entra ID

we are unsure what is causing the issue. This is affecting multiple users randomly.

Cheers

[Moderator note: personal info removed]

Outlook | Outlook for mobile | Outlook for Android | For business
Answer accepted by question author and recommended by moderator
Avramović Andrej 90 Reputation points
2026-03-26T10:13:48.2166667+00:00

It is almost certainly service degradation on MS side:

Following up on our discussion, I was able to review the matter further internally, and I would like to advise you that the reported issue appears to be related to the ongoing service incident EX1259209 (sharing the latest update for reference): Title: Some users are seeing past calendar invites being present in Outlook on Android devices

User impact: Users are seeing past calendar invites being present in Outlook on Android devices.

Current status: We've identified that a code issue introduced in build 5.2609 of the Outlook for Android client was causing syncing delays, resulting in past calendar invites reappearing. We're rolling out a fix for the issue in the updated 5.2610.1 and subsequent Android client builds, and we're proceeding with further assessment to validate whether impact is fully remediated or if the fix may need additional time to reach all impacted users.

Scope of impact: Your organization is affected by this event, and some users utilizing calendar invites in Outlook on Android devices are impacted. This information may be updated as our investigation continues.

Root cause: A code issue introduced in build 5.2609 of the Outlook for Android client was causing syncing delays, resulting in past calendar invites reappearing.

 

As per the above, it seems like the issue originated from the Outlook for Android update mentioned above (our backend logs are also confirming this), and our development team is currently working on deploying a fix in the following updates (if possible, the affected users can try to update manually as well to the 5.2610.1 build). Having said that, we should ideally see that the impact is significantly reduced (or ideally fully gone) over the next days, and you can advise the affected users in the meantime that there is nothing to worry about, as this is related to a service degradation.

Was this answer helpful?

2 people found this answer helpful.

2 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Vergil-V 16,990 Reputation points Microsoft External Staff Moderator
    2026-03-26T03:31:19.07+00:00

    Please note that our forum is a public platform, and we will modify your question to hide your personal information in the description. Kindly ensure that you hide any personal or organizational information the next time you post an error or other details to protect personal data. 

    Hi @Priya Jayaraman   

    In addition to reviewing the Entra sign-in logs, you may also consider checking the Microsoft Purview audit logs to gain further insight into what is triggering the resend of the meeting request. 

    Microsoft Purview audit logs can help track related activities and provide a clearer picture of the events involved. For more information, you may find the following resources helpful: 

     To better understand your situation, I would appreciate it if you could help clarify the following points: 

    1. Since you mentioned that other users are experiencing the same behavior, are they part of the same organization? 
    2. Does this behavior also occur when using Outlook on the web or the Outlook desktop application, or is it limited to Outlook on Android? 

    At this time, I am not experiencing the same behavior on my test device using the same version of Outlook for Android. However, to receive more specialized assistance, you may consider opening a support case as recommended through the Q&A Assist reference. You can submit a support ticket through the Microsoft Admin Center by following the guidance in: Get support - Microsoft 365 admin | Microsoft Learn  

    I hope this provides additional insight. If you have any updates or new findings, please feel free to share them. 

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    Was this answer helpful?

  2. AI answer

    2026-03-25T17:38:06.88+00:00

    The behavior matches known calendar/meeting issues related to Outlook Mobile and mobile devices processing meeting items in the background.

    Given that:

    • It affects multiple users randomly.
    • It is specifically tied to Outlook Mobile on Android.
    • There is no suspicious authentication activity in Entra ID.

    The most likely cause is that mobile devices (or their calendar sync processes) are reprocessing existing meetings and sending updates without explicit user action.

    Recommended steps:

    1. Confirm Outlook Mobile is fully up to date
      • Check Google Play Store for Outlook and ensure all affected users are on the latest build.
      • Outlook for iOS/Android is updated weekly and many calendar issues are fixed via app updates. See the release cadence in the Outlook mobile release notes.
    2. Check for known Outlook Mobile calendar issues
      • There are active investigations for several Outlook Mobile calendaring problems (e.g., invitations sent twice, recurring meeting instances not deleting, location changes not syncing).
      • Review the “Outlook for mobile features, add-ins, and known issues” article and specifically the item:
        • “Invitations might be sent twice from an Outlook mobile app when a new attendee is added to a meeting.”
      • Even if the exact symptom differs, these known issues confirm that Outlook Mobile can sometimes mis-handle meeting updates.
    3. Rule out non-Outlook processors (other mobile/calendar apps)
      • Ensure affected users do not have additional mail/calendar apps on the same device (native Android mail/calendar, OEM mail apps, or third‑party clients) connected to the same mailbox.
      • Other mobile clients using Exchange ActiveSync can process meeting items and cause unexpected updates.
    4. Temporarily disable mobile access to isolate the cause
      • For a test user, temporarily disable mobile access (or remove the account from Outlook Mobile and any other mail apps) and reproduce the scenario by sending that user a meeting.
      • If the issue stops when mobile access is disabled, this confirms a mobile client is re-triggering the updates and further investigation of that device or app is needed.
    5. Check for device‑side OS issues and keep OS updated
      • Ensure Android OS on affected devices is fully updated.
      • Microsoft guidance for similar meeting-response issues is to keep iOS/Android devices on the latest OS to avoid already-fixed bugs in the sync stack.
    6. If using on‑premises Exchange, analyze ActiveSync logs
      • If mailboxes are on Exchange Server (not Exchange Online), use IIS/ActiveSync logs to identify which device is issuing MeetingResponse/meeting update commands.
      • The provided Log Parser Studio query can be adapted to see which DeviceType/DeviceId is generating MeetingResponse commands most frequently. This helps pinpoint problematic devices.
    7. If the issue persists, open a Microsoft support case
      • Since this is affecting multiple users on a current Outlook Mobile build and appears random, it may be a service-side or client bug that requires escalation.
      • Provide Microsoft Support with:
        • Sample mailboxes and meetings where updates were re-triggered.
        • Timestamps and message IDs of the unexpected updates.
        • Device model, Android version, and Outlook Mobile version (which is already noted as 5.2610.1).

    These steps align with Microsoft’s existing guidance for diagnosing when meeting responses/updates are being processed by something other than Outlook on the desktop and with the documented Outlook Mobile known-issues pattern.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.