Exchange Online automatic forwarding no longer preserves forwarded recipient in Microsoft Graph or MIME headers

Abhi Dashadiya 5 Reputation points
2026-08-04T12:00:40.9966667+00:00

Hello Microsoft Team,

We have a SaaS application that receives emails through Exchange Online mailbox forwarding.

Our routing logic depends on identifying the forwarded recipient address (for example ******@evisionits.com) from the message received in Microsoft Graph.

Our scenario

  1. A customer mailbox is hosted in Outlook / Exchange Online. Example:
       @outlook.com
    
  2. Mailbox-level automatic forwarding is configured to forward all emails to:
        @evisionits.com
    
  3. When someone sends an email to:
        @outlook.com
    
    The message is forwarded successfully to our Microsoft 365 mailbox. Our application receives the forwarded message using:

Microsoft Graph Change Notifications (Webhook) Microsoft Graph /messages/{id} Raw MIME (/$value)

Previous behavior

Until approximately 1–2 weeks ago, the forwarded recipient (@evisionits.com) was available either:

in the To header, in one of the Internet Message Headers, or in the MIME headers.

This allowed us to determine which customer/project the email belonged to.

Current behavior

Now the forwarded recipient is no longer present.

The message only contains the original recipient, for example:

To: @outlook.com

The forwarded address:

@evisionits.com

does not appear in:

toRecipients internetMessageHeaders raw MIME extended MAPI properties (tested) any other available Graph properties.

The forwarding itself succeeds correctly.

Additional observations

We also noticed Exchange adds transport headers such as:

X-MS-Exchange-Transport-CrossTenantHeadersStripped

which makes us wonder whether a recent Exchange Online transport update changed how forwarding metadata is preserved across tenants.

Comparison

We tested the exact same workflow with multiple providers.

Provider Forwarding recipient available
Gmail Yes
-------- --------
Gmail Yes
-------- --------
Gmail Yes
Yahoo Previously Yes
Zoho Previously Yes
Outlook / Exchange Online No (started approximately 1–2 weeks ago)

Questions

Has Exchange Online recently changed the behavior of mailbox-level automatic forwarding so that the forwarded recipient is no longer preserved in the stored message or exposed through Microsoft Graph? Is this an intentional security/privacy change related to cross-tenant transport? Is there any supported Microsoft Graph property, ((RedactedbyCredScan)) Online setting, or transport configuration that allows retrieving the actual forwarded recipient? Is this expected behavior or a regression?

We can provide:

Microsoft Graph JSON response Raw MIME Internet Message Headers Comparison with Gmail forwarding

if required.

Thank you.

Exchange | Hybrid management
Exchange | Hybrid management

The administration of a hybrid deployment that connects on-premises Exchange Server with Exchange Online, enabling seamless integration and centralized control.

0 comments No comments

1 answer

Sort by: Most helpful
  1. Kristen Tran 170 Reputation points Independent Advisor
    2026-08-04T13:05:50.8166667+00:00

    Hi Abhi Dashadiya,

    Thank you for reaching out and for the detailed information regarding the forwarded recipient address no longer appearing in messages retrieved through Microsoft Graph after Exchange Online mailbox level forwarding.

    This change is connected to a recent update in the way Exchange Online handles transport headers during cross tenant mail forwarding. As you noted, the X-MS-Exchange-Transport-CrossTenantHeadersStripped header confirms that certain metadata is now being removed for privacy and security reasons when a message crosses tenant boundaries. Consequently, the original forwarded recipient is no longer preserved in the toRecipients field, internetMessageHeaders, or raw MIME content once the message reaches your application through Microsoft Graph.

    To address this matter effectively, please follow the steps below, as they will suit your situation. If you don't have a permission, please contact your IT's administrator to follow this steps below:   

    1/ Verify forwarding behavior through message trace (admin only)

    2/ Preserve the forwarded address with a mail flow rule

    • Go to the Exchange Admin Center.    
    • Navigate to Mail Flow > Rules
    • Create a mail flow rule (transport rule) that inserts a custom header containing the forwarded recipient address before the message leaves the tenant User's image

    3/ Use redirect instead of standard forwarding

    If the issue persists after these checks, ask your IT administrator to submit a support request directly to Microsoft Support team and attach the Microsoft Graph JSON response, raw MIME sample, and the Gmail comparison you already prepared. In this cases, further investigation may be required at the service level, which is not accessible through standard administrative tools. 

    The Microsoft Support team has the capability to review backend service behavior, analyze logs not available to administrators, and identify any underlying issues affecting message delivery.     

    A support ticket can be created via the following link: Get support - Microsoft 365 admin | Microsoft Learn 

    In case you do not know who is your IT admin, kindly refer to this article: How do I find my Microsoft 365 admin? - Microsoft Support    

    Or you can contact them via phone number to Microsoft Support: Customer service phone numbers - Microsoft Support - Select your country/region own phone number for support.   

    As forum users, we appreciate your understanding that our access to internal development details is limited. Our primary role is to guide users toward the appropriate resources and support channels. While we may not have visibility into deeper backend analysis, we’ll continue doing our best to support you within the scope of our responsibilities.           

    I hope this information is helpful. Please follow these steps and let me know if it works for you. If you have any updates regarding the issue, please feel free to share them with me.            

    Thank you for your patience and your understanding. I look forward to continuing the conversation.  


    If the answer is helpful, please click "Yes". If you have extra questions about this answer, please click "Comment".  

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

    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.