Merge pull request #4687 from MicrosoftDocs/main

m365-skilling-repo-management[bot] · web-flow · commit d35e338ebc64 · 2025-08-06T17:36:01.000Z
[AutoPublish] main to live - 08/06 10:33 PDT | 08/06 23:03 IST
diff --git a/defender-office-365/air-view-investigation-results.md b/defender-office-365/air-view-investigation-results.md
@@ -349,7 +349,7 @@ On the investigation details page, the **Entities** tab shows details about the
 
 The **Entities** tab is organized by a view selection pane (a summary view and a view for each entity type) and a corresponding details table for that view:
 
-- **Evidence summary** view: This is the default view.
+- **Evidence summary** view: This view is the default.
 
   You can sort the entries in the details table by clicking on an available column header. Select :::image type="icon" source="media/m365-cc-sc-customize-icon.png" border="false"::: **Customize columns** to change the columns that are shown. By default, all available columns are selected:
 
diff --git a/defender-office-365/anti-phishing-policies-mdo-configure.md b/defender-office-365/anti-phishing-policies-mdo-configure.md
@@ -112,7 +112,7 @@ For anti-phishing policy procedures in organizations without Defender for Office
 5. On the **Phishing threshold & protection** page, configure the following settings:
 
    - **Phishing email threshold**: Use the slider to select one of the following values:
-     - **1 - Standard** (This is the default value.)
+     - **1 - Standard** (This value is the default.)
      - **2 - Aggressive**
      - **3 - More aggressive**
      - **4 - Most aggressive**
diff --git a/defender-office-365/anti-spam-policies-asf-settings-about.md b/defender-office-365/anti-spam-policies-asf-settings-about.md
@@ -52,7 +52,7 @@ For each ASF setting, the following options are available in anti-spam policies:
 - **On**: ASF adds the corresponding X-header field to the message:
   - For [Increase spam score settings](#increase-spam-score-settings), the message has a higher chance of being marked as**Spam**.
   - For [Mark as spam settings](#mark-as-spam-settings), the message is marked as **Spam** or **High confidence spam**.
-- **Off**: The ASF setting is disabled. This is the default value.
+- **Off**: The ASF setting is disabled. This value is the default.
 - **Test**: The ASF setting is in Test Mode. What happens to the message is determined by the **Test mode** (_TestModeAction_) value:
   - **None**: Message delivery is unaffected by the ASF detection. The message is still subject to other types of filtering and rules.
   - **Add default X-header text** (_AddXHeader_): The X-header value `X-CustomSpam: This message was filtered by the custom spam filter option` is added to the message. You can use this value in Inbox rules (not mail flow rules) to affect the delivery of the message.
diff --git a/defender-office-365/attack-simulation-training-end-user-notifications.md b/defender-office-365/attack-simulation-training-end-user-notifications.md
@@ -111,7 +111,7 @@ On the details flyout from the **Tenant notifications** tab only, select **Edit
    - **From display name**: Enter the display name of the sender.
    - **From email address**: Enter the email address of the sender.
    - **Select the language of the email**: Select one of the following languages: **Chinese (Simplified)**, **Chinese (Traditional, Taiwan)**, **English**, **French**, **German**, **Italian**, **Japanese**, **Korean**, **Portuguese**, **Russian**, **Spanish**, **Dutch**, **Polish**, **Arabic**, **Finnish**, **Greek**, **Hungarian**, **Indonesian**, **Norwegian Bokmål**, **Romanian**, **Slovak**, **Swedish**, **Thai**, **Turkish**, **Vietnamese**, **Catalan**, **Croatian**, or **Slovenian**.
-   - **Mark this as the default language**: Because this is the first and only language for the notification, this language value is selected as the default, and you can't change it.
+   - **Mark this as the default language**: Because this language is the first and only language for the notification, this language value is selected as the default, and you can't change it.
    - **Subject**: The default that's used depends on the notification type that you selected in the previous step, but you can change it:
      - Positive reinforcement: **Thank you for reporting a phish!**
      - Simulation: **Thank you for participating in a phishing campaign!**
diff --git a/defender-office-365/attack-simulation-training-simulation-automations.md b/defender-office-365/attack-simulation-training-simulation-automations.md
@@ -276,12 +276,12 @@ Use the following options on the page to assign trainings as part of the simulat
 
 - **Preferences** section: In **Select training content preference**, choose one of the following options in the dropdown list:
 
-  - **Microsoft training experience (Recommended)**: This is the default value. This value has the following associated options to configure on the page:
+  - **Microsoft training experience (Recommended)**: This value is the default. This value has the following associated options to configure on the page:
     - Select one of the following values:
-      - **Assign training for me (Recommended)**: This is the default value. We assign training based on a user's previous simulation and training results.
+      - **Assign training for me (Recommended)**: This value is the default. We assign training based on a user's previous simulation and training results.
       - **Select training courses and modules myself**: If you select this value, the next step in the wizard is **Training assignment** where you find and select trainings. The steps are described in the [Training assignment](#training-assignment) subsection.
     - **Due date** section: In **Select a training due date**, choose one of the following values:
-      - **30 days after simulation ends** (this is the default value)
+      - **30 days after simulation ends** (this value is the default)
       - **15 days after simulation ends**
       - **7 days after simulation ends**
 
@@ -291,7 +291,7 @@ Use the following options on the page to assign trainings as part of the simulat
     - **Custom training description**
     - **Custom training duration (in minutes)**: The default value is 0, which means there's no specified duration for the training.
     - **Due date** section: In **Select a training due date**, choose one of the following values:
-      - **30 days after simulation ends** (this is the default value)
+      - **30 days after simulation ends** (this value is the default)
       - **15 days after simulation ends**
       - **7 days after simulation ends**
 
diff --git a/defender-office-365/attack-simulation-training-simulations.md b/defender-office-365/attack-simulation-training-simulations.md
@@ -303,12 +303,12 @@ Use the following options on the page to assign trainings as part of the simulat
 
 - **Preferences** section: In **Select training content preference**, choose one of the following options in the dropdown list:
 
-  - **Microsoft training experience (Recommended)**: This is the default value. This value has the following associated options to configure on the page:
+  - **Microsoft training experience (Recommended)**: This value is the default. This value has the following associated options to configure on the page:
     - Select one of the following values:
-      - **Assign training for me (Recommended)**: This is the default value. We assign training based on a user's previous simulation and training results.
+      - **Assign training for me (Recommended)**: This value is the default. We assign training based on a user's previous simulation and training results.
       - **Select training courses and modules myself**: If you select this value, the next step in the wizard is **Training assignment** where you find and select trainings. The steps are described in the [Training assignment](#training-assignment) subsection.
     - **Due date** section: In **Select a training due date**, choose one of the following values:
-      - **30 days after simulation ends** (this is the default value)
+      - **30 days after simulation ends** (this value is the default)
       - **15 days after simulation ends**
       - **7 days after simulation ends**
 
@@ -318,7 +318,7 @@ Use the following options on the page to assign trainings as part of the simulat
     - **Custom training description**
     - **Custom training duration (in minutes)**: The default value is 0, which means there's no specified duration for the training.
     - **Due date** section: In **Select a training due date**, choose one of the following values:
-      - **30 days after simulation ends** (this is the default value)
+      - **30 days after simulation ends** (this value is the default)
       - **15 days after simulation ends**
       - **7 days after simulation ends**
 
@@ -427,7 +427,7 @@ On the **Select end user notification** page, select from the following notifica
 - **Do not deliver notifications**: No other configuration options are available on the page. Users don't receive **Training assignment notifications**, **Training reminder notifications** or **Positive reinforcement notifications** from the simulation. Select **Proceed** in the warning dialog.
 
 - **Microsoft default notification (recommended)**: The notifications that users receive are shown on the page:
-  - **Microsoft default positive reinforcement notification** (for the **How-to Guide** [social engineering technique](#select-a-social-engineering-technique), this is the only available notification)
+  - **Microsoft default positive reinforcement notification** (for the **How-to Guide** [social engineering technique](#select-a-social-engineering-technique), this notification is the only available notification)
   - **Microsoft default training assignment notification**
   - **Microsoft default training reminder notification**
 
diff --git a/defender-office-365/campaigns.md b/defender-office-365/campaigns.md
@@ -329,7 +329,7 @@ The tabs in the campaign details flyout allow you to further investigate the cam
   - **SPF passed**: The sender was authenticated by the [Sender Policy Framework (SPF)](email-authentication-spf-configure.md). A sender that doesn't pass SPF validation indicates an unauthenticated sender, or the message is spoofing a legitimate sender.
 
 - **Senders**
-  - **Sender**: This is the actual sender address in the SMTP **MAIL FROM** command, which isn't necessarily the **From:** email address that users see in their email clients.
+  - **Sender**: This address is the actual sender address in the SMTP **MAIL FROM** command, which isn't necessarily the **From:** email address that users see in their email clients.
   - **Total count**
   - **Inboxed**
   - **Not Inboxed**
diff --git a/defender-office-365/email-authentication-dkim-configure.md b/defender-office-365/email-authentication-dkim-configure.md
@@ -311,10 +311,10 @@ If you'd rather use PowerShell to enable DKIM signing of outbound messages using
         ```
 
         - The _BodyCanonicalization_ parameter specifies the sensitivity level to changes in the message body:
-          - Relaxed: Changes in whitespace and changes in empty lines at the end of the message body are tolerated. This is the default value.
+          - Relaxed: Changes in whitespace and changes in empty lines at the end of the message body are tolerated. This value is the default.
           - Simple: Only changes in empty lines at the end of the message body are tolerated.
         - The _HeaderCanonicalization_ parameter specifies the sensitivity level to changes in the message header:
-          - Relaxed: Common modifications to the message header are tolerated. For example, header field line rewrapping, changes in unnecessary whitespace or empty lines, and changes in case for header fields. This is the default value.
+          - Relaxed: Common modifications to the message header are tolerated. For example, header field line rewrapping, changes in unnecessary whitespace or empty lines, and changes in case for header fields. This value is the default.
           - Simple: No changes to the header fields are tolerated.
         - The _KeySize_ parameter specifies the bit size of the public key in the DKIM record:
            - 1024 (default)
@@ -367,10 +367,10 @@ If you'd rather use PowerShell to enable DKIM signing of outbound messages using
    ```
 
    - The _BodyCanonicalization_ parameter specifies the sensitivity level to changes in the message body:
-     - Relaxed: Changes in whitespace and changes in empty lines at the end of the message body are tolerated. This is the default value.
+     - Relaxed: Changes in whitespace and changes in empty lines at the end of the message body are tolerated. This value is the default.
      - Simple: Only changes in empty lines at the end of the message body are tolerated.
    - The _HeaderCanonicalization_ parameter specifies the sensitivity level to changes in the message header:
-     - Relaxed: Common modifications to the message header are tolerated. For example, header field line rewrapping, changes in unnecessary whitespace or empty lines, and changes in case for header fields. This is the default value.
+     - Relaxed: Common modifications to the message header are tolerated. For example, header field line rewrapping, changes in unnecessary whitespace or empty lines, and changes in case for header fields. This value is the default.
      - Simple: No changes to the header fields are tolerated.
 
    For example:
diff --git a/defender-office-365/mdo-deployment-guide.md b/defender-office-365/mdo-deployment-guide.md
@@ -283,7 +283,7 @@ The important parts of user message reporting are:
 - Non-Microsoft reporting tools that use the [supported message submission format](submissions-user-reported-messages-custom-mailbox.md#message-submission-format-for-non-microsoft-reporting-tools).
 
 - **Where do user reported messages go?**: You have the following options:
-  - To a designated reporting mailbox and to Microsoft (this is the default value).
+  - To a designated reporting mailbox and to Microsoft (this value is the default).
   - To a designated reporting mailbox only.
   - To Microsoft only.
 
diff --git a/defender-office-365/outbound-spam-policies-configure.md b/defender-office-365/outbound-spam-policies-configure.md
@@ -117,7 +117,7 @@ You can configure outbound spam policies in the Microsoft Defender portal or in
 
      For all actions, the senders specified in the **User restricted from sending email** alert policy (and in the now redundant **Notify these users and groups if a sender is blocked due to sending outbound spam** setting on this page) receive email notifications.
 
-     - **Restrict the user from sending mail until the following day**: This is the default value. Email notifications are sent, and the user is unable to send any more messages until the following day, based on UTC time.
+     - **Restrict the user from sending mail until the following day**: This value is the default. Email notifications are sent, and the user is unable to send any more messages until the following day, based on UTC time.
        - The alert policy named **User restricted from sending email** notifies admins (via email and on the **Incidents & alerts** \> **View alerts** page).
        - Any recipients specified in the **Notify specific people if a sender is blocked due to sending outbound spam** setting in the policy are also notified.
        - The user is unable to send any more messages until the following day, based on UTC time.
@@ -128,7 +128,7 @@ You can configure outbound spam policies in the Microsoft Defender portal or in
 
      Select one of the following actions from the **Automatic forwarding rules** dropdown list:
 
-     - **Automatic - System-controlled**: This is the default value. This value is now the same as **Off - Forwarding is disabled**. When this value was originally introduced, it was equivalent to **On - Forwarding is enabled**. Over time, thanks to the principles of [secure by default](secure-by-default.md), the effect of this value was eventually changed to **Off - Forwarding is disabled** for all customers. For more information, see [this blog post](https://techcommunity.microsoft.com/blog/exchange/all-you-need-to-know-about-automatic-email-forwarding-in-exchange-online/2074888).
+     - **Automatic - System-controlled**: This value is the default. This value is now the same as **Off - Forwarding is disabled**. When this value was originally introduced, it was equivalent to **On - Forwarding is enabled**. Over time, thanks to the principles of [secure by default](secure-by-default.md), the effect of this value was eventually changed to **Off - Forwarding is disabled** for all customers. For more information, see [this blog post](https://techcommunity.microsoft.com/blog/exchange/all-you-need-to-know-about-automatic-email-forwarding-in-exchange-online/2074888).
      - **On - Forwarding is enabled**: Automatic external email forwarding isn't disabled by the policy.
      - **Off - Forwarding is disabled**: All automatic external email forwarding is disabled by the policy.
 
diff --git a/defender-office-365/outbound-spam-policies-external-email-forwarding.md b/defender-office-365/outbound-spam-policies-external-email-forwarding.md
@@ -41,7 +41,7 @@ The following types of automatic forwarding are available in Microsoft 365:
 
 You can use outbound spam filter policies to control automatic forwarding to external recipients. Three settings are available:
 
-- **Automatic - System-controlled**: This is the default value. This value is now the same as **Off - Forwarding is disabled**. When this value was originally introduced, it was equivalent to **On - Forwarding is enabled**. Over time, thanks to the principles of [secure by default](secure-by-default.md), the effect of this value was eventually changed to **Off - Forwarding is disabled** for all customers. For more information, see [this blog post](https://techcommunity.microsoft.com/blog/exchange/all-you-need-to-know-about-automatic-email-forwarding-in-exchange-online/2074888).
+- **Automatic - System-controlled**: This value is the default. This value is now the same as **Off - Forwarding is disabled**. When this value was originally introduced, it was equivalent to **On - Forwarding is enabled**. Over time, thanks to the principles of [secure by default](secure-by-default.md), the effect of this value was eventually changed to **Off - Forwarding is disabled** for all customers. For more information, see [this blog post](https://techcommunity.microsoft.com/blog/exchange/all-you-need-to-know-about-automatic-email-forwarding-in-exchange-online/2074888).
 - **On - Forwarding is enabled**: Automatic external forwarding is allowed and not restricted.
 - **Off - Forwarding is disabled**: Automatic external forwarding is disabled and results in a non-delivery report (also known as an NDR or bounce message) to the sender.
 
diff --git a/defender-office-365/protection-stack-microsoft-defender-for-office365.md b/defender-office-365/protection-stack-microsoft-defender-for-office365.md
@@ -134,7 +134,7 @@ The last stage takes place after mail or file delivery, acting on mail that is i
 
 ## The filtering stack diagram
 
-The final diagram (as with all parts of the diagram composing it) *is subject to change as the product grows and develops*. Bookmark this page and use the **feedback** option you'll find at the bottom if you need to ask after updates. For your records, this is the stack with all the phases in order:
+The final diagram (as with all parts of the diagram composing it) _is subject to change as the product grows and develops_. Bookmark this page and use the **feedback** option at the bottom of the page if you need to ask after updates. For your records, the following diagram shows the stack with all the phases in order:
 
 :::image type="content" source="media/mdo-filtering-stack/mdo-filter-stack-phase5.PNG" alt-text="All the phases of filtering in Defender for Office 365 in order, from 1 to 4" lightbox="media/mdo-filtering-stack/mdo-filter-stack-phase5.PNG":::
 
diff --git a/defender-office-365/reports-email-security.md b/defender-office-365/reports-email-security.md
@@ -109,7 +109,7 @@ On the **Compromised users** page, the :::image type="icon" source="media/m365-c
 
 ## Mailflow status report
 
-The **Mailflow status report** is a smart report that shows information about incoming and outgoing email, spam detections, malware, email identified as "good", and information about email allowed or blocked on the edge. This is the only report that contains edge protection information. The report shows how much email is blocked before entering the service for examination by Microsoft 365.
+The **Mailflow status report** is a smart report that shows information about incoming and outgoing email, spam detections, malware, email identified as "good", and information about email allowed or blocked on the edge. This report is the only report that contains edge protection information. The report shows how much email is blocked before entering the service for examination by Microsoft 365.
 
 > [!TIP]
 >
diff --git a/defender-office-365/safe-attachments-about.md b/defender-office-365/safe-attachments-about.md
diff --git a/defender-office-365/safe-attachments-policies-configure.md b/defender-office-365/safe-attachments-policies-configure.md
diff --git a/defender-office-365/safe-links-about.md b/defender-office-365/safe-links-about.md
diff --git a/defender-office-365/submissions-teams.md b/defender-office-365/submissions-teams.md
diff --git a/defender-office-365/submissions-user-reported-messages-custom-mailbox.md b/defender-office-365/submissions-user-reported-messages-custom-mailbox.md
