| Service | Microsoft Docs article | Related commit history on GitHub | Change details |
|---|---|---|---|
| SharePoint | Delve Retirement | https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointOnline/delve-retirement.md | + Last updated : 09/24/2024 + Title: "Guidance for retiring Delve in your organization" +++++recommendations: true +audience: Admin +f1.keywords: +- NOCSH ++++ms.localizationpriority: medium ++search.appverid: +- SPO160 +- MOE150 +- DEL150 +- FRP150 +- MET150 +ms.assetid: 54f87a42-15a4-44b4-9df0-d36287d9531b +description: "With the December 2024 planned retirement of Delve, this article contains information to assist administrators with the Delve offboarding process." ++++# Guidance for retiring Delve in your organization ++In December 2024, Delve will be retired. This change was first announced in an MC Post available in the [Microsoft 365 Message Center](https://admin.microsoft.com/Adminportal/Home?#/MessageCenter/:/messages/MC698136). There's also an article you can refer to, [Alternatives to Delve in Microsoft 365](https://support.microsoft.com/office/alternatives-to-delve-in-microsoft-365-59e29736-de90-40ce-93ee-0bbe23902a42), that focuses on helping end users find alternatives for their tasks within Microsoft 365. The purpose of this article is to assist administrators with the Delve offboarding process. ++## What will be retired? ++Delve offers many features that are built on top of multiple Microsoft 365 services. When we say we're retiring Delve, it's important to note that we're not changing or retiring anything on the services side. Both documents and people data that are surfaced in Delve will continue to be stored and managed as today. ++There are a couple of exceptions regarding data storage. Delve stores a limited set of Delve-specific data, such as list of users recently viewed in Delve, Delve favorite documents, Delve favorite tags, and some Delve-specific settings. These will be retired together with Delve. You can export this data before December 16, 2024, in Delve by going to **Select settings** > **Feature settings** > **Export data**. ++## Where can users view user properties currently surfaced in Delve? ++Starting December 2024, properties currently surfaced in Delve, including custom user profile properties, will be added to the profile cards available in search experiences on Microsoft365.com, Office.com, and in SharePoint. Eventually, these changes will be enabled everywhere the profile card is available. However, for technical reasons, this change will take time. For December 2024, we recommend directing users to Microsoft365.com, Office.com, or SharePoint, which also offer a people search similar to what's offered in the Delve search. ++## Direct links to profile cards ++The modern search experiences on Microsoft365.com, Office.com, and in SharePoint include profile pages built on the same data as profile cards. They have a unique link and can be used in documentation, email signatures, etc. Starting December 16, we'll handle redirects from Delve profiles to these profile pages on Microsoft365.com. Although there are three places and URLs that offer the same experience, we suggest you refer to Microsoft365.com. ++### Example links ++- For Microsoft365.com: ++ :::image type="content" source="media/delve-retirement-microsoft365-links.png" alt-text="Screenshot showing an example link syntax for Microsoft 365."::: ++- For Office.com: ++ :::image type="content" source="media/delve-retirement-office-links.png" alt-text="Screenshot showing an example link syntax for Office.com."::: ++- For SharePoint: ++ :::image type="content" source="media/delve-retirement-sharepoint-links2.png" alt-text="Screenshot showing an example link syntax for SharePoint."::: ++## What happens to existing URLs pointing to Delve or SharePoint profiles? ++Both Delve URLs and SharePoint profile URLs will be redirected to the modern search profile pages on Microsoft365.com. For tenants not using Delve today, there will be no change to URLs and their legacy profile experiences in SharePoint. However, they get the extended profile page in modern search and the extended profile cards across Microsoft 365, which will include the properties that are visible in Delve. ++## Where can users edit properties currently editable in Delve? ++A new edit profile experience, tightly coupled with the profile card, is currently being developed and is targeted for release in November 2024. This will allow users to easily edit their profiles across Microsoft 365. Some properties that are viewable in Delve today aren't editable in Delve, but in the SharePoint edit profile experience. ++The same will be true for the new edit experience. Only properties that today are editable in the Delve edit profile experience will be editable in the profile cards. For other properties, for example custom user profile properties, users will have to go to the legacy edit profile experience in SharePoint. ++Visibility attributes follow the same pattern. Users won't be able to change them in the new edit experience and will have to go to the legacy edit profile experience in SharePoint. To make this effortless, a link to the legacy edit profile experience will be part of the new experience. ++The link to the legacy SharePoint edit profile experience. ++The SharePoint Edit Details dialog box. ++## What will the new edit experience in profile cards look like? ++The new edit profile experience is built on top of Microsoft 365 profile cards, and it will be presented in an overlay as profile cards are handled today. A most common user pattern is for the user to open their own profile card and select "edit profile." Instead of being redirected to Delve, the edit experience will open in the profile card. Below is an example of what this process will look like. ++Please note that if the new edit profile experience isn't yet enabled in the experience where a user is, clicking "edit profile" will redirect the user to the modern search profile page on Microsoft365.com. ++++## Where can users search for people and user profile properties that are currently supported in Delve? ++Users can search for people in the modern search experience in Microsoft365.com, Office.com, and SharePoint. Classic search will continue to work as before and clicks on people results that today link to Delve will redirect to the modern search profile page on Microsoft365.com. ++Note that people are presented in multiple ways in modern search. Clicks on a people result in the "all" vertical will take the user to the modern search profile experience. Clicks on people results in the people vertical will open the large profile card. Both experiences will include properties that today are surfaced in Delve. ++## Custom people search solutions ++If your tenant depends on custom solutions for people search it should continue to work as before. They're built on services powering Delve and not on the Delve experience itself. One common third-party solution in use is the PnP Modern Search app. This particular app allows administrators to create custom search-based experiences based on SharePoint web parts. It's easy to configure people results to support opening profile cards on hover and click. It's also possible to include links to Delve profiles and the legacy SharePoint profile (_person.aspx_/_personimmersive.aspx_). These links will continue to work as users will be redirected to the modern search profile page in Microsoft365.com. ++## Properties not supported by the new edit experience ++In general, the new edit experience built on profile cards will support editing properties in the profile card, but there are exceptions. One exception is with properties hosted by Microsoft Entra ID and synced to UPA (SharePoint). By default, these aren't editable in Delve or in the legacy profile edit experience in SharePoint. However, administrators can override the default behavior to make them editable for the user. If administrators make this change, some properties can be edited in Delve, and some can be edited in the legacy edit profile experience in SharePoint. ++The new edit profile experience built on profile cards won't support editing these properties. Users can still edit them if administrators have made the setting changes mentioned above, in the legacy edit profile experience, but by default they'll not be visible anywhere and only provide value if you have a custom solution. The following list contains these properties. ++### Properties synced from Microsoft Entra ID that aren't editable (by default) in Delve ++- UserPrincipalName +- DisplayName +- GivenName +- Sn +- telephoneNumber +- proxyAddresses +- PhysicalDeliveryOfficeName +- Title +- Department +- WWWHomePage +- PreferredLanguage +- msExchHideFromAddressList +- Manager ++## When will Delve no longer be available? ++Delve will be retired on December 16, 2024. The extended profile card experience, the updated profile pages in modern search, and the new edit profile experience will be available before Delve is retired. For a limited period, both Delve and the new experiences will be available for users. Delve retires when the redirect of Delve URLs is activated. ++## What do we recommend administrators do? ++- Educate your users about the upcoming changes by updating internal documentation and training material relevant for the Delve retirement. +- Once released, validate that your users can solve their Delve tasks in the new edit profile experience, updated profile pages in modern search, people search in Microsoft365.com, and in the extended profile cards. ++## More resources ++[Alternatives to Delve in Microsoft 365](https://support.microsoft.com/office/alternatives-to-delve-in-microsoft-365-59e29736-de90-40ce-93ee-0bbe23902a42) ++[Add and edit user profile properties in SharePoint](add-and-edit-user-profile-properties.md) ++[Tips and tricks on how to search for organizational content more effectively](https://techcommunity.microsoft.com/t5/microsoft-search-blog/tips-and-tricks-on-how-to-search-for-organizational-content-more/ba-p/3838452) ++[Profile cards in Microsoft 365](https://support.microsoft.com/en-us/office/profile-cards-in-microsoft-365-e80f931f-5fc4-4a59-ba6e-c1e35a85b501) ++[User profile synchronization](user-profile-sync.md) |
| SharePoint | Restricted Sharepoint Search | https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointOnline/restricted-sharepoint-search.md | description: "Helps you prevent certain content on SharePoint sites from being s ## What is Restricted SharePoint Search? -Restricted SharePoint Search is a setting that helps you as a [SharePoint Administrator](/sharepoint/sharepoint-admin-role) or [above](/microsoft-365/admin/add-users/about-admin-roles) in Microsoft 365 to maintain a list of SharePoint sites ("allowed list") that you have checked the permissions and applied data governance for. The allowed list defines which SharePoint sites can participate in organization-wide search and Copilot experiences. By default, the Restricted SharePoint Search setting is turned off and the allowed list is empty. This feature is currently available as Public Preview for customers who have Microsoft 365 and Copilot licenses. +Restricted SharePoint Search is a setting that helps you as a [SharePoint Administrator](/sharepoint/sharepoint-admin-role) or [above](/microsoft-365/admin/add-users/about-admin-roles) in Microsoft 365 to maintain a list of SharePoint sites ("allowed list") that you have checked the permissions and applied data governance for. The allowed list defines which SharePoint sites can participate in organization-wide search and Copilot experiences. By default, the Restricted SharePoint Search setting is turned off and the allowed list is empty. Restricted SharePoint Search allows you to restrict both organization-wide search and Copilot experiences to a curated set of SharePoint sites of your choice. Additionally, whether you have enabled Restricted SharePoint Search, users in your organization are still able to interact with files and content they own or that they have previously accessed in Copilot. |
| SharePoint | Sharepoint View In Edge | https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointOnline/sharepoint-view-in-edge.md | - Previously updated : 09/08/2021 Title: "View SharePoint files with File Explorer in Microsoft Edge"---- -recommendations: true -- NOCSH----- Strat_SP_admin-- M365-collaboration--- seo-marvel-apr2020-- SPO160-- BSA160-- GSP150-- MET150-description: "Learn about SharePoint view in File Explorer for Microsoft Edge." ---# View SharePoint files with File Explorer in Microsoft Edge --> [!IMPORTANT] -> In June 2022, we stopped supporting Internet Explorer 11 (IE 11) at Microsoft 365 apps and services. As a result, we no longer recommend View in File Explorer and encourage using the OneDrive sync client. The OneDrive sync client provides [Files On-Demand](https://support.office.com/article/0e6860d3-d9f3-4971-b321-7092438fb38e), which allows you to access all your files in SharePoint without using up local storage space. For info about using OneDrive to sync SharePoint files, visit [SharePoint file sync](sharepoint-sync.md). --By default, the View in File Explorer menu option won't be visible to you or users in the SharePoint modern document library interface. In certain cases, organizations may still need to use View in File Explorer to access modern document libraries. Starting in Microsoft Edge Stable version 93, you can enable the View in File Explorer capability on SharePoint for modern document libraries. --## Configure View in File Explorer with Microsoft Edge --Follow the steps below to use View in File Explorer in Microsoft Edge: --1. Verify that devices are on Microsoft Edge build 93 or later using [Find out which version of Microsoft Edge you have](https://support.microsoft.com/en-us/microsoft-edge/find-out-which-version-of-microsoft-edge-you-have-c726bee8-c42e-e472-e954-4cf5123497eb). --2. Ensure that Windows instances are joined to a Microsoft Active Directory domain, Windows 10 Pro, or Enterprise instances that are enrolled for device management. --3. Enable the [ConfigureViewInFileExplorer](/deployedge/microsoft-edge-policies#configureviewinfileexplorer) policy for Microsoft Edge that allows URLs with the viewinfileexplorer: scheme to open WebDAV URLs in Windows File Explorer. --Use the options below to enable View in File Explorer using group policy or Intune: --- **To enable by using group policy**:-- 1. Configure Microsoft Edge policy settings by following the steps at [Configure Microsoft Edge policy settings on Windows](/deployedge/configure-microsoft-edge). -- 2. Make sure you've downloaded the Microsoft Edge administrative template [based on the operating system version](/troubleshoot/windows-client/group-policy/create-and-manage-central-store#links-to-download-the-administrative-templates-files-based-on-the-operating-system-version) or you may not see the policy listed. -- 3. Once the template is downloaded, open the Group Policy Object Editor. Right-click **Administrative Templates** in the Computer Configuration or User Configuration node and select **Add/Remove Templates** and browse to the downloaded template. -- 4. When applying the policy, ensure you update the domain to your tenant domain or use **sharepoint.com** if you plan on visiting multiple SharePoint tenants. -- 5. Enabling the group policy may require a refresh of client group policy settings. After changing the group policy settings, refresh the settings. From a Command Prompt, enter **GPUpdate.exe /force**. -- Example below with the Group Policy value: -- `[{"cookies": ["rtFa", "FedAuth"], "domain": "sharepoint.com"}]` -- :::image type="content" source="media/edgepolicy-adeejoseph.png" alt-text="Enable Configure the View in File Explorer feature for SharePoint pages in Microsoft Edge"::: -- For more examples, see [ConfigureViewInFileExplorer](/deployedge/microsoft-edge-policies#configureviewinfileexplorer) on Microsoft Edge policy reference. --- **To enable by using Intune**:-- Configure Microsoft Edge policy settings by following the steps at [Configure Microsoft Edge policy settings with Microsoft Intune](/deployedge/configure-edge-with-intune). --5. Verify the policy has been enabled by opening Microsoft Edge and navigating to **Microsoft Edge://policy/**. -- :::image type="content" source="media/microsoft-edge-policy.png" alt-text="Snapshot of Microsoft Edge Policies page "::: -- > [!TIP] - > You may need to close and re-open Microsoft Edge for the policy to appear. --6. As a tenant administrator, update your SharePoint Online tenant configuration via SharePoint Online Management Shell to allow the "View in File Explorer" option to be visible in the Microsoft Edge Browser interface with these steps: -- 1. Connect to SharePoint Online Management Shell by running: -- ```PowerShell - Connect-SPOService -Url https://contoso-admin.sharepoint.com - ``` -- 1. Run the following cmdlet to show the "View in File Explorer" menu option: -- ```PowerShell - Set-SPOTenant -ViewInFileExplorerEnabled $True - ``` -- > [!NOTE] - > Ensure the management shell version is 16.0.21610.12000 or higher or the ViewInFileExplorerEnabled option will not be available. --7. **(Required)** _View in File Explorer_ requires persistent cookies to operate correctly; when you sign in, select **Yes** when the **Stay signed in?** prompt appears. -- You can locate the View in Explorer button by navigating to the **Library** > Select the **Library View Menu** on the right-hand side > Select **View In File Explorer**. -- :::image type="content" source="media/view-in-file-explorer.png" alt-text="Menu for View in File Explorer"::: -- > [!NOTE] - > Once the tenant setting has been enabled, it may take up to 15 minutes for the View in Explorer button to appear in the SharePoint interface. --### Troubleshooting --**How can I confirm that the ConfigureViewInFileExplorer policy has been applied?** --You can verify that the policy has been applied by navigating to **edge://policy**. --**The error message _This policy is blocked - its value will be ignored_ appeared while checking to see if the policy was applied via edge://policy. What's wrong?** --This error occurs when you attempt to apply this policy to a nondomain joined device. Currently, the ConfigureViewInFileExplorer policy can only be applied to Windows instances that are joined to a Microsoft Active Directory domain, Windows 10 Pro, or Enterprise instances enrolled for device management. ---**What happens if I have the policy applied without the tenant setting enabled?** --If you don't enable ViewInFileExplorerEnabled via [Set-SPOTenant](/powershell/module/sharepoint-online/set-spotenant?view=sharepoint-ps&preserve-view=true), the View in File Explorer button won't appear in the interface of the SharePoint site. --**What happens if the tenant setting is enabled without the Edge policy applied?** --If you have enabled ViewInFileExplorerEnabled, you may see the View In File Explorer button appear in your SharePoint library, however, clicking the button results in a blank screen. ---**When running Set-SPOTenant -ViewInFileExplorerEnabled $True I received the error "The requested operation is part of an experimental feature that is not supported in the current environment". What's wrong?** --You may receive this error if this functionality isn't supported in your current environment. We're still rolling out functionality to all Production environments and will update this article once worldwide rollout has been completed. --## Learn More --- [Sync SharePoint and Team files with your computer](https://support.microsoft.com/office/sync-sharepoint-and-teams-files-with-your-computer-6de9ede8-5b6e-4503-80b2-6190f3354a88)-- [View and open SharePoint with File Explorer](https://support.microsoft.com/office/view-and-open-sharepoint-files-with-file-explorer-66b574bb-08b4-46b6-a6a0-435fd98194cc)-- [Troubleshoot View in File Explorer](/sharepoint/troubleshoot/lists-and-libraries/troubleshoot-issues-using-open-with-explorer)-- [Set-SPOTenant](/powershell/module/sharepoint-online/set-spotenant?view=sharepoint-ps&preserve-view=true)-- [OneDrive sync reports in the Apps Admin Center](/onedrive/sync-health) |