Microsoft Graph returns 404 MailboxNotEnabledForRESTAPI on GET /me/calendars after successful OAuth sign-in

Olena Pod 0 Reputation points
2026-11-16T12:01:33.67+00:00

Our scheduling app, SimplyMeet.me, connects users’ Outlook calendars through Microsoft Graph (v1.0, OAuth authorization code flow, delegated permissions).

For the account [Mod edit: PII redacted], sign-in and consent succeed and we receive a valid access token. However, the first calendar request fails:

GET https://graph.microsoft.com/v1.0/me/calendars
404 Not Found
{"error":{"code":"MailboxNotEnabledForRESTAPI","message":"The mailbox is either inactive, soft-deleted, or is hosted on-premise."}}

When: 16 November 2026, 11:37:38 (our server time). Repeated attempts the same day failed with the same error.

Questions:

  1. Why does Graph treat the mailbox of [Mod edit: PII redacted] as inactive, soft-deleted or on-premises?
  2. Is there a known issue or recent change, for example after the Microsoft 365 incident on 12–13 November 2026 (MO1550821 / EX1550543), that could cause this for cloud mailboxes?
  3. If it’s a mailbox or licence issue, what should the notando.is admin check or change?

Thank you Screenshot 2026-11-16 at 11.22.03

Screenshot 2026-11-16 at 13.28.44

Microsoft Security | Microsoft Entra | Microsoft Entra ID

1 answer

Sort by: Most helpful
  1. AI answer

    2026-11-16T12:02:55.0266667+00:00

    The notando.is administrator should first verify that this identity has an active Exchange Online user mailbox—not merely a valid Entra ID account—and restore its Exchange Online licence or mailbox if it is disconnected or soft-deleted.

    GET /me/calendars is the correct endpoint, and delegated Calendars.ReadBasic is sufficient, so the successful OAuth flow plus MailboxNotEnabledForRESTAPI points to mailbox availability rather than an incorrect calendar URL.^1^ Microsoft documents this error when the associated mailbox lacks an Exchange Online licence, is disabled, or resides in an on-premises hybrid deployment.^2^

    Administrator checks

    1. Confirm the Exchange Online licence
      • Microsoft 365 admin center → Users → Active users → select the user → Licences and apps.
      • Confirm that a product containing Exchange Online is assigned and that its Exchange Online service is enabled.
      • Check Billing → Licences → Errors & Issues for assignment failures.
      • If missing, assign the licence and save.^3^
      Removing or expiring a regular user’s Exchange Online licence immediately disconnects the mailbox. Reassigning it within 30 days reconnects it; after 30 days, an unprotected mailbox can become unrecoverable.^4^
    2. Determine what Exchange recipient currently owns the address In Exchange Online PowerShell, substitute the actual UPN:
         $upn = "[Email]"
      
         Get-EXORecipient -Identity $upn |
           Format-List DisplayName,PrimarySmtpAddress,RecipientType,RecipientTypeDetails
      
         Get-EXOMailbox -Identity $upn |
           Format-List DisplayName,PrimarySmtpAddress,RecipientTypeDetails,ExternalDirectoryObjectId
      
      Get-EXORecipient returns mail-enabled objects, whereas Get-EXOMailbox returns Exchange Online mailboxes.^5^ ^6^ Expected result: an active Exchange Online mailbox with RecipientTypeDetails such as UserMailbox. If the recipient exists but Get-EXOMailbox finds no active mailbox, continue with deletion-state and hybrid checks.
    3. Check whether it is soft-deleted or inactive
         $upn = "[Email]"
      
         Get-Mailbox -Identity $upn -SoftDeletedMailbox |
           Format-List Name,PrimarySmtpAddress,ExchangeGuid,WhenSoftDeleted
      
         Get-Mailbox -Identity $upn -IncludeInactive |
           Format-List Name,PrimarySmtpAddress,ExchangeGuid,WhenSoftDeleted
      
      A soft-deleted mailbox can result from deletion or recycling of its associated Entra user and is generally retained for 30 days.^7^ Restore it from the same system where it was deleted; do not create a replacement mailbox until the existing ExchangeGuid and recovery path have been checked, because conflicting objects can complicate recovery.
    4. If this is a hybrid tenant, verify mailbox placement If the object represents an on-premises mailbox or a mail user rather than an Exchange Online mailbox, Graph cannot obtain the expected cloud mailbox. Microsoft’s documented resolution for a mailbox hosted on dedicated/on-premises Exchange is to have the Exchange administrator migrate it to a valid Microsoft 365 mailbox.^8^
    5. Allow provisioning to complete After assigning a licence, restoring a user, or changing synchronized mailbox attributes, provisioning usually completes in under 30 minutes but can take up to 24 hours. The admin should run the mailbox-provisioning diagnostic, resolve any user validation errors, and retest after provisioning completes.^9^

    Incident question

    There is insufficient public Microsoft evidence to attribute this user’s 16 November failure to MO1550821 or EX1550543. The tenant admin should check Microsoft 365 admin center → Health → Service health → Issue history for those incident IDs and confirm whether the tenant was listed as affected.^10^

    If the mailbox is confirmed active, cloud-hosted, licensed, and fully provisioned but the request still fails, open a Microsoft 365 support case. Include the UTC timestamp, tenant ID, affected user object ID, HTTP status and error, and Graph response request-id and date headers. Future requests should also send and log a unique client-request-id; Microsoft identifies these values as necessary for support correlation.^11^

    The browser screenshot showing InvalidAuthenticationToken is a separate result: navigating directly to the URL supplied no Bearer [Token] and therefore does not test the app’s authenticated request.


    References

    1. List calendars
    2. Error code 8005E274 when you test and enable mailbox
    3. Assign or unassign licenses for users in the Microsoft 365 admin center
    4. Can't access the mailbox of an unlicensed user in Exchange Online
    5. Get-EXORecipient-Syntax
    6. Get-EXOMailbox-Syntax
    7. Delete or restore user mailboxes in Exchange Online
    8. REST API is not yet supported error - Exchange | Microsoft Learn
    9. Delays in provisioning of user/mailbox or synchronizing changes in Exchange Online
    10. How to check Microsoft 365 service health
    11. How to debug Microsoft Graph API calls
    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.