Merge pull request #6896 from MicrosoftDocs/main

Publish main to live, Wednesday 10:30 AM PST, 10/17

SharePoint/SharePointOnline/manage-result-sources.md

@@ -47,19 +47,22 @@ For the classic search experience, you can create your own result sources, or us
 2. On the **Manage Result Sources** page, select **New Result Source**.
 
 3. In the **General Information** section, type a name and a description for the new result source. 
-    
-4. In the **Protocol** section, select one of the following protocols for retrieving search results: 
-
+
+4. In the **Protocol** section, select one of the following protocols for retrieving search results:
+        
    - **Local SharePoint**, the default protocol, provides results from the search index of this tenant (Search Service).
+
+   - **Remote SharePoint** (retired) provides results from the index of a search service in a different farm (external source). In the **Remote Service URL** box, type the address of the root site collection of the remote SharePoint farm. 
 
-   - **Remote SharePoint** provides results from the index of a search service in a different farm (external source). In the **Remote Service URL** box, type the address of the root site collection of the remote SharePoint farm. 
-
-   - **OpenSearch 1.0/1.1** provides results from a search engine that uses the OpenSearch 1.0/1.1 protocol. 
+   - **OpenSearch 1.0/1.1** (retired) provides results from a search engine that uses the OpenSearch 1.0/1.1 protocol. 
 
    - **Exchange** provides results from Microsoft Exchange Server. Select **Use AutoDiscover** to have the search system find an Exchange Server endpoint automatically, or type the URL of the Exchange web service to retrieve results from — for example, https://contoso.com/ews/exchange.asmx 
+
+> [!IMPORTANT]
+> As of September 2024, for SharePoint Online Microsoft 365 Result Sources, the OpenSearch and Remote SharePoint protocol options have been retired and will soon be removed from the Result Source configuration UI.  Any SharePoint Online Result Source currently configured to use these options will have zero results returned.    
     
-    > [!NOTE]
-    >  The Exchange Web Services Managed API must be installed on the computer where the search service is running. 
+> [!NOTE]
+>  The Exchange Web Services Managed API must be installed on the computer where the search service is running. 
   
 5. If you choose **Local SharePoint** or **Remote SharePoint** for protocol, choose a **Type**:
 
@@ -91,7 +94,7 @@ For the classic search experience, you can create your own result sources, or us
 | Choose this option | To do this |
 |:-----|:-----|
 |Sort results  |Define sorting for results. The **Sort by** list contains managed properties that are set as sortable in the search schema.  <br/> Select a property to sort by, and then select **Descending** or **Ascending**. To sort by relevance, select **Rank**.  <br/> Click **Add sort level** if you want to specify more levels of sorting.  |
-|Dynamic ordering  |Click **Add dynamic ordering rule** to specify additional ranking by adding rules that change the order of results within the result block when certain conditions are met. You can add conditions by choosing from the lists that appears.  |
+|Dynamic ordering  |Click **Add dynamic ordering rule** to specify additional ranking by adding rules that change the order of results within the result block when certain conditions are met. You can add conditions by choosing from the lists that appear.  |
 
 ### The TEST tab
 

SharePoint/SharePointOnline/manage-search-schema.md

@@ -348,6 +348,9 @@ If you need a property of a different type, or one that has different characteri
 8. In the **Include in full-text index** section, if you want to include the content of this crawled property in the full-text index, select the box. 
 
 9. Select **OK**.
+
+> [!NOTE]
+> To help clarify the the scope of Managed and Crawled Property mappings, Crawled Properties list **Scope** and **Override** values whose values are the scope at which the property was discovered or created and if the property overrides a property at a higher scope. If crawled properties with same name and property set Id exist in different scopes, the lower scope's value will (e.g., Site Collection) will override the higher scope (e.g., System). The scope override precidence from low to high is Site Collection -> Tenant -> System. An overridden property will be greyed out and can only be modified at the scope at which it was created.
     
 ## View or edit crawled property categories
 <a name="__toc351360847"> </a>