Merge branch 'main' of https://github.com/MicrosoftDocs/SupportArticles-docs-pr into sql2022-cu23

Author: haywoodsloan

.openpublishing.redirection.exchange.json

@@ -6,7 +6,7 @@
     },
     {
       "source_path": "Exchange/ExchangeServer/Administration/exchange-2013-end-of-support.md",
-      "redirect_url": "exchange-2016-2019-end-of-support"
+      "redirect_url": "exchange-2019-2016-end-of-support"
     },
     {
       "source_path": "Exchange/ExchangeOnline/outlook-on-the-web-issues/archive-mailbox-not-visible.md",

Exchange/ExchangeHybrid/administration/hybrid-412-cookies-disabled-error.md

@@ -4,18 +4,19 @@ description: Fixes a disabled cookies error that's triggered when you click hybr
 author: cloud-writer
 ms.author: meerak
 manager: dcscontentpm
+ms.reviewer: v-mosha, v-six, v-kccross
 audience: ITPro
 ms.topic: troubleshooting
 ms.custom: 
   - sap:Hybrid
   - Exchange Hybrid
   - CSSTroubleshoot
-ms.reviewer: v-mosha, v-six
 appliesto: 
   - Exchange Online
 search.appverid: MET150
 ms.date: 01/24/2024
 ---
+
 # 412 Cookies Are Disabled when you click hybrid in the Exchange admin center
 
 _Original KB number:_   2888500
@@ -42,11 +43,11 @@ This issue may occur for one or more of the following reasons:
 To resolve this issue, follow these steps:
 
 1. Make sure that the computer's system date and time are set correctly.
-2. Clear cookies from the web browser. The steps for doing this vary, depending on the browser that you're using. If you're using Internet Explorer, see [How to delete cookie files in Internet Explorer](https://support.microsoft.com/help/278835).
-3. Enable the option to accept cookies. The steps for doing this vary, depending on the browser that you're using. To do this in Internet Explorer, follow these steps:
+1. Clear cookies from the web browser. The steps for doing this vary, depending on the browser that you're using.
+1. Enable the option to accept cookies. The steps for doing this vary, depending on the browser that you're using. To do this in Internet Explorer, follow these steps:
 
    1. On the **Tools** menu, select **Internet options**, and then select the **Privacy** tab.
-   2. Under **Settings**, move the slider to the level that's appropriate for you, and then click **OK**.
+   1. Under **Settings**, move the slider to the level that's appropriate for you, and then click **OK**.
 
    > [!NOTE]
    > Blocking cookies might prevent some pages from being displayed correctly.

Exchange/ExchangeHybrid/calendars/freebusy-lookups-stop-working.md

@@ -4,13 +4,13 @@ description: Discusses an issue that prevents users from looking up free/busy in
 author: cloud-writer
 ms.author: meerak
 manager: dcscontentpm
+ms.reviewer: timothyh, v-six, v-kccross
 audience: ITPro
 ms.topic: troubleshooting
 ms.custom: 
   - sap:Calendaring
   - Exchange Hybrid
   - CSSTroubleshoot
-ms.reviewer: timothyh, v-six
 appliesto: 
   - Exchange Online
   - Exchange Server 2016 Enterprise Edition
@@ -20,6 +20,7 @@ appliesto:
 search.appverid: MET150
 ms.date: 01/24/2024
 ---
+
 # Free/busy lookups stop working in a cross-premises environment or an Exchange Server hybrid deployment
 
 > [!NOTE]

Exchange/ExchangeHybrid/calendars/hybird-free-busy-diagnostic.md

@@ -4,18 +4,19 @@ description: Describes the data that's collected by the Exchange Online Free/Bus
 author: cloud-writer
 ms.author: meerak
 manager: dcscontentpm
+ms.reviewer: farshadt, v-six, v-kccross
 audience: ITPro
 ms.topic: troubleshooting
 ms.custom: 
   - sap:Calendaring
   - Exchange Hybrid
   - CSSTroubleshoot
-ms.reviewer: farshadt, v-six
 appliesto: 
   - Exchange Online
 search.appverid: MET150
 ms.date: 08/13/2024
 ---
+
 # Exchange Online Hybrid Free/Busy Diagnostic
 
 <!-- This article has been reviewed and approved for the specific use of global admin perms.  -->
@@ -81,7 +82,3 @@ _Original KB number:_ &nbsp; 2957394
 |Get-mailbox -arbitration cmdlet output|\<HYBRIDSERVERNAME>_Arbitration Mailbox_FL.TXT|
 |Get-PublicFolderClientPermission cmdlet output|\<HYBRIDSERVERNAME>_NON_IPM_SUBTREE_SCHEDULE_FREE_BUSY_FIRST ORGANIZATION_EXTERNAL_FYDIBOHF25SPDLT.log_FL.TXT|
 |Get-PublicFolder cmdlet output|\<HYBRIDSERVERNAME>_NON_IPM_SUBTREE_SCHEDULE_FREE BUSY.log_FL|
-
-## References
-
-For more information about Microsoft Automated Troubleshooting Services and about the Support Diagnostics Platform, see [Information about Microsoft Automated Troubleshooting Services and Support Diagnostic Platform](https://support.microsoft.com/help/2598970).

Exchange/ExchangeHybrid/email-delivery/email-messages-incorrectly-quarantined.md

@@ -13,7 +13,7 @@ ms.custom:
 ms.reviewer: alehud, v-six
 appliesto: 
   - Exchange Online
-  - Exchange Online Protection
+  - Built-in security features for all cloud mailboxes
   - Exchange Server 2010 Enterprise
   - Exchange Server 2010 Standard
   - Exchange Server 2013 Enterprise

Exchange/ExchangeHybrid/email-delivery/emails-are-rejected-and-receive-ndrs.md

@@ -13,7 +13,7 @@ ms.custom:
 ms.reviewer: jhayes, rorylen, v-six
 appliesto: 
   - Exchange Online
-  - Exchange Online Protection
+  - Built-in security features for all cloud mailboxes
   - Exchange Server 2010 Enterprise
   - Exchange Server 2010 Standard
 search.appverid: MET150
@@ -32,26 +32,26 @@ You run the Hybrid Configuration wizard in Exchange Server 2010 to set up a shar
 
 ## Cause
 
-This issue can occur if the IP addresses that are associated with Exchange Online Protection changed. These IP addresses aren't automatically updated in the on-premises environment. Therefore, the IP addresses that are set in the on-premises Exchange Online Protection receive connector may become invalid. When this issue occurs, mail that's routed from Microsoft 365 users through Exchange Online Protection to the on-premises environment may be rejected.
+This issue can occur if the IP addresses that are associated with Microsoft 365 changed. These IP addresses aren't automatically updated in the on-premises environment. Therefore, the IP addresses that are set in the on-premises receive connector for Microsoft 365 may become invalid. When this issue occurs, mail that's routed from Microsoft 365 users to the on-premises environment may be rejected.
 
 ## Resolution
 
 To fix this issue, use the following steps:
 
-- Rerun the Hybrid Configuration wizard. Rerunning the wizard configures the on-premises Exchange Online Protection receive connector to use the correct IP addresses.
+- Rerun the Hybrid Configuration wizard. Rerunning the wizard configures the on-premises receive connector for Microsoft 365 to use the correct IP addresses.
 
   > [!NOTE]
   > This step applies only to the Hybrid Configuration wizard in Exchange Server 2010. When you run the Hybrid Configuration wizard in Exchange Server 2013, no receive connectors are created or are necessary.
 
-- Manually update the IP addresses that are listed under **Receive mail from remote servers that have these IP addresses** for the on-premises Exchange Online Protection receive connector.
+- Manually update the IP addresses that are listed under **Receive mail from remote servers that have these IP addresses** for the on-premises receive connector for Microsoft 365.
 
 ## More information
 
-In a shared namespace and centralized mail control scenario, an Exchange Online Protection receive connector must be created on the hybrid Exchange 2010 hub transport server to make sure that the on-premises environment receives mail from Microsoft 365 users. The Hybrid Configuration wizard creates the receive connector on the appropriate Exchange 2010 server. Then, the wizard configures the connector with the IP addresses to enable incoming Exchange Online Protection traffic from Microsoft 365 users to be routed to the on-premises environment.
+In a shared namespace and centralized mail control scenario, an receive connector for Microsoft 365 must be created on the hybrid Exchange 2010 Hub transport server to make sure that the on-premises environment receives mail from Microsoft 365 users. The Hybrid Configuration wizard creates the receive connector on the appropriate Exchange 2010 server. Then, the wizard configures the connector with the IP addresses to enable incoming traffic from Microsoft 365 users to be routed to the on-premises environment.
 
-The following screenshot shows an example of an Exchange Online Protection receive connector that the Hybrid Configuration wizard creates.
+The following screenshot shows an example of an receive connector for Microsoft 365 that the Hybrid Configuration wizard creates.
 
-:::image type="content" source="media/emails-are-rejected-and-receive-ndrs/example-of-eop-receive-connector.png" alt-text="Screenshot of an Exchange Online Protection receive connector.":::
+:::image type="content" source="media/emails-are-rejected-and-receive-ndrs/example-of-eop-receive-connector.png" alt-text="Screenshot of a Microsoft 365 receive connector.":::
 
 For more information about the Hybrid Configuration wizard in Exchange 2010, see [Hybrid Deployments with the Hybrid Configuration wizard](/previous-versions/office/exchange-server-2010/hh529920(v=exchg.141)).
 

Exchange/ExchangeHybrid/email-delivery/hybrid-messages-not-routed-through-on-premises.md

@@ -13,7 +13,7 @@ ms.custom:
 ms.reviewer: joelric, v-six
 appliesto: 
   - Exchange Online
-  - Exchange Online Protection
+  - Built-in security features for all cloud mailboxes
   - Exchange Server 2016 Enterprise Edition
   - Exchange Server 2016 Standard Edition
   - Exchange Server 2013 Enterprise
@@ -33,11 +33,11 @@ Consider the following scenario:
 - You configured the outbound send connector in Exchange Online to use a remote domain of "*", and you enabled centralized mail transport on that connector.
 - A user or application in the on-premises organization sends an email message to a mailbox that's hosted in Exchange Online, for example, *[email protected]*. And the Exchange Online recipient, *[email protected]*, has a forwarding SMTP address that's set to an external recipient (*[email protected]*).
 
-In this scenario, the message tracking logs show the message that was forwarded to *[email protected]* isn't routed back through the on-premises organization, as expected. Instead, the message is sent directly through Exchange Online Protection.
+In this scenario, the message tracking logs show the message that was forwarded to *[email protected]* isn't routed back through the on-premises organization, as expected. Instead, the message is sent directly through Microsoft 365.
 
 ## More information
 
-This behavior is by design. To forward the message, an exact copy of the original message is created and sent to the external recipient. Mail routing logic sees that this new message originated in the on-premises environment and therefore doesn't send the message back to the on-premises environment. Instead, it's routed directly to the external recipient domain through Exchange Online Protection.
+This behavior is by design. To forward the message, an exact copy of the original message is created and sent to the external recipient. Mail routing logic sees that this new message originated in the on-premises environment and therefore doesn't send the message back to the on-premises environment. Instead, it's routed directly to the external recipient domain through Microsoft 365.
 
 This behavior also applies to other similar scenarios. For example, email is sent from on-premises to a distribution group hosted in Exchange Online, and there is an external recipient in the distribution group. In this scenario, email sent to that external recipient will be routed directly instead of following centralized mail routing, because the message originates from the on-premises environment.
 

Exchange/ExchangeHybrid/send-emails/emails-show-addresses-not-display-names-in-from.md

@@ -41,7 +41,7 @@ To fix this issue, follow these steps:
 
 1. Check the mail route.
 
-    The simplest route is Exchange 2010 mailbox server to Exchange 2010 hub server (hybrid server) to the Exchange Online Protection (EOP) inbound connector to Exchange Online. Make sure that there are no unnecessary network devices such as anti-spam gateway devices between the Exchange 2010 hub server (hybrid server) and EOP. Those devices could remove the necessary header.
+    The simplest route is Exchange 2010 mailbox server to Exchange 2010 hub server (hybrid server) to the inbound connector in Microsoft 365. Make sure that there are no unnecessary network devices such as anti-spam gateway devices between the Exchange 2010 hub server (hybrid server) and Microsoft 365. Those devices could remove the necessary header.
 
 2. Check the remote domain of the on-premises Exchange server. To do this, follow these steps:
 
@@ -72,9 +72,9 @@ To fix this issue, follow these steps:
    3. In the output, make sure that the `TrustedMailnboundEnabled` attribute is set to **True**.
    4. If the attribute in step 3C isn't set to **True**, use the `Set-RemoteDomain` command to change the value to **True**.
 
-4. Make sure that Transport Layer Security (TLS) is implemented and enabled in both environments and that the fully qualified domain name (FQDN) is set correctly. Check the on-premises send connector and the EOP inbound connector by using the Exchange Server Deployment Assistant at [Exchange Deployment Assistant](/exchange/exchange-deployment-assistant?view=exchserver-2019&preserve-view=true).
+4. Make sure that Transport Layer Security (TLS) is implemented and enabled in both environments and that the fully qualified domain name (FQDN) is set correctly. Check the on-premises send connector and the Microsoft 365 inbound connector by using the Exchange Server Deployment Assistant at [Exchange Deployment Assistant](/exchange/exchange-deployment-assistant?view=exchserver-2019&preserve-view=true).
 
-5. Check the Exchange certificate of the send connector on the on-premises Exchange servers that are responsible for delivering mail to EOP. The Exchange certificate should have Simple Mail Transfer Protocol (SMTP) enabled and should match the FQDN of the send connector.
+5. Check the Exchange certificate of the send connector on the on-premises Exchange servers that are responsible for delivering mail to Microsoft 365. The Exchange certificate should have Simple Mail Transfer Protocol (SMTP) enabled and should match the FQDN of the send connector.
 
 If the issue persists after you follow these steps, contact Microsoft 365 Support.
 

Exchange/ExchangeHybrid/send-emails/overview-delegation-office-365-hybrid.md

@@ -4,19 +4,20 @@ description: Describes the Full Access, Send As, Send on Behalf of, and Folder p
 author: cloud-writer
 ms.author: meerak
 manager: dcscontentpm
+ms.reviewer: kellybos, v-six, v-kccross
 audience: ITPro
 ms.topic: troubleshooting
 ms.custom: 
   - sap:Mail Flow
   - Exchange Hybrid
   - CSSTroubleshoot
-ms.reviewer: kellybos, v-six
 search.appverid: 
   - MET150
 appliesto: 
   - Exchange Online
 ms.date: 01/24/2024
 ---
+
 # Overview of delegation in a Microsoft 365 hybrid environment
 
 ## Symptoms
@@ -124,7 +125,7 @@ This article describes the necessary configuration, administration details, and
   - Misconfigured delegates may result in a non-delivery report. For more information, see [Users receive NDR 5.2.0 when they send meeting invites in Microsoft 365 hybrid environment](../email-delivery/ndr-5-2-0-when-sending-meeting-invites.md).
   - The `LegacyExchangeDN` attribute of objects from Exchange Online and on-premises should be synching as x500 addresses between forests to avoid resolution issues that require enabling Exchange hybrid deployment settings in AD Connect. For more information, see [Exchange hybrid writeback](/azure/active-directory/hybrid/reference-connect-sync-attributes-synchronized#exchange-hybrid-writeback).
 
-  - If the Exchange hybrid deployment setting isn't enabled, delegates may see a non-delivery report when they update meetings. For more information, see ["550 5.1.11 RESOLVER.ADR.ExRecipNotFound" when delegate sends update to meeting after manager moved to Microsoft 365 hybrid environment](https://support.microsoft.com/help/4039597).
+  - If the Exchange hybrid deployment setting isn't enabled, delegates may see a non-delivery report when they update meetings.
 
 > [!NOTE]
 > Be aware that delegation also affects external calendar sharing. For more information, see [Unable to accept an external sharing invitation by using Outlook in a hybrid environment](../calendars/cannot-accept-external-sharing-invitation-in-outlook.md).

Exchange/ExchangeOnline/administration/release-messages-prompted-client-certificate.md

@@ -1,6 +1,6 @@
 ---
 title: Can't release a message for a certificate
-description: Describes an issue that returns a website 'na01-quarantine.dataservice.protection.outlook.com' requires a client certificate error when a Mac user tries to release a message from Exchange Online Protection quarantine.
+description: Describes an issue that returns a website 'na01-quarantine.dataservice.protection.outlook.com' requires a client certificate error when a Mac user tries to release a message from quarantine in Microsoft 365.
 author: cloud-writer
 ms.author: meerak
 manager: dcscontentpm
@@ -13,17 +13,17 @@ ms.custom:
 ms.reviewer: v-six
 appliesto: 
   - Exchange Online
-  - Exchange Online Protection
+  - Built-in security features for all cloud mailboxes
 search.appverid: MET150
 ms.date: 01/24/2024
 ---
-# Mac users can't release messages from Exchange Online Protection quarantine
+# Mac users can't release messages from quarantine in Microsoft 365
 
 _Original KB number:_   2909418
 
 ## Problem  
 
-When a user tries to release a message from the Exchange Online Protection quarantine when using the Safari browser on a Mac, the user is prompted for a certificate as follows:
+When a user tries to release a message from quarantine in Microsoft 365 when using the Safari browser on a Mac, the user is prompted for a certificate as follows:
 
 > The website "na01-quarantine.dataservice.protection.outlook.com" requires a client certificate.