diff --git a/MicrosoftSearch/azure-devops-wiki-connector.md b/MicrosoftSearch/azure-devops-wiki-connector.md index 3cb7997a..51a6d126 100644 --- a/MicrosoftSearch/azure-devops-wiki-connector.md +++ b/MicrosoftSearch/azure-devops-wiki-connector.md @@ -12,7 +12,7 @@ search.appverid: - BFB160 - MET150 - MOE150 -description: "Set up the Azure DevOps Wiki Microsoft Graph connector for Microsoft Search and Microsoft 365 Copilot" +description: "Set up the Azure DevOps Wiki Microsoft Graph connector for Microsoft Search and Microsoft 365 Copilot" ms.date: 06/03/2022 --- @@ -20,50 +20,49 @@ ms.date: 06/03/2022 The Azure DevOps Wiki Microsoft Graph connector allows your organization to index wikis in its instance of the Azure DevOps service. After you configure the connector, end users can search for project wikis and code wikis from Azure DevOps in Microsoft Search and Microsoft 365 Copilot. -This article is for anyone who configures, runs, and monitors an Azure DevOps Wiki Microsoft Graph connector. It supplements the general setup process and shows instructions that apply only to the Azure DevOps Wiki Microsoft Graph connector. - -> [!NOTE] -> Read the [**Setup for your Graph connector**](configure-connector.md) article to understand the general Graph connectors setup instructions. +This article is for Microsoft 365 administrators or anyone who configures, runs, and monitors an Azure DevOps Wiki Microsoft Graph connector. >[!IMPORTANT] >The Azure DevOps Wiki Microsoft Graph connector supports only the Azure DevOps cloud service. Azure DevOps Server 2019, TFS 2018, TFS 2017, TFS 2015, and TFS 2013 are not supported by this connector. -## Before you get started - -You must be the **search admin** for your organization's Microsoft 365 tenant as well as the admin for your organization's Azure DevOps instance. - -To allow the connector to connect to your Azure DevOps organization, you must enable **Third-party application access via OAuth**. Refer Azure DevOps documentation to [manage security policies](/azure/devops/organizations/accounts/change-application-access-policies?view=azure-devops#manage-a-policy&preserve-view=true) to learn more. +## Capabilities +- Index wikis from Azure DevOps +- Enable your end users to ask questions related to project wikis and code wikis. +- Use [Semantic search in Copilot](semantic-index-for-copilot.md) to enable users to find relevant content based on keywords, personal preferences, and social connections. -![Third-party application access via OAuth](media/ado-workitems-connector-security-policies.png) +## Limitations +- The connector only indexes one ADO organization per connection. -You need the following permissions granted to the user account whose credentials are used during the connector configuration: +## Prerequisites +- You must be the **search admin** for your organization's Microsoft 365 tenant. +- To allow the connector to connect to your Azure DevOps organization, you must enable **Third-party application access via OAuth**. Refer Azure DevOps documentation to [manage security policies](/azure/devops/organizations/accounts/change-application-access-policies?view=azure-devops#manage-a-policy&preserve-view=true) to learn more. -| Permission name | Permission type | Required for | -| ------------ | ------------ | ------------ | -| View project-level information | [Project permission](/azure/devops/organizations/security/permissions?view=azure-devops&tabs=preview-page#project-level-permissions&preserve-view=true) | Crawling Azure DevOps Work Items. This permission is **mandatory** for the projects that need to be indexed. | + ![Third-party application access via OAuth](media/ado-workitems-connector-security-policies.png) ->[!IMPORTANT] ->The user account must have **Basic** access level. To learn more about access levels in Azure DevOps, read [supported access levels](/azure/devops/organizations/security/access-levels). - -## Step 1: Add a Microsoft Graph connector in the Microsoft 365 admin center +- **Service Account**: To connect to Azure DevOps and allow the Microsoft Graph Connector to update wikis regularly, you need a service account with the following permissions granted to it. -[Add Azure DevOps Wiki Microsoft Graph connector](https://admin.microsoft.com/adminportal/home#/MicrosoftSearch/Connectors/add?ms_search_referrer=MicrosoftSearchDocs_AzureDevOpsWiki&type=AzureDevOpsWiki) + | Permission name | Permission type | Required for | + | ------------ | ------------ | ------------ | + | View project-level information | [Project permission](/azure/devops/organizations/security/permissions?view=azure-devops&tabs=preview-page#project-level-permissions&preserve-view=true) | Crawling Azure DevOps Work Items. This permission is **mandatory** for the projects that need to be indexed. | -Follow the general [setup instructions](./configure-connector.md). + >[!IMPORTANT] + >The service account must have **Basic** access level. To learn more about access levels in Azure DevOps, read [supported access levels](/azure/devops/organizations/security/access-levels). -## Step 2: Name the connection +## Get Started -Follow the general [setup instructions](./configure-connector.md). +[![Screenshot that shows connection creation screen for Microsoft Graph Connector for Azure DevOps Wikis.](media/ado-wiki-create-page.png)](media/ado-wiki-create-page.png#lightbox) -## Step 3: Configure the connection settings +### 1. Display name +A display name is used to identify each citation in Copilot, helping users easily recognize the associated file or item. Display name also signifies trusted content. Display name is also used as a [content source filter](/MicrosoftSearch/custom-filters#content-source-filters). A default value is present for this field, but you can customize it to a name that users in your organization recognize. -To authenticate and sync content from Azure DevOps, choose **one of the two** supported methods:
+### 2. Authentication type +To authenticate and sync wikis from Azure DevOps, choose **one of the two** supported methods:
> [!IMPORTANT] -> - [Microsoft Entra ID OAuth](/azure/devops/integrate/get-started/authentication/oauth?preserve-view=true&view=azure-devops) is in preview and available to select customers. This is the recommended OAuth mechanism. +> - [Microsoft Entra ID OAuth](/azure/devops/integrate/get-started/authentication/oauth?preserve-view=true&view=azure-devops) is in preview and available to select customers. This is the **recommended** OAuth mechanism. > - [Azure DevOps OAuth](/azure/devops/integrate/get-started/authentication/oauth?preserve-view=true&view=azure-devops) is the legacy authentication mechanism, not being actively invested upon. -### Microsoft Entra ID OAuth (Preview) +#### a. **Microsoft Entra ID OAuth (Preview)** **Ensure your ADO Organization is connected to Microsoft Entra** @@ -129,60 +128,114 @@ Mandatory fields | Description | Recommended value | Authorization callback URL| A required callback URL that the authorization server redirects to. | For **Microsoft 365 Enterprise**: https://gcs.office.com/v1.0/admin/oauth/callback,
For **Microsoft 365 Government**: https://gcsgcc.office.com/v1.0/admin/oauth/callback| | Authorized scopes | The scope of access for the application | Select the following scopes: Identity (read), Code (read), Entitlements (read), Project and Team (read), Graph (read), Member Entitlement Management (read), Wiki (read).| - >[!IMPORTANT] >The authorized scopes selected for the app should exactly match the scopes listed above. If either more or less scopes are selected, authorization fails. -When On registering the app, you get the **App ID** and **Client Secret** that is used to configure the connector. +On registering the app, you get the **App ID** and **Client Secret** that is used to configure the connector. To revoke access to any app registered in Azure DevOps, go to User settings at the right top of your Azure DevOps instance. Select **Profile** and then select **Authorizations** in the Security section of the side pane. Hover over an authorized OAuth app to see the Revoke button at the corner of the app details. -### Connection settings +### 3. Select Organization +The Azure DevOps connector allows indexing of one organization per connection. To connect to your Azure DevOps service, select the right organization from the list of organizations accessible to the service account. -After registering the Microsoft Search app and Microsoft 365 Copilot with Azure DevOps, you can complete the connection settings step. Enter your App ID and client secret. +### 4. Roll out to limited audience +Deploy this connection to a limited user base if you want to validate it in Copilot and other Search surfaces before expanding the rollout to a broader audience. To know more about limited rollout, see [staged rollout](staged-rollout-for-graph-connectors.md). -![Connection Application Settings.](media/azure-devops-wiki-connection-settings.png) +At this point, you're ready to create the connection for Azure DevOps wikis. You can click **Create** to publish your connection and index wikis from your Azure DevOps organization. -### Configure data: select organization, projects, and fields - -In this step, you specify the scope of data that you want to index using the Azure DevOps Wiki Microsoft Graph connector. +For other settings, like **Access Permissions**, **Data Inclusion Rules**, **Schema**, **Crawl frequency**, etc., we have defaults based on what works best with ADO data. You can see the default values below: + +| Users | Description | +|----|---| +| Access permissions | _Only people with access to content in Data source._ | +| Map Identities | _Data source identities mapped using Microsoft Entra IDs._ | + +| Content | Description | +|---|---| +| Site projects | _All projects are indexed._ | +| Manage Properties | _To check default properties and their schema, see [content](#content)_ | + +| Sync | Description | +|---|---| +| Incremental Crawl | _Frequency: Every 15 mins_ | +| Full Crawl | _Frequency: Every Day_ | + +If you want to edit any of these values, you need to choose the "Custom Setup" -As the first step, you choose the organization you want to index, out of all organizations you have access to. You can then choose for the connection to index either the entire organization or specific projects within the selected organization. +## Custom Setup + +Custom setup is for those admins who want to edit the default values for settings listed in the above table. Once you click on the "Custom Setup" option, you see three more tabs - Users, Content, and Sync. + +### Users + +[![Screenshot that shows Users tab where you can configure access permissions and user mapping rules.](media/ado-wiki-users-tab.png)](media/ado-wiki-users-tab.png#lightbox) + +**Access Permissions** + +The Azure DevOps Wiki connector supports search permissions visible to **Everyone** or **Only people with access to this data source**. If you choose **Everyone**, indexed data appears in the search results for all users. If you choose **Only people with access to this data source**, indexed data appears in the search results for users who have access to them. + +>[!NOTE] +> +> Updates to groups governing access permissions are synced in full crawls only. Incremental crawls don't support processing of updates to permissions. + +### Content + +[![Screenshot that shows Content tab where you can configure projects and connection schema.](media/ado-wiki-content-tab.png)](media/ado-wiki-content-tab.png#lightbox) + +**Choose projects** + +In this step, you specify the scope of data that you want to index using the Azure DevOps Wiki Microsoft Graph connector. You can then choose for the connection to index either the entire organization or specific projects within the selected organization. If you choose to index the entire organization, wikis in all projects in the organization are indexed. New projects and wikis are indexed during the next crawl after they're created. If you choose to index individual projects, only wikis in the selected projects are indexed. -## Step 4: Manage search permissions - -The Azure DevOps Wiki Microsoft Graph connector supports search permissions visible to **Everyone**. With the **Everyone** option, indexed data appears in the search results for all users. +**Manage Properties** -## Step 5: Assign property labels +Here, you can add or remove available properties from your Azure DevOps data source, assign a schema to the property (define whether a property is searchable, queryable, retrievable, or refinable), change the semantic label and add an alias to the property. Properties that are selected by default are listed below. -Follow the general [setup instructions](./configure-connector.md). +|Source Property|Label|Description|Schema| +|---|---|---|---| +| Authors | Authors | Name all the people who participated/collaborated on the item in the data source | Retrieve | +| CommitId | | | | +| Content | Content | The content body of the wiki | Search | +| GitItemPath | | | | +| IconUrl | IconUrl | Icon url that represents the wiki | Retrieve | +| isParentPage | | | | +| LastPublishedAuthorEmail | Last modified by | | Retrieve | +| LastPublishedDate | Last modified date time | Date and time the item was last modified in the data source | Retrive | +| Organization | | | Retrieve | +| Path | | | | +| Project | | | Retrieve | +| ProjectId | | | Retrieve | +| RemoteURL | url | The URL of the wiki in the data source | Retrieve | +| Title | Title | The title of the wiki page | Search, Retrieve | +| Version | | | Retrieve | +| WikiId | | | Retrieve | +| WikiIdentifier | | | Retrieve | +| WikiType | | | | -## Step 6: Manage schema +**Preview Data** -Follow the general [setup instructions](./configure-connector.md). +Use the preview results button to verify the sample values of the selected properties. -## Step 7: Choose refresh settings +### Sync -The Azure DevOps Wiki Microsoft Graph connector supports refresh schedules for both full and incremental crawls. -The recommended schedule is one hour for an incremental crawl and one week for a full crawl. +[![Screenshot that shows Sync tab where you can configure crawl frequency.](media/ado-wiki-sync-tab.png)](media/ado-wiki-sync-tab.png#lightbox) -## Step 8: Review connection +The refresh interval determines how often your data is synced between the data source and the Graph connector index. There are two types of refresh intervals - full crawl and incremental crawl. For more information, see [refresh settings](configure-connector.md#step-8-refresh-settings). -Follow the general [setup instructions](./configure-connector.md). +You can change the default values of refresh interval from here if you want to. -## Step 9: Set up search result page +### Set up search result page After publishing the connection, you need to customize the search results page with verticals and result types. To learn about customizing search results, review how to [manage verticals](manage-verticals.md) and [result types](manage-result-types.md). - You may also use the [sample result layout](azure-devops-wiki-connector-result-layout.md) for the Azure DevOps Wiki Microsoft Graph connector. Simply copy-paste the result layout JSON to get started. +You may also use the [sample result layout](azure-devops-wiki-connector-result-layout.md) for the Azure DevOps Wiki Microsoft Graph connector. Simply copy-paste the result layout JSON to get started. ## Troubleshooting After publishing your connection, you can review the status under the **Data sources** tab in the [admin center](https://admin.microsoft.com). To learn how to make updates and deletions, see [Manage your connector](manage-connector.md). You can find troubleshooting steps for commonly seen issues [here](troubleshoot-azure-devops-wiki-connector.md). -If you have issues or want to provide feedback, contact [Microsoft Graph | Support (https://developer.microsoft.com/en-us/graph/support). +If you have issues or want to provide feedback, contact [Microsoft Graph](https://developer.microsoft.com/graph/support). diff --git a/MicrosoftSearch/connectors-gallery.md b/MicrosoftSearch/connectors-gallery.md index 927af951..72f98bcf 100644 --- a/MicrosoftSearch/connectors-gallery.md +++ b/MicrosoftSearch/connectors-gallery.md @@ -56,6 +56,7 @@ The following connectors are under collaboration & communications. |Microsoft Entra ID (formerly known as Azure Active Directory)|Rhein Insights|Enterprise search connector for indexing Entra ID. It can serve as a profile search, also for Azure B2C profiles, or as a source for early-binding security trimming. Comes with full sets of profile metadata and indexes all user-group relationships. For more information, see [Microsoft Entra ID](https://www.rheininsights.com/en/connectors/entra-id.php).| |Azure DevOps|Microsoft|Allows your organization to search for work items in your Azure DevOps instance. For more information, see [Azure DevOps Microsoft Graph connector](/MicrosoftSearch/azure-devops-connector).| |Box|Accenture|Box connector crawls content from a Box repository. The connector retrieves the supported elements using the RESTful API (Content API Basics 2.0 version); for authentication, it uses Box API (that uses OAuth 2). Each file is submitted with its metadata (size, location, last accessed, etc.). Updates are discovered automatically. For more information, see [Box connector](https://contentanalytics.digital.accenture.com/display/aspire40/Box++Connector).| +|CB Insights|CB Insights|Integrate CB Insights’ proprietary data and insights directly into Microsoft Copilot to instantly generate unique insights across all Microsoft 365 applications. Access data for public and private companies like funding events, business relationships, predictive outlook, and more. The CBI connector allows you to research, analyze, and share trusted, data-backed insights to bet on the right markets, source the right companies, and stay ahead of competitors. All teams across an organization can benefit from the connector — from sales, to IT, to finance — to help make informed, data-driven decisions. For more information, see [CB Insights connector](https://www.cbinsights.com/copilot-connector/).| |Deltek|BA Insight|BA Insight's Deltek Vision connector honors the security of the source system and provides both full and incremental crawls so that users have the latest information available to them all the time. It indexes content from Deltek Vision into Azure, SharePoint Online, or SharePoint 2016/2013, surfacing it through BA Insight’s SmartHub to provide users with integrated search results. For more information, see [Deltek connector](https://www.bainsight.com/connectors/deltek-connector-sharepoint-azure-elasticsearch/).| |Elite/3E|BA Insight|BA Insight’s Elite connector provides a single point of access for lawyers to access firm content and knowledge in line with Elite content using Microsoft Search. For more information, see [Elite/3E connector](https://www.bainsight.com/connectors/elite-connector-sharepoint-azure-elasticsearch/).| |Symantec Enterprise Vault|Raytion| Secure enterprise search connector for reliably indexing content from Symantec Enterprise Vault and intelligently searching it with Microsoft Graph. It robustly indexes archived data, such as e-mails, attachments, files, calendar items, and contacts from Enterprise Vault in near real-time. The connector fully supports Symantec Enterprise Vault’s authentication models Basic, NTLM, and Kerberos authentication. For more information, see [Symantec Enterprise Vault connector](https://www.raytion.com/connectors/raytion-enterprise-vault-connector-2).| @@ -123,6 +124,7 @@ The following connectors are under content management systems. |LegalKEY|BA Insight|Securely indexes both the full text and metadata of client and matter records in LegalKEY into the Microsoft search engine, enabling a single searchable result set across content from multiple repositories. It allows organizations to tap into the wealth of information accessible within LegalKEY, SharePoint, and other repositories, making that data instantly actionable to users through search. For more information, see [LegalKEY connector](https://www.bainsight.com/connectors/legalkey-connector-sharepoint-azure-elasticsearch/).| |Lotus Notes Databases|BA Insight|With BA Insight's IBM Notes Database connector, users have the ability to find content stored in Notes databases using Microsoft Search. Security defined within IBM Notes is automatically reflected in the search experience, which ensures that users see content for which they're authorized. Ultimately, users can find everything they need in one place. For more information, see [Lotus Notes Databases connector](https://www.bainsight.com/connectors/ibm-lotus-notes-connector-sharepoint-azure-elasticsearch/).| |Lucid|Lucid Software|Find the Lucid document you need without leaving Microsoft 365. Microsoft admins can connect Lucid with Microsoft Graph connectors to surface Lucid documents right in Microsoft 365, plus set user permissions so that documents stay secure. For more information, see [Lucid connector](https://lucid.co/marketplace/0953d9f2/microsoft-graph-connector).| +|LumApps|LumApps|Empowers employees with seamless access to knowledge and resources across both LumApps and Microsoft 365. By leveraging LumApps, Microsoft 365 Copilot seamlessly integrates information from LumApps' intranet, news, and community posts with Microsoft 365 data like SharePoint documents and Teams conversations. It allows employees to get comprehensive answers, and collaborate more effectively, all within their familiar Microsoft 365 environment. For more information, see [LumApps connector](https://www.lumapps.com/platform/integrations/microsoft-365).| |MediaPlatform PrimeTime|BA Insight|BA Insight’s MediaPlatform PrimeTime indexing connector makes it possible to make the content accessible to users via an organization’s enterprise search platform, combining the connector with BA Insight’s SmartHub. The BA Insight MediaPlatform PrimeTime connector retrieves information about channels and videos from MediaPlatform PrimeTime and indexes them via Microsoft Search. For more information, see [MediaPlatform PrimeTime connector](https://www.bainsight.com/connectors/mediaplatform-primetime-connector-sharepoint-azure-elasticsearch/).| |MediaWiki|Microsoft|Enables your organization to search knowledge-based articles on sites it creates with MediaWiki. For more information, see [MediaWiki Microsoft Graph connector](/MicrosoftSearch/mediawiki-connector).| |MediaWiki|Raytion|Secure enterprise search connector for reliably indexing content from MediaWiki and intelligently searching it with Microsoft Graph. It robustly indexes pages, discussion pages, and attachments from MediaWiki instances in near real-time. The connector fully supports MediaWiki’s built-in permission model, and MediaWiki installations based on Entra ID and other directory services. For more information, see [MediaWiki connector](https://www.raytion.com/connectors/raytion-mediawiki-connector).| @@ -156,6 +158,7 @@ The following connectors are under content management systems. |SharePoint Online|Rhein Insights|Enables the Enterprise search and Microsoft 365 connector for indexing Microsoft SharePoint Online. Reliably indexes all SharePoint sites, pages, lists, list items, and documents also in multi-geo scenarios. Comes with full metadata sets, advanced processing pipelines, document preview integrations, and full support for SharePoint Online's permission model. For more information, see [SharePoint Online connector](https://contentanalytics.digital.accenture.com/display/aspire40/SharePoint+Online+Connector).| |Sitecore|BA Insight|BA Insight's Sitecore connector honors the security of the source system and provides both full and incremental crawls so the users have the latest information available to them all the time. For more information, see [Sitecore connector](https://www.bainsight.com/connectors/sitecore-connector-sharepoint-azure-elasticsearch/).| |Sitecore|Raytion|Secure enterprise search connector for reliably indexing content from Sitecore and intelligently searching it with Microsoft Graph. It robustly indexes pages and attachments, and further generates document types in near real-time. The connector fully supports Sitecore’s permission model and the user and group management in the associated Entra ID. For more information, see [Sitecore connector](https://www.raytion.com/connectors/raytion-sitecore-connector).| +|S&P Global|S&P Global|Empowers clients by integrating S&P Global data directly into their Office 365 environment. This seamless integration allows users to access and surface critical S&P Global content within their familiar Microsoft tools like Copilot, SharePoint, Outlook, and Teams. The connector provides direct links to the wealth of information available on S&P Global platforms, enhancing productivity and decision-making by bringing data to your fingertips. The first datasets to be made available will be Commodity Insights Research datasets in early 2025. For more information, see [S&P Global connector](https://www.marketplace.spglobal.com/en/solutions/microsoft-graph-connector-(6a8b56b9-4c0c-4ddc-85ed-21a4648ee569)).| |Veritas Enterprise Vault (Symantec eVault)|BA Insight|BA Insight's Veritas Enterprise Vault connector honors the security of the source system and provides full and incremental crawls. Hence, the users have the latest information available to them all the time. For more information, see [Veritas Enterprise Vault (Symantec eVault) connector](https://www.bainsight.com/connectors/enterprise-vault-connector-sharepoint-azure-elasticsearch/).| |West km|BA Insight|The BA Insight West km connector supports search across transaction and litigation documents, including the creation of custom search results pages. For more information, see [West km connector](https://www.bainsight.com/connectors/westkm-connector-sharepoint-azure-elasticsearch/).| |Xerox DocuShare|BA Insight|Users of BA Insight's Xerox DocuShare connector are able to search for the content housed in DocuShare repositories directly from within Microsoft Search, eliminating the need to perform multiple searches to locate needed content. For more information, see [Xerox DocuShare connector](https://www.bainsight.com/connectors/docushare-connector-sharepoint-azure-elasticsearch/).| diff --git a/MicrosoftSearch/create-search-results-pages.md b/MicrosoftSearch/create-search-results-pages.md index cf6e829e..0db64ca5 100644 --- a/MicrosoftSearch/create-search-results-pages.md +++ b/MicrosoftSearch/create-search-results-pages.md @@ -1,8 +1,8 @@ --- title: "Create a custom search results page in SharePoint Online" -ms.author: bstucker -author: bstuck -manager: bstuck +ms.author: misvenso +author: wobba +manager: wobba ms.audience: Admin ms.topic: article ms.service: mssearch @@ -18,6 +18,8 @@ One way to customize the search experience in SharePoint is to create a custom s >[!NOTE] > To make changes to the default Microsoft Search results page that is available by default, please see [Customize the search results page](customize-search-page.md). +> +> A custom redirect URL pointing to the result page provided by Microsoft Search at `_layouts/15/search.aspx` is an unsupported scenario. SharePoint will navigate to `_layouts/15/search.aspx` with the needed parameters based on search box configuration. With a custom results page, you can create a new page that can be used to control the layout and design of search results to support your organization's needs. You can use any built-in web parts, open-source search web parts from SharePoint Patterns and Practices community, and any custom web parts that you have developed using SharePoint Framework. diff --git a/MicrosoftSearch/edge-shortcuts.md b/MicrosoftSearch/edge-shortcuts.md index ea6cd6a0..6d7cca28 100644 --- a/MicrosoftSearch/edge-shortcuts.md +++ b/MicrosoftSearch/edge-shortcuts.md @@ -6,7 +6,7 @@ manager: kellis ms.audience: Admin ms.topic: article ms.service: mssearch -localization_priority: Normal +ms.localizationpriority: Medium ms.date: 03/15/2022 search.appverid: - BFB160 diff --git a/MicrosoftSearch/github-connector.md b/MicrosoftSearch/github-connector.md new file mode 100644 index 00000000..1e46e456 --- /dev/null +++ b/MicrosoftSearch/github-connector.md @@ -0,0 +1,121 @@ +--- +title: "GitHub Graph connector for Microsoft Search and Copilot" +ms.author: efgilboa +author: vivg +manager: igala +audience: Admin +ms.audience: Admin +ms.topic: article +ms.service: mssearch +ms.localizationpriority: medium +search.appverid: +- BFB160 +- MET150 +- MOE150 +description: "Set up the GitHub Microsoft Graph connector for Microsoft Search and Microsoft 365 Copilot" +ms.date: 11/11/2024 +--- + +# GitHub Microsoft Graph connector (Preview) + +The GitHub Graph Connector allows you to index content from GitHub repositories, making it easily searchable within the Microsoft 365 ecosystem. This connector is ideal for organizations that use GitHub for documentation, project files, or content management. By integrating GitHub data with Microsoft Search, users can access relevant content directly within Microsoft 365 applications, streamlining workflows and reducing the need to switch between platforms. + +This article is for Microsoft 365 administrators or anyone who configures, runs, and monitors a GitHub Graph connector. + +>[!NOTE] +>The GitHub Graph connector is in preview. If you wish to get early access to try it, sign up using [this form](https://forms.office.com/r/JniPmK5bzm). + +## Capabilities +- Index GitHub repositories and markdown files to make project documentation accessible in Microsoft 365. +- Enable end users to ask questions in Copilot related to project documentation and technical guides. + - How do I set up Project Alpha? + - Where can I find the deployment instructions? + - What is the architecture overview for this project? + - Summarize key sections in project documentation for quick reference +- Use [Semantic search in Copilot](semantic-index-for-copilot.md) to enable users to find relevant content based on keywords, personal preferences, and social connections. + +## Limitations +- Only repository metadata and markdown files are indexed. Other GitHub entities such as issues, pull requests, and comments aren't indexed. +- Only markdown files up to 1 MB in size are supported. Larger files aren't indexed. + +## Prerequisites +- You must be the **search admin** for your organization's Microsoft 365 tenant. +- You must have an active GitHub account where you have access to all the repositories you intend to index. + + a. For personal repositories, you must be one of: + - A repository owner + - A repository collaborator + + b. For organization-owned repositories, you must be one of: + - An outside collaborator + - An organization member as a direct collaborator + - An organization member with access through team memberships + - An organization member with access through default organization permissions + - An organization owner. +- You must have a personal access token (PAT). To learn more about the personal access tokens, see [Managing your personal access tokens - GitHub Docs](https://docs.github.com/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens). +- Your personal access token must have access to all repositories you want to index and must be granted the permission listed below. + + For classic token: + + | Category | Permission | Remarks | + | ------------ | ------------ | ------------ | + | Repo | All | Full control of private repositories | + | User | read:user | Read ALL user profile data | + | User | read:email | Access user email addresses (read-only) | + + For the fine-grained token: + + | Category | Permission | Permission Level | + | ------------ | ------------ | ------------ | + | Account Permissions | Email addresses | Read-only | + | Repository Permissions | Metadata | Read-only | + | Repository Permissions | Contents | Read-only | + +- If you have organization-owned repositories, follow these extra steps: + - The organization administrator needs to allow access via personal access tokens. For instructions, see [Setting a personal access token policy for your organization - GitHub Docs](https://docs.github.com/organizations/managing-programmatic-access-to-your-organization/setting-a-personal-access-token-policy-for-your-organization#restricting-access-by-personal-access-tokens) + - If you're using fine-grained tokens, select the organization as the resource owner. + +## Get Started + +### 1. Display name +A display name is used to identify each citation in Copilot, helping users easily recognize the associated file or item. Display name also signifies trusted content. Display name is also used as a [content source filter](/MicrosoftSearch/custom-filters#content-source-filters). A default value is present for this field, but you can customize it to a name that users in your organization recognize. + +### 2. Authentication Type + +To authenticate and sync content from GitHub:
+ +1. **Authentication type**
+Choose the "Basic" option + +2. **Personal Access Token (PAT)**
+Use your personal access token in place of a password. The repositories available for indexing depends on the access granted by your token. + +## Custom Setup + +Custom setup is for those admins who want to edit the default values for settings listed. Once you click on the "Custom Setup" option, you see three more tabs - Users, Content, and Sync. + +### Users + +**Access Permissions** + +The GitHub connector supports search permissions visible to **Everyone** with access to this data source. For Everyone, indexed data appears in the search results for all users. +For identity transformation, refer to the [Map your non-Azure AD Identities | Microsoft Learn](map-non-aad.md). + +### Content + +Choose the repositories and file types (initially markdown files and other non-code documentation) you wish to make searchable. + +**Manage Properties** + +Here, you can add or remove available properties from your GitHub data source, assign a schema to the property (define whether a property is searchable, queryable, retrievable, or refinable), change the semantic label and add an alias to the property. + +### Sync + +The refresh interval determines how often your data is synced between the data source and the Graph connector index. There are two types of refresh intervals - full crawl and incremental crawl. For more information, see [refresh settings](configure-connector.md#step-8-refresh-settings). + +You can change the default values of refresh interval from here if you want to. + +## Troubleshooting +After publishing your connection, you can review the status under the **Data Sources** tab in the [admin center](https://admin.microsoft.com). To learn how to make updates and deletions, see [Manage your connector](manage-connector.md). + +If you have issues or want to provide feedback, contact [Microsoft Graph | Support](https://developer.microsoft.com/en-us/graph/support). diff --git a/MicrosoftSearch/manage-access-files-sites.md b/MicrosoftSearch/manage-access-files-sites.md index bc089f90..6fba1176 100644 --- a/MicrosoftSearch/manage-access-files-sites.md +++ b/MicrosoftSearch/manage-access-files-sites.md @@ -6,7 +6,7 @@ manager: kellis ms.audience: Admin ms.topic: article ms.service: mssearch -localization_priority: Normal +ms.localizationpriority: Medium search.appverid: - BFB160 - MET150 diff --git a/MicrosoftSearch/manage-search-schema.md b/MicrosoftSearch/manage-search-schema.md index f55b7bb4..18fe6fd4 100644 --- a/MicrosoftSearch/manage-search-schema.md +++ b/MicrosoftSearch/manage-search-schema.md @@ -8,7 +8,7 @@ audience: Admin ms.audience: Admin ms.topic: article ms.service: mssearch -localization_priority: Normal +ms.localizationpriority: Medium search.appverid: - BFB160 - MET150 diff --git a/MicrosoftSearch/media/ado-wiki-content-tab.png b/MicrosoftSearch/media/ado-wiki-content-tab.png new file mode 100644 index 00000000..d4780a2e Binary files /dev/null and b/MicrosoftSearch/media/ado-wiki-content-tab.png differ diff --git a/MicrosoftSearch/media/ado-wiki-create-page.png b/MicrosoftSearch/media/ado-wiki-create-page.png new file mode 100644 index 00000000..e7f84ed4 Binary files /dev/null and b/MicrosoftSearch/media/ado-wiki-create-page.png differ diff --git a/MicrosoftSearch/media/ado-wiki-sync-tab.png b/MicrosoftSearch/media/ado-wiki-sync-tab.png new file mode 100644 index 00000000..b7206104 Binary files /dev/null and b/MicrosoftSearch/media/ado-wiki-sync-tab.png differ diff --git a/MicrosoftSearch/media/ado-wiki-users-tab.png b/MicrosoftSearch/media/ado-wiki-users-tab.png new file mode 100644 index 00000000..d10826ef Binary files /dev/null and b/MicrosoftSearch/media/ado-wiki-users-tab.png differ diff --git a/MicrosoftSearch/media/sharepoint-server/addclientappgca.png b/MicrosoftSearch/media/sharepoint-server/addclientappgca.png new file mode 100644 index 00000000..a080920d Binary files /dev/null and b/MicrosoftSearch/media/sharepoint-server/addclientappgca.png differ diff --git a/MicrosoftSearch/media/sharepoint-server/exposeanapi.png b/MicrosoftSearch/media/sharepoint-server/exposeanapi.png new file mode 100644 index 00000000..30c521c4 Binary files /dev/null and b/MicrosoftSearch/media/sharepoint-server/exposeanapi.png differ diff --git a/MicrosoftSearch/select-work-school-search-experience.md b/MicrosoftSearch/select-work-school-search-experience.md index fc85cd0a..41db2526 100644 --- a/MicrosoftSearch/select-work-school-search-experience.md +++ b/MicrosoftSearch/select-work-school-search-experience.md @@ -6,7 +6,7 @@ manager: bstucker ms.audience: Admin ms.topic: article ms.service: mssearch -localization_priority: Normal +ms.localizationpriority: Medium ms.date: 03/15/2022 search.appverid: - BFB160 diff --git a/MicrosoftSearch/semantic-index-for-copilot.md b/MicrosoftSearch/semantic-index-for-copilot.md index b9769e1e..000290dc 100644 --- a/MicrosoftSearch/semantic-index-for-copilot.md +++ b/MicrosoftSearch/semantic-index-for-copilot.md @@ -28,7 +28,7 @@ Interactions with data in Microsoft Graph are based on keyword matching, persona ## How the semantic index helps manage your data -Semantic index enhances the features of Microsoft 365 that allow you to find relevant content based on keywords, personal preferences, and social connections. It does this by creating vectorized indices. A vector is a numerical representation of a word, image pixel, or other data point. The vector is arranged or mapped with close numbers placed in proximity to one another to represent similarity. Vectors are stored in multi-dimensional spaces where semantically similar data points are clustered together in the vector space, enabling Microsoft 365 to handle a broader set of search queries beyond “exact match." +Semantic index enhances the Microsoft 365 Copilot experience in both Business Chat and in the Microsoft 365 apps. It supports an enhanced content grounding and conceptual understanding of your online data that is automatically enabled by Microsoft. It does this by creating vectorized indices. A vector is a numerical representation of a word, image pixel, or other data point. The vector is arranged or mapped with close numbers placed in proximity to one another to represent similarity. Vectors are stored in multi-dimensional spaces where semantically similar data points are clustered together in the vector space, enabling Microsoft 365 to handle a broader set of search queries beyond “exact match." In practical terms, this means that Microsoft 365 services such as Microsoft 365 Copilot can: @@ -88,6 +88,9 @@ The semantic index supports indexing of user mailbox and file types listed in th | OneNote files (one) | Supported | Supported | | Graph Connector data | Not applicable | Supported | +>[!NOTE] +>Files up to 512MB are now supported for PDF, PPTX, and DOCX extensions. This enhancement allows Copilot users to effectively analyze, summarize, and generate insights from these large files. + ## Index updates When Semantic index completes indexing for a customer for the first time, documents created by users are indexed in near real-time in the user's mailbox. New documents that are added to SharePoint Online sites that are accessible, via site inheritance, by two or more users are indexed daily. When an indexed user and tenant level document is updated, the changes are immediately indexed. @@ -107,9 +110,9 @@ There are times when organizations without Microsoft Purview Data Loss Preventio 1. Select **View all site settings** to bring up the Site Settings page. 1. Select **Search and offline availability** under the **Search** category and select **No** for **Allow this site to appear in search results** to exclude it from both Microsoft Search and the semantic index search. This can also be performed with PowerShell for multiple sites. -:::image type="content" source="media/semantic-index-settings.png" alt-text="Screenshot showing the settings for excluding SharePoint online sites." lightbox="media/semantic-index-settings.png"::: + :::image type="content" source="media/semantic-index-settings.png" alt-text="Screenshot showing the settings for excluding SharePoint online sites." lightbox="media/semantic-index-settings.png"::: -Microsoft Search and the semantic index support the exclusion of SharePoint online content from the tenant-level index only. There's no option to exclude results from Microsoft Search only or the semantic index only; actions apply to both at the same time. + Microsoft Search and the semantic index support the exclusion of SharePoint online content from the tenant-level index only. There's no option to exclude results from Microsoft Search only or the semantic index only; actions apply to both at the same time. ## Configuring item insights diff --git a/MicrosoftSearch/servicenow-knowledge-connector.md b/MicrosoftSearch/servicenow-knowledge-connector.md index 2654bea5..19f3fa79 100644 --- a/MicrosoftSearch/servicenow-knowledge-connector.md +++ b/MicrosoftSearch/servicenow-knowledge-connector.md @@ -272,19 +272,6 @@ The default method for mapping your data source identities with Microsoft Entra **Query String** -*The list of properties that you select here, can impact how can you filter, search and view your results in Copilot for Microsoft 365.* - -**Source property** | **Label** | **Description** ---- | --- | --- -AccessUrl | `url` | The target URL of the item in the data source. -Author | `authors` | Name of all the people who participated/collaborated on the item in the data source. -IconUrl | `iconUrl` | Icon url that represents the article’s category or type. -Short_description | `title` | The title of the item that you want shown in search and other experiences. -SysUpdatedBy | `lastModifiedBy` | Name of the person who most recently edited the item in the data source. -SysUpdatedOn | `lastModifiedDateTime` | Date and time the item was last modified in the data source. -SysCreatedBy | `createdBy` | Name of the person who created the item in the data source. -SysCreatedOn | `createdDateTime` | Date and time that the item was created in the data source. - With a ServiceNow query string, you can specify conditions for syncing articles. It's like a **Where** clause in a **SQL Select** statement. For example, you can choose to index only articles that are published and active. To learn about creating your own query string, see [Generate an encoded query string using a filter](https://docs.servicenow.com/bundle/vancouver-platform-user-interface/page/use/using-lists/task/t_GenEncodQueryStringFilter.html). **Manage Properties** diff --git a/MicrosoftSearch/sharepoint-server-connector.md b/MicrosoftSearch/sharepoint-server-connector.md index cd9b4755..5af89751 100644 --- a/MicrosoftSearch/sharepoint-server-connector.md +++ b/MicrosoftSearch/sharepoint-server-connector.md @@ -18,7 +18,7 @@ description: "Set up the SharePoint Server Microsoft Graph connector for Microso # SharePoint Server Microsoft Graph connector -The SharePoint on-prem graph connector allows users in your organization to search for content stored in on-prem SharePoint server or use the content in Copilot for specific use cases and scenarios. It crawls over Documents and site pages from the on-prem instance. +SharePoint server graph connector allows users in your organization to search for content stored in on-premises SharePoint server or use the content in Copilot for specific use cases and scenarios. It crawls over Documents and site pages from the on-premises instance. > [!NOTE] > Active directory synchronization is a pre-requisite for enabling security trimming in SharePoint Server content search. @@ -26,13 +26,13 @@ The SharePoint on-prem graph connector allows users in your organization to sear ## Capabilities - Uses the authenticated account to crawl SharePoint documents and web-pages along with permissions. -- Users that do not have permissions on the items do not find the item in their Search or Copilot results. +- Users that don't have permissions on the items don't find the item in their Search or Copilot results. - Lists all available site collections available that the users can choose to include for indexing. - Use exclusion feature to exclude sites from indexing. - Enable users to utilize connector content for Copilot queries and prompts. Here are some of capabilities: - - Ask questions around the content of the documents. Example, What is the current sales projections mentioned in the file Sales_Report.doc. - - Summarize the content of documents. Example, Summarize the file Sales_Report.doc. - - Create content using existing documents. Example, Create a FAQs document to be shared with sales personnel using file Sales_Report.doc + - Ask questions around the content of the documents. Example, What is the current sales projections mentioned in the file *Sales_Report.doc*. + - Summarize the content of documents. Example, summarize the file *Sales_Report.doc*. + - Create content using existing documents. Example, Create a FAQs document to be shared with sales personnel using file *Sales_Report.doc*. ## Limitations @@ -43,11 +43,11 @@ The SharePoint on-prem graph connector allows users in your organization to sear ### Install the Graph connector agent -To index your SharePoint on-prem content, you must install and register the Graph connector agent. See [Install Graph Connector Agent](graph-connector-agent.md) to learn more. The Graph connector agent can be installed on the same machine as the SharePoint server or on a machine which has access to the SharePoint on-prem server. +To index your SharePoint on-premises content, you must install and register Graph Connector Agent. See [Install Graph Connector Agent](graph-connector-agent.md) to learn more. Graph Connector Agent can be installed on the same machine as the SharePoint server or on a machine which has access to the SharePoint on-premises server. -Each source (SharePoint web application) can be configured in one connection. One Graph Connector Agent can be used to source content from multiple connections of SharePoint on-prem sources. It is advised to limit the number of connections to an agent to three sources, to ensure an optimal ingestion rate. +Each source (SharePoint web application) can be configured in one connection. One Graph Connector Agent can be used to source content from multiple connections of SharePoint on-premises sources. It's advised to limit the number of connections to an agent to three sources, to ensure an optimal ingestion rate. -User should have full control access to the SharePoint server or should be a farm admin. Items which the user does not have permission are skipped. +User should have full control access to the SharePoint server or should be a farm admin. Items which the user doesn't have permission are skipped. ## Mandatory and optional settings @@ -55,15 +55,15 @@ To get you quickly started with Microsoft Graph connectors, the steps in the set **Mandatory settings** - Default setup screen that you see when you enter the setup flow. You must provide inputs for these fields to create the connection. The inputs (connection name, data source settings, etc.) vary based on your organization's context and use case. -**Custom Setup (optional settings)** - Custom setup has advanced configuration steps for super users. The steps are optional and for your convenience, the settings in the setup process are preconfigured with default values based on the most common selections made by admins. You can choose to accept the default values or modify them to suit your organization's needs. +**Custom Setup (optional settings)** - Custom setup has advanced configuration steps for super users. The steps are optional and for your convenience, the settings in the setup process are pre-configured with default values based on the most common selections made by admins. You can choose to accept the default values or modify them to suit your organization's needs. ## Get started -[Add the SharePoint Server Microsoft Graph connector](https://admin.microsoft.com/adminportal/home#/MicrosoftSearch/Connectors/add) +[Add the SharePoint Server Microsoft Graph connector](https://admin.microsoft.com/adminportal/home#/MicrosoftSearch/Connectors/add). -(For more information, see general [setup instructions](./configure-connector.md)) +For more information, see general [setup instructions](./configure-connector.md). -[![Screenshot that shows connection creation screen for Microsoft Graph Connector for SharePoint Server.](media/sharepoint-server/firstscreen.png)](media/sharepoint-server/firstscreen.png#lightbox) +[![Screenshot that shows connection creation screen for Microsoft Graph Connector for SharePoint Server.](media/sharepoint-server/firstscreen.png)](media/sharepoint-server/firstscreen.png#lightbox). ### 1. Display name @@ -73,19 +73,46 @@ A display name is a user facing name in Copilot. Choose the right display name f Enter the URL for SharePoint site/site collection in the format https://\{domain}/sites/{site-name}. The connector identifies the site url and lists all site collections present in that web application. Admins can choose from these site collections to index the content. -### 3. Select the Graph Connector Agent +### 3. Select Graph Connector Agent Select from the list of available Graph Connector Agents registered to your tenant. ### 4. Authentication -Choose the authentication type from the drop-down menu of options. Currently supported options are Basic and Windows. You need to provide the Username and Password for the SharePoint site. +Choose the authentication type from the drop-down menu of options. Currently supported options are Basic, Windows and Microsoft Entra ID. > [!NOTE] > Use Domain\username format in username to authenticate to the SharePoint server instance using the Windows option. To authenticate with the provided credentials, you need to click on Sign-in to load the list of available site collections. +#### Microsoft Entra ID based authentication for Microsoft SharePoint Server Graph Connector + +Before using Entra ID based authentication method, ensure the following prerequisites are met: + +- Microsoft Entra ID based authentication is supported for Graph Connector Agent versions 3.1.2.0 and above. Upgrade your agent before proceeding. See [Install Graph Connector Agent](graph-connector-agent.md) to learn more. +- Microsoft Entra ID based authentication is supported only for SharePoint Server Edition. Take the path released in November 2024 (patch 16.0.17928.20238) or later from [SharePoint Updates](/officeupdates/sharepoint-updates). +- You'll need to set up OpenID Connect (OIDC) with Microsoft Entra ID. Hence, ensure that SharePoint must use HTTPS as OpenID Connect (OIDC) step requires HTTPS. + +##### Steps + +1. [Download](https://www.microsoft.com/download/details.aspx?id=47594) Microsoft Entra ID Connect. +1. Follow [steps](/entra/identity/hybrid/connect/how-to-connect-install-roadmap) to install Microsoft Entra ID Connect. +1. Set up and enable OpenID Connect (OIDC) with Microsoft Entra ID using the steps [here](/sharepoint/security-for-sharepoint-server/set-up-oidc-auth-in-sharepoint-server-with-msaad). This step will require you to set up third party application in your Azure portal. Ensure that you have admin rights to perform this step. + +###### Configure "Expose an API" + +- Go to "Expose an API" tab from the left hand navigation pane. Make sure the application ID uri matches your sharepoint server URL. + + [![Screenshot that shows expose an api configuration.](media/sharepoint-server/exposeanapi.png)](media/sharepoint-server/exposeanapi.png#lightbox) + +- Click "Add a scope", enter user_impersonation for scope name, admin consent display name, and admin consent description. +- Click "Add a client application", enter GCA's client id cb15c983-0c91-416f-8dc0-6c0e1de4ed42 + + [![Screenshot that shows how to add client application](media/sharepoint-server/addclientappgca.png)](media/sharepoint-server/addclientappgca.png#lightbox) + +- Check user_impersonation scope. + ### 5. Select Site Collections Select which site collections you want to index. The site collections belong to the web application that we identify from the SharePoint url provided. This list can be long based on the number of site-collections available in the data source. @@ -106,13 +133,13 @@ Once the connection creation is successful, it starts syncing the content. At th [![Screenshot that shows success screen.](media/sharepoint-server/successscreen.png)](media/sharepoint-server/successscreen.png#lightbox) -## Custom Setup +## Custom Set up -Custom setup is for those admins who want to edit the default values for settings. Once you click on the "Custom Setup" option, you see three more tabs - Users, Content, and Sync. +Custom set up is for those admins who want to edit the default values for settings. Once you click on the "Custom Set up" option, you see three more tabs - Users, Content, and Sync. -If you edit any connection, it always opens in a custom setup window. +If you edit any connection, it always opens in a custom set up window. -[![Screenshot that shows custom setup window.](media/sharepoint-server/customsetup.png)](media/sharepoint-server/customsetup.png#lightbox) +[![Screenshot that shows custom set up window.](media/sharepoint-server/customsetup.png)](media/sharepoint-server/customsetup.png#lightbox) ### Users @@ -126,19 +153,19 @@ The below options are available. > [!NOTE] > Graph Connectors support Users, Security Groups and Distribution Lists. However, the data source (SharePoint Server) does not support Distribution Lists as Access Control Lists. If there are nested distribution lists, members of those distribution lists may also get access to content through Graph connectors. -The default and preferred option is the one where connector honors the data source permissions and only allowed users can see the results. You are free to change it to "Everyone" if you want to make it available for everyone in the organization. +The default and preferred option is the one where connector honors the data source permissions and only allowed users can see the results. You're free to change it to "Everyone" if you want to make it available for everyone in the organization. [![Screenshot that shows users tab](media/sharepoint-server/userstabsp.png)](media/sharepoint-server/userstabsp.png#lightbox) -The SharePoint on-prem connector supports existing Access Controlled List on given items. Indexed data appears in the search results and is visible to users who have permission to view it. Microsoft 365 experiences understand and honor Entra Id permissions. To support Access Controlled Lists on items, we require that Active Directory identities and Entra Identities are synced. +The SharePoint on-premises connector supports existing Access Controlled List on given items. Indexed data appears in the search results and is visible to users who have permission to view it. Microsoft 365 experiences understand and honor Entra Id permissions. To support Access Controlled Lists on items, we require that Active Directory identities and Entra Identities are synced. ### Content #### Add site urls to exclude from indexing -Add the URLs of the sites you want to exclude from indexing. Exclusion rules work at the site or subsite level. Add site URLs to exclude them from crawling. Do not add URLs of site contents. If the URL contains site contents such as documents, it is not be honored. To exclude all site contents or subsites that start from these URLs, use * at the end of the URL. +Add the URLs of the sites you want to exclude from indexing. Exclusion rules work at the site or sub-site level. Add site URLs to exclude them from crawling. Don't add URLs of site contents. If the URL contains site contents such as documents, it isn't honored. To exclude all site contents or sub-sites that start from these URLs, use * at the end of the URL. -If the URL ends with /\*, then all URLs prefixed with this URL are excluded from crawl. Example, abc.com/private/* excludes abc.com/private/terms.html and all content inside "/private". But, if you provide abc.com/private/terms.html as the URL to exclude, it is not honored as exclusion rules work at site or subsite level. +If the URL ends with /\*, then all URLs prefixed with this URL are excluded from crawl. Example, abc.com/private/* excludes abc.com/private/terms.html and all content inside "/private". But, if you provide abc.com/private/terms.html as the URL to exclude, it is not honored as exclusion rules work at site or sub-site level. [![Screenshot that shows exclusion rules.](media/sharepoint-server/exclusionrulessp.png)](media/sharepoint-server/exclusionrulessp.png#lightbox) @@ -162,7 +189,7 @@ Properties define what data is available for searching, querying, retrieving and | ObjectType | | The type of object as returned from the data source | Query, Retrieve, Search | | Url | | Item url | Retrieve | -You can add custom properties defined in your sites to better manage the search or Copilot outcomes for your users. To add the custom property, click "Add Property" where you need to specify the exact string from the data source. To configure a custom property, you define a property name and specify a data type (String, StringCollection, DateTime, Boolean, Int64, and Double). Custom properties match the custom columns in SharePoint. Be careful when specifying property names as the connector ignores any property names that do not match with any existing properties during crawling. To avoid any issues, double check property names to ensure they are spelled correctly. +You can add custom properties defined in your sites to better manage the search or Copilot outcomes for your users. To add the custom property, click "Add Property" where you need to specify the exact string from the data source. To configure a custom property, you define a property name and specify a data type (String, StringCollection, DateTime, Boolean, Int64, and Double). Custom properties match the custom columns in SharePoint. Be careful when specifying property names as the connector ignores any property names that don't match with any existing properties during crawling. To avoid any issues, double check property names to ensure they're spelled correctly. > [!NOTE] > Currently a total of 128 properties are supported. If you are selecting multiple site collections in a single connection, only default properties are supported. If you want to support custom properties defined in a site, create a different connection and add custom properties for that site. @@ -171,7 +198,7 @@ You can add custom properties defined in your sites to better manage the search The refresh interval determines how often your data is synced between the data source and the Graph connector index. There are two types of refresh intervals - full crawl and incremental crawl. For more information, see [refresh settings](configure-connector.md#step-8-refresh-settings). -The default values setup for the connector are: +Default values of refresh interval: | Sync | Description | |---|---| diff --git a/MicrosoftSearch/toc.yml b/MicrosoftSearch/toc.yml index a4f6a517..cc197bd4 100644 --- a/MicrosoftSearch/toc.yml +++ b/MicrosoftSearch/toc.yml @@ -50,6 +50,12 @@ items: href: connectors-overview.md - name: Connectors gallery href: connectors-gallery.md + - name: Frequently asked questions + href: frequently-asked-questions.md + - name: Index quota + href: licensing.md + - name: Terms of use + href: terms-of-use.md - name: Set up Microsoft-built connectors items: - name: Setup overview @@ -141,6 +147,10 @@ items: href: fileshare-connector.md - name: Troubleshooting href: troubleshoot-file-share-connector.md + - name: GitHub (preview) + items: + - name: Setup + href: GitHub-connector.md - name: Google Drive items: - name: Setup @@ -150,11 +160,7 @@ items: - name: Setup href: mediawiki-connector.md - name: Troubleshooting - href: troubleshoot-media-wiki-connector.md - - name: MediaWiki - items: - - name: Setup - href: mediawiki-connector.md + href: troubleshoot-media-wiki-connector.md - name: Oracle SQL items: - name: Setup @@ -201,8 +207,6 @@ items: items: - name: Setup href: zendesk-help-center-connector.md - - name: Deploy Microsoft Graph connectors in Teams admin center - href: connectors-deploy-teams.md - name: Manage connections items: - name: Monitor connections @@ -215,12 +219,8 @@ items: href: connector-error-responses.md - name: Item delete notification href: connectors-viva-topics-item-delete-notification.md - - name: Index quota - href: licensing.md - - name: Frequently asked questions - href: frequently-asked-questions.md - - name: Terms of use - href: terms-of-use.md + - name: Deploy Microsoft Graph connectors in Teams admin center + href: connectors-deploy-teams.md - name: Federated Search connectors items: - name: Dataverse and Dynamics 365