Edit

Share via

User reported settings

Tip

Did you know you can try the features in Microsoft Defender XDR for Office 365 Plan 2 for free? Use the 90-day Defender for Office 365 trial at the Microsoft Defender portal trials hub. Learn about who can sign up and trial terms on Try Microsoft Defender for Office 365.

In Microsoft 365 organizations with Exchange Online mailboxes, you can identify a reporting mailbox (formerly known as a custom mailbox or submissions mailbox) to hold messages that users report as malicious or not malicious in Outlook. For Microsoft reporting tools, you can decide whether to send user reported messages to the reporting mailbox, to Microsoft, or to the reporting mailbox and Microsoft. These selections were formerly part of the User submissions policy or User submissions.

User reported settings and the reporting mailbox work with the following message reporting tools:

Delivering user reported messages to a reporting mailbox instead of directly to Microsoft allows admins to selectively and manually submit messages to Microsoft from the User reported tab on the Submissions page at https://security.microsoft.com/reportsubmission?viewid=user. For more information, see Admin submission.

Note

The ReportJunkEmailEnabled parameter on the Set-OwaMailboxPolicy cmdlet no longer controls whether user message reporting is enabled or disabled. User reporting of messages is now controlled on the User reported settings page at https://security.microsoft.com/securitysettings/userSubmission as described in this article.

For information about user reported message settings in Microsoft Teams in Defender for Office 365 Plan 2, see User reported message settings in Microsoft Teams.

If the User reported settings in the organization send user reported messages (email and Microsoft Teams) to Microsoft (exclusively or in addition to the reporting mailbox), we do the same checks as when admins submit messages to Microsoft for analysis from the Submissions page. So, submitting or resubmitting messages to Microsoft is useful to admins only for messages that have never been submitted to Microsoft, or when you disagree with the original verdict.

Configuration requirements for the reporting mailbox

Before you get started, you need to use the following steps to configure Exchange Online Protection and Defender for Office 365 so user reported messages are delivered to the reporting mailbox without being filtered:

After you verify that the reporting mailbox meets all of these requirements, use the procedures in this article to identify the reporting mailbox and to configure the related settings.

What do you need to know before you begin?

Use the Microsoft Defender portal to configure user reported settings

In the Microsoft Defender portal at https://security.microsoft.com, go to Settings > Email & collaboration > User reported settings tab. To go directly to the User reported settings page, use https://security.microsoft.com/securitysettings/userSubmission.

On the User reported settings page, the available settings for reporting messages in Outlook are determined by the Monitor reported messages in Outlook setting in the Outlook section at the top of the page:

  • Monitor reported messages in Outlook isn't selected: The Microsoft-integrated reporting experience for email messages is turned off, and all settings related to reporting email messages aren't configurable on the User reported settings page, including the ability for users to report email messages from quarantine.

  • Monitor reported messages in Outlook is selected: The following configurations are supported:

    • Use the built-in Report button in supported versions of Outlook or the Microsoft Report Message or Report Phishing add-ins in virtually all Outlook platforms to report email messages.

      • Configure user reported messages to go to the reporting mailbox, to Microsoft, or both.
      • Decide whether users receive default or customized pre-reporting and post-reporting pop-ups in supported version of Outlook.
      • Decide whether to customize the feedback email that's sent to users after an admin reviews and marks the message on the User submissions tab on the Submissions page.
      • Decide whether users can report email messages from quarantine as they release quarantined messages.

      For details, see the Options for Microsoft reporting tools section in this article.

    • Use a third-party, non-Microsoft add-in to report email messages.

      • Decide whether to customize the feedback email that's sent to users after an admin reviews and marks the message on the User submissions tab on the Submissions page.
      • Decide whether users can report email messages from quarantine as they release quarantined messages.

      For details, see the Options for third-party reporting tools section in this article.

Options for Microsoft reporting tools

When Monitor reported messages in Outlook is selected and you also select Use the built-in Report button in Outlook, the following options are available on the User reported settings page:

  • Outlook section > Select an Outlook report button configuration section > When the user reports an email section:

    • Ask the user to confirm before reporting: A pre-reporting pop-up is shown in supported versions of Outlook for the following user actions:
      • Report phishing
      • Report junk
      • Report not junk
    • Show a success message after the message is reported: A post-reporting pop-up is shown in supported versions of Outlook for the following user actions:
      • Phishing reported
      • Junk reported

    Notification pop-ups contain default English text that's automatically localized for users based on their client language. To customize the pop-up text, you can create custom versions of the five reporting pop-ups in up to seven different languages.

    Note

    Customized pre-reporting and post-reporting pop-ups are shown when using the Report button in supported versions of Outlook.

    The Microsoft Report Message add-in supports only customized Title and Description values, and only for pre-reporting pop-ups (Report phishing, Report junk, and Report not junk).

    The Microsoft Report Phishing add-in supports all customized values, but only for the Report phishing pre-reporting pop-up.

    To view the default or customized notification pop-ups, select Customize messages. The following information is available in the Customize messages flyout that opens:

    • Language: The value Default for the default notifications or the language for a custom notification.
    • Status: The value is 5 of 5 messages configured for the default notifications or n of 5 notifications configured for custom notifications.
    • Action: The View link for the default notifications. The Edit and Delete links for custom notifications.

    To create customized pop-up notifications in specific languages, select Add customized message. In the Add customized message flyout that opens, configure the following settings:

    • Select the tab for the notification pop-up to customize:

      • Report phishing (this is the default selection)
      • Report junk
      • Report not junk
      • Phishing reported
      • Junk reported

    • Choose language: The available values are: Amharic, Arabic, Bangla (India), Basque, Bulgarian, Catalan, Chinese (Simplified), Croatian, Czech, Danish, Dutch, English, Estonian, Filipino, Finnish, French, Galician, German, Greek, Gujarati, Hebrew, Hindi, Hungarian, Icelandic, Indonesian, Italian, Japanese, Kannada, Kazakh, Korean, Latvian, Lithuanian, Malayalam, Malayalam, Marathi, Norwegian, Norwegian (Nynorsk), Polish, Portuguese, Romanian, Russian, Serbian, Slovak, Slovenian, Spanish, Swahili, Swedish, Tamil, Telugu, Thai, Turkish, Ukrainian, Urdu, and Vietnamese.

      After you select a language, the following settings are available:

    • Title: Enter a maximum of 50 characters.

    • Description: Enter a maximum of 300 characters.

    • Add a link to more information: Select the check box and enter values in the following boxes that appear:

      • Link text: Enter a maximum of 30 characters.
      • URL: Enter the URL.

    When you're finished in the Add customized message flyout, select Save or Save & apply to all the message types.

  • Reported message destinations section > Send the reported messages to: Select one of the following options:

    • Microsoft and my reporting mailbox: For Microsoft 365 organizations created after March 1 2023, this is the default value. User reported messages go to Microsoft for analysis and to the specified reporting mailbox for an admin or security operations team to analyze.

      The default user reporting mailbox is the Exchange Online mailbox of the global admin. Currently, the global admin isn't shown as the user reported mailbox on the User reported settings page until after the first user in the organization reports a message from Outlook.

      To specify a different mailbox, select next to any existing entry in the Add an Exchange Online mailbox to send reported messages to box. Click in the box and wait for the list of mailboxes to populate, or start typing a value to filter the list, and then select the mailbox in the results. Distribution groups and routing to an external or on-premises mailbox aren't allowed.

    • My reporting mailbox only: User reported messages go only to the specified reporting mailbox for an admin or the security operations team to analyze.

      Follow the previous instructions to select the mailbox in the Add an Exchange Online mailbox to send reported messages to box.

      On the User reported tab on the Submissions page at https://security.microsoft.com/reportsubmission?viewid=user, the Result value for these entries is Not Submitted to Microsoft. Messages don't go to Microsoft for analysis unless an admin manually submits the message. For instructions, see Submit user reported messages to Microsoft for analysis.

    • Microsoft only: User reported messages go directly to Microsoft for analysis.

    Note

    • When you select Use the built-in Report button in Outlook and users report messages using the built-in Report button in supported versions of Outlook or the Microsoft Report Message or Report Phishing add-ins in virtually all versions of Outlook, user reported messages are available to admins on the User reported tab on the Submissions page at https://security.microsoft.com/reportsubmission?viewid=user, regardless of the value you select for Send the reported messages to. For more information, see Admin options for user reported messages.

    • In U.S. Government organizations (Microsoft 365 GCC, GCC High, and DoD), the only available value for Send the reported messages to is My reporting mailbox only. The other two options are unavailable for compliance reasons (data isn't allowed to leave the organization boundary).

  • Email notifications section: These options affect the notification email message that's sent to users when an admin selects Mark as and notify on the Submissions page at https://security.microsoft.com/reportsubmission. The following options are available:

    • Results email section:

      • Select Customize results email. In the Customize admin review email notifications flyout that opens, configure the following settings on the Phishing, Junk and No threats found tabs:

        • Email body results text: Enter the custom text to use. You can use different text for Phishing, Junk and No threats found.
        • Email footer text: Enter the custom message footer text to use. The same text is used for Phishing, Junk and No threats found.

        When you're finished in the Customize admin review email notifications flyout, select Confirm to return to the User reported settings page.

    • Automatically email users the results of the investigation: This feature is available only in Defender for Office 365 Plan 2 organizations with automated investigation and response (AIR).

      If a user reports a message as phishing, an investigation in AIR is automatically created. The following options send notification email to the user who reported the message based on the results from AIR (select one or more options):

      • Phishing or malware: An email notification is sent to the user who reported the message as phishing when AIR identifies the threat as phishing, high confidence phishing, or malware.
      • Spam: An email notification is sent to the user who reported the message as phishing when AIR identifies the threat as spam.
      • No threats found: An email notification is sent to the user who reported the message as phishing when AIR identifies no threat.

      For more information, see Automatic user notifications for user reported phishing results in AIR.

    • Customize sender and branding section:

      • Specify a Microsoft 365 mailbox to use ads the From address of email notifications: Select this option and enter the sender's email address in the box that appears. If you don't select this option, the default sender is submissions@messaging.microsoft.com.
      • Replace the Microsoft logo with my organization's logo across all reporting experiences: Select this option to replace the default Microsoft logo that's used in notifications. Before you do this step, follow the instructions in Customize the Microsoft 365 theme for your organization to upload your custom logo.

  • Report from quarantine section > Allow reporting for quarantined messages: Verify that this setting is selected to let users report messages from quarantine as they release quarantined email messages. Otherwise, uncheck this setting.

When you're finished on the User reported settings page, select Save.

Options for third-party reporting tools

If you're using a third-party reporting button for end users (for example, KnowBe4 Phish Alert Button, Cofense Report Phishing, or PhishAlarm), you can benefit from the power of Defender incident management, in-product phishing triage, and native automated response capabilities by integrating the reporting button with Microsoft Defender for Office 365.

When Monitor reported messages in Outlook is selected and you also select Use a non-Microsoft add-in button, the following options are available on the User reported settings page:

  • Reported message destinations section > Add an Exchange Online mailbox to send reported messages to: Click in the box to find and select an existing Exchange Online mailbox to use as the reporting mailbox that holds user-reported messages from third-party reporting tools. In organizations with Defender for Office 365 Plan 2, Automatic investigation and response to threats, is triggered which automatically carries out the analysis and clean up actions for you.

    Messages can appear on the User reported settings tab of the Submissions page at https://security.microsoft.com/reportsubmission?viewid=user. The Result value for these entries is Not Submitted to Microsoft. The message formatting requirements are described in the next section.

  • Email notifications section: These options affect the notification email message that's sent to users when an admin selects Mark as and notify on the Submissions page at https://security.microsoft.com/reportsubmission. The following options are available:

    • Results email section:

      • Select Customize results email. In the Customize admin review email notifications flyout that opens, configure the following settings on the Phishing, Junk and No threats found tabs:

        • Email body results text: Enter the custom text to use. You can use different text for Phishing, Junk and No threats found.
        • Email footer text: Enter the custom message footer text to use. The same text is used for Phishing, Junk and No threats found.

        When you're finished in the Customize admin review email notifications flyout, select Confirm to return to the User reported settings page.

    • Automatically email users the results of the investigation: This feature is available only in Defender for Office 365 Plan 2 organizations with automated investigation and response (AIR).

      Note

      This feature is currently in Private Preview, isn't available in all organizations, and is subject to change.

      If a user reports a message as phishing, an investigation in AIR is automatically created. The following options send notification email to the user who reported the message based on the results from AIR (select one or more options):

      • Phishing or malware: An email notification is sent to the user who reported the message as phishing when AIR identifies the threat as phishing, high confidence phishing, or malware.
      • Spam: An email notification is sent to the user who reported the message as phishing when AIR identifies the threat as spam.
      • No threats found: An email notification is sent to the user who reported the message as phishing when AIR identifies no threat.

      For more information, see Automatic user notifications for user reported phishing results in AIR.

    • Customize sender and branding section:

      • Specify a Microsoft 365 mailbox to use ads the From address of email notifications: Select this option and enter the sender's email address in the box that appears. If you don't select this option, the default sender is submissions@messaging.microsoft.com.
      • Replace the Microsoft logo with my organization's logo across all reporting experiences: Select this option to replace the default Microsoft logo that's used in notifications. Before you do this step, follow the instructions in Customize the Microsoft 365 theme for your organization to upload your custom logo.

  • Report from quarantine section > Allow reporting for quarantined messages: Verify that this setting is selected to let users report messages from quarantine as they release quarantined email messages. Otherwise, uncheck this setting.

When you're finished on the User reported settings page, select Save.

Tip

If Monitor reported messages in Microsoft Teams is selected in the Microsoft Teams section when Use a non-Microsoft add-in button is also selected, the settings in the Email notifications sections are available. But, these settings apply only to user-reported Teams messages. For more information, see User reported message settings in Microsoft Teams.

Message submission format for third-party reporting tools

Messages sent by third-party reporting tools to the reporting mailbox required specific formatting so they're correctly identified on the User reported tab on the Submissions page at https://security.microsoft.com/reportsubmission?viewid=user.

Messages that don't follow the required formatting are always identified as phishing.

To correctly identify why the original messages were reported, messages sent to the reporting mailbox must meet the following criteria:

  • The user reported message is unmodified and is included as an uncompressed .EML or .MSG attachment. Don't forward the original user reported message to the reporting mailbox.

    Caution

    Messages that contain multiple attached messages are discarded.

  • The user reported message should contain the following required headers:

    • X-Microsoft-Antispam-Message-Info
    • Message-Id
    • X-Ms-Exchange-Organization-Network-Message-Id
    • X-Ms-Exchange-Crosstenant-Id

    Note

    TenantId in X-Ms-Exchange-Crosstenant-Id should be the same as the tenant.

    X-Microsoft-Antispam-Message-Info should be a valid xmi.

  • The Subject line (Envelope Title) of messages sent to the reporting mailbox must start with one of the following prefix values:

    • 1| or Junk:.
    • 2| or Not junk:.
    • 3| or Phishing:.

    For example:

    • 3|This text in the Subject line is ignored by the system
    • Not Junk:This text in the Subject line is also ignored by the system

Use Exchange Online PowerShell to configure the reported message settings

After you connect to Exchange Online PowerShell, use the *-ReportSubmissionPolicy and *-ReportSubmissionRule cmdlets to manage and configure the user reported settings.

In Exchange Online PowerShell, the basic elements of the user reported settings are:

  • The report submission policy: Turns reporting in Outlook on or off, turns sending reported messages to Microsoft on or off, turns sending reported messages to the reporting mailbox on or off, and most other settings.
  • The report submission rule: Specifies the email address of the reporting mailbox or a blank value when the reporting mailbox isn't used (report messages to Microsoft only).

The difference between these two elements isn't obvious when you manage the user reported settings in the Microsoft Defender portal:

  • An organization has one report submission policy and one report submission rule.

    If you never opened the User reported settings page at https://security.microsoft.com/securitysettings/userSubmission, there's no report submission policy or report submission rule (the Get-ReportSubmissionPolicy and Get-ReportSubmissionRule cmdlets return nothing).

    After you visit the User reported settings page for the first time (even if you don't change any settings), the report submission policy named DefaultReportSubmissionPolicy is created with the default values and is visible in PowerShell.

    Only after you specify a reporting mailbox (used by Microsoft or third-party reporting tools) and save the changes on the User reported settings page is the report submission rule named DefaultReportSubmissionRule created. It might take several seconds before the rule is visible in PowerShell.

    Note

    The default settings on the User reported settings page include Send reported messages to > Microsoft and my reporting mailbox with a blank value for the reporting mailbox. In PowerShell, there's no report submission rule. This default configuration means the reporting mailbox is the global admin's Exchange Online mailbox. The global admin isn't shown as the reporting mailbox in the output of the Get-ReportSubmissionPolicy and Get-ReportSubmissionRule cmdlets or on the User reported settings page until after the first user in the organization reports a message from Outlook. Learn more about what Microsoft does to your submitted messages.

  • You can delete the report submission rule and recreate it with a different name, but the rule is always associated with the report submission policy, and you can't select or change the name of the policy. So, we recommend naming the rule DefaultReportSubmissionRule if you create or recreate the rule.

  • When you specify the email address of the reporting mailbox in the Microsoft Defender portal, that value is primarily set in the report submission rule, but the value is also copied into the related properties in the report submission policy. In PowerShell, when you set the email address in the rule, the value isn't copied into the related properties in the policy. For consistency with the User reported settings page and for clarity, we recommend that you add or update the email address in the policy and the rule.

Use PowerShell to view the report submission policy and the report submission rule

To view the report submission policy, run the following command in Exchange Online PowerShell:

Get-ReportSubmissionPolicy

To view the report submission rule, run the following command:

Get-ReportSubmissionRule

To view both the policy and the rule at the same time, run the following commands:

Write-Output -InputObject `r`n,"Report Submission Policy",("-"*79); Get-ReportSubmissionPolicy; Write-Output -InputObject `r`n,"Report Submission Rule",("-"*79); Get-ReportSubmissionRule

Remember, the report submission policy doesn't exist if any of the following statements are true:

Likewise, the report submission rule doesn't exist if either of the following statements are true:

  • No one ever specified a reporting mailbox on the User reported settings page (but remember, the global admin's Exchange Online mailbox is used by default).
  • No one ever manually created the report submission rule in PowerShell.
  • Someone manually deleted the report submission rule in PowerShell.

So, it's possible that the Get-ReportSubmissionPolicy and Get-ReportSubmissionRule cmdlets return nothing.

For detailed syntax and parameter information, see Get-ReportSubmissionPolicy and Get-ReportSubmissionRule.

Use PowerShell to create the report submission policy and the report submission rule

If the Get-ReportSubmissionPolicy and Get-ReportSubmissionRule cmdlets return no output, you can create the report submission policy and the report submission rule. If you try to create them after they already exist, you get an error.

Always create the report submission policy first, because you specify the report submission policy in the report submission rule.

For detailed syntax and parameter information, see New-ReportSubmissionPolicy and New-ReportSubmissionRule.

Use PowerShell to configure reporting in Outlook with report messages to Microsoft and the reporting mailbox

This example creates the report submission policy with the default settings:

  • Reporting in Outlook is turned on: -EnableThirdPartyAddress $false is the default value, so you don't need to use the parameter to get:

    • Outlook section: Monitor reported messages in Outlook selected.
    • Select an Outlook report button configuration section: Use the built-in Report button in Outlook selected.

  • Reported message destinations section:

    • Send reported messages to: Microsoft and my reporting mailbox is selected: -EnableReportToMicrosoft $true, -ReportJunkToCustomizedAddress $true, -ReportNotJunkToCustomizedAddress $true, and -ReportPhishToCustomizedAddress $true are the default values, so you don't need to use those parameters.

      To populate Add an Exchange Online mailbox to send reported messages to with the email address of the reporting mailbox, use the following cmdlets and parameters:

      • New-ReportSubmissionPolicy: -ReportJunkAddresses <emailaddress>, -ReportNotJunkAddresses <emailaddress>, and -ReportPhishAddresses <emailaddress>.
      • New-ReportSubmissionRule: -SentTo <emailaddress>.

      Note

      The default value of the parameters that identify the reporting mailbox is blank, which means the default reporting mailbox is the global admin's Exchange Online mailbox. The global admin isn't shown as the reporting mailbox in the output of the Get-ReportSubmissionPolicy and Get-ReportSubmissionRule cmdlets or on the User reported settings page in the Defender portal until after the first user in the organization reports a message from Outlook.

      Use the same email address value in all parameters that identify the reporting mailbox.

Other settings:

  • Outlook section > Select an Outlook report button configuration section:

    • When the user reports an email section:

      • Ask the user to confirm before reporting:

        • When you go to the User reported settings page in the Defender portal for the first time (which creates the report submission policy), this setting is not selected (equivalent to -PreSubmitMessageEnabled -$false).

        • When you use PowerShell to create the policy, the default value is -PreSubmitMessageEnabled $true.

          So, to use PowerShell to recreate the default settings, you need to use -PreSubmitMessageEnabled $false.

      • Show a success message after the message is reported:

        • When you go to the User reported settings page in the Defender portal for the first time (which creates the report submission policy), this setting is not selected (equivalent to -PostSubmitMessageEnabled -$false).

        • When you use PowerShell to create the policy, the default value is -PostSubmitMessageEnabled $true.

          So, to use PowerShell to recreate the default settings, you need to use -PostSubmitMessageEnabled $false.

      • Customize messages: Nothing is customized (-EnableCustomizedMsg $false is the default value).

        The syntax to enter customized values for up to 7 different languages with the line split for clarity is:

        -PreSubmitMessageEnabled $true -MultiLanguageSetting LanguageCode1,LanguageCode2...LanguageCode7 `
-MultiLanguagePreSubmitMessageTitleForPhishing "Language1 Before Phishing Title Text","Language2 Before Phishing Title Text",..."Language7 Before Phishing Title Text" `
-MultiLanguagePreSubmitMessageForPhishing "Language1 Before Phishing Description Text","Language2 Before Phishing Description Text",..."Language7 Before Phishing Description Text" `
[-MultiLanguagePreSubmitMessageButtonTextForPhishing "Language1 Before Phishing Info Button Text","Language2 Before Phishing Info Button Text",..."Language7 Before Phishing Info Button Text"] `
[-MultiLanguagePreSubmitMessageButtonLinkForPhishing "Language1 Before Phishing Info Button URL","Language2 Before Phishing Info Button URL",..."Language7 Before Phishing Info Button URL"] `
-MultiLanguagePreSubmitMessageTitleForJunk "Language1 Before Junk Title Text","Language2 Before Junk Title Text",..."Language7 Before Junk Title Text" `
-MultiLanguagePreSubmitMessageForJunk "Language1 Before Junk Description Text","Language2 Before Junk Description Text",..."Language7 Before Junk Description Text" `
[-MultiLanguagePreSubmitMessageButtonTextForJunk "Language1 Before Junk Info Button Text","Language2 Before Junk Info Button Text",..."Language7 Before Junk Info Button Text"] `
[-MultiLanguagePreSubmitMessageButtonLinkForJunk "Language1 Before Junk Info Button URL","Language2 Before Junk Info Button URL",..."Language7 Before Junk Info Button URL"]
-MultiLanguagePreSubmitMessageTitleForNotJunk "Language1 Before Not Junk Title Text","Language2 Before Not Junk Title Text",..."Language7 Before Not Junk Title Text" `
-MultiLanguagePreSubmitMessageForNotJunk "Language1 Before Not Junk Description Text","Language2 Before Not Junk Description Text",..."Language7 Before Not Junk Description Text" `
[-MultiLanguagePreSubmitMessageButtonTextForNotJunk "Language1 Before Not Junk Info Button Text","Language2 Before Not Junk Info Button Text",..."Language7 Before Not Junk Info Button Text"] `
[-MultiLanguagePreSubmitMessageButtonLinkForNotJunk "Language1 Before Not Junk Info Button URL","Language2 Before Not Junk Info Button URL",..."Language7 Before Not Junk Info Button URL"] `
-MultiLanguagePostSubmitMessageTitleForPhishing "Language1 After Phishing Title Text","Language2 After Phishing Title Text",..."Language7 After Phishing Title Text" `
-MultiLanguagePostSubmitMessageForPhishing "Language1 After Phishing Description Text","Language2 After Phishing Description Text",..."Language7 After Phishing Description Text" `
[-MultiLanguagePostSubmitMessageButtonTextForPhishing "Language1 After Phishing Info Button Text","Language2 After Phishing Info Button Text",..."Language7 After Phishing Info Button Text"] `
[-MultiLanguagePostSubmitMessageButtonLinkForPhishing "Language1 After Phishing Info Button URL","Language2 After Phishing Info Button URL",..."Language7 After Phishing Info Button URL"] `
-MultiLanguagePostSubmitMessageTitleForJunk "Language1 After Not Junk Title Text","Language2 After Not Junk Title Text",..."Language7 After Not Junk Title Text" `
-MultiLanguagePostSubmitMessageForJunk "Language1 After Not Junk Description Text","Language2 After Not Junk Description Text",..."Language7 After Not Junk Description Text" `
[-MultiLanguagePostSubmitMessageButtonTextForJunk "Language1 After Not Junk Info Button Text","Language2 After Not Junk Info Button Text",..."Language7 After Not Junk Info Button Text"] `
[-MultiLanguagePostSubmitMessageButtonLinkForJunk "Language1 After Not Junk Info Button URL","Language2 After Not Junk Info Button URL",..."Language7 After Not Junk Info Button URL"]
        • For valid language codes, see New-ReportSubmissionPolicy.
        • The order that you enter the language codes doesn't matter, but you must use the same order for the corresponding MultiLanguagePre* and MultiLanguagePost* parameter values.
        • A text value for each language is required in the MultiLanguage*SubmitMessageTitleFor* and MultiLanguage*SubmitMessageFor* parameters (for example, MultiLanguagePreSubmitMessageTitleForPhishing and MultiLanguagePreSubmitMessageForPhishing). The corresponding MultiLanguage*SubmitMessageButtonTextFor* and MultiLanguage*SubmitMessageButtonLinkFor* are optional, but you must use them both together.
        • For the number of language codes that you specify, you need to provide the same number of blank values for all of the MultiLanguage*SubmitMessage* parameters that you aren't using. For example, if you're using three languages, but you aren't using the MultiLanguagePostSubmitMessageButtonTextForJunk and MultiLanguagePostSubmitMessageButtonLinkForJunk parameters, you need to use the value "","","" for those parameters. You might need to add these blank values for up to 18 of the MultiLanguage*SubmitMessage* parameters.

      Note

      Customized pre-reporting and post-reporting pop-ups are shown when using the Report button in supported versions of Outlook.

      The Microsoft Report Message add-in supports only customized Title and Description values, and only for pre-reporting pop-ups (Report phishing, Report junk, and Report not junk).

      The Microsoft Report Phishing add-in supports all customized values, but only for the Report phishing pre-reporting pop-up.

  • Email notifications section:

    • Results email section:
      • Customize results email: Nothing is entered in the Email body results text or Email footer text boxes on the Phishing, Junk, or No threats found tabs in the flyout (-EnableCustomizedMsg $false is the default value).
      • Automatically email users the results of the investigation.
    • Customize sender and branding section:
      • Specify a Microsoft 365 mailbox to use as the From address of email notifications isn't selected (-EnableCustomNotificationSender $false is the default value).
      • Replace the Microsoft logo with my organization's logo across all reporting experiences isn't selected (-EnableOrganizationBranding $false is the default value).

  • Reporting from quarantine section: Allow reporting for quarantined messages is selected (-DisableQuarantineReportingOption $false is the default value).

In this example, the email address of the reporting mailbox is reportedmessages@contoso.com in Exchange Online (you can't specify an external email address).

$usersub = "reportedmessages@contoso.com"

New-ReportSubmissionPolicy -ReportJunkAddresses $usersub -ReportNotJunkAddresses $usersub -ReportPhishAddresses $usersub -PreSubmitMessageEnabled $false -PostSubmitMessageEnabled $false

New-ReportSubmissionRule -Name DefaultReportSubmissionRule -ReportSubmissionPolicy DefaultReportSubmissionPolicy -SentTo $usersub

Use PowerShell to configure reporting in Outlook with report messages to the reporting mailbox only

This example creates the report submission policy and the report submission rule with the following settings:

  • Reporting in Outlook is turned on: -EnableThirdPartyAddress $false is the default value, so you don't need to use the parameter to get:

    • Outlook section: Monitor reported messages in Outlook selected.
    • Select an Outlook report button configuration section: Use the built-in Report button in Outlook selected.

  • Reported message destinations section:

    • Send reported messages to > My reporting mailbox only: -EnableReportToMicrosoft $false and -EnableUserEmailNotification $true are required. -ReportJunkToCustomizedAddress $true, -ReportNotJunkToCustomizedAddress $true, and -ReportPhishToCustomizedAddress $true are the default values, so you don't need to use those parameters.

      To populate Add an Exchange Online mailbox to send reported messages to with the email address of the reporting mailbox, use the following cmdlets and parameters:

      • New-ReportSubmissionPolicy: -ReportJunkAddresses <emailaddress>, -ReportNotJunkAddresses <emailaddress>, and -ReportPhishAddresses <emailaddress>.
      • New-ReportSubmissionRule: -SentTo <emailaddress>.

      Tip

      The default value of the parameters that identify the reporting mailbox is blank, which means the default reporting mailbox is the global admin's Exchange Online mailbox. The global admin isn't shown as the reporting mailbox in the output of the Get-ReportSubmissionPolicy and Get-ReportSubmissionRule cmdlets until after the first user in the organization reports a message from Outlook.

      Use the same email address value in all parameters that identify the reporting mailbox.

The remaining settings are the default values in "Other settings" as described in the Use PowerShell to configure reporting in Outlook with report messages to Microsoft and the reporting mailbox section.

In this example, the email address of the reporting mailbox is userreportedmessages@fabrikam.com in Exchange Online (you can't specify an external email address).

Tip

The value -ReportChatMessageEnabled $false is required to achieve Send reported messages to > My reporting mailbox only. Even when the ReportChatMessageEnabled property value is $false in PowerShell, the Monitor reported message in Microsoft Teams settings on the User reported settings page is selected. Selecting or unselecting Monitor reported message in Microsoft Teams on the User reported settings page doesn't change the value of the ReportChatMessageEnabled property in PowerShell.

$usersub = "userreportedmessages@fabrikam.com"

New-ReportSubmissionPolicy -EnableReportToMicrosoft $false -EnableUserEmailNotification $true -ReportJunkAddresses $usersub -ReportNotJunkAddresses $usersub -ReportPhishAddresses $usersub -PreSubmitMessageEnabled $false -PostSubmitMessageEnabled $false -ReportChatMessageEnabled $false

New-ReportSubmissionRule -Name DefaultReportSubmissionRule -ReportSubmissionPolicy DefaultReportSubmissionPolicy -SentTo $usersub

Use PowerShell to configure reporting in Outlook with report messages to Microsoft only

This example creates the report submission policy with the following settings:

  • Reporting in Outlook is turned on: -EnableThirdPartyAddress $false is the default value, so you don't need to use the parameter to get:

    • Outlook section: Monitor reported messages in Outlook selected.
    • Select an Outlook report button configuration section: Use the built-in Report button in Outlook selected.

  • Reported message destinations section:

    • Send reported messages to > Microsoft only: -EnableReportToMicrosoft $true is the default value, so you don't need to use the parameter. -ReportJunkToCustomizedAddress $false, -ReportNotJunkToCustomizedAddress $false, and -ReportPhishToCustomizedAddress $false are required.

    Tip

    The default value of the parameters that identify the reporting mailbox is blank, which means the default reporting mailbox is the global admin's Exchange Online mailbox. The global admin isn't shown as the reporting mailbox in the output of the Get-ReportSubmissionPolicy and Get-ReportSubmissionRule cmdlets until after the first user in the organization reports a message from Outlook.

The remaining settings are the default values in "Other settings" as described in the Use PowerShell to configure reporting in Outlook with report messages to Microsoft and the reporting mailbox section.

Tip

The value -ReportChatMessageEnabled $false is required to achieve Send reported messages to > Microsoft only. Even when the ReportChatMessageEnabled property value is $false in PowerShell, the Monitor reported message in Microsoft Teams setting on the User reported settings page is selected. Selecting or unselecting Monitor reported message in Microsoft Teams on the User reported settings page doesn't change the value of the ReportChatMessageEnabled property in PowerShell.

The values -EnableUserEmailNotification $true and -ReportChatMessageToCustomizedAddressEnabled $false are required to achieve Send reported messages to > Microsoft only.

New-ReportSubmissionPolicy -ReportJunkToCustomizedAddress $false -ReportNotJunkToCustomizedAddress $false -ReportPhishToCustomizedAddress $false -PreSubmitMessageEnabled $false -PostSubmitMessageEnabled $false -EnableUserEmailNotification $true -ReportChatMessageToCustomizedAddressEnabled $false -ReportChatMessageEnabled $false

Because a reporting mailbox isn't used, the report submission rule isn't needed or created.

Use PowerShell to configure reporting in Outlook to use third-party reporting tools

This example creates the report submission policy and the report submission rule with the following settings:

  • Reporting in Outlook is turned on:

    • Outlook section: Monitor reported messages in Outlook is selected.
    • Select an Outlook report button configuration section: Use a non-Microsoft add-in button is selected (-EnableThirdPartyAddress $true is required).

  • Reported message destinations section:

    • Send reported messages to > My reporting mailbox only: -EnableReportToMicrosoft $false, -EnableUserEmailNotification $true, -ReportJunkToCustomizedAddress $false, -ReportNotJunkToCustomizedAddress $false, and -ReportPhishToCustomizedAddress $false are required.

      To populate Add an Exchange Online mailbox to send reported messages to with the email address of the reporting mailbox, use the following cmdlets and parameters:

      • New-ReportSubmissionPolicy: -ThirdPartyReportAddresses <emailaddress>, -ReportJunkAddresses <emailaddress>, -ReportNotJunkAddresses <emailaddress>, and -ReportPhishAddresses <emailaddress> are required.
      • New-ReportSubmissionRule: -SentTo <emailaddress> is required.

      Tip

      Use the same email address value in all parameters that identify the reporting mailbox.

The remaining settings are the default values in "Other settings" as described in the Use PowerShell to configure reporting in Outlook with report messages to Microsoft and the reporting mailbox section.

In this example, the email address of the reporting mailbox is thirdpartyreporting@wingtiptoys.com in Exchange Online (you can't specify an external email address).

$usersub = "thirdpartyreporting@wingtiptoys.com"

New-ReportSubmissionPolicy -EnableThirdPartyAddress $true -EnableReportToMicrosoft $false -EnableUserEmailNotification $true -ThirdPartyReportAddresses $usersub -ReportJunkAddresses $usersub -ReportNotJunkAddresses $usersub -ReportPhishAddresses $usersub -PreSubmitMessageEnabled $false -PostSubmitMessageEnabled $false

New-ReportSubmissionRule -Name DefaultReportSubmissionRule -ReportSubmissionPolicy DefaultReportSubmissionPolicy -SentTo $usersub

Use PowerShell to turn off reporting in Outlook

Turning off reporting in Outlook has the following consequences:

  • The built-in Report button and the Microsoft Report Message and Report Phishing add-ins are unavailable in all Outlook platforms.
  • Third-party reporting tools still work, but reported messages don't appear on the User reported tab on the Submissions page in the Defender portal.
  • Allow reporting for quarantined messages (DisableQuarantineReportingOption) is unaffected, and can be enabled or disabled when reporting in Outlook is turned off.

This example creates the report submission policy with reporting in Outlook turned off (Outlook section > Monitor reported messages in Outlook not selected): -EnableThirdPartyAddress $false is the default value, so you don't need to use the parameter. -EnableReportToMicrosoft $false, -EnableThirdPartyAddress $false, -ReportJunkToCustomizedAddress $false, -ReportNotJunkToCustomizedAddress $false, and -ReportPhishToCustomizedAddress $false are required.

Tip

The values -PreSubmitMessageEnabled $true and -PostSubmitMessageEnabled $true are required to achieve Monitor reported messages in Outlook not selected.

New-ReportSubmissionPolicy -EnableReportToMicrosoft $false -ReportJunkToCustomizedAddress $false -ReportNotJunkToCustomizedAddress $false -ReportPhishToCustomizedAddress $false -PreSubmitMessageEnabled $true -PostSubmitMessageEnabled $true

Because a reporting mailbox isn't used, the report submission rule isn't needed or created.

Use PowerShell to modify the report submission policy and the report submission rule

The same settings are available when you modify the report submission policy in PowerShell as when you created the policy as described in the previous section.

When you modify the existing settings in the report submission policy, you might need to undo or nullify other settings that might or might not be configured. And, you might need to create or delete the report submission rule to allow or prevent message reporting to a reporting mailbox.

For detailed syntax and parameter information, see Set-ReportSubmissionPolicy.

The following examples show how to change the user reporting experience without concern for the existing settings or values:

  • Turn on reporting in Outlook if necessary, select Use the built-in Report button in Outlook, and change Send reported messages to to Microsoft and my reporting mailbox with reportedmessages@contoso.com as the reporting mailbox:

    $usersub = "reportedmessages@contoso.com"

Set-ReportSubmissionPolicy -Identity DefaultReportSubmissionPolicy -EnableReportToMicrosoft $true -EnableThirdPartyAddress $false -ThirdPartyReportAddresses $null -ReportJunkToCustomizedAddress $true -ReportJunkAddresses $usersub -ReportNotJunkToCustomizedAddress $true -ReportNotJunkAddresses $usersub -ReportPhishToCustomizedAddress $true -ReportPhishAddresses $usersub -PreSubmitMessageEnabled $false -PostSubmitMessageEnabled $false -ReportChatMessageEnabled $true

    And then run one of the following commands, depending on the existing configuration:

    • If the report submission rule already exists:

      Set-ReportSubmissionRule -Identity DefaultReportSubmissionRule -SentTo $usersub

    • If the report submission rule doesn't exist:

      New-ReportSubmissionRule -Name DefaultReportSubmissionRule -ReportSubmissionPolicy DefaultReportSubmissionPolicy -SentTo $usersub

  • Turn on reporting in Outlook if necessary, select Use the built-in Report button in Outlook, and change Send reported messages to to My reporting mailbox only with userreportedmessages@fabrikam.com as the reporting mailbox:

    $usersub = "userreportedmessages@fabrikam.com"

Set-ReportSubmissionPolicy -Identity DefaultReportSubmissionPolicy -EnableReportToMicrosoft $false -EnableThirdPartyAddress $false -ThirdPartyReportAddresses $null -ReportJunkToCustomizedAddress $true -ReportJunkAddresses $usersub -ReportNotJunkToCustomizedAddress $true -ReportNotJunkAddresses $usersub -ReportPhishToCustomizedAddress $true -ReportPhishAddresses $usersub -PreSubmitMessageEnabled $false -PostSubmitMessageEnabled $false -ReportChatMessageEnabled $false

    And then run one of the following commands, depending on the existing configuration:

    • If the report submission rule already exists:

      Set-ReportSubmissionRule -Identity DefaultReportSubmissionRule -SentTo $usersub

    • If the report submission rule doesn't exist:

      New-ReportSubmissionRule -Name DefaultReportSubmissionRule -ReportSubmissionPolicy DefaultReportSubmissionPolicy -SentTo $usersub

  • Turn on reporting in Outlook if necessary, select Use the built-in Report button in Outlook, and change Send reported messages to to Microsoft only:

    Set-ReportSubmissionPolicy -Identity DefaultReportSubmissionPolicy -EnableReportToMicrosoft $true -EnableThirdPartyAddress $false -ThirdPartyReportAddresses $null -ReportJunkToCustomizedAddress $false -ReportJunkAddresses $null -ReportNotJunkToCustomizedAddress $false -ReportNotJunkAddresses $null -ReportPhishToCustomizedAddress $false -ReportPhishAddresses $null -PreSubmitMessageEnabled $false -PostSubmitMessageEnabled $false -EnableUserEmailNotification $true -ReportChatMessageToCustomizedAddressEnabled $false -ReportChatMessageEnabled $false

    The following command is required only if the report submission rule already exists:

    Get-ReportSubmissionRule | Remove-ReportSubmissionRule

  • Turn on reporting in Outlook if necessary, select Use a non-Microsoft add-in button, and use thirdpartyreporting@wingtiptoys.com as the reporting mailbox:

    $usersub = "thirdpartyreporting@wingtiptoys.com"

Set-ReportSubmissionPolicy -Identity DefaultReportSubmissionPolicy -EnableReportToMicrosoft $false -EnableThirdPartyAddress $true -ThirdPartyReportAddresses $usersub -ReportJunkToCustomizedAddress $true -ReportJunkAddresses $usersub -ReportNotJunkToCustomizedAddress $true -ReportNotJunkAddresses $usersub -ReportPhishToCustomizedAddress $true -ReportPhishAddresses $usersub -PreSubmitMessageEnabled $false -PostSubmitMessageEnabled $false -ReportChatMessageEnabled $true

    And then run one of the following commands, depending on the existing configuration:

    • If the report submission rule already exists:

      Set-ReportSubmissionRule -Identity DefaultReportSubmissionRule -SentTo $usersub

    • If the report submission rule doesn't exist:

      New-ReportSubmissionRule -Name DefaultReportSubmissionRule -ReportSubmissionPolicy DefaultReportSubmissionPolicy -SentTo $usersub

  • Turn off reporting in Outlook (Monitor reported messages in Outlook isn't selected):

    Set-ReportSubmissionPolicy -Identity DefaultReportSubmissionPolicy -EnableReportToMicrosoft $false -EnableThirdPartyAddress $false -ThirdPartyReportAddresses $null -ReportJunkToCustomizedAddress $false -ReportJunkAddresses $null -ReportNotJunkToCustomizedAddress $false -ReportNotJunkAddresses $null -ReportPhishToCustomizedAddress $false -ReportPhishAddresses $null -PreSubmitMessageEnabled $true -PostSubmitMessageEnabled $true

    And then run the following command if the report submission rule already exists:

    Get-ReportSubmissionRule | Remove-ReportSubmissionRule

The only meaningful setting that you can modify in the report submission rule is the email address of the reporting mailbox (the SentTo parameter value). For example:

Set-ReportSubmissionRule -Identity DefaultReportSubmissionRule -SentTo newemailaddress@contoso.com

Note

If you change the email address of the reporting mailbox in the report submission rule, be sure to change the corresponding values in the report submissions policy. For example:

  • ThirdPartyReportAddresses
  • ReportJunkAddresses, ReportNotJunkAddresses, and ReportPhishAddresses

For detailed syntax and parameter information, see Set-ReportSubmissionRule.

To temporarily disable sending email messages to the reporting mailbox without deleting the report submission rule, use Disable-ReportSubmissionRule. For example:

Get-ReportSubmissionRule | Disable-ReportSubmissionRule -Confirm:$false

To enable the report submission rule, use Enable-ReportSubmissionRule. For example:

Get-ReportSubmissionRule | Disable-ReportSubmissionRule -Confirm:$false

Use PowerShell to remove the report submission policy and the report submission rule

To start over with the default settings of the report submission policy, you can delete it and recreate it. Removing the report submission policy doesn't remove the report submission rule, and vice-versa.

To remove the report submission policy, run the following command in Exchange Online PowerShell:

Remove-ReportSubmissionPolicy -Identity DefaultReportSubmissionPolicy

To remove the report submission rule, run the following command:

Get-ReportSubmissionRule | Remove-ReportSubmissionRule

To remove both the report submission policy and report submission rule in the same command without a confirmation, run the following command:

Remove-ReportSubmissionPolicy -Identity DefaultReportSubmissionPolicy; Get-ReportSubmissionRule | Remove-ReportSubmissionRule -Confirm:$false

For detailed syntax and parameter information, see Remove-ReportSubmissionPolicy and Remove-ReportSubmissionRule.