"Run Rules Now" option doesn't update all messages after a migration to Office 365 dedicated/ITAR (vNext)


You create a new rule after you're moved to Microsoft Office 365 Dedicated/ITAR (vNext). However, the Run Rules Now option doesn't update all your messages as expected.


If the rule has a parameter that identifies messages based on a local user, the information that's stored in the rule points to the vNext legacyExchangeDN parameter. Mail that's sent to or from a local user before the migration to vNext has the legacyExchangeDN parameter from the legacy dedicated or on-premises environment. Mail that's sent after the migration is processed as expected.


This behavior is by design. For example, assume that you create a rule that moves messages from a local user to a specific folder. The cmdlet is as follows:
Get-InboxRules -Mailbox “Test mailbox” 
The result resembles the following:
Name:  Mail from John  
From: {"John Smith" [EX:/o=ExchangeLabs/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=John Smith]}
NoteJohn Smith is a placeholder that represents the local user.

The legacyExchangeDN parameter that's stored in the rule is for the object in the vNext environment. Messages that are sent before your migration to vNext contain the legacy dedicated or on-premises legacyExchangeDN parameter in the message metadata. Because this legacyExchangeDN parameter value doesn't match the legacyExchangeDN parameter value in the rule, the messages aren't processed.

Article ID: 3192989 - Last Review: Sep 22, 2016 - Revision: 1