Merge pull request #27163 from MicrosoftDocs/main

Publish main to live, Tuesday 3:30PM PST, 12/10

microsoft-365/enterprise/configure-search-for-multi-geo.md

@@ -1,7 +1,7 @@
 ---
 title: "Configure search for Microsoft 365 Multi-Geo"
 ms.reviewer:
-ms.date: 07/26/2024
+ms.date: 12/10/2024
 ms.author: kvice
 author: kelleyvice-msft
 manager: scotv
@@ -111,14 +111,14 @@ Some search features you might be familiar with, work differently in a multi-geo
 <tbody>
 <tr class="odd">
 <td align="left">Promoted results</td>
-<td align="left">You can create query rules with promoted results at different levels: for the whole _Tenant_, for a site collection, or for a site. In a Multi-Geo environment, define promoted results at the _Tenant_ level to promote the results to the Search Centers in all _Geography_ locations. If you only want to promote results in the Search Center that's in the _Geography_ location of the site collection or site, define the promoted results at the site collection or site level. These results are not promoted in other _Geography_ locations.</td>
-<td align="left">If you don't need different promoted results per _Geography_ location, for example different rules for traveling, we recommend defining promoted results at the _Tenant_ level.</td>
+<td align="left">You can create query rules with promoted results at different levels: for the whole <i>Tenant</i>, for a site collection, or for a site. In a Multi-Geo environment, define promoted results at the <i>Tenant</i> level to promote the results to the Search Centers in all <i>Geography</i> locations. If you only want to promote results in the Search Center that's in the <i>Geography</i> location of the site collection or site, define the promoted results at the site collection or site level. These results are not promoted in other <i>Geography</i> locations.</td>
+<td align="left">If you don't need different promoted results per <i>Geography</i> location, for example different rules for traveling, we recommend defining promoted results at the <i>Tenant</i> level.</td>
 </tr>
 <tr class="even">
 <td align="left">Search refiners</td>
-<td align="left">Search returns refiners from all the _Geography_ locations of a _Tenant_ and then aggregates them. The aggregation is a best effort, meaning that the refiner counts might not be 100% accurate. For most search-driven scenarios, this accuracy is sufficient.
+<td align="left">Search returns refiners from all the <i>Geography</i> locations of a <i>Tenant</i> and then aggregates them. The aggregation is a best effort, meaning that the refiner counts might not be 100% accurate. For most search-driven scenarios, this accuracy is sufficient.
 </td>
-<td align="left">For search-driven applications that depend on refiner completeness, query each _Geography_ location independently.</td>
+<td align="left">For search-driven applications that depend on refiner completeness, query each <i>Geography</i> location independently.</td>
 </tr>
 <tr class="odd">
 <td align="left"></td>
@@ -127,12 +127,12 @@ Some search features you might be familiar with, work differently in a multi-geo
 </tr>
 <tr class="even">
 <td align="left">Document IDs</td>
-<td align="left">If you're developing a search-driven application that depends on document IDs, note that document IDs in a Multi-Geo environment aren't unique across _Geography_ locations, they are unique per _Geography_ location.</td>
-<td align="left">We've added a column that identifies the _Geography_ location. Use this column to achieve uniqueness. This column is named "GeoLocationSource".</td>
+<td align="left">If you're developing a search-driven application that depends on document IDs, note that document IDs in a Multi-Geo environment aren't unique across <i>Geography</i> locations, they are unique per <i>Geography</i> location.</td>
+<td align="left">We've added a column that identifies the <i>Geography</i> location. Use this column to achieve uniqueness. This column is named "GeoLocationSource".</td>
 </tr>
 <tr class="odd">
 <td align="left">Number of results</td>
-<td align="left">The search results page shows combined results from the _Geography_ locations, but it's not possible to page beyond 500 results.</td>
+<td align="left">The search results page shows combined results from the <i>Geography</i> locations, but it's not possible to page beyond 500 results.</td>
 <td align="left"></td>
 </tr>
 <tr class="even">
@@ -161,7 +161,7 @@ Some of the search features you might be familiar with, aren't supported in a mu
 </tr>
 <tr class="even">
 <td align="left">Guests</td>
-<td align="left">Guests only get results from the _Geography_ location that they're searching from.</td>
+<td align="left">Guests only get results from the <i>Geography</i> location that they're searching from.</td>
 </tr>
 </tbody>
 </table>
@@ -231,7 +231,7 @@ MultiGeoSearchConfiguration - This is an optional list of which geo locations in
 <tbody>
 <tr class="odd">
 <td align="left">DataLocation</td>
-<td align="left">The _Geography_ location, for example NAM.</td>
+<td align="left">The <i>Geography</i> location, for example NAM.</td>
 </tr>
 <tr class="even">
 <td align="left">EndPoint</td>
@@ -260,11 +260,11 @@ MultiGeoSearchStatus – This is a property that the SharePoint Search API retur
 <tbody>
 <tr class="odd">
 <td align="left">Full</td>
-<td align="left">Full results from <strong>all</strong> the _Geography_ locations.</td>
+<td align="left">Full results from <strong>all</strong> the <i>Geography</i> locations.</td>
 </tr>
 <tr class="even">
 <td align="left">Partial</td>
-<td align="left">Partial results from one or more _Geography_ locations. The results are incomplete due to a transient error.</td>
+<td align="left">Partial results from one or more <i>Geography</i> locations. The results are incomplete due to a transient error.</td>
 </tr>
 </tbody>
 </table>

microsoft-365/enterprise/m365-dr-workload-exo.md

@@ -9,7 +9,7 @@ ms.subservice: advanced-data-residency
 ms.topic: article
 f1.keywords:
 - NOCSH
-ms.date: 02/29/2024
+ms.date: 12/10/2024
 ms.reviewer: deanw, brianday
 ms.custom:
  - it-pro
@@ -123,15 +123,15 @@ The following connection instructions work for accounts that are or aren't confi
 
 1. In a Windows PowerShell window, load the EXO V2 module by running the following command:
 
- ```powershell
- Import-Module ExchangeOnlineManagement
- ```
+    ```powershell
+    Import-Module ExchangeOnlineManagement
+    ```
  
 1. In the following example, [email protected] is the admin account, and the target geo location is where the mailbox [email protected] resides.
  
- ```powershell
- Connect-ExchangeOnline -UserPrincipalName [email protected] -ConnectionUri https://outlook.office365.com/[email protected]
- ```
+    ```powershell
+    Connect-ExchangeOnline -UserPrincipalName [email protected] -ConnectionUri https://outlook.office365.com/[email protected]
+    ```
  
 1. Enter the password for the [email protected] in the prompt that appears. If the account is configured for MFA, you also need to enter the security code.
  
@@ -261,9 +261,9 @@ You can't move inactive mailboxes that are preserved for compliance purposes (fo
 
 1. Prevent the Managed Folder Assistant from processing the recovered mailbox by replacing \<MailboxIdentity\> with the name, alias, account, or email address of the mailbox and running the following command in [Exchange Online PowerShell](/powershell/exchange/connect-to-exchange-online-powershell):
 
- ```powershell
- Set-Mailbox <MailboxIdentity> -ElcProcessingDisabled $true
- ```
+    ```powershell
+    Set-Mailbox <MailboxIdentity> -ElcProcessingDisabled $true
+    ```
 
 1. Assign an **Exchange Online Plan 2** license to the recovered mailbox. This step is required to place the mailbox back on Litigation Hold. For instructions, see [Assign licenses to users](/microsoft-365/admin/manage/assign-licenses-to-users).
 
@@ -273,9 +273,9 @@ You can't move inactive mailboxes that are preserved for compliance purposes (fo
 
 1. After verifying that the Litigation Hold is in place, allow the Managed Folder Assistant to process the mailbox again by replacing \<MailboxIdentity\> with the name, alias, account, or email address of the mailbox and running the following command in [Exchange Online PowerShell](/powershell/exchange/connect-to-exchange-online-powershell):
 
- ```powershell
- Set-Mailbox <MailboxIdentity> -ElcProcessingDisabled $false
- ```
+    ```powershell
+    Set-Mailbox <MailboxIdentity> -ElcProcessingDisabled $false
+    ```
 
 1. Make the mailbox inactive again by removing the user account associated with the mailbox. For instructions, see [Delete a user from your organization](/admin/add-users/delete-a-user). This step also releases the Exchange Online Plan 2 license for other uses.
 
@@ -365,15 +365,15 @@ Or, you can use the following steps to onboard mailboxes directly in a specific
 
 1. In Exchange Online PowerShell, store the on-premises administrator credentials used to perform a mailbox migration in a variable by running the following command:
 
- ```powershell
- $RC = Get-Credential
- ```
+    ```powershell
+    $RC = Get-Credential
+    ```
 
 1. In Exchange Online PowerShell, create a new **New-MoveRequest** similar to the following example:
 
- ```powershell
- New-MoveRequest -Remote -RemoteHostName mail.contoso.com -RemoteCredential $RC -Identity [email protected] -TargetDeliveryDomain <YourAppropriateDomain>
- ```
+    ```powershell
+    New-MoveRequest -Remote -RemoteHostName mail.contoso.com -RemoteCredential $RC -Identity [email protected] -TargetDeliveryDomain <YourAppropriateDomain>
+    ```
 
 1. Repeat step #4 for every mailbox you need to migrate from on-premises Exchange to the satellite geo location you're currently connected to.