Policy cannot be deployed to the content source due to a temporary Office 365 datacenter issue. The current policy is not applied to any content in the source, so there's no impact from the blocked deployment. To fix this issue, please try redeploying the policy.
Poison message ({1}) received at {2} from {3} (source {4}) with SCL={5} has exceeded the poison message count threshold ({7}). ...
Poison Message queue ({3}) on server {2} has one or more entries. This queue contains messages that are determined to be ...
Policy "{0}" has end-user spam notifications enabled and can only be applied to domains. This rule applies to groups or users. ...
Policy "{0}" is marked as the default. Creating a rule to apply the default policy is not allowed. The default policy is ...
Policy cannot be deployed to the content source due to a temporary Office 365 datacenter issue. The current policy is not ...
Policy deployment has been interrupted by an unexpected Office 365 datacenter issue. Please contact Microsoft support to ...
Policy deployment is taking longer than expected. It may take an additional 2 hours for DistributionStatus to be updated ...
Policy parameter '{0}' and Identity parameter '{1}' should not be used together. Please use only one of them to get compliance ...
Policy provider instance processing recipient. Recipient DN: %1 Current recipient proxies: %2 Applicable policies: %3 Chosen ...