Datasets:

anihitk07

/

ms_docs

like 0

title: "Customize address bar shortcuts for Microsoft Edge" ms.author: davidedwards author: dawholl manager: kellis ms.audience: Admin ms.topic: article ms.service: mssearch localization_priority: Normal ms.date: 03152022 search.appverid: - BFB160 - MET150 - MOE150 description: "Add custom Microsoft Edge shortcuts for Microsoft Search in Bing or turn off these shortcuts for your organization" Customize address bar shortcuts for Microsoft Edge Help your users stay focused and find work results faster when searching from the Microsoft Edge address bar. Two shortcuts are enabled by default, 'work' and your organization's preferred or shortened name. In the Microsoft Edge address bar, users can type a keyword, then press the Tab key. The address bar will indicate they're searching within your organization. When they type their search and press the Enter key, they'll see a search results page with relevant answers and results. You can add two custom shortcuts keywords. :::image type="content" alt-text="Animated GIF of entering work keyword and using Microsoft Edge shortcut to search work." source="mediaedge-shortcutsmicrosoft-edge-address-bar-shortcut.gif" lightbox="mediaedge-shortcutsmicrosoft-edge-address-bar-shortcut.gif"::: [!NOTE] This article applies to Microsoft Edge version 96 or later. Manage shortcuts and keywords In the Microsoft 365 admin center, go to Configurations. Under Microsoft Search in Bing shortcut, select Change. In the panel, Enable the Microsoft Search in Bing shortcut is selected by default. To disable these shortcuts, clear the check box. In Search Keywords field, enter one or two more keywords. You can include spaces and special characters. Select Save. Frequently asked questions Q: The keywords don't work. What's wrong? A: In the Microsoft Edge address bar, enter edge:settingssearch to go to your search settings. Verify that Show me search and site suggestions using my typed characters is enabled. You can also use Microsoft Edge group policy to enable search suggestions. To learn more, see SearchSuggestEnabled. Q: Do these shortcuts only support English keywords? A: No. For localized keywords, you'll need to add the language-specific keyword in the Search Keywords field. Q: How long does it take for new keywords to be recognized as shortcuts? A: It takes up to two days for Microsoft Edge to recognize custom keywords as a shortcut. Q: Can I add shortcuts for my Google Chrome users? A: Not through the Microsoft 365 admin center. Users can create their own shortcuts in Chrome by going to settings for Manage search engines, and under Other search engines, adding a site name, keyword, and Query URL. Q: Can I use these same keywords when using Windows Search? A: No, only Microsoft Edge supports these keywords shortcuts.

OfficeDocs-MicrosoftSearch/MicrosoftSearch/edge-shortcuts.md/0

Customize address bar shortcuts for Microsoft Edge

OfficeDocs-MicrosoftSearch/MicrosoftSearch/edge-shortcuts.md

OfficeDocs-MicrosoftSearch

title: "Monitor Microsoft Graph connectors for Microsoft Search" ms.author: mecampos author: monaray97 manager: mnirkhe audience: Admin ms.audience: Admin ms.topic: article ms.service: mssearch ms.localizationpriority: medium search.appverid: - BFB160 - MET150 - MOE150 description: "Monitor your connection state and index quota utilization." ms.date: 10082019 Monitor your connections To access and manage your Microsoft Graph connectors, you must be designated as a search administrator for your organization. Contact your administrator to assign you the search administrator role. Connection operations In the Microsoft 365 admin center, go to the Connectors tab. For each connector type, the Microsoft 365 admin center supports the operations shown in the following table. Operation Connectors by Microsoft Connectors by partners --- --- --- Add a connection :heavy_check_mark: (see Setup overview) :x: (refer to your partner or custom-built connector admin UX) Delete a connection :heavy_check_mark: :heavy_check_mark: Edit a published connection :heavy_check_mark: Name and description :heavy_check_mark: Connection settings :heavy_check_mark: Property labels :heavy_check_mark: Schema :heavy_check_mark: Refresh schedule :heavy_check_mark: Name :heavy_check_mark: Description Edit a draft connection :heavy_check_mark: :x: Monitor your connection state After you create a connection, the number of processed items shows on the Connectors tab on the Microsoft Search page. After the initial full crawl completes successfully, the progress for periodic incremental crawls displays. This page provides information about the connector's day-to-day operations and an overview of the logs and error history. Five states show up in the State column against each connection: Syncing. The connector is crawling the data from the source to index the existing items and make any updates. Ready. The connection is ready, and there's no active crawl running against it. Last sync time indicates when the last successful crawl happened. The connection is as fresh as the last sync time. Paused. The crawls are paused by the admins through the pause option. The next crawl runs only when it's manually resumed. However, the data from this connection continues to be searchable. Failed. The connection had a critical failure. This error requires manual intervention. The admin needs to take appropriate action based on the error message shown. Data that was indexed until the error occurred is searchable. Next section talks about getting notified if such failures happen in a connection. Delete Failed. The deletion of the connection failed. Depending upon the failure reason, the data might still be indexed, item quota might still be consumed, and crawls might still run for the connection. We recommend that you try deleting the connection again in this state. Notifications for permanent crawl failures in your connections The connection crawls are scheduled to run at specific times. The crawls can fail because of certain issues in the connections. Some times these issues are temporary and the crawls resume automatically and some times these failures are permanent where admin intervention is needed to start the crawls. In such cases of permanent failures, we mark the connection as "Failed" and send notifications to the Service Health Dashboard under the section: Issues for your organization to act on. :::image type="content" alt-text="Screenshot that shows issues in your environment section of Service health." source="mediamanage-connectorshd-notification-home.png" lightbox="mediamanage-connectorshd-notification-home.png"::: The same can also be seen in the form of Advisory in the "Service Status" section of Service Health page, under Microsoft 365 suite category. :::image type="content" alt-text="Screenshot that shows service status section" source="mediamanage-connectornotification-service-status.png" lightbox="mediamanage-connectornotification-bar-mac.png"::: If there are active notifications, admins get alerts in the form of notification bars in the Microsoft admin center home page. Notification bars contain the connectionId of the connection for which the crawls have failed. Admins can navigate to see more details of the notifications or remove the notification bars from the page. :::image type="content" alt-text="Screenshot that shows sample notification bar" source="mediamanage-connectornotification-bar-mac.png" lightbox="mediamanage-connectornotification-bar-mac.png"::: Admins can check the notification details by clicking the notification. :::image type="content" alt-text="Screenshot that shows sample notification" source="mediamanage-connectorsample-notification.png" lightbox="mediamanage-connectorsample-notification.png"::: Some points to note: The notification is live in the Service Health Dashboard for six days. After that the notification is automatically moved to the "Issue History" section where the same is stored for a maximum of 30 days. If the connection resumes the crawl, the notification is automatically moved to the "Issue History" section. No new notification is sent for the same connection until the crawls on that connection restart. Once the crawls are restarted and if a failure happens again, a new notification is sent. If there are crawl failures in multiple connections, each connection has a separate notification bar in the admin center home page and service health dashboard landing page. Subscribing for getting notifications in e-mail To get these failure notifications and updates on the e-mail, admins can add up to two e-mail addresses for the same. Go to Customize section in Service Health page and open the Email tab. Select the check box for - Issues in your environment that require action. In the "Include these services" section, select Microsoft 365 suite. Admins get all notifications for Microsoft 365 suite, including Graph connector notifications, after they subscribe to the service health notifications. Save :::image type="content" alt-text="Screenshot that shows e-mail subscription for notifications" source="mediamanage-connectornotification-mail.png" lightbox="mediamanage-connectoron-demand-crawl.png"::: Manage crawls in your connections During connection creation or edit connection flow, you can configure the crawl schedule through Refresh Settings. To learn more about different types of crawls available see: Setup Overview. Apart from the scheduled crawls, you can run on-demand crawls for your connection through the connection pane. :::image type="content" alt-text="Screenshot that shows on-demand crawl connection pane." source="mediamanage-connectoron-demand-crawl.png" lightbox="mediamanage-connectoron-demand-crawl.png"::: On-demand crawl helps you start a crawl irrespective of the crawl schedule. You can choose to run a full or incremental crawl using the drop-down as shown in the image: :::image type="content" alt-text="Screenshot that shows on-demand crawl drop-down." source="mediamanage-connectoron-demand-dropdown.png" lightbox="mediamanage-connectoron-demand-dropdown.png"::: [!NOTE] Graph Connector Agent, only from version 2.1.0.0 onwards, supports on-demand crawl. There can be only one category of crawl, scheduled or on-demand, running on a connection at any time. If a connection is in "Syncing" state, on-demand crawls are disabled. Scheduled crawls are auto triggered. If a scheduled or an on-demand crawl continues beyond the time of the schedule of the next full or incremental crawl, the ongoing crawl is stopped, and the next scheduled crawl is skipped and queued. After the ongoing crawl completes, the crawl of the opposite type (full or incremental) is picked from the skipped queue and triggered. For example, if the previous crawl was of the type full crawl, only the incremental crawl, if present in the skipped queue, is triggered and vice versa. Monitor your index quota utilization The available index quota and consumption is displayed on the connectors landing page. :::image type="content" alt-text="Screenshot that shows index quota utilization bar." source="mediamanage-connectorquota-exceeded.png" lightbox="mediamanage-connectorquota-exceeded.png"::: The quota utilization bar indicates various states based on consumption of quota by your organization: State Quota utilization levels --- --- Normal 0–79% High 80–89% Critical 90%–99% Quota Exceeded >=100% The number of items indexed is also displayed with each connection. The number of items indexed by each connection contributes to the total quota available for your organization. When index quota is exceeded for your organization, all active connections are impacted, and those connections operate in a limit exceeded state. In this state, your active connections: Will not be able to add new items. Are able to update or delete existing items. To fix this, you can do any of the following actions: Purchase index quota for your organization, to learn more see: Licensing requirements and pricing. Identify connections that have some items that you didn't want to index. To update this connection, you must delete and create a new connection with a data source exclusion filter to exclude the items you don't want to index anymore. Permanently delete one or more connections.

OfficeDocs-MicrosoftSearch/MicrosoftSearch/manage-connector.md/0

Monitor your connections

OfficeDocs-MicrosoftSearch/MicrosoftSearch/manage-connector.md

OfficeDocs-MicrosoftSearch

title: Allow or prevent custom script ms.reviewer: lucaband ms.author: ruihu author: maggierui manager: jtremper recommendations: true ms.date: 05142024 audience: Admin f1.keywords: - CSH ms.topic: article ms.custom: - 'O365M_NoScript' - 'O365E_NoScript' - 'seo-marvel-apr2020' - admindeeplinkSPO ms.service: sharepoint-online ms.localizationpriority: medium ms.collection: - Strat_SP_admin - M365-collaboration search.appverid: - SPO160 - ODB160 - ODB150 - BSA160 - MET150 ms.assetid: 1f2c515f-5d7e-448a-9fd7-835da935584f description: Learn how global and SharePoint admins can change the custom script setting for SharePoint sites in the organization. Allow or prevent custom script As a Global Administrator or SharePoint Administrator in Microsoft 365, you can allow custom script as a way of letting users change the look, feel, and behavior of sites and pages to meet organizational objectives or individual needs. If you allow custom script, all users who have Add and Customize Pages permission to a site or page can add any script they want. (By default, users who create sites are site owners and therefore have this permission.) [!NOTE] For simple ways to change the look and feel of a site, see Change the look of your SharePoint site. By default, script is not allowed on most sites that admins create using the SharePoint admin center as well as all sites created using the New-SPOSite PowerShell command. Same applies to OneDrive, sites users create themselves, modern team and communication sites, and the root site for your organization. For more info about the security implications of custom script, see Security considerations of allowing custom script. [!IMPORTANT] If SharePoint was set up for your organization before 2015, your custom script settings might still be set to Not Configured even though in the SharePoint admin center they appear to be set to prevent users from running custom script. In this case, users won't be able to copy items between SharePoint sites and between OneDrive and SharePoint. On the Settings page in the SharePoint admin center, to accept the custom script settings as they appear, select OK, and enable cross-site copying. For more info about copying items between OneDrive and SharePoint, see Copy files and folders between OneDrive and SharePoint sites. To allow custom script on OneDrive or user-created sites [!NOTE] This feature will be removed during H1 calendar year 2024. Once removed, it will no longer be possible to allow custom script on OneDrive sites. In the SharePoint admin center, you can choose to allow users to run custom script on OneDrive (referred to as personal sites) or on all classic team sites they create. For info about letting users create their own sites, see Manage site creation in SharePoint. [!CAUTION] Before you allow custom script on sites in your organization, make sure you understand the security implications. Go to Settings in the SharePoint admin center, and sign in with an account that has admin permissions for your organization. [!NOTE] If you have Office 365 operated by 21Vianet (China), sign in to the Microsoft 365 admin center, then browse to the SharePoint admin center and open the Settings page. At the bottom of the page, select classic settings page. Under Custom Script, select: Allow users to run custom script on personal sites. Allow users to run custom script on self-service created sites. :::image type="content" alt-text="Screenshot of custom script section of settings page in SharePoint admin center." source="mediaa96d5c23-6389-4343-81cb-7f055617f6e8.png" lightbox="mediaa96d5c23-6389-4343-81cb-7f055617f6e8.png"::: [!NOTE] Because self-service site creation points to your organization's root site by default, changing the Custom Script setting allows custom script on your organization's root site. For info about changing where sites are created, see Manage site creation in SharePoint. Select OK. It can take up to 24 hours for the change to take effect. To allow custom script on other SharePoint sites [!CAUTION] Before you allow custom script on sites in your organization, make sure you understand the security implications. To allow custom script on a particular site (previously called site collection) immediately, follow these steps: Download the latest SharePoint Online Management Shell. [!NOTE] If you installed a previous version of the SharePoint Online Management Shell, go to Add or remove programs and uninstall SharePoint Online Management Shell. Connect to SharePoint as a Global Administrator or SharePoint Administrator in Microsoft 365. To learn how, see Getting started with SharePoint Online Management Shell. Run the following command. PowerShell Set-SPOSite -DenyAddAndCustomizePages 0 or by means of the PnP.PowerShell cmdlet Set-PnPSite PowerShell Set-PnPSite -Identity -NoScriptSite $false If you change this setting for a classic team site, it will be overridden by the Custom Script setting in the admin center within 24 hours. [!NOTE] You cannot allow or prevent custom scripts to an individual user's OneDrive. Manage custom script from SharePoint admin center [!NOTE] If you do not see the new options in SharePoint tenant admin center, the feature is not enabled in your tenant yet. Every customer will have this new set of capabilities enabled by end of June 2024 Tenants administrators have a set of tools available in SharePoint tenant administration to manage custom script within their organization. Specifically, tenant administrators can do the following: verify custom script status change custom script settings persist custom script settings Verify custom script status A new Custom script column is now available in the Active sites page under Sites. :::image type="content" alt-text="Screenshot of active sites view with custom script column visible." source="media232a2283-7f38-4f77-b32d-e076bbcbbb01.png" lightbox="media232a2283-7f38-4f77-b32d-e076bbcbbb01.png"::: The column can be added to any view. A new Custom script allowed sites is also available to provide an easy access to all the sites where custom script is enabled: :::image type="content" alt-text="Screenshot of the list of default views, which includes the 'custom script allowed sites' view." source="mediae19f29a8-601a-416a-b8fd-2f128461b52c.png"::: Change custom script settings In the Active sites page, upon selecting a site, under settings, a Custom scripts setting is available for administrators: :::image type="content" alt-text="Screenshot of the 'Custom scripts' setting." source="media7a9c6b79-db8b-4577-9a8c-978f011196a9.png"::: Administrators can control custom script settings for a specific site; deciding if they want to allow or block custom script on a specific site: :::image type="content" alt-text="Screenshot of 'Custom scripts' values." source="media05b24a6e-7dec-4b50-80e8-f09fe18e7dd4.png" lightbox="media05b24a6e-7dec-4b50-80e8-f09fe18e7dd4.png"::: By default, any changes to custom script settings for a specific site only last for a maximum of 24 hours. After that time, the setting will reset to its original value for that specific site. Persist custom script settings To prevent SharePoint in resetting custom script settings to its original value to the whole tenant follow these steps: Download the latest SharePoint Online Management Shell. [!NOTE] If you installed a previous version of the SharePoint Online Management Shell, go to Add or remove programs and uninstall "SharePoint Online Management Shell." Connect to SharePoint as a Global Administrator or SharePoint Administrator in Microsoft 365. To learn how, see Getting started with SharePoint Online Management Shell. Run the following command. PowerShell Set-SPOTenant -DelayDenyAddAndCustomizePagesEnforcement $True [!NOTE] This setting affects all sites. There are no options to preserve changes to custom script settings only on some specific sites. This parameter will be available until November 2024. After that date, it will no longer be possible to prevent SharePoint in resetting custom script settings to its original value for all sites. Running the command where Multi-Geo capabilities on OneDrive and SharePoint are configured, will only affect the current geo from which you ran the command. To persiste custom script settings across the entire tenant you must run the command on each geo. Features affected when custom script is blocked When users are prevented from running custom script on OneDrive or the classic team sites they create, site admins and owners won't be able to create new items such as templates, solutions, themes, and help file collections. If you allowed custom script in the past, items that were already created will still work. The following site settings are unavailable when users are prevented from running custom script: Site feature Behavior Notes :-----:-----:----- Save Site as Template No longer available in Site Settings Users can still build sites from templates created before custom script was blocked. Save document library as template No longer available in Library Settings Users can still build document libraries from templates created before custom script was blocked. Save list as template No longer available in List Settings Users can still build lists from templates created before custom script was blocked. Solution Gallery No longer available in Site Settings Users can still use solutions created before custom script was blocked. Theme Gallery No longer available in Site Settings Users can still use themes created before custom script was blocked. Help Settings No longer available in Site Settings Users can still access help file collections available before custom script was blocked. Sandbox solutions Solution Gallery is no longer available in Site Settings Users can't add, manage, or upgrade sandbox solutions. They can still run sandbox solutions that were deployed before custom script was blocked. SharePoint Designer Pages that are not HTML can no longer be updated. Handling List: Create Form and Custom Action will no longer work. Subsites: New Subsite and Delete Site redirect to the Site Settings page in the browser. Data Sources: Properties button is no longer available. Users can still open some data sources. To open a site that does not allow custom script in SharePoint Designer, you must first open a site that does allow custom script. Uploading files that potentially include script The following file types can no longer be uploaded to a library .asmx .ascx .aspx .htc .jar .master .swf .xap .xsf Existing files in the library are not impacted. Uploading Documents to Content Types Access denied message when attempting to attach a document template to a Content Type. We recommend using Document Library document templates. Publishing of SharePoint 2010 Workflows Access denied message when attempting to publish a SharePoint 2010 Workflow. The following web parts and features are unavailable to site admins and owners when you prevent them from running custom script. Web part category Web part :-----:----- Business Data Business Data Actions Business Data Item Business Data Item Builder Business Data List Business Data Related List Excel Web Access Indicator Details Status List Visio Web Access Community About This Community Join My Membership Tools What's Happening Content Rollup Categories Project Summary Relevant Documents RSS Viewer Site Aggregator Sites in Category Term Property Timeline WSRP Viewer XML Viewer Document Sets Document Set Contents Document Set Properties Advanced Embed Forms HTML Form Web Part Media and Content Content Editor Script Editor Silverlight Web Part Search Refinement Search Box Search Navigation Search Results Search-Driven Content Catalog-Item Reuse Social Collaboration Contact Details Note Board Organization Browser Site Feed Tag Cloud User Tasks Master Page Gallery Can't create or edit master pages Publishing Sites Can't create or edit master pages and page layouts Best practice for communicating script setting changes to users Before you prevent custom script on sites where you previously allowed it, we recommend communicating the change well in advance so users can understand the impact of it. Otherwise, users who are accustomed to changing themes or adding web parts on their sites will suddenly not be able to and will see the following error message. :::image type="content" alt-text="Screenshot of the Error message that's displayed when scripting is disabled on a site." source="media1c7666a0-9538-484f-a691-6e424c5db71a.png"::: Communicating the change in advance can reduce user frustration and support calls.

OfficeDocs-SharePoint/SharePoint/SharePointOnline/allow-or-prevent-custom-script.md/0

Allow or prevent custom script

OfficeDocs-SharePoint/SharePoint/SharePointOnline/allow-or-prevent-custom-script.md

OfficeDocs-SharePoint

ms.date: 05312024 title: Build Learning and Training Experiences for Employees ms.reviewer: ms.author: ruihu author: maggierui manager: jtremper recommendations: true audience: Admin f1.keywords: - NOCSH ms.topic: article ms.service: sharepoint-online localization_priority: Priority ms.collection: - Strat_SP_modern - M365-collaboration - m365solution-corpcomms - m365solution-scenario - highpri - best-practices search.appverid: - SPO160 - MET150 description: "Learn how to build a learning and training experience for employees using Microsoft 365" Build learning and training experiences for employees Learn how to build a training and learning experience that will keep employees and team members up to date with important skills and proficiencies required for professional success. This article will show you how to create a training solution that includes a durable training site, online learning, virtual training events, promotion, and tracking insights and feedback to improve your experience overtime. Create a learning and training experience by: Taking inventory of all organizational needs, learning objectives and goals, and identifying important timelines Choosing the best tools that fit your organization's learning and training goals and objectives Keeping employees up to date about important learning and training due dates and opportunities Launching an accessible and scalable experience by ensuring employees know how to access modules, courses, and resources and asking for feedback to make improvements along the way Overview of creating a training and learning experience for employees PlanBuildLaunch :---::---::---: - Understand your organizational needs - List all learning objectives - Personalize the experience based on role and career stage - Identify timelines - Define goals and outcomes- Choose the best tools for your training and learning experience - Ensure tools and resources can be accessed by everyone - Create a place where employees with similar learning objectives can connect- Set realistic deadlines - Notify employees of upcoming training and learning opportunities and initiatives - Gather insights from each platform used to measure overall effectiveness of training and learning experience Plan a training and learning experience Planning considerations: For some professions and disciplines, federal or state mandates may be in place requiring specific learning and training. Be sure to keep up with these dates to inform your organization's practice. Employees have varying and busy schedules. Be sure to notify employees more than one time about upcoming required learning before the due date to make sure it's top of mind. Depending on the organization, employees may be working across multiple regions and time zones. For live learning events, choose times that accommodate most employees. :---::---::---::---: Step 1: Understand your organizational needsStep 2: List and categorize all learning objectivesStep 3: Define goals and outcomesStep 4: Review Microsoft 365 Learning and Training tools Step 1: Understand your organizational needs Take inventory of all organizational departments, teams, and disciplines. Are there any legally required continued learning mandates for any employee groups in your organization? How many? Is there a broad range of disciplines and areas of expertise across your organization? Is there a certain budget that needs to be set and adhered to for learning and training resources? Set aside time to list all factors out to get a full scope of what is needed. Step 2: List and categorize all learning objectives Now that you have listed out your organizational needs, identify the learning objectives for each employee group. Separate the required learning from suggested or recommended learning. Identify timelines for completion based on organizational needs. Establish starting points and finish lines for each module or experience. Step 3: Define goals and outcomes Every organization has its own variation of technical and soft skills that need to be upheld and maintained over time. These skills can range from learning how to use job-related tools and in-house resources to learning about the intricacies of the company's culture and policies. Define what needs to be prioritized as learning goals and outcomes from the employees in your organization, prioritize these goals and begin curating modules and learning materials that best meet these desired goals and outcomes. Step 4: Review Microsoft 365 Learning and Training tools Use Viva Learning to surface all your learning content in one place. Bring learning content from Microsoft, your organization's SharePoint, and the learning management systems your organization already uses into Viva Learning so your employees can easily access the learning and training content they need without leaving Microsoft Teams. Curate custom training playlists on SharePoint with Learning Pathways. Bring custom content and Microsoft training content together to create learning and training playlists. Use Learning Pathways web parts with audience targeting to make sure that your employees see the content that's most relevant to them. Create a learning and development landing page using SharePoint. Create a SharePoint communication site using the Learning Central SharePoint Communication site template. Use the site to direct employees to events, news, and information about required learning and extra-curricular resources. Use Microsoft Teams to hold live learning events. Meetings in Teams include audio, video, and screen sharing, and are great for communicating with groups of fewer than 300 individuals. Teams can be used for meetings that happen in person, remotely, or a combination of the two. Additionally, the meeting can be recorded and shared with new employees who were unable to attend the meeting. Provide an opportunity for employees to learn from each other in Viva Engage. Create a Viva Engage channel just for new employees. Choose to create one NEO channel for the entire organization or region or create channels for each new group of new employees. Then, use the Viva Engage web part on the SharePoint NEO site to integrate the conversation with other resources and contacts. Build the learning and training experience Build out the learning and training experience one platform at a time. The tools listed here can be connected to each other, providing a thorough and connected learning and training journey for all employees. Review learning and training tools Use Viva Learning to make learning content easily accessible from within Teams Viva Learning in Microsoft Teams allows users to discover, recommend, and access learning modules from different platforms to help users gain knowledge in any specific focus area. Viva Learning pulls content from LinkedIn Learning, Microsoft Learn, and Microsoft 365 Training. You can also add your organization's own custom content from SharePoint, and integrate Viva Learning with learning management systems and third-party content providers that you already use. Use Viva Learning to make sure each of your employees has the knowledge they need for organizational needs, team needs, and the tools that they will be working with daily. In Viva Learning, managers of an organization or team can recommend learning and track the learning progress of each module. The Viva Learning home view aggregates a variety of information, including assigned content from learning management systems, recommended learnings, trending content, and learning provider content libraries. Learn more about Viva Learning Curate and target custom training playlists with Learning Pathways Learning pathways is a customizable, on-demand learning solution in SharePoint that brings together out-of-the-box Microsoft 365 training playlists and custom playlists created by your organization. Surface your learning pathways playlists on any site in your organization using the Microsoft 365 learning pathways web part, and use audience targeting to make sure your playlists are seen by everyone who needs them. Get started with learning pathways and easily provision learning pathways to begin using your customizable learning pathways portal. Create a learning and development landing page using SharePoint Create an internal communication site that acts as a home for the learning and training experience. This site should lay out resources, deliverables, and learning objectives in and organized way. This site should also contain the most up-to-date information to ensure the employee has everything needed to be successful. Try organizing action items on this site in a way that signals priority. List the things that need to be finished first at the top. This will help employees organize their learning and training to the best of their ability. Microsoft offers a new customizable Learning Central SharePoint communication site template that can help get you started. Get started with SharePoint site templates. Use Teams to hold live learning events Many learning experiences require hands-on training. Some experiences are better held in live environments where employees can ask questions and get guidance in real time. With the emergence of virtual work, having face time with other people in the organization is still important in making sure employees can communicate with learning instructors and other peers and ask top-of-mind questions. Use Microsoft Teams to administer live learning and training experiences. Make this live event fun and engaging by giving employees an opportunity to communicate with each other in the Teams chat box or allow employees to ask questions on camera or through the moderated Q&A in Teams live events. Record each session so employees can review the learning material later, or so future employees can experience the session as well. Make this recording available through the SharePoint Learning and Training site or through the Viva Learning platform. Learn more about Teams live events.. Provide an opportunity for employees to learn from each other in communities on Viva Engage Give employees that have similar learning objectives the opportunity to connect with each other and build a supportive virtual community in Viva Engage. Viva Engage is a platform that connects leaders, communicators, and employees to build communities, share knowledge, and engage across the organization. Viva Engage allows you to set up a community specifically for employees within the same or similar disciplines. Naturally, employees come across information at different times in their learning and training process. Creating a space where new employees can build a community for themselves gives them the opportunity to share information as they come across it. In this virtual space, new employees can share resources, share ideas, and get to know each other. It also helps them build internal bonds that can last over the course of their career. Learn more about building communities in Viva Engage. Make sure all tools and experiences are accessible Ensure each learning and training experience is accessible by incorporating accessibility best practices across all relevant Microsoft 365 tools. Make sure everything in your learning and training experience is visible and labeled properly. Use alternative text for images and graphics. Incorporate transcripts in videos and training material. Share this experience with the right people. Make sure employees know how to access all the tools needed in the learning experience. Use all sharing options including email, Teams messages, Viva Engage posts, SharePoint web parts, Viva Learning, and Viva Connections to build awareness and increase accessibility. Ensure every employee and instructor has access to all tools and resources. Consider the unique needs of everyone involved in making sure the learning and training experience is successful. Stay informed about the specific time zones of every stakeholder to make sure all timelines and deliverables are feasible for everyone involved. Lastly, make the starting point and ending point for each training opportunity. Review your experience to ensure employees know exactly where to start and when the experience has been completed successfully. This can be done within the experience, or by planning to generate an email through Outlook that lets them know when they have finished each learning objective and if anything else is required of them. Launch a training and learning experience After the learning and training experience has been planned and the tools have been selected, it's time to launch your experience. Notify employees of upcoming training Build awareness of upcoming training by sending an email in Outlook or by adding a SharePoint news posts to spread the word across various platforms. Let employees know if the training is required or suggested. List important details about the training like the due date and the learning objectives. Ensure all employees know how to access the learning module or experience. Gather insights to determine success Gather insights from each platform along the way. Use these insights to inform managers, team leads, and other stakeholders. Look for insights such as live event attendance, audience reach, site traffic, module completion, and more. Maintain your experience by updating things frequently, providing the most up-to-date and relevant information across all platforms. Learn more about maintaining your SharePoint communication sites and keeping SharePoint news posts updated. Ask for feedback on the learning and training experience often using Microsoft Forms. Use this feedback to determine what needs to be improved or altered for the next learning and training experience. More Resources Corporate communications overview Overview of Viva Learning Use the SharePoint Learning central site template

OfficeDocs-SharePoint/SharePoint/SharePointOnline/build-learning-and-training-experiences-for-employees.md/0

Build learning and training experiences for employees

OfficeDocs-SharePoint/SharePoint/SharePointOnline/build-learning-and-training-experiences-for-employees.md

OfficeDocs-SharePoint

ms.date: 06102022 title: Plan compliance requirements for SharePoint and OneDrive ms.reviewer: ms.author: ruihu author: maggierui manager: jtremper recommendations: true audience: Admin f1.keywords: NOCSH ms.topic: concept-article ms.service: sharepoint-online ms.localizationpriority: medium ms.collection: essentials-compliance ms.custom: intro-get-started search.appverid: MET150 description: Learn what features are available in Microsoft 365 to help you plan your compliance requirements for SharePoint and OneDrive. Plan compliance requirements for SharePoint and OneDrive Most organizations have business or legal requirements that govern how data is used, shared, and retained. Some organizations also have data residency requirements or regulatory requirements that restrict communication between certain users and groups. Microsoft 365 has a wide range of governance and compliance features to address these needs. This article provides an overview of features you may want to consider as part of your OneDrive and SharePoint rollout. Data lifecycle management Use data lifecycle management capabilities in Microsoft Purview to govern your OneDrive and SharePoint content for compliance or regulatory requirements. The following table describes the capabilities to help you keep the content you need you and delete what you don't need. CapabilityWhat problems does it solve?Get started :------:------------:---------------------------- Retention policies and retention labelsLearn about retention for SharePoint and OneDrive Retain or delete content with policy management for SharePoint and OneDrive documents Create and configure retention policies Create retention labels for exceptions to your retention policies Deleted users' data When a user leaves your organization and you've deleted that user's account, what happens to the user's data? When considering data retention compliance, determine what needs to happen with the deleted user's data. For some organizations, retaining deleted user data could be important continuity and preventing critical data loss. If a user's Microsoft 365 account is deleted, their OneDrive files are preserved for 30 days. To change this setting, Set the OneDrive retention for deleted users. By default, when a user is deleted, the user's manager is automatically given access to the user's OneDrive. To change this, see OneDrive retention and deletion. Information protection Microsoft Purview Information Protection capabilities help you discover, classify, and protect sensitive information in OneDrive and SharePoint. The following table describes these capabilities. Consider if you want to implement any of these capabilities as part of your OneDrive and SharePoint rollout. CapabilityWhat problems does it solve?Get started :------:------------:-------------------- Sensitive information types Identifies sensitive data by using built-in or custom regular expressions or a function. Corroborative evidence includes keywords, confidence levels, and proximity. Customize a built-in sensitive information type Trainable classifiers Identifies sensitive data by using examples of the data you're interested in rather than identifying elements in the item (pattern matching). You can use built-in classifiers or train a classifier with your own content. Get started with trainable classifiers Sensitivity labels A single solution across apps, services, and devices to label and protect your data as it travels inside and outside your organization. Sensitivity labels can be used to protect files themselves or individual SharePoint sites and teams.Enable sensitivity labels for Office files in SharePoint and OneDrive Use sensitivity labels to protect content in Microsoft Teams, Microsoft 365 Groups, and SharePoint sites Data loss prevention Helps prevent unintentional sharing of sensitive items. Get started with the default DLP policy File sync The OneDrive sync app has policies that you can use to help you maintain a compliant environment. Consider configuring these policies before you roll out SharePoint and OneDrive. PolicyWindows GPOMac :-----:----------:-- Allow syncing OneDrive accounts for only specific organizationsAllowTenantListAllowTenantList Block syncing OneDrive accounts for specific organizationsBlockTenantListBlockTenantList Prevent users from syncing libraries and folders shared from other organizationsBlockExternalSyncBlockExternalSync Prevent users from syncing personal OneDrive accountsDisablePersonalSyncDisablePersonalSync Exclude specific kinds of files from being uploadedEnableODIgnoreListFromGPOEnableODIgnore Data residency Multi-Geo is Microsoft 365 feature that allows organizations to span their storage over multiple geo locations and specify where to store users' data. For multinational customers with data residency requirements, you can use this feature to ensure that each user's data is stored in the geo location necessary for compliance. For more info about this feature, see Multi-Geo Capabilities in OneDrive and SharePoint. Features such as file sync and mobile device management work normally in a multi-geo environment. There's no special configuration or management needed. The multi-geo experience for your users has minimal difference from a single-geo configuration. For details, see User experience in a multi-geo environment. For more information about Microsoft 365 Multi-Geo, see Microsoft 365 Multi-Geo. Information barriers Microsoft Purview Information Barriers is a compliance solution that allows you to restrict two-way communication and collaboration between groups and users in Microsoft Teams, SharePoint, and OneDrive. Often used in highly regulated industries, information barriers can help to avoid conflicts of interest and safeguard internal information between users and organizational areas. When information barrier policies are in place, users who shouldn't communicate or share files with other specific users won't be able to find, select, chat, or call those users. Information barrier policies automatically put checks in place to detect and prevent unauthorized communication and collaboration among defined groups and users. If your business requires information barriers, see Learn about information barriers and Use information barriers with SharePoint to get started. Next steps [!div class="nextstepaction"] Plan sharing and collaboration options Related topics Plan for SharePoint and OneDrive in Microsoft 365 B2B Sync Implement compliance in Microsoft 365 Protect your enterprise data using Windows Information Protection (WIP) Control OneDrive and SharePoint access based on network authentication or app

OfficeDocs-SharePoint/SharePoint/SharePointOnline/compliant-environment.md/0

Plan compliance requirements for SharePoint and OneDrive

OfficeDocs-SharePoint/SharePoint/SharePointOnline/compliant-environment.md

OfficeDocs-SharePoint

ms.date: 04242024 title: "Create a hub site in SharePoint" ms.reviewer: metorres ms.author: ruihu author: maggierui manager: jtremper recommendations: true audience: Admin f1.keywords: - CSH ms.topic: article ms.service: sharepoint-online ms.localizationpriority: medium ms.collection: - Strat_SP_admin - M365-collaboration - m365initiative-spsitemanagement ms.custom: - seo-marvel-apr2020 - admindeeplinkSPO search.appverid: - SPO160 - MET150 ms.assetid: 92bea781-15d8-4bda-805c-e441e2191ff3 description: "In this article, you'll learn how to register a site as a hub site in the SharePoint admin center." Create a hub site in SharePoint If you're a Global Administrator or SharePoint Administrator in Microsoft 365, you can convert any existing site to a hub site. [!NOTE] We recommend selecting a communication site, or a team site that uses the new template. If you use a classic team site, the hub navigation will appear only on modern pages, and hub site settings will only appear on modern pages.Sites that are already associated with another hub can't be converted to a hub site. You can create up to 2,000 hub sites for an organization. This applies to hub-to-hub associations as well. Any site labeled as a hub site will count against this limit. There is no limit on the number of sites that can be associated with a hub site. When users associate their sites with a hub, it doesn't impact the permissions of either the hub site or the associated sites. It's important to make sure all users you allow to associate sites to the hub have permission to the hub. Create a hub site in the new SharePoint admin center Go to Active sites in the SharePoint admin center, and sign in with an account that has admin permissions for your organization. [!NOTE] If you have Office 365 operated by 21Vianet (China), sign in to the Microsoft 365 admin center, then browse to the SharePoint admin center and open the Active sites page. Select the site, select Hub on the command bar, and then select Register as hub site. [!TIP] Using the Hub site menu, you can also associate a site with the hub site, change a site's association to a different hub site, or disassociate a site from a hub site. Enter a display name for the hub site, and specify the individual users or security groups you want to allow to associate sites with the hub. [!IMPORTANT] If you leave the People who can associate sites with this hub box empty, any user can associate their site with the hub.If you later want to change the hub site display name or the list of people who can associate sites with the hub, you need to use PowerShell or go to hub site settings on the hub site. Select Save. Related topics For info about using a site design that gets applied when sites join the hub, see Set up a site design for your hub site. For more info about site designs and site scripts, see SharePoint site design and site script overview. To learn how to use Microsoft PowerShell to create and manage hub sites, see Manage SharePoint hub sites. For info about how site owners can customize hub sites, see Set up your SharePoint hub site. For info about removing a hub site, see Remove a hub site.

OfficeDocs-SharePoint/SharePoint/SharePointOnline/create-hub-site.md/0

Create a hub site in SharePoint

OfficeDocs-SharePoint/SharePoint/SharePointOnline/create-hub-site.md

OfficeDocs-SharePoint

ms.date: 08172018 title: "Difference between classic & modern search experiences - SharePoint" ms.reviewer: ms.author: ruihu author: maggierui manager: jtremper recommendations: true audience: Admin f1.keywords: - NOCSH ms.topic: article ms.service: sharepoint-online ms.collection: M365-collaboration ms.localizationpriority: medium search.appverid: - SPO160 - MET150 ms.custom: - seo-marvel-apr2020 - admindeeplinkSPO description: "This article provides an overview of the difference between the classic and modern search experiences in Microsoft SharePoint." Differences between the classic and modern search experiences in SharePoint SharePoint in Microsoft 365 has both a classic and a modern search experience. Microsoft Search in SharePoint is the modern search experience. Both search experiences use the same search index to find results. As a search admin, you can’t enable or disable either search experience, both are enabled by default. Users get the classic search experience on publishing sites, classic team sites, and in the Search Center. Users get the Microsoft Search experience on the SharePoint start page, hub sites, communication sites, and modern team sites. Learn about classic and modern sites The most visible difference is that the Microsoft Search box is placed at the top of the SharePoint, in the header bar. Another difference is that Microsoft Search is personal. The results you see are different from what other people see, even when you search for the same words. You'll see results before you start typing in the search box, based on your previous activity and trending content in Microsoft 365, and the results update as you type. Learn more about the Microsoft Search experience for users. Search admin can customize the classic search experience, but not the Microsoft Search experience. As a search admin you can tailor Microsoft Search to your organization so it's easy for your users to find often needed content in your organization. For example, if your organization has Microsoft Search fully deployed, custom result sources at site collection or tenant level won't affect the search result. The search admin can use Microsoft search verticals instead. To learn more, see Manage search verticals. You use the SharePoint admin center to manage classic search and the Microsoft 365 admin center to manage Microsoft Search. Certain aspects of the classic search settings also impact the modern search experience: The search schema determines how content is collected in and retrieved from the search index. Because both search experiences use the same search index to find search results, any changes you make to the search schema, apply to both experiences. The Microsoft Search experience doesn't support changing the sort order of results or building refiners based on metadata. Therefore, the following search schema settings don’t affect the Microsoft Search experience: Sortable Refinable Company name extraction (deprecated since November 15, 2019) In environments where vertical configuration is available the modern search experience only shows results from the standard result source (Local SharePoint Results). To learn more, see Manage search verticals. In environments where vertical configuration is not available the modern search experience only shows results from the default result source. If you change the default result source, both modern and classic search experiences are impacted. Depending on the search scenario, some Microsoft Search features might not work if the classic global Search Center URL is not set to point to the URL of the default classic Search Center. Depending on your tenant, this URL is "yourcompanyname.sharepoint.comsearch" or "yourcompanyname.sharepoint.comsearchpages". Furthermore, ensure that the Search Center site collection exists and that all users have read access to it. If you temporarily remove a search result, the result is removed in both search experiences. The classic search experience lets admins define promoted results to help users find important content, while the Microsoft Search experience uses bookmarks to achieve the same. When you create a promoted result at the organization level, users might also see it on the All tab on the Microsoft Search results page if they searched across the whole organization. For example, when users search from the search box on a hub site, they're only searching in the sites associated with the hub and therefore they don't see any promoted results even if they are on the All tab. But when users search from the SharePoint start page, they might see promoted results on the All tab. If you have defined both a promoted result and a bookmark for the same content (same URL), only the bookmark will appear on the All tab.

OfficeDocs-SharePoint/SharePoint/SharePointOnline/differences-classic-modern-search.md/0

Differences between the classic and modern search experiences in SharePoint

OfficeDocs-SharePoint/SharePoint/SharePointOnline/differences-classic-modern-search.md

OfficeDocs-SharePoint

ms.date: 02252024 title: "Find your Microsoft 365 tenant ID" ms.reviewer: ms.author: mactra author: MachelleTranMSFT manager: jtremper audience: Admin f1.keywords: - CSH ms.topic: article ms.service: one-drive ms.localizationpriority: medium ms.custom: - Adm_O365 - onedrive-toc - has-azure-ad-ps-ref - azure-ad-ref-level-one-done search.appverid: - MET150 - BCS160 ms.collection: - Strat_OD_admin - M365-collaboration ms.assetid: 6891b561-a52d-4ade-9f39-b492285e2c9b description: "Learn how to find the Microsoft 365 tenant ID using the Microsoft Entra admin center." Find your Microsoft 365 tenant ID Your Microsoft 365 tenant ID is a globally unique identifier (GUID) that is different than your organization name or domain. You can use this identifier when you configure OneDrive policies. Find your Microsoft 365 tenant ID in the Microsoft Entra admin center Your tenant ID can be found in the Tenant ID box on the Overview page. [!NOTE] For info about finding your tenant ID by using PowerShell instead, first read Microsoft Graph PowerShell and then use Get-MgOrganization.

OfficeDocs-SharePoint/SharePoint/SharePointOnline/find-your-office-365-tenant-id.md/0

Find your Microsoft 365 tenant ID

OfficeDocs-SharePoint/SharePoint/SharePointOnline/find-your-office-365-tenant-id.md

OfficeDocs-SharePoint

author: omondiatieno ms.author: jomondi ms.date: 04042024 ms.topic: include ms.service: microsoft-graph-powershell [!NOTE] Azure AD and MSOnline PowerShell modules are deprecated as of March 30, 2024. To learn more, read the deprecation update. After this date, support for these modules are limited to migration assistance to Microsoft Graph PowerShell SDK and security fixes. The deprecated modules will continue to function through March, 30 2025. We recommend migrating to Microsoft Graph PowerShell to interact with Microsoft Entra ID (formerly Azure AD). For common migration questions, refer to the Migration FAQ. Be aware that versions 1.0.x of MSOnline may experience disruption after June 30, 2024.

OfficeDocs-SharePoint/SharePoint/SharePointOnline/includes/aad-powershell-deprecation-note.md/0

OfficeDocs-SharePoint/SharePoint/SharePointOnline/includes/aad-powershell-deprecation-note.md

OfficeDocs-SharePoint

ms.date: 06292021 title: "Use Microsoft 365 to connect leaders and teams" ms.reviewer: ms.author: ruihu author: maggierui manager: jtremper recommendations: true audience: Admin ms.topic: article ms.service: sharepoint-online localization_priority: Normal search.appverid: MET150 ms.collection: - m365solution-corpcomms - m365solution-scenario - highpri description: "Use Microsoft 365 to connect leaders and teams" Leadership connection: Use Microsoft 365 to connect leaders and teams Microsoft 365 can help your organization's leadership teams connect with employees to build community around a common purpose and goal. Learn how to create a culture and internal place to help engage and connect leadership teams with the rest of your organization. Help unite your organization by: Creating a sustainable, two-way dialogue between leadership and the rest of the organization by removing communication barriers Hosting organizational or department-wide meetings with live Q&A sessions so everyone is up-to-speed on leadership initiatives Sharing relevant news, ideas, and updates to encourage employees to engage and network with leadership teams Using analytics to gain insights on engagement and understand the impact of activities Bringing elements of the experience together using Viva Connections StageTasks ------ Plan- Define audience profile and scope audience size - Align with stakeholders - Develop a support team that ensures content is relevant, plan future events, and publish news - Consider multi-geo and multi-lingual options - Find corporate sponsorship and champions - Determine success metrics Build- Create a SharePoint leadership site - Start a new community in Viva Engage - Set up news that can be shared in SharePoint, Teams, and Outlook - Use M365 groups to provide access to large audiences - Use audience targeting to make sure your audience can find the right content - Get user feedback before launching your communications - Plan a kickoff event and identify promotional channels Launch- Share the leadership SharePoint site, Viva Engage community, and event invites with their intended audiences - Send email invites to the kickoff event - Use Microsoft Teams and Viva Engage to post messages about the kickoff event - Equip champions and corporate sponsors with promotional materials - Produce and host a live event with Q&A - Create feedback channels - Post the event recording on the leadership connection site Maintain- Ensure content stays relevant - Audit M365 group membership, access, and settings periodically - Develop a news publishing cycle - Schedule regular events and share them in advance Plan your leadership connection strategy Start by making sure you understand your audience's needs and preferences. Review how to profile and scope your audience. This scenario will have the most successful outcome when multiple communication methods are combined. Start with a SharePoint communication site and a Viva Engage channel that connects the organization with leadership. Then, plan and host a live event that is recorded and shared with others. Finally, bring all these communication elements together into an engaging mobile experience using Viva Connections. 1. SharePoint communication site - Create a SharePoint communication site that houses all things leadership – everything from news and announcements to events, people profiles and networking opportunities. Use the Leadership connection site template. 2. Viva Engage community - Use Viva Engage to instantly connect, ask questions, and share ideas with the leadership team. Then, use the Viva Engage web part to embed the conversation on the leadership connection SharePoint site. 3. Viva Engage live events - Use the Viva Engage community for live events and questions and answers. 4. Viva Connections - Bring the SharePoint site and Viva Engage conversation into one place where users can catch up and connect with leaders in the Microsoft Teams mobile app. Learn more about Viva Connections. Planning considerations Multiple communication solutions can be combined to provide opportunities across the organization to connect with leadership regardless of worksite location or time zone. Create opportunities outside of a live event to allow everyone within the organization to connect, network, and learn from leadership teams. Develop communication channels that collect feedback and questions for the leadership team, and save responses for the next live event. Create a practice of recording live events that can be shared and viewed later. Build durable communication methods that do not require organized events to generate content. Identify other opportunities across the organization to spread awareness about the leadership connection initiative such as new. employee orientation, regular communications to networking groups, and promotion in employee resource groups. Build your communication strategy Start by creating or using an existing SharePoint communication site. Then connect a new or existing Viva Engage community to the SharePoint site using the Viva Engage conversations web part. Then, plan and host live events, share the recordings on the leadership site, and keep the conversation going in Viva Engage channels. Step 1: Create a SharePoint leadership site SharePoint communication sites are a great tool to create a landing place to share leadership news, initiatives, and opportunities to network and connect. This is an ideal opportunity to use the Viva Engage web part on the home page to connect to an existing Viva Engage community that connects leadership team members with the rest of the organization. Use the Events web part to post and target leadership events to specific audiences. Image of the Leadership connection site template: Share recording from leadership events: Showcase leadership profiles: Get started creating your SharePoint leadership site There are several resources that can help you quickly create a leadership site: Use a SharePoint site template provided by Microsoft. Apply the Leadership connection template, then customize the site to for the needs of your organization. Create your own leadership site following step-by-step instructions in this guided walkthrough. Use the Leadership connection template in the SharePoint look book. The SharePoint look book Leadership connection template requires the use of SharePoint PowerShell and administrative credentials. Publish news from the leadership site Once your leadership site has been created and shared with the right audiences, you can publish news from this site. Then, use the News web part on the home page to display leadership news and target leadership news to specific audiences. Other sites across your organization can customize the settings in the News web part to pull news from an organizational news site. Consider cross promoting leadership news on the home site, on a new employee onboarding site, and where other leadership-oriented news can be found. Monitor usage analytics for your SharePoint site As a SharePoint site owner, you can view information about how users interact with your site. For example, you can view the number of people who have visited the site, how many times people have visited the site, and a list of files that have received the most views. Learn more about how to access usage data for your leadership site. Step 2: Create a leadership community in Viva Engage Communities in Viva Engage help employees share knowledge, engage with others in the employee experience, and provide a social platform for company-wide communications. It can also be used to drive leadership engagement by providing a central place for your conversations, documents, events, and updates. Viva Engage can help you host a live event with moderated Q&A for up to 10,000 attendees. Use Viva Engage to help engage your organization by: Engaging employees in the goals and vision of the company Informing employees about strategic initiatives and important updates Showing employees that their feedback is being heard by senior leadership If your organization doesn't already have a Viva Engage community that includes members of the leadership team, start by creating a new Viva Engage community. Then, use the Viva Engage web part to embed conversations or highlights from existing Viva Engage communities on the SharePoint site. New to Viva Engage? Learn more about managing a community in Viva Engage and administrative tips and tricks. Help onboard your organization to Viva Engage and help others understand how to use Viva Engage. Monitor conversations and engagement insights Viva Engage community insights help you measure your community's reach and engagement. You can find out more about the people, conversations, and questions and answers that make up your community. Learn more about managing communities in Viva Engage. Step 3: Host a live leadership event in Viva Engage with Q&A Create and produce live events for people in the leadership Viva Engage network, with built-in discussions for use before, during, and after the event. Up to 10,000 people can attend at once from anywhere on their device or computer (higher limits for event attendees are temporarily available through the Microsoft 365 Live Events Assistance program. Make the video available after the event on the leadership site, so that people who can't make it at the scheduled time can still participate. Image of live questions and answers during an event There are two ways live events in Viva Engage can be produced. The requirements depend on which video production methods you intend to use in your organization. Learn more about which method of live event you should use. For live events that only require visual and audio support, consider hosting a live event using Viva Engage in Teams. Once you've determined the right method for your live event, get started organizing and scheduling the event. Learn more about how to organize the live event in Viva Engage. Review the Viva Engage live event playbook and Viva Engage live event FAQs to understand all the different roles and responsibilities, how to ensure the event goes smoothly, and how to drive engagement. Consider using guidance from How to host a town hall for your organization to plan your live event. Insights and engagement metrics for live events Before the event starts, you will have access to a dashboard that will help you understand event reach, engagement during the event, top conversations, and more. Insights are only available to event organizers and producers. Learn more about how to view live event data and use insights to host powerful live events. Step 4: Expand your reach and engagement using Viva Connections Bring the SharePoint leadership site, news, and conversations from the Viva Engage community into one central place in Microsoft Teams using Viva Connections. Viva Connections creates an opportunity to push specific content and display popular resources by combining the power of your SharePoint intranet with Microsoft Teams and other Microsoft 365 apps like Viva Engage and Stream. Use Viva Connections to: Meet your employees in the apps and devices they know and love with a personalized view of news, conversations, and communities Promote events, news, and conversations in Viva Connections dashboard to specific audiences using audience targeting Boost important news and announcements to the top of employees' news feeds Viva Connections offers added functionality through three primary components - the Dashboard, the Feed, and Resources. Dashboard: The Viva Connections Dashboard is your employee’s digital toolset. It brings together the tools your employees need, enabling quick and easy access whether they are in the office or in the field. Feed: The Feed delivers updates to the right people at the right time and is tightly integrated with Viva Engage, SharePoint news, and Stream to display a personalized feed, based on post-level targeting of the groups that employees belong to. Resources: The Resources experience enables way finding across platforms. It uses navigation elements from the SharePoint app bar, which can be audience targeted. Launch and manage your communication strategy Help others in your organization discover the leadership connection resource. Consider hosting a kickoff event in Viva Engage to announce the new SharePoint site and Viva Engage community. Set the tone for what to expect in terms of ongoing engagement, mentorship and networking opportunities, event, and news publishing schedules. Launch checklist: Assign site owners and content authors who will be responsible for making sure the leadership site and news are always up to date Make sure your audience has access to the SharePoint site Make sure your audience has been added to the Viva Engage community Assign a Viva Engage community moderator and review Viva Engage community best practices Use audience targeting to highlight leadership events, news, and links to the leadership SharePoint site across your intranet Check site SharePoint usage and analytics and Viva Engage community insights during and after the launch to measure engagement More resources Overview of corporate communications Use the SharePoint Leadership connection site template Viva Connections for leaders

OfficeDocs-SharePoint/SharePoint/SharePointOnline/leadership-connection.md/0

Leadership connection: Use Microsoft 365 to connect leaders and teams

OfficeDocs-SharePoint/SharePoint/SharePointOnline/leadership-connection.md

OfficeDocs-SharePoint

ms.date: 07112018 title: Manage Business Connectivity Service Applications ms.reviewer: abloesch ms.author: ruihu author: maggierui manager: jtremper recommendations: true audience: Admin f1.keywords: - CSH ms.topic: article ms.service: sharepoint-online ms.localizationpriority: medium ms.collection: - M365-collaboration ms.custom: admindeeplinkSPO search.appverid: - SPO160 - MET150 ms.assetid: 2ced10aa-db9a-4828-a7a5-e47a57c3a823 description: Learn how to create BCS connections to data sources, such as SQL Azure databases or Windows Communication Foundation (WCF) web services, that are outside the SharePoint site. Manage Business Connectivity Service Applications In SharePoint in Microsoft 365, you can create Business Connectivity Services (BCS) connections to data sources, such as SQL Azure databases or Windows Communication Foundation (WCF) web services, that are outside the SharePoint site. Once you've created these connections, you can manage or edit BCS information in the SharePoint admin center. Microsoft SharePoint uses BCS together with Secure Store Services to access and retrieve data such as BDC Models from external data systems. See also Deploy a Business Connectivity Services hybrid solution in SharePoint. [!NOTE] Business Connectivity Services (BCS) in Microsoft 365 is a deprecated feature. On January 8, 2024, it will be disabled in new tenants as well as existing tenants that haven't used the feature since October 30, 2023. It will be retired and removed from all tenants on September 30, 2024. Customers are encouraged to explore using Microsoft Power Apps to replace their Business Connectivity Services solutions in Microsoft 365. For more information, see Business Connectivity Services (BCS) Retirement in Microsoft 365. Manage BCS permissions After setup is complete, user permissions control access to the data that the connection provides. BCS has two types of permissions: Object permissions Metadata Store permissions Object permissions Object permissions apply only to a specific External System, BDC Model, or External Content Type (ECT). Each ECT is a securable object. For example, if you have an ECT called WCFBookSales, object permissions apply only to the WCFBookSales object, and not to any other ECT that might be defined. To set object permissions for an object, follow these steps. Go to More features in the SharePoint admin center, and sign in with an account that has admin permissions for your organization. [!NOTE] If you have Office 365 operated by 21Vianet (China), sign in to the Microsoft 365 admin center, then browse to the SharePoint admin center and open the More features page. Under BCS, select Open. In the business data catalog section, select Manage BDC Models and External Content Types. Select the check box next to the name of the ECT or external system that you want to manage. On the ribbon, select Set Object Permissions. Enter a user account or group name in the text box, and then select Add. You can also select Browse to look for the name that you want. Select the name of the account or group for which you want to set access to the ECT or external system. You can set permissions for only one account at a time. If you have multiple accounts or groups, you have to set levels of access for each account separately, by selecting them one at a time. The following table describes the permissions and their associated access levels. PermissionNotes :-----:----- Edit Allows the user or group to create External Systems and BDC Models, to import BDC Models, and to Export BDC Models. This setting should be reserved for highly privileged users. Execute Allows the user or group to execute operations (create, read, update, delete, or query) on ECTs. Selectable in clients Allows the user or group to create external lists for any ECTs, and to view the ECTs in the external item picker. Set permissions Allows the user, group, or claim to set permissions on the Metadata Store. At least one user or group must have this permission on every BCS connection so that permissions management can occur. With this permission, a user can grant Edit permissions to the Metadata Store. This setting should be reserved for highly privileged users Metadata Store Permissions Metadata Store permissions apply globally to the whole BCS store. That is, they apply to all BDC Models, external systems, ECTs, methods, and methods instances that are defined for that external data system. You can set permissions on the metadata store to determine who can edit items and set permissions for the store. Metadata Store permissions apply to many objects, such as BDC Models, ECTs, and external systems. Because Metadata Store permissions can replace object permissions, they must be managed carefully. When applied with forethought, Metadata Store permissions can grant access quickly and completely. To set Metadata Store permissions, follow these steps. In the left pane of the new SharePoint admin center, select More features. Under BCS, select Open. Select Manage BDC Models and External Content Types. On the ribbon, select Set Metadata Store Permissions. Enter a user account or group into the text box, and then select Add. You can also select Browse to look for the account that you want. The account or group will appear in the second text box. If you have multiple accounts or groups, you must select them one at a time to set the level of access. PermissionNotes :-----:----- Edit Allows the user or group to create External Systems and BDC Models, to import BDC Models, and to export BDC Models. This setting should be reserved for highly privileged users. Execute Allows the user or group to execute operations (create, read, update, delete, or query) on ECTs. Selectable in clients Allow the user or group to create external lists for any ECTs, and to view the ECTs in the external item picker. Set Permissions Allows the user, group, or claim to set permissions on the Metadata Store. At least one user or group must have this permission on every BCS connection so that permissions management can occur. With this permission, a user can grant Edit permissions to the Metadata Store. This setting should be reserved for highly privileged users. To propagate permissions to all items in the Metadata Store, select Propagate permissions to all BDC Models, External Systems and External content types in the BDC Metadata Store. If you select this option, you'll replace all existing permissions (including object permissions) that you may have set anywhere else in your selected BCS Application. Import or export a Business Data Connectivity (BDC) Model The BDC Model view allows a user to import and export the underlying framework for the business data connection. This is very useful if you have to re-create the connection in a new environment. A BDC Model file can be imported to create an ECT connection to an external system. You can import or export two types of model files: Model Exports the XML metadata for a selected system. Resource Exports the localized names, properties, and permissions for a selected system. [!NOTE] You can create a BDC Model using XML code. If you do so, it's important to know that you cannot use the authentication modes RevertToSelf and PassThrough with SharePoint. Although you might be able to import a BDC Model that was written in XML, the connection will not be usable. Import a BDC Model When you import a BDC Model, you also import its specified permissions. Before you import a BDC Model, it's a good idea to understand how imported permissions interact with existing permissions. Imported permissions for a BDC Model are added to the store of existing permissions in the BDC service. If an entry for an object already exists in the access control list, the existing value is overwritten with the permissions information from the imported file. To import a BDC Model, follow these steps: In the left pane of the new SharePoint admin center, select More features. Under BCS, select Open. In the business connectivity services section, select Manage BDC Models and External Content Types. On the ribbon, select Import. In the BDC Model section, enter the name of the BDC Model File. The Model name must not include any special characters, such as ~ " % & : \ ? \ { } or the character 0x7f. You can also select Browse to locate the .bdcm file for a BDC Model. In the File Type section, select Model or Resource as the file type that you want to import. In the Advanced Settings section, select one or more of the following resources to import: Localized names to import localized names for the ECTs in a particular locale. Imported localized names are merged with the existing localized names by Business Data Connectivity. Properties to import properties for ECTs. Imported properties are merged with the existing property descriptions by Business Data Connectivity. Permissions to import permissions for ECTs and other securable objects in the model. (Optional) To save the resource settings in a file for later use, type a name for the resource file in the Use Custom Environment Settings text box. Select Import. Export a BDC Model You can export a BDC Model and then read its contents to determine differences between connections. This can be useful if you are troubleshooting. You can also import an exported BDC Model file into another environment for testing or reuse. To export a BDC Model or Resource file, follow these steps: In the left pane of the new SharePoint admin center, select More features. Under BCS, select Open. Select Manage BDC Models and External Content Types. Select the dropdown, and in the View group, select BDC Model. Select the name of the BDC Model that you want to export, on the ribbon, select Export. On the Business Data Connectivity Models page, select the model or resource file to export. On the Export page, in the File Type section, to specify the type of file that you want to export, select Model or Resource. In the Advanced Settings section, to further refine the data export, select one or more of the following: To export localized names for the ECTs in a particular locale, selectLocalized names. To export properties for ECTs, select Properties. To export permissions for ECTs, select Permissions. To export an implementation-specific proxy that is used to connect to the external system, select Proxies. . If you saved a file of resource settings for later use, enter the name of the file to export in the Use Custom Environment Settings field. Select Export to start a dialog that enables you to save a .bdcm file to your local drive. You can open the .bdcm file in a text editor. Add actions to external content types By adding actions to ECTs, administrators associate a uniform resource locator (URL) with an ECT. This automatically starts a specified program or opens a specified web page. Actions can specify parameters that are based on one or more fields in an ECT. For example, you can create an action for an ECT that specifies a Search page URL. The parameter for this action might be the ID of an item in the external data source. This would allow you to specify a custom action for the ECT that automates search for this item. [!NOTE] When you add a new action to an ECT, that action is not added to existing external lists for that ECT. The action is only available in new external lists for the ECT. To add an action to an ECT, follow these steps. In the left pane of the new SharePoint admin center, select More features. Under BCS, select Open. Select Manage BDC Models and External Content Types. Point to the name of the ECT to which you want to add an action, and then select the arrow that appears. From the menu, to open the Add Action page, select Add Action. In the Name field, give the action a meaningful name. In the URL field, for the action you want to open, enter the URL. [!NOTE] Under the control, you can find an example URL. The example shows how to add one (or more) parameter place-holders such as {0}, or {1} (http:www.adventure-works.comsample.aspx?p0={0}&p1={1} ). If you want web parts on the site to be able to use this new action, select one of the following options: CommandAction :-----:----- Yes Starts the action in a new browser window (preserves the page context). No Starts the action in the same browser window. In the URL Parameters field, specify any parameters that are required by the URL. These are numbered in the interface starting at 0. Decide if you want to use an Icon or not. This field also allows you to use Standard icons. If you want the action to be the default action, select the Default Action check box. [!IMPORTANT] Parameters can contain personally identifying information such as names and Social Security numbers. When you design an action, be careful not to use fields that display personally identifying information. View external data and external data settings You use the View section of the ribbon to choose different views of BCS connections. The three views display information about the BCS connection in different ways, and give you access to different actions. It is important to become familiar with these views because some tasks are available only in specific views. The three view options are BDC Models, External Systems, and External Content Types, as shown in the following illustration. For more information about how you can use these views to help manage BCS, see the sections that follow. External Content Types view By default, the BCS connection uses the External Content Types view. This view shows Service Application Information, and lists the following information: ECT name ECT display name ECT type namespace Namespace version External system name For most processes in BCS, this view is sufficient. However, if there are many ECTs, this view can be difficult to navigate. External Systems view The External Systems view shows a BCS connection in terms of its system of origin. This view is useful if you want to know the BCS connection information after you create the BCS. In this view, you can see the property settings for a named External System. In addition, you can configure some of the property settings. View property settings The name of the External System appears on this page as a selectable link (a navigable URL). You can select the URL to open a window that shows the original property settings for that store. In addition, if you are connected to SQL Azure, you can see the database server name and database, in this view. Depending on the type of BCS connection, the property settings can include any combination of the following items: Access Provider (such as WCF Service) Authentication Mode (such as User's Identity) Database Server Impersonation Level (such as None, Anonymous, Identification, Impersonation, Delegation) Initial Database name Integrated Security (such as SSPI) Secure Store Implementation Secure Store Target Application ID (as the ID entered in Secure Store) Service EndPoint Address (such as the URL pointing to SomeWCFService.svc) Connection Pooling (ActiveInactive) Secondary Secure Store Target Application ID Secure Store Implementation Configure property settings If you point to an External System Name, you can open a shortcut menu that includes a Settings command. This is useful for SharePoint connections that use Windows Communication Foundation (WCF) Web Services. By selecting the Settings option from the menu, you can configure any of the following settings: Metadata Exchange URL Metadata Exchange Discovery Mode Web Services Description Language (WDSL) Authentication Mode WSDL Secure Store Target Application Id Secure Store Implementation. BDC Model view The BDC Model view offers ribbon commands that enable you to import or export BDC Models. In addition, the BDC Model view can make it easier to move around in a very large collection of ECTs. Because the BDC Model shows hyperlinks for each distinct connection, rather than showing all ECTs for each connection, it can make a more manageable list. If you want to see all the ECTs for a BDC Model, select the name of the Model. If you select the name of an ECT, open a table that shows the fields that are defined for the ECT. It resembles the following table. NameTypeDisplay by Default :-----:-----:----- Order Id System.String No Employee Id System.String No Freight System.Nullable '1[[System.Decimal, .... No This display can closely mirror the layout of the data source connected via an ECT, and give better insight into the structure of the underlying data. Also, at the bottom of the page, any Associations, Actions, or Filters for this ECT appear.

OfficeDocs-SharePoint/SharePoint/SharePointOnline/manage-business-connectivity-service-applications.md/0

Manage Business Connectivity Service Applications

OfficeDocs-SharePoint/SharePoint/SharePointOnline/manage-business-connectivity-service-applications.md

OfficeDocs-SharePoint

ms.date: 03212024 title: "Manage sites in the SharePoint admin center" ms.reviewer: daminasy ms.author: ruihu author: maggierui manager: jtremper recommendations: true audience: Admin f1.keywords: - CSH ms.topic: how-to ms.service: sharepoint-online ms.collection: - Strat_SP_admin - M365-collaboration - m365initiative-spsitemanagement - essentials-manage ms.custom: - seo-marvel-apr2020 - admindeeplinkSPO search.appverid: - SPO160 - MET150 - BSA160 ms.assetid: d8c63491-0410-405c-880a-8cef7fa4480a description: "In this article, you learn about tasks you can perform on the Active sites page of the SharePoint admin center, such as view site details, view and change site membership, and change a site's hub association." Manage sites in the SharePoint admin center The Active sites page of the SharePoint admin center lets you view the SharePoint sites in your organization, including communication sites, channel sites, and sites that belong to Microsoft 365 groups. It also lets you sort and filter sites, search for a site, and create new sites. The Active sites page lists the root website for each site collection. [!NOTE] Subsites and the following sites aren't included: Sites with these URLs aren't included for the Active sites page: URLDescription :-----:----- sitescontentTypeHub Content hub host sitesCompliancePolicyCenter Policy center portalhub PointPublishing hub search Search site personal OneDrive sites Sites with these templates aren't included for the Active sites page: IDNameDescription :-----:-----:----- 6000 REVIEWCTR Review center 10043 FunSite SharePoint tenant fundamental site 65 POINTPUBLISHINGHUB PointPublishing hub 66 POINTPUBLISHINGPERSONAL0 Personal blog 67 POINTPUBLISHINGTOPIC0 PointPublishing topic 3500 POLICYCTR Compliance policy center 30003 TestSite Test site 3 CENTRALADMIN Central admin site 54 SPSMSITEHOST My Site host 21 SPSPERS SharePoint Portal Server personal space 16 TENANTADMIN Tenant admin site 301 REDIRECTSITE Redirect site 70 CSPCONTAINER CSP container Note that you may see differences between the sites in the active sites list and those listed in the SharePoint site usage report in the Microsoft 365 admin center because the site templates and URLs listed above are included in the SharePoint site usage report. For more info about tasks on the Active sites page, see: Create a site Register a site as a hub site and Unregister a site as a hub site Change sharing settings for a site Delete a site Manage site storage limits Add or remove site admins and group owners For all site types except channel sites, you can add or remove site admins and change the primary admin. For group-connected team sites, you can also add and remove group owners. Note that if you remove a person as a primary admin, they will still be listed as an additional admin. For info about each role, see About site permissions. In the SharePoint admin center, select Sites > Active sites or browse to the Active sites page. In the left column, select a site. Select Membership on the command bar to open the details panel to update the permissions of the members. :::image type="content" source="mediaadd-remove-site-members.png" alt-text="Screenshot of membership tab in details panel"::: Add or remove people or change their role, and then select Save. Change a site's hub association In the SharePoint admin center, select Sites > Active sites or browse to the Active sites page. In the left column, select a site. Select Hub on the command bar. The options that appear depend on whether the site you selected is registered as a hub site, or associated with a hub. The Hub menu lets you register a site as a hub site, associate it with a hub, change its hub association, and unregister it as a hub site. For more information, see More info about hubs. View site details For more info about a site, select the site name or click anywhere on the site row except on the URL column to open the details panel or for channel sites select the link in the Channel sites column and then select the site name. To view site activity including the number of files stored and storage usage, select the Activity tab. Activity information is not available for US Government GCC High and DoD customers. To view site admins, owners, members, and visitors, select the Membership tab. :::image type="content" source="mediaview-site-members.png" alt-text="Screenshot of Membership tab selection on details panel"::: For info about the roles in this panel, see About site permissions. Related topics Manage site storage limits

OfficeDocs-SharePoint/SharePoint/SharePointOnline/manage-sites-in-new-admin-center.md/0

Manage sites in the SharePoint admin center

OfficeDocs-SharePoint/SharePoint/SharePointOnline/manage-sites-in-new-admin-center.md

OfficeDocs-SharePoint

ms.date: 09232021 title: Onboard new employees into your organization ms.reviewer: ms.author: ruihu author: maggierui manager: jtremper recommendations: true audience: Admin f1.keywords: - NOCSH ms.topic: article ms.service: sharepoint-online localization_priority: Priority ms.collection: - Strat_SP_modern - M365-collaboration - m365solution-corpcomms - m365solution-scenario - highpri search.appverid: - SPO160 - MET150 description: "Learn how to onboard new employees into your organization using Microsoft 365" Onboard new employees into your organization Make new employee onboarding (sometimes referred to as NEO) a great experience by fostering an all-in-one hybrid work environment where new employees can find important resources, meet people in their organization, and prepare to be successful in their new role. When entering a new organization, knowing where resources are located, who to go to for help, and how to find training materials in an organized and personalized environment will help new employees navigate your organization efficiently. This article will guide you on how to create a welcoming onboarding environment for new employees using Microsoft’s modern work tools. Create a virtual onboarding experience by: Planning and implementing an end-to-end experience based on your organization’s tools, resources, and initiatives Hosting a virtual welcome event to share resources and introduce onboarding buddies Using a SharePoint site template to provide a home base for new team members Creating a personalized onboarding checklist using the Onboarding checklist list template Curating a training experience for new team members using Viva Learning Overview of how to create an onboarding experience Icon Phase Tasks :-------------------: :-------------------: :---------------- Plan - Scope your audience - Map out the employee onboarding experience - Review Microsoft 365 onboarding tools - Consider creating a new employee support community in Viva Engage Build - Consider using a live event to welcome and orient new team members - Include partners like hiring managers, business owners, and human resources in the planning process - Have a plan to maintain NEO content over time - Create an onboarding site using the New employee onboarding template - Customize an Onboarding checklist template in Microsoft 365 Lists - Prepare a survey to ask for feedback at the end of onboarding Launch - Send out invites, instructions, and resources using Outlook Mail and Calender. - Gather insights from each platform used to measure overall performance of the employee onboarding process - Use feedback to inform the next onboarding session. Plan the onboarding experience :-------------: :--------------: :------------: Step 1: Scope your audience and goals Step 2: Map the onboarding experience Step 3: Review Microsoft 365 tools -Determine the needs and the size of your audience. -Define deliverables and desired outcomes of the onboarding experience -Establish tone and messaging -Establish and onboarding timeline -Define which onboarding tasks need to be completed - Prioritize onboarding tasks -Curate learning materials -Ask for feedback frequently - choose onboarding tools that will best suit your needs. Planning considerations: Even before a new employee’s first day on the job, they will need some information about NEO before the event itself. Consider a pre-onboarding SharePoint site that can help new employees gather the right documents and prepare for the NEO event as soon as they sign their offer letter. Some new employees cannot attend the NEO event in person. Consider if it’s better to pre-record an event that can be shown to people who cannot attend in person or if you can live-stream the in-person event and new employees who are remote can join online. Regardless of the NEO event attendance is in person or remotely, the NEO audience will need access to the same resources on desktop and mobile devices. Step 1: Start by determining your audience profile and size New employees will have diverse backgrounds, roles, and career experience. Some new employees will be able to attend an event in person while other can only attend remotely. Some tools and resources will need to be accessible from a mobile device. The same resources will need to be available regardless of the new employee orientation method. The size of your onboarding group will determine the platforms and resources you use. Learn more about defining your audience profile and scoping audience size. Groups of 1-19 Groups of 20 or more :--------------- :---------------- Office (PowerPoint, word) SharePoint Teams Viva Learning Viva Connections SharePoint Spaces Office (PowerPoint, word) SharePoint Teams Viva Learning Viva Connections SharePoint Spaces Viva Engage Define the desired outcome and priority content Spend time defining what success looks like when orientation is complete. In many organizations, onboarding happens for more than one part of the business, consider offering an onboarding structure that allows the new employee to become familiar with the organization and the team they will be working with. Consider setting up modules that guide employees through onboarding and lets them know about their progress. Consider the tone and messaging for your onboarding process Make new employees feel welcome and excited to be joining your organization. Use PowerPoint to prepare a well-crafted message that lists out the various benefits and resources your new employees can take advantage of as members of your organization. Introduce them to the culture of your company by laying out company history, fun facts, and more. Step 2: Map the ideal employee onboarding experience From inception to orientation to day one on the job, the new employee journey has a huge impact on the success of that employee. Ensure the new employee is provided the best tools to start out with by mapping out the new employee onboarding experience. A. Establish an onboarding timeline Determine how long the onboarding process should take based on the role and level of career experience. Think about how often new team members should be taking training courses and attending events that connect them with leadership and the rest of the organization. B. Scope and define the most important content and tasks Create deliverables that let you know that each employee has achieved full competency in a specific subject that is important to the job. This can be learning about the company itself, specific tools, organizational expectations, and more. C. Collect, prioritize, and organize resources and content When entering a new environment, understanding the order in which deliverables should be completed may be a blind spot for new employees. Help them prioritize onboarding deliverables by laying them out in a way that signals priority. This could be as simple as writing them out for them or integrating Microsoft Lists. Learn how to use Microsoft Lists to help onboard employees. D. Create a personalized training experience Which learning materials are needed to help make the new employee successful? Curate learning modules for each employee that helps orient them on organizational needs, team needs, and the tools that they will be working with daily. Learn more about using Viva Learning. E. Get feedback along the way The goal of every onboarding process is to make sure each new employee feels fully equipped to be successful in their new job. Receiving honest feedback once employees are finished with the onboarding process is the best way to fill in the gaps and improve onboarding for incoming employees. Find out what worked and what could use improvement by creating simple and thoughtful surveys. Learn more about getting feedback using Microsoft Forms. Step 3: Review Microsoft 365 onboarding tools A great option is to use Teams live meetings, live events, and chat functionality to welcome new employees and provide an engaging experience for those that can attend in-person as well as remote. Direct users to information and contacts on a SharePoint communications site. Consider using a NEO Viva Engage channel where new people can ask questions and get answers. You can even consider using SharePoint spaces for virtual training or facility tours. Then, bring it all together using Viva Connections, which integrates SharePoint content into Microsoft Teams. Microsoft Teams meeting - Meetings in Teams include audio, video, and screen sharing, and are great for communicating with groups of fewer than 300 individuals. Teams can be used for meetings that happen in person, remotely, or a combination of the two. Additionally, the meeting can be recorded and shared with new employees who were unable to attend the meeting. SharePoint communication site - Create a SharePoint communication site using the New employee onboarding site template. Use the site to direct new employees to relevant resources, contacts, and conversations in new employee Viva Engage communities. Viva Engage channel – Create a Viva Engage channel just for new employees. Choose to create one NEO channel for the entire organization or region or create channels for each new group of new employees. Then, use the Viva Engage web part on the SharePoint NEO site to integrate the conversation with other resources and contacts. Microsoft Viva – Viva modules are personalized employee experiences that display as apps in Microsoft Teams. Use Viva Connections to bring onboarding resources and tools into one place. Content in the Viva Connections experience can be targeted to specific audiences. Use Viva Learning to curate learning modules for each employee that helps orient them on organizational needs, team needs, and the tools that they will be working with daily. SharePoint spaces - Use SharePoint Spaces to create an immersive platform that allows new employees to take a virtual tour of the campus. Build the new employee onboarding experience Build out the employee onboarding experience one platform at a time. The tools listed here can be connected to each other providing a thorough and connected onboarding journey for the new employee. Create an onboarding site using SharePoint Create an internal communication site that acts as a home for new employees. This site should lay out resources, deliverables, and company information in and organized way. This site should also contain the most up-to-date information to ensure the new employee has everything needed to be successful. Try organizing action items on this site in a way that signals priority. List the things that need to be finished first at the top. This will help employees organize their work in onboarding to the best of their ability and gives each new employee the same starting point. Microsoft offers a new customizable employee onboarding SharePoint communication site template that can help get you started. Get started with SharePoint site templates Use live meetings to administer a virtual employee orientation With the emergence of virtual work, having face time with other people in the organization is still important in making sure employees can communicate with leaders, peers, and ask top-of-mind questions. Use Microsoft Teams to administer virtual employee orientation. Make this live event fun and engaging by giving employees an opportunity to communicate with each other in the Teams chat box or allow employees to ask questions on camera or through the moderated Q&A in Teams live events. Learn more about Teams live events. Give employees a tour of the campus using SharePoint Spaces SharePoint Spaces is a tool that provides immersive online experiences using 2D and 3D web parts. Guide new employees through a virtual 360-degree tour of the campus. Incorporate helpful links and web parts that provide important information and helps the employee complete onboarding tasks.Learn more about SharePoint Spaces. Help the new employee prioritize deliverables with Microsoft Lists When entering a new environment, understanding the order in which onboarding tasks should be completed is important. Help them prioritize onboarding deliverables by laying them out in a way that signals priority. Consider using Microsoft Lists and List templates and add them as tabs in the New employee Teams channel for easy access. You can also integrate List into the new employee onboarding SharePoint site using the List web part. Use Viva Connections and integrate with other Microsoft Viva experiences Help orient new employees by providing them with the most important company information, resources, and updates regularly. Viva Connections is a digital platform built on the existing capabilities of Microsoft 365 that allows organizations to customize employee experiences and gain access to the most important information the most used tools and resources on both desktop and mobile devices. Learn more about creating onboarding experiences using Microsoft Viva. Integrate multiple Viva modules to create a rich onboarding experience In the image above, Viva Connections is being used to display cards that integrate with other Viva experiences. Create a card that links to Viva Insights to help new team members understand how to spend time productively and help managers provide better guidance on time management. Learn more about Viva Insights and how it helps protect and organize worklife balance. A separate card integrates with Topics, which helps to address a key business issue in many companies — providing the information to users when they need it. For example, new employees need to learn a lot of new information quickly, and encounter terms they know nothing about when reading through company information. Learn more about how Topics can help with knowledge management. Viva Learning is an application for Microsoft Teams that allows users to discover, recommend, and access learning modules from different platforms to help users gain knowledge in any specific focus area. Viva Learning pulls content from LinkedIn Learning, Microsoft Learn, Microsoft 365 Training, and other partners. Use Viva Learning to curate learning modules for each employee that helps orient them on organizational needs, team needs, and the tools that they will be working with daily. In Viva Learning, managers of an organization or team can assign learning and track the learning progress of each module. The Viva Learning home view aggregates a variety of information, including assigned content from learning management systems, recommended learnings, trending content, and learning provider content libraries. Learn more about Viva Learning. Learn more about Viva modules: Viva Learning Topics Viva Insights Viva Connections --------------- Target specific training for new employees. New team members can learn about popular terms, acronyms, projects, and more. Help new team members spend time productively. Provide easy access to benefits, training materials, and resources. Create Virtual Communities for new employees in Viva Engage Give new employees the opportunity to connect with each other and build a supportive virtual community in Viva Engage. Viva Engage is a platform that connects leaders, communicators, and employees to build communities, share knowledge, and engage across the organization. Viva Engage allows you to set up a community specifically for new employees within the organizational platform. Naturally, employees come across information at different times in their onboarding process. Creating a space where new employees can build a community for themselves gives them the opportunity to share information as they come across it. In this virtual space, new employees can share resources, share ideas, and get to know each other. It also helps them build internal bonds that can last over the course of their career. Learn more about building communities in Viva Engage. Ask for feedback using Microsoft Forms The best way to improve the new employee onboarding experience is by asking for feedback. Understand what worked best and what could use improvement by asking for feedback after all deliverables have been completed by new employees. Use Microsoft forms to build short surveys that answer the questions that could inform the onboarding experience moving forward. Learn more about Microsoft forms. Launch the new employee onboarding experience Use Outlook to invite all new employees to orientation. In this email, lay out all the resources starting with the Viva Connections homepage that contains links to the New Employee SharePoint site, the New Employee orientation live meeting event post, learning objectives and more. Be sure to include any necessary information and important direct contact. Gather insights from each platform along the way. Use these insights to inform managers, team leads, and other stakeholders. Look for insights such as live event attendance, audience reach, site traffic, and more. Use the feedback gathered from each onboarding cycle to inform the next onboarding cycle. More Resources Review Microsoft 365 communication tools and methods Corporate communications overview Use the SharePoint New employee onboarding site template

OfficeDocs-SharePoint/SharePoint/SharePointOnline/onboard-employees.md/0

Onboard new employees into your organization

OfficeDocs-SharePoint/SharePoint/SharePointOnline/onboard-employees.md

OfficeDocs-SharePoint

ms.date: 06102022 title: Plan file sync for SharePoint and OneDrive in Microsoft 365 ms.reviewer: ms.author: ruihu author: maggierui manager: jtremper recommendations: true audience: Admin f1.keywords: NOCSH ms.topic: concept-article ms.service: sharepoint-online ms.localizationpriority: medium ms.collection: - essentials-get-started ms.custom: intro-get-started search.appverid: MET150 description: Learn how to plan file sync for SharePoint and OneDrive in your organization Plan file sync for SharePoint and OneDrive in Microsoft 365 Even though users can upload, download, and interact with SharePoint and OneDrive files from a web browser, the ideal experience comes with the OneDrive sync app for Windows and Mac, and the iOS and Android mobile apps. The OneDrive sync app has a variety of configuration options for compliance, performance, user experience, and disk space management. While these can be configured at any time, it's important to consider some of them as part of your rollout plan. Key decisions for sync: How do you want to deploy the sync app? How do you want to manage sync on Windows computers? Which update ring do you want to use? Do you want to limit network utilization for sync? Do you want to sync commonly used folders with OneDrive Do you want to limit which organizations users can sync with? Do you want to allow users to sync their personal OneDrive? Do you want to block certain file types from being uploaded? Do you need to sync files in a hybrid environment with SharePoint Server? Do you want to limit sync to computers joined to a specific domain? For information about the recommended configuration options for the sync app, see Recommended sync app configuration. How do you want to deploy the sync app? You have several different options for deploying the OneDrive sync app: manually, using scripting, using Windows Autopilot (for the sync app on Windows), using a mobile device management solution such as Intune, or using Microsoft Endpoint Configuration Manager. The OneDrive sync app is included as part of Windows 10, Windows 11, and Office 2016 or higher. You do not need to deploy the sync app to devices running these, though you may need to update the sync app to the latest version. To deploy the OneDrive sync app to Windows using Microsoft Endpoint Configuration Manager, see Deploy OneDrive apps by using Microsoft Endpoint Configuration Manager. If you need to install the sync app on a single computer, see Install the sync app per machine. For a full list of OneDrive sync app requirements, see OneDrive sync app system requirements. How do you want to manage sync on Windows computers? You can manage OneDrive sync app settings on Windows computers using Windows Group Policy or by using administrative templates in Intune. Using group policy requires that Windows computers be joined to an Active Directory domain. Using Intune requires that the device be managed by Microsoft Endpoint Manager. For information, see: Use OneDrive policies to control sync settings Use administrative templates in Intune Mac settings are configured using .plist files. For information, see Deploy and configure the OneDrive sync app for Mac. Which update ring do you want to use? You can select how soon your users receive updates we release for the sync app. Insiders ring - In this ring, users get the first changes that are released to the public. We recommend selecting several people in your IT department to join this ring. Production ring – In this ring, users get fixes and new features in a timely fashion. We recommend leaving everyone else in the organization in this ring. Enterprise ring – In this ring, you have more control over the deployment of updates, but users have to wait longer to receive fixes and new features. Configure the following policy to set the sync app update ring. PolicyWindows GPOMac :-----:----------:-- Set the sync app update ringGPOSetUpdateRingTier For details about the update process for the OneDrive sync app, see The OneDrive sync app update process. Do you want to limit network utilization for sync? Depending on your network capacity, you may want to consider limiting how much network bandwidth the sync app can use. This can be useful during a migration phase when large amounts of content are being synced. Use the following policies to limit the network bandwidth used by the sync app. PolicyWindows GPOMac :-----:----------:-- Limit the sync app upload rate to a percentage of throughputAutomaticUploadBandwidthPercentageAutomaticUploadBandwidthPercentage Enable automatic upload bandwidth management for OneDriveEnableAutomaticUploadBandwidthManagementNA Do you want to sync commonly used folders with OneDrive? Users often save files to their documents folder or desktop. They may not realize that they should save these files in OneDrive. You can automatically sync these commonly used folders to OneDrive, prompt users to do so, or prevent them from doing so. Use the following policies to configure how users commonly used folders are synced with OneDrive. PolicyWindows GPOMac :-----:----------:-- Silently move commonly used folders to OneDriveKFMSilentOptInKFMSilentOptIn Prompt users to move their commonly used folders to OneDriveKFMOptInWithWizardKFMOptInWithWizard Prevent users from stopping sync of their commonly used folders to OneDriveKFMBlockOptOutKFMBlockOptOut Prevent users from moving their commonly used folders to OneDriveKFMBlockOptInKFMBlockOptIn For more information about syncing commonly used folder with OneDrive, see Redirect and move Windows known folders to OneDrive and Redirect and move macOS Desktop and Documents folders to OneDrive. Do you want to limit which organizations users can sync with? By default, users can sync shared libraries from other organizations. You can limit this to specific organizations or disable it all together. Use the following policies to configure which organizations users can sync with. PolicyWindows GPOMac :-----:----------:-- Allow syncing OneDrive accounts for only specific organizationsAllowTenantListAllowTenantList Block syncing OneDrive accounts for specific organizationsBlockTenantListBlockTenantList Prevent users from syncing libraries and folders shared from other organizationsBlockExternalSyncBlockExternalSync For more information about syncing with other organizations, see B2B Sync. Do you want to allow users to sync their personal OneDrive? Depending on your governance practices, you can prevent users from syncing their personal OneDrive accounts to devices managed by your organization. Use the following policies to specify if users can sync personal OneDrive accounts. PolicyWindows GPOMac :-----:----------:-- Prevent users from syncing personal OneDrive accountsDisablePersonalSyncDisablePersonalSync Do you want to block certain file types from being uploaded? You can specify if you don't want users to be able to upload certain types of files using the sync app. Use the following policy to configure this. PolicyWindows GPOMac :-----:----------:-- Exclude specific kinds of files from being uploadedEnableODIgnoreListFromGPOEnableODIgnore This can also be configured in the SharePoint admin center. For more information, see Block syncing of specific file types. Do you need to sync files in a hybrid environment with SharePoint Server? If your organization uses SharePoint Server 2019 or SharePoint Server Subscription Edition, you can sync files using the OneDrive sync app. For information, see Configure syncing with the new OneDrive sync app. If you are using the previous OneDrive sync app (Groove.exe), see Transition from the previous OneDrive for Business sync app for information on how to move to the new OneDrive sync app. Do you want to limit sync to computers joined to a specific domain? To make sure that users sync OneDrive files only on managed computers, you can configure OneDrive to sync only on PCs that are joined to specific domains. For more information, see Allow syncing only on computers joined to specific domains. Next steps [!div class="nextstepaction"] Plan for content migration Related topics Plan for SharePoint and OneDrive in Microsoft 365

OfficeDocs-SharePoint/SharePoint/SharePointOnline/plan-file-sync.md/0

Plan file sync for SharePoint and OneDrive in Microsoft 365

OfficeDocs-SharePoint/SharePoint/SharePointOnline/plan-file-sync.md

OfficeDocs-SharePoint

ms.date: 07112018 title: "Manage query client types" ms.reviewer: ms.author: ruihu author: maggierui manager: jtremper recommendations: true audience: Admin f1.keywords: - NOCSH ms.topic: article ms.service: sharepoint-online ms.collection: M365-collaboration ms.custom: admindeeplinkSPO ms.localizationpriority: medium search.appverid: - SPS150 - SPO160 - MET150 ms.assetid: 0d335bc4-e7a0-46bc-ba40-da34e414174f description: "Learn how query client types decide in which order queries are performed." Manage query client types [!INCLUDEappliesto-2013-2016-2019-SUB-xxx-md] Learn how query client types decide in which order queries are performed. A query client type is how a client performing a query tells the system what type of client it is. For example, a client might tell us it is UI, or an automated query. Query throttling monitors the use of resources and protects the search system. Administrators can use client-type information for throttling, to make sure lower-priority clients like automated queries don't squeeze out higher-priority clients like UI. Query client types are also used for things like logging, reports, and determining relevance. The client sets the client type as a label in the query. The administrator configures the valid client types (though some are default and mandatory), and the client chooses one for each query. [!NOTE] You can't turn query throttling on or off. Add a query client type [!NOTE] You can change the name of a client type that has been created for your tenant only. Go to More features in the SharePoint admin center, and sign in with an account that has admin permissions for your organization. [!NOTE] If you have Office 365 operated by 21Vianet (China), sign in to the Microsoft 365 admin center, then browse to the SharePoint admin center and open the More features page. Under Search, select Open. On the search administration page, select Manage Query Client Types. To add a client type, select New Client Type. On the Edit a client type page, in the Query Client Type field, for the client type, enter a name. From the Throttling Tier list, select either Top, Middle, or Bottom. [!NOTE] Lower priority queries are throttled first. The search system processes queries from top tier to bottom tier. Select OK. Prioritize a client query type You can use throttling tiers to prioritize query processing. When the resource limit is reached, query throttling kicks in, and the search system processes queries, starting from the top tier, right through to the bottom tier. Go to More features in the SharePoint admin center, and sign in with an account that has admin permissions for your organization. [!NOTE] If you have Office 365 operated by 21Vianet (China), sign in to the Microsoft 365 admin center, then browse to the SharePoint admin center and open the More features page. Under Search, select Open. On the search administration page, select Manage Query Client Types. Go to the Client Type section, and select the System Type that you want to change. From the Throttling Tier list, select either Top, Middle, or Bottom. [!NOTE] Lower priority queries are throttled first. The search system processes queries from top tier to bottom tier. Select OK.

OfficeDocs-SharePoint/SharePoint/SharePointOnline/query-throttling.md/0

Manage query client types

OfficeDocs-SharePoint/SharePoint/SharePointOnline/query-throttling.md

OfficeDocs-SharePoint

ms.date: 04122024 title: "Curate the allowed list for Restricted SharePoint Search" ms.reviewer: ms.author: ruihu author: maggierui manager: jtremper recommendations: true audience: administrator ms.topic: how-to ms.service: sharepoint-online ms.localizationpriority: medium ms.collection: - Ent_O365_Hybrid - M365-collaboration - m365copilot - magic-ai-copilot description: "Learn how to use SharePoint Admin Center active sites report and SharePoint Advanced Management Data Access Governance report to find the most active and shared sites for the Restricted SharePoint Search allowed list. " Curate the allowed list for Restricted SharePoint Search [!IMPORTANT] Restricted SharePoint Search is designed for customers of Copilot for Microsoft 365. Visit here and the overview of Restricted SharePoint Search for more information. As a Global and SharePoint admin, you can set up an allowed list of Restricted SharePoint Search with a maximum of 100 selected SharePoint sites. For Copilot and organization-wide search, besides the contents that they already have access to, either by direct sharing, visiting, or owning, your organization’s users will only be able to reach the sites on the allowed list, honoring these sites’ current permissions. Setting up the allowed list in Restricted SharePoint Search gives you time to review and audit site permissions. But which sites should be included in the allowed list? This article introduces strategies and techniques for curating the allowed list. Steps to create the curated allowed list To create a curated allowed list for Restricted SharePoint Search, we recommend you start by creating an initial list of sites. Then you work with your site admins and stakeholders to assess permissions and review the sites. Finally, you can apply the list with PowerShell scripts as a Global admin. Step 1: Get an initial list of sites Every organization might have different criteria on what sites you choose to be searched across your organization and discoverable by Copilot. You can use SharePoint Admin Center (SPAC) features to identify sites that can be part of the allowed list based on your own criteria. To keep the list manageable, we recommend starting with the following two types of sites when for the allowed list: The “Known” sites: You and your SharePoint site admins already know set of sites from your organization that are safe to participate in organization wide search and the Copilot experience. These sites can be included in the allowed list. The top active and shared sites: the allowed list affects what users can see in their organization-wide search results and their Copilot experience. To optimize users’ search and Copilot experience, the hypothesis is that those top active and shared sites need to be included in the allowed list. Depending on your license, you can use either the SharePoint Admin Center (SPAC) or the SharePoint Admin Center Data access governance (SPAC DAG) Activity(sharing) report to identify the most active and shared sites. Step 2: Review site permissions Once you have the list of sites (up to 100), make sure the site permissions and content controls are implemented well enough to make them visible for search and Copilot experience. You can work with your site admins and stakeholders to assess permissions and review the sites. [!NOTE] The limit of up to 100 SharePoint sites includes Hub sites, but not their sub-sites. When you enable Hub sites, the sub-sites under a Hub site are included in the allowed-list but do not count towards the 100-site limit. So if you are picking Hub sites, make sure all the child sites have proper permissions. Step 3: Use PowerShell Scripts to apply the allowed list After you review permissions in your curated sites, you can use PowerShell Scripts to turn on Restricted SharePoint Search, add, and remove sites. You can also use PowerShell Scripts to get the list of all sites in your allowed list. Find the most active and shared sites You can find the most active sites using the SharePoint Admin Center (SPAC). If you have either Microsoft 365 E5 licensing or Microsoft Syntex - SharePoint Advanced Management, you can also use SPAC DAG to find the most shared sites. Using SharePoint Admin Center (SPAC): If your organization has SharePoint, you have access to SPAC. You can get this list of sites using SPAC Active sites feature that had most page views and files in the last 30 days. This can be an indicator to get to the list of sites interested by the broadest possible audience in the organization. Using SPAC DAG Activity(sharing) report to identify sites that have been shared most in the last 28 days. Use SharePoint Admin Center (SPAC) to find the most active sites Admins can use SharePoint Admin Center (SPAC) features to identify sites that can be part of the allowed list based on their criteria. The Active sites page in the SharePoint admin center lets you view the SharePoint sites in your organization. Based on your organization’s needs, you can sort and filter sites based on columns such as Last activity, Page views, Page visits. You can search for sites, and customize the columns and views. Step 1: In SPAC left pane, select “Active Sites.” Step 2: Using the sorting and filtering functionality of the Active sites you can curate top 100 sites based on your organization needs and create a custom view. Step 3: First move the columns by scrolling to right and clicking the “Customize columns”. Use up and down arrows next to each column's name to move up the Page Views and Files next to the URL, so it's easy for you to see the important columns together for analysis. Step 4: To create custom view of the top 100 sites sorted by “page views” for last 30 days do the following: Select the arrow next to the column header of Page views and select Large to Small. Select the arrow next to the column header of Last activity select on the Filter by last activity> Last 30 days. You can use the other columns to sort, or filter based on your needs. Step 5: Once you're done with your sorting and filtering, you can create a custom view based on your current setting, and save it for future use. To create a custom view, select All sites > Save view as. Enter a name for your custom view: Your saved custom view is now available for you to choose from the drop-down menu next time. Step 6: Export the sites and manage the list in CSV file that you can use to add to the list by selecting the Export tab. Your exported CSV file looks similar to the following CSV file: Use SPAC DAG Activity (sharing) report to find most shared sites The SPAC DAG report (Data access governance reports for SharePoint sites) is part of SharePoint admin center. Admins with Microsoft 365 E5 licensing or Microsoft Syntex - SharePoint Advanced Management can access this report. This report helps you identify potential sites that are active and shared in the last 28 days. Step 1: In the left pane, select Reports > Data access governance. Select the Sharing links report. Step 2: In the right pane Sharing Links page, select on the Anyone links report. Step 3: "Anyone" links report gives you a list of sites in which the highest number of Anyone links were created. These links let anyone access files and folders without signing in. These sites might be great candidates to allow in tenantorg wide search. Resources Microsoft Copilot for Microsoft 365 - best practices with SharePoint

OfficeDocs-SharePoint/SharePoint/SharePointOnline/restricted-sharepoint-search-allowed-list.md/0

Curate the allowed list for Restricted SharePoint Search

OfficeDocs-SharePoint/SharePoint/SharePointOnline/restricted-sharepoint-search-allowed-list.md

OfficeDocs-SharePoint

ms.date: 07112018 title: "Set up a new term set" ms.reviewer: shrganguly ms.author: ruihu author: maggierui manager: jtremper recommendations: true audience: Admin f1.keywords: NOCSH ms.topic: article ms.service: sharepoint-online ms.collection: M365-collaboration ms.custom: admindeeplinkSPO ms.localizationpriority: medium search.appverid: - SPO160 - OSU150 - MET150 ms.assetid: 8255dbdf-1c0a-4987-88d8-8f4a0a980953 description: "Learn how to create a new term set for managed metadata in SharePoint" Set up a new term set To add a term set, you must be a contributor, group manager or a term store admin. To set up a new term set In the SharePoint admin center, under Content services, select Term store. In the tree-view navigation pane, expand the groups to select the group to which you want to add a term set. Click Add term set. . Type a name for the term set and press ENTER. General tab On the General tab, for Owner, select Edit. The Edit Properties panel appears. Specify the following information about who owns and maintains this term set: Term Set owner: If you want the owner of the term set to be someone other than you, enter the person, group, or email address for who will maintain this term set. Stakeholders: Add the names of users, groups, or email addresses that should be notified before major changes are made to the term set. Contact: If you want site users to be able to provide feedback on the term set, enter an email address. Click Save. Usage settings tab To configure the term submission policy On the Usage settings tab, for Submission policy, select Edit. The Edit submission policy panel appears. Specify whether you want the term set to be Closed or Open. If you select Closed, only people with contribute permissions can add terms to this term set. If you select Open, users can add terms from a tagging application. Click Save. To configure the tagging policy Under the Usage settings tab, for Available for tagging, select Edit. The Available for tagging panel appears. Select the Enable check box to make the terms in the term set available for tagging. If you clear the Enable check box, this term set won't be visible to most users. If the term set is still in development, or is not otherwise ready for use, you might want to clear the Enable check box. Select Save. Navigation tab Enabling site navigation means you can use the terms in this term set for site navigation links with friendly URLs and dynamic content. Enabling faceted navigation means users can use refiners based on managed metadata from the search index to quickly browse to specific content Under the Navigation tab, for Use term set for site navigation, select Edit. The Edit Properties panel appears. Click the Enable check boxes to use this term set for site or faceted navigation. Click Save. Enabling either using the term set for site or faceted navigation enables options to set a custom target page and a custom catalog item page. You can choose a custom target page if you want to display a specific page. Custom target pages that you set for individual terms will override this setting. To set a custom target page For Custom target page, select Edit. The Edit term set target page panel appears. Move the toggle switch to enable Use a custom target page. Click Select, and then select Save. The target page appears when users navigate to a friendly URL in this term set. If terms in this term set are used as catalog categories, you can select the page used to render catalog data for items under those categories. To set a custom catalog item page For Custom catalog item page, select Edit. The Edit term set catalog item page panel appears. Move the toggle switch to enable Use a custom catalog item page. Click Select and then select Save. Advanced tab You can use machine translation to translate your terms, or you can export and import XLIFF files. You must repeat the translation each time you update the term set. To configure translations Under the Advanced tab, for Translation, select Manage. The Translation panel appears. To use machine translation to translate this term set into the working languages for the term store, select Start. The Machine translation panel appears. For the terms you want to translate, select either All terms, or Only the terms updated since the last translation. From both the Translate from and Translate to dropdowns, select a language. Click Translate. You can use custom properties to store additional data about a term set. To edit custom properties For Custom properties, select Edit. The Edit Custom properties panel appears. Enter a Property name and Value, and then select Add.\ Click Save. To learn how to add a term to the new term set, see Create and manage terms in a term set.

OfficeDocs-SharePoint/SharePoint/SharePointOnline/set-up-new-term-set.md/0

Set up a new term set

OfficeDocs-SharePoint/SharePoint/SharePointOnline/set-up-new-term-set.md

OfficeDocs-SharePoint

ms.date: 04232024 title: "Admin center site permissions reference" ms.reviewer: srice ms.author: ruihu author: maggierui manager: jtremper recommendations: true audience: Admin ROBOTS: NOINDEX f1.keywords: - CSH ms.topic: article ms.service: sharepoint-online ms.localizationpriority: medium ms.custom: admindeeplinkSPO layout: ContentPage ms.collection: - Strat_OD_share - M365-collaboration search.appverid: - SPO160 - MET150 description: "Learn about site permissions that you can configure in the SharePoint admin center." Admin center site permissions reference On the Membership tab, you can manage permissions for the site and also for any associated Microsoft 365 group or Microsoft Teams team. These roles are specific to the selected site or group and don't give users access to the SharePoint admin center. Owners Microsoft 365 group owners can manage group membership, privacy, and classification, as well as the associated SharePoint site. If the Microsoft 365 group is associated with a team, then the group owners are also team owners. Members Microsoft 365 group members can participate in the group and have access to the associated SharePoint site. If the Microsoft 365 group is associated with a team, then the group members are also team members and can send messages and participate in channels if allowed by the team owner. Site admins Site admins (formerly called site collection administrators) have the highest level of SharePoint permissions. They have the same Full Control permissions of a site owner, plus they can do more things, such as managing search, the recycle bin, and site collection features. They also have access to any items in the site, including in subsites, even if permissions inheritance has been broken. If there's a Microsoft 365 group or team connected to the site, then group or team owners are automatically included as site admins and group or team members are automatically included as site members. Managing site permissions through group or team membership is recommended over giving people permissions directly to the site. This method allows for easier administration and consistent access for users across group and team resources. Non-primary admins Additional admins beyond the Primary admin are site admins only and can only manage the SharePoint site. They have no access to the associated Microsoft 365 group or team unless they have also been directly added to the group or team. Site owners Site owners have full control of the SharePoint site. If the site has an associated Microsoft 365 group or team, then group or team owners are automatically included as site owners. However, people added directly to the site owners group don't have access to the Microsoft 365 group or team unless they are added there directly. Site members Site members have edit permissions to the SharePoint site and can add and remove files, lists, and libraries. If the site has an associated Microsoft 365 group or team, then group or team members are automatically included as site members. However, people added directly to the site members group don't have access to the Microsoft 365 group or team unless they are added there directly. Site visitors Site visitors have view-only permissions to the SharePoint site. This permission level is only used by SharePoint and isn't related to permissions in an associated Microsoft 365 group or team. [!NOTE] For information on how to manage Site owners, Site members and Site visitors permission groups, see Sharing and permissions in the SharePoint modern experience. Additional permissions There are additional permission levels in SharePoint beyond those shown on this panel. Users may have access to the site or its contents through those roles. Users may also have access to files or folders in the site through sharing links. See also External sharing overview Overview of Microsoft 365 Groups for administrators

OfficeDocs-SharePoint/SharePoint/SharePointOnline/site-permissions.md/0

Admin center site permissions reference

OfficeDocs-SharePoint/SharePoint/SharePointOnline/site-permissions.md

OfficeDocs-SharePoint

ms.date: 11142023 title: "Transition from the previous OneDrive for Business sync app" ms.reviewer: ms.author: mactra author: MachelleTranMSFT manager: jtremper audience: Admin f1.keywords: - NOCSH ms.topic: article ms.service: one-drive ms.localizationpriority: medium ms.collection: - Strat_OD_admin - M365-collaboration ms.custom: - seo-marvel-apr2020 - onedrive-toc search.appverid: - ODB160 - ODB150 - GOB150 - GOB160 - MET150 ms.assetid: 4100df3a-0c96-464f-b0a8-c20de34da6fa description: "Learn how to upgrade users from the previous OneDrive for Business sync app to the new OneDrive sync app (OneDrive.exe)." Transition from the previous OneDrive for Business sync app [!IMPORTANT] Support for the previous OneDrive sync app (Groove.exe) ended on January 11, 2021. As of February 1, 2021, users can no longer sync OneDrive or SharePoint files in Microsoft 365 by using Groove.exe. Groove.exe will continue to work only for files in SharePoint Server. This article is for global and SharePoint admins who want to transition their users off of the previous OneDrive sync app (Groove.exe) so that they sync with only the new OneDrive sync app (OneDrive.exe). If you're not an IT admin, to learn how to begin syncing files using the new OneDrive sync app, see Sync files with the new OneDrive sync app in Windows. [!NOTE] If your organization never used the previous OneDrive sync app, or had fewer than 250 licensed Office 365 users in June 2016, your users are already using the new OneDrive sync app to sync files in OneDrive and SharePoint. Syncing files with OneDrive sync app to OneDrive sync app When users who are syncing files with the previous OneDrive sync app (Groove.exe) sign in to the new OneDrive sync app (OneDrive.exe), the following things happen: If the new OneDrive sync app can take over syncing a library, the previous sync app stops syncing it,, and the new OneDrive sync app takes over syncing it without redownloading the content. If the new OneDrive sync app can't sync the library, the previous sync app continues to sync it. If a library requires checkout or has required columns or metadata, it's synced read-only. The previous sync app stops running and removes itself from automatic startup, unless it's still syncing libraries that the new OneDrive sync app can't sync. When SharePoint libraries begin syncing with the new OneDrive sync app, the folder hierarchy that appears in File Explorer may be simplified. Limits The following library types aren't yet supported by the new OneDrive sync app, and won't transition from the previous sync app: On-premises locations in SharePoint Server 2016 or earlier. Learn about using the OneDrive sync app with SharePoint Server 2019 SharePoint libraries that people from other organizations shared that your users are syncing with the previous sync app. For more info about sync restrictions and limitations, see Invalid file names and file types in OneDrive and SharePoint Requirements To transition users off of the previous sync app, first make sure users have: Windows 10, Windows 8.1, Windows 8, or Windows 7. A current version of the new OneDrive sync app installed. For info about deploying the new OneDrive sync app, see Deploy OneDrive apps using Microsoft Endpoint Configuration Manager. OneDrive.exe must be deployed and configured before you try the takeover command. Download the latest version of the new OneDrive sync app that's fully released to production. To learn about the versions that are rolling out to different rings, see New OneDrive sync app release notes. The following versions of Office or higher installed. For info about deploying Office, see Choose how to deploy Microsoft 365 Apps for enterprise. Make sure you don't install the previous OneDrive sync app. For info, see Changes to OneDrive sync app deployment in Office Click-to-Run. Office version Minimum version ------------------ Microsoft 365 Apps for enterprise 16.0.7167.2 Office 2016 MSI 16.0.4432.1 Office 2013 MSIC2R 15.0.4859.1 [!NOTE] If any users have Office 2010 installed, we strongly recommend removing the SharePoint Workspace component. If users previously set up SharePoint Workspace (even if they're no longer using it), it will cause problems syncing team sites. Before starting OneDrive Setup, either Uninstall Office from a PC or modify the installation. To do this by running Setup, first create the following XML file: xml Then run Setup: console Setup.exe modify ProPlus config RemoveSharepointDesigner.xml For more info, see Setup command-line options for Office 2010 and Config.xml file in Office 2010. The latest Rights Management Service (RMS) client if you want users to be able to sync IRM-protected SharePoint document libraries and OneDrive locations. Configure takeover When the required software is installed on your users' computers, you can configure automatic takeover of syncing silently (review the prerequisites and steps), and then use this policy. After you install and configure OneDrive.exe, Groove.exe should no longer be able to sync. If the takeover didn't succeed, or your users are stuck in a hybrid state (some content syncing with OneDrive.exe and some with Groove.exe), try running: %localappdata%\Microsoft\OneDrive\OneDrive.exe takeover. [!TIP] Make sure to run the command in a user context, rather than as admin, or the error "OneDrive.exe cannot be run with Admin privileges" appears. To affect all users on the computer, configure the command to run on every user account so it will run for any user who signs in. If the takeover didn't succeed, the previous OneDrive sync app (Groove.exe) may be an older version that can't successfully transition to the new client. To patch the previous sync app, update groove-x in Office 2016 or Office 2013, and then try again. See also To help your users get started with the OneDrive sync app, you can refer them to the following articles: Sync files with the new OneDrive sync app in Windows Get started with the new OneDrive sync app for Mac Sync SharePoint files with the new OneDrive sync app

OfficeDocs-SharePoint/SharePoint/SharePointOnline/transition-from-previous-sync-client.md/0

Transition from the previous OneDrive for Business sync app

OfficeDocs-SharePoint/SharePoint/SharePointOnline/transition-from-previous-sync-client.md

OfficeDocs-SharePoint

title: "About user profile synchronization" ms.reviewer: amysim ms.author: ruihu author: maggierui manager: jtremper recommendations: true ms.date: 5212020 audience: Admin f1.keywords: - NOCSH ms.topic: article ms.service: sharepoint-online ms.collection: M365-collaboration ms.localizationpriority: medium search.appverid: - SPO160 - MET150 ms.assetid: description: "This article describes the user profile sync process for SharePoint in Microsoft 365, and the properties that are synced into user profiles." User profile synchronization Microsoft SharePoint uses the Active Directory synchronization job to import user and group attribute information into the User Profile Application (UPA). When a new user is added to Microsoft Entra ID, the user account information is sent to the SharePoint directory store and the UPA sync process creates a profile in the User Profile Application based on a predetermined set of attributes. Once the profile has been created, any modifications to these attributes will be synced as part of regularly scheduled sync process. [!NOTE] The profile properties that are synced by the UPA sync process are not configurable. Synchronization times will vary based on workloads. Sync process There are four steps in the sync process. StepDescription ------ 1. Active Directory to Microsoft Entra ID Microsoft Entra Connect syncs data from on-premises Active Directory to Microsoft Entra ID. For more info, see What is hybrid identity with Microsoft Entra ID? and Attributes synchronized. 2. Microsoft Entra ID to SharePoint Microsoft Entra ID syncs data from Microsoft Entra ID to the SharePoint directory store. 3. SharePoint to UPA The UPA sync process syncs user account information in SharePoint directory store to the User Profile Application (UPA). 4. UPA to sitesUser account information from the UPA is synced to SharePoint sites (previously called "site collections"). Typically, user profiles are created automatically for all accounts that are created in Microsoft 365. For organizations that have a Microsoft 365 Education subscription, user profiles are not created for new accounts by default. The user must access SharePoint once, at which time a basic stub profile will be created for the user account. The stub profile will be updated with all remaining data as part of the sync process. If block sign-in is set on the user account in Microsoft Entra ID or disabled accounts are synced from Active Directory on premises, those user accounts will not be processed as part of the UPA sync process. The user must be enabled and licensed for changes to be processed. Properties that are synced into SharePoint user profiles The following Microsoft Entra user attributes are synced to the UPA. Microsoft Entra attributeUser profile property display namesNotesSync to sites :-------:-------:-------:------- UserPrincipalNameAccount Name User Name User Principal NameExample: i:0.f membership gherrera@contoso.com gherrera@contoso.comYes DisplayNameNameYes GivenNameFirstNameYes snLastNameYes telephoneNumberWork phoneExample: (123) 456-7890Yes proxyAddressesWork Email SIP AddressWork Email is set to the value prefixed with SMTP. (SMTP:gherrera@contoso.com) Example: gherrera@contoso.comYes PhysicalDeliveryOfficeNameOfficeYes TitleTitle Job TitleJob Title contains the same value as Title and is connected to a term set.Yes DepartmentDepartmentDepartment is connected to a term set.Yes WWWHomePagePublic site redirectNo PreferredLanguageLanguage PreferencesUsed by SharePoint to determine language for the user when the multilingual user interface (MUI) feature is enabled.Yes msExchHideFromAddressListSPS-HideFromAddressListsNo ManagerManagerUser Manager for organization hierarchyYes [!NOTE] To update additional or custom properties, see Bulk update custom user profile properties. Some property names could differ between Azure AD Graph and Microsoft Graph, see Property differences between Azure AD Graph and Microsoft Graph. Frequently asked questions (FAQs) How often are changes synced into the User Profile Application? User account attribute changes are collected in batches and processed for UPA synchronization. Times will vary based on the amount of changes requested in a single batch. The UPA synchronization is schedule to run at regular intervals. Will UPA synchronization overwrite existing properties in SharePoint user profiles? For the default properties that are synced by UPA synchronization, values will be overwritten to align with Microsoft Entra ID. Does UPA synchronization update only properties that have changed? UPA synchronization is driven primarily by changes that are made Microsoft Entra ID, including adding new users. A full import can occur under certain maintenance events. Why isn't it possible to map additional properties for UPA synchronization to sync from Microsoft Entra ID to the User Profile Application? UPA synchronization is limited to a preconfigured set of properties to guarantee consistent performance across the service.

OfficeDocs-SharePoint/SharePoint/SharePointOnline/user-profile-sync.md/0

User profile synchronization

OfficeDocs-SharePoint/SharePoint/SharePointOnline/user-profile-sync.md

OfficeDocs-SharePoint

title: "Configuration failure during removal" ms.reviewer: ms.author: serdars author: SerdarSoysal manager: serdars ms.date: 312018 audience: ITPro f1.keywords: - NOCSH ms.topic: article ms.service: sharepoint-server-itpro ms.localizationpriority: medium ROBOTS: NOINDEX ms.collection: - IT_Sharepoint_Server - IT_Sharepoint_Server_Top ms.assetid: 4451ffa5-3119-4402-9c67-168e58c5154d description: "Summary: Learn how to remove SharePoint Server during a configuration failure." Configuration failure during removal Summary: Learn how to remove SharePoint Server during a configuration failure. When you choose Uninstall from Uninstall or change a program, the Setup Wizard starts and attempts to uninstall the product. If an error is encountered, the uninstall process won't complete and the error will be noted in the setup log file. [!NOTE] The setup log file is stored in the temp directory for the user account that is running setup (%USERTEMP% or %WINDIR%\Users\user account\AppData\Local\Temp) and is named "SharePoint Server Setup ( YYYYMMDDHHMMSSrandomnumber).log" where YYYYMMDD is the date and HHMMSS is the time (hours in 24-hour clock format, minutes, seconds, and milliseconds) and the random number is used to differentiate between possible simultaneous attempts to run the setup program. You can review the log file for error messages. After you understand why the error occurred, you can address the issue, and then you can choose to either stop the uninstall process, address the problem, and then run Uninstall again, or you can continue the uninstall process. If you exit Setup when an error is encountered, the binary files won't be removed. However, tasks that were successfully completed won't be undone. This approach will enable you to restore the server to working condition by running the configuration wizard in Repair mode. If you choose to continue with the uninstall process, the binary files will be removed. The resulting state of the computer will depend on when the configuration wizard failed. For example, the computer might still: Be joined to the server farm. Be registered in the configuration database and the connection string on the local computer could exist. Include services that are running. With the binary files removed, you won't be able to use the configuration wizard to clean up the configuration settings on the local computer or in the configuration database.

OfficeDocs-SharePoint/SharePoint/SharePointServer/PSConfigHelp/configuration-failure-during-removal.md/0

Configuration failure during removal

OfficeDocs-SharePoint/SharePoint/SharePointServer/PSConfigHelp/configuration-failure-during-removal.md

OfficeDocs-SharePoint

title: "Specify farm security settings" ms.reviewer: ms.author: serdars author: SerdarSoysal manager: serdars ms.date: 312018 audience: ITPro f1.keywords: - NOCSH ms.topic: article ms.service: sharepoint-server-itpro ms.localizationpriority: medium ROBOTS: NOINDEX ms.collection: - IT_Sharepoint_Server - IT_Sharepoint_Server_Top ms.assetid: 01d6f28f-675c-4418-a9ad-fcc8bbfdc58c description: "Summary: Learn how to use a passphrase in SharePoint Server." Specify farm security settings Summary: Learn how to use a passphrase in SharePoint Server. Type a passphrase to help to secure farm configuration data, and then select Next. Although a pass phrase is similar to a password, it's usually longer to enhance security. It's used to encrypt credentials of accounts that are registered in SharePoint products, for example, the system account that you provide when you run the SharePoint 2016 Products Configuration Wizard. Ensure that you remember the pass phrase, because you must use it each time you add a server to the farm. Ensure that the passphrase meets the following criteria: Has at least eight characters Contains at least three of the following four character groups: English uppercase characters (A through Z) English lowercase characters (a through z) Numerals (0 through 9) Nonalphabetic characters (such as !, $, , %) You can change the passphrase after the farm has been configured by running the Set-SPPassphrase cmdlet in Microsoft PowerShell. By default, the new passphrase will be deployed across all servers in the farm. However, if there's a failure in the deployment of the new passphrase, you must manually update the passphrase on the individual server on which the deployment failed. Run the Set-SPPassphrase - LocalServerOnly cmdlet in Microsoft PowerShell to manually update the passphrase. [!NOTE] When you perform an upgrade, the Specify Farm Security Settings page does not appear.

OfficeDocs-SharePoint/SharePoint/SharePointServer/PSConfigHelp/specify-farm-security-settings.md/0

Specify farm security settings

OfficeDocs-SharePoint/SharePoint/SharePointServer/PSConfigHelp/specify-farm-security-settings.md

OfficeDocs-SharePoint

title: "Assign a category page and a catalog item page to a term in SharePoint Server" ms.reviewer: ms.author: serdars author: SerdarSoysal manager: serdars ms.date: 7142017 audience: ITPro f1.keywords: - NOCSH ms.topic: article ms.service: sharepoint-server-itpro ms.localizationpriority: medium ms.collection: IT_Sharepoint_Server_Top ms.assetid: a2c1b8a0-68a2-4399-931f-cf58cfc3875d description: "Learn how to assign a category page and a catalog item page to a term in term store management." Assign a category page and a catalog item page to a term in SharePoint Server [!INCLUDEappliesto-2013-2016-2019-SUB-xxx-md] Category pages and catalog item pages are page layouts that you can use to show structured content consistently across a site. They are often used when displaying catalog content on a site that uses managed navigation. This saves you from having to create many individual pages for content that you want to show in the same manner across your site. You can assign a category page or a catalog item page to all terms in a term set, or to specific terms in a term set. For more information, see "Catalog pages and catalog item pages" in Overview of cross-site publishing in SharePoint Server. Before you begin [!NOTE] Because SharePoint Server runs as websites in Internet Information Services (IIS), administrators and users depend on the accessibility features that browsers provide. SharePoint Server supports the accessibility features of supported browsers. For more information, see the following resources: > Plan browser support> Accessibility guidelines in SharePoint> Accessibility in SharePoint> Keyboard shortcuts> Touch. Before you assign a category page and a catalog item page in term store management, verify the following: The publishing site is using managed navigation. By default, site collections that are created by using the Publishing Portal Site Collection template use managed navigation. You have created a navigation term set in term store management as described in Create and manage terms in a term set. You have created a category page and a catalog item page. [!IMPORTANT] If you have connected a publishing site to a catalog and selected to integrate the catalog into the publishing site as described in Connect a publishing site to a catalog in SharePoint Server, the category page and catalog item page configurations that you specified are displayed in term store management. Assign a category page and a catalog item page to a term By default, when you assign a category page to a term, the page that you specify will also be assigned to the children of the term unless you specify a different page to be used on all the children of a term. [!NOTE] You should only assign catalog item pages to a term if the term set is used as a tagging term set for catalog content. To assign a category page and a catalog item page to a term Verify that the user account that performs this procedure is a member of the Owners SharePoint group on the site. On the site, on the Settings menu, click Site Settings. On the Site Settings page, in the Site Administration section, click Term store management. On the Term Store Management Tool page, in the TAXONOMY TERM STORE section, click the term to which you want to assign a category page and a catalog item page. Click the tab TERM-DRIVEN PAGES. To assign a category page to a term, in the Target Page Settings section, select the check box Change target page for this term, and then type the URL of the category page that you want to assign to the term. Or you can click the Browse button, and then go to the category page that you want to assign to the term. To assign a category page to the children of a term, select the check box Change target page for the children of this term, and then type the URL of the category page that you want to assign to the children of the term. Or, you can click the Browse button, and then go to the category page that you want to assign to the children of the term. To assign a catalog item page for catalog items that are tagged with the current term, select Change Catalog Item Page for this category, and then type the URL of the catalog item page that you want to assign to catalog items that are tagged with the term. Or you can click the Browse button, and then go to the catalog item page that you want to assign to catalog items that are tagged with the term. To assign a catalog item page for catalog items that are tagged with a child of the current term, select Change Catalog Item Page, and then type the URL of the catalog item page that you want to assign to catalog items that are tagged with children of the term. Or you can click the Browse button, and then go to the catalog item page that you want to assign to catalog items tagged with children of the term. See also Other Resources Blog post: Assign a category page and a catalog item page to a term

OfficeDocs-SharePoint/SharePoint/SharePointServer/administration/assign-a-category-page-and-a-catalog-item-page-to-a-term.md/0

Assign a category page and a catalog item page to a term in SharePoint Server

OfficeDocs-SharePoint/SharePoint/SharePointServer/administration/assign-a-category-page-and-a-catalog-item-page-to-a-term.md

OfficeDocs-SharePoint

ms.date: 03132018 title: "Back up site collections in SharePoint Server" ms.reviewer: ms.author: serdars author: SerdarSoysal manager: serdars audience: ITPro f1.keywords: - NOCSH ms.topic: article ms.service: sharepoint-server-itpro ms.localizationpriority: medium ms.collection: - IT_Sharepoint_Server - IT_Sharepoint_Server_Top ms.assetid: 45acdd33-b322-4f36-97f1-0701159e15f0 description: "Learn how to back up a single site collection in SharePoint Server." Back up site collections in SharePoint Server [!INCLUDEappliesto-2013-2016-2019-SUB-xxx-md] You can back up a site collection in SharePoint Server by using the SharePoint Central Administration website or Microsoft PowerShell. Before you begin We recommend that you regularly back up the complete farm. However, IT practices might require you to also back up a site collection. For more information about what to back up, see Plan for backup and recovery in SharePoint Server. Before you begin this operation, review the following information: You must first create a folder on the local computer or the network in which to store the backups. For better performance, we recommend that you back up to the local computer and then move the backup files to a network folder. For more information about how to create a backup folder, see Prepare to back up and restore farms in SharePoint Server. If the site collection's Lock status is set to Not locked or Adding content prevented, SharePoint Server temporarily sets the site to Read-Only while the backup operation is occurring. SharePoint Server does this to reduce the possibilities of users changing the site collection while it is being backed up. After the backup is complete, the setting is changed back its normal status. Performing a site collection backup might require resources and might slightly affect farm performance when the backup is running. You can help avoid performance issues by backing up the farm during hours when farm use is lowest, such as outside office hours. Use PowerShell to back up a site collection in SharePoint Server You can use PowerShell to back up a site collection manually or as part of a script that can be run at scheduled intervals. To back up a site collection by using PowerShell Verify that you have the following memberships: securityadmin fixed server role on the SQL Server instance. db_owner fixed database role on all databases that are to be updated. Administrators group on the server on which you are running the PowerShell cmdlets. An administrator can use the Add-SPShellAdmin cmdlet to grant permissions to use SharePoint Server cmdlets. [!NOTE] If you do not have permissions, contact your Setup administrator or SQL Server administrator to request permissions. For additional information about PowerShell permissions, see Add-SPShellAdmin. Start the SharePoint Management Shell. At the PowerShell command prompt, type the following command: powershell Backup-SPSite -Identity -Path [-Force] [-NoSiteLock] [-UseSqlSnapshot] [-Verbose] Where: \ is the ID or URL for the site collection you want to back up. \ is the path to where the backup file is located. If you want to overwrite a previously used backup file, use the Force parameter. You can use the NoSiteLock parameter to keep the read-only lock from being set on the site collection while it is being backed up. However, using this parameter can enable users to change the site collection while it is being backed up and could lead to possible data corruption during backup. To display the site collection GUID or URL at the PowerShell command prompt, type the following command: powershell Get-SPSite format-list -property id,url If the database server is running an Enterprise Edition of SQL Server, we recommend that you also use the `UseSqlSnapshot` parameter for more consistent backups. You can also export sites or lists from these snapshots. > [!NOTE] > If the RBS provider that you are using does not support snapshots, you cannot use snapshots for content deployment or backup. For example, the SQL FILESTREAM provider does not support snapshots. For more information about how to use SQL snap-shots, see [Back up databases to snapshots in SharePoint Server](back-up-databases-to-snapshots.md). For more information, see Backup-SPSite. [!NOTE] We recommend that you use Microsoft PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions. Use Central Administration to back up a site collection in SharePoint Server You can use Central Administration to back up a site collection. To back up a site collection by using Central Administration Verify that the user account performing this procedure is a member of the Farm Administrators group. Additionally, verify that the Windows SharePoint Services Timer V4 service has Full Control permissions on the backup folder. Start Central Administration. In Central Administration, on the home page, in the Backup and Restore section, click Perform a site collection backup. On the Site collection backup page, select the site collection from the Site Collection list. Type the local path of the backup file in the Filename box. [!NOTE] If you want to reuse a file, select the Overwrite existing file check box. Click Start Backup. You can view the general status of all backup jobs at the top of the Granular Backup Job Status page in the Readiness section. You can view the status for the current backup job in the lower part of the page in the Site Collection Backup section. The status page updates every 30 seconds automatically. You can manually update the status details by clicking Refresh. Backup and recovery are Timer service jobs. Therefore, it may take several seconds for the backup to start. If you receive any errors, you can review them in the Failure Message column of the Granular Backup Job Status page. See also Concepts Plan for backup and recovery in SharePoint Server Restore site collections in SharePoint Server

OfficeDocs-SharePoint/SharePoint/SharePointServer/administration/back-up-site-collections.md/0

Back up site collections in SharePoint Server

OfficeDocs-SharePoint/SharePoint/SharePointServer/administration/back-up-site-collections.md

OfficeDocs-SharePoint

title: "Change the Content Search Web Part display template and use Windows PowerShell to start Usage analytics in SharePoint Server" ms.reviewer: ms.author: serdars author: SerdarSoysal manager: serdars ms.date: 382018 audience: ITPro f1.keywords: - NOCSH ms.topic: article ms.service: sharepoint-server-itpro ms.localizationpriority: medium ms.collection: IT_Sharepoint_Server_Top ms.assetid: df979ec9-bdf7-4d96-b3a6-37213c45e5da description: "Learn how to change the Content Search Web Part display template and use Microsoft PowerShell to start Usage analytics in SharePoint Server." Change the Content Search Web Part display template and use Windows PowerShell to start Usage analytics in SharePoint Server [!INCLUDEappliesto-2013-2016-2019-SUB-xxx-md] [!NOTE] The examples in this series are based on an on-premises SharePoint Server deployment. Change the mapping of the UsageAnalyticsID managed property In our Contoso website, we want to recommend one product per product group, that is, we want Usage analytics to ignore the product color. This means that our recommendations must be calculated on Group Number. We can do this, because Group Number is part of the friendly URL (FURL) on our item detail page (see Stage 10: Configure the query in a Content Search Web Part on a catalog item page in SharePoint Server). In the previous blog post, we told you that managed property that's used to specify how recommendations between individual catalog items should be calculated is UsageAnalyticsID (see About the UsageAnalyticsID managed property). For Usage analytics to do its calculation on Group Number, we must change the mapping of the UsageAnalyticsID property. Here's how you do that: [!IMPORTANT] You have to change the property mapping on the authoring site. On your authoring site, go to Site settings --> Search Schema. On the Managed Properties page, in the Managed property field, type UsageAnalyticsID, and then select the arrow button. From the Property Name field, select EditMap Property. On the Edit Managed Property page, select Add a Mapping. Notice that by default, this property is mapped to the crawled property ows_ProductCatalogItemNumber. In the Crawled property selection dialog, use the Search for crawled property name field to search for the crawled property that you want to map to this managed property. In our Contoso scenario, we want to map the site column called Group Number. Crawled properties don't contain spaces. Therefore, exclude the space, enter GroupNumber and select Find. Two crawled properties are found. Select the crawled property with the ows_ prefix, and select OK. If you are confused because two crawled properties that look about the same are found, you're not alone. This is somewhat tricky. The article From site column to managed property - What's up with that? explains the naming convention for crawled and managed properties. If you are interested in an abbreviated version, here it is as follows: When mapping a crawled property to the UsageAnalyticsID managed property, you should select the crawled property with the ows_ prefix! On the Edit Managed Property page, select the ows_ProductCatalogItemNumber crawled property and then Remove Mapping. Select OK to save the new mapping. [!IMPORTANT] Map only one crawled property to the UsageAnalyticsID managed property. If you map more than one crawled property, the Usage analytics calculation won't work correctly. After you have changed the mapping of the UsageAnalyticsID managed property, perform a full crawl of your catalog, as explained in Stage 4: Set up search and enable the crawling of your catalog content in SharePoint Server. Change a Content Search Web Part display template so the usage events are logged correctly On our Contoso site, we use a Content Search Web Part (CSWP) to display items on the catalog item page, as explained in Stage 10: Configure the query in a Content Search Web Part on a catalog item page in SharePoint Server. By default, the CSWP does not log usage events. To enable our CSWP to log usage events we must change the display template the CSWP is using. Here's what you have to do: In your How to map your network drive, open the display template that you have applied to your CSWP. In the ManagedPropertyMapping element, add the following two properties: powershell 'Original Path'{Original Path}:'OriginalPath', 'SiteID'{SiteID}:'SiteID', Add the following JavaScript just above the HTML part of your display template: ```javascript Log Views usage event on URL of catalog item window.LogViewsToEventStore = function(url, site) { SP.SOD.executeFunc("sp.js", "SP.ClientContext", function() { var spClientContext = SP.ClientContext.get_current(); if(!$isNull(spClientContext)) { var spWeb = spClientContext.get_web(); var spUser = spWeb.get_currentUser(); var spScope = "{00000000-0000-0000-0000-000000000000}"; SP.Analytics.AnalyticsUsageEntry.logAnalyticsEvent2(spClientContext, 1, url, spScope, site, spUser);spClientContext.executeQueryAsync(null, null); } }); }; var originalPath = $getItemValue(ctx, "Original Path"); var originalSite = $getItemValue(ctx, "SiteID"); LogViewsToEventStore(originalPath.value, originalSite.value); ``` In View the usage event definitions we explained the EventTypeIDs for the usage events. The value 1 in this script represents the EventTypeID of the Views usage event. To log a different usage event, substitute this value with the EventTypeID of the usage event that you want to log. Save the file. Why you should simulate the generation of Views usage events Now that our CSWP can correctly log usage events, the next step is to actually generate usage events. In our case, we changed the CSWP to log Views. If the Contoso site was in production, visitors would create a Views usage event every time that they viewed an item on the website. But, the Contoso site is only a demo site. Therefore, it doesn't have any visitors. When you set up your site, you'll most likely want to test the Usage analytics feature before you put it into production. To be able to test the Usage analytics feature, you'll have to generate usage events. To generate recommendations based on usage events, a minimum of three users have to click the same items. There is no single correct way of simulating the generation of Views usage events. To generate Views usage events for the Contoso site, you may want to invite coworkers to a "click party." To to make sure that recommendations are generated, give each user a list of items to click. That way, you can make sure that at least three users click the same items. Here's an example of the instructions that you can give your coworkers: When Usage analytics is run, SV Keyboard E10 will generate a recommendation for WWI Desktop PC2.30 M2300 (people who viewed WWI Desktop PC2.30 M2300 also viewed SV Keyboard E10), and WWI Desktop PC2.30 M2300 will generate a recommendation for SV Keyboard E10 (people who viewed SV Keyboard E10 also viewed WWI Desktop PC2.30 M2300). Run Microsoft PowerShell scripts to start search analytics and push usage events to the Event store After you have generated Views usage events, you have two options on how to continue. The Usage analytics timer job runs once every 24 hours. If you want results faster, you can use some Microsoft PowerShell scripts to speed up the process. Here's what you have to do: Verify that you meet the minimum permission requirements. On the server where SharePoint Server is installed, open the SharePoint 2013 Management Shell as an Administrator. At the Microsoft PowerShell command prompt, type the following commands to start Search analytics. The output from Search analytics is used by Usage analytics to map usage events against the actual items in the search index. powershell $job = Get-SPTimerJob -Type Microsoft.Office.Server.Search.Analytics.AnalyticsJobDefinition $sa = $job.GetAnalysis("Microsoft.Office.Server.Search.Analytics.SearchAnalyticsJob") $sa.StartAnalysis() Wait for the search analytics job to finish. To check the status of the search analytics job, type the following command: powershell $sa.GetAnalysisInfo() As long as the search analytics job is running, State is Running. The search analytics job is finished when State is Stopped and Status is 100. The usage events are added to the Event store in 10-minute intervals. To push the usage events to the Event store, type the following commands: powershell $job = Get-SPTimerJob -Identity ("job-usage-log-file-import") $job.RunNow() View usage events in the Event store After you have pushed the usage events into the Event store, you should verify that the usage events are recorded correctly. To do this, on the machine where SharePoint Server is installed, go to the Event store. In most cases, you can find the Event store in the following folder: C:\Program Files\Microsoft Office Servers\15.0\Data\Office Server\Analytics_\\EventStore In the Event store, the usage events of each day are stored in a separate folder. In our scenario, we can see that a folder was added. In this folder, you'll see some text files. These files contain our usage events. Notice that all file names start with 1_. This number is the EventTypeID of the usage event that is logged in the file. Remember, 1 is the EventTypeID of the Views usage event (see View the usage event definitions). At this point the only usage event we are logging is the Views event. So this is a good sign that we are doing things right. Open one of the files in a text editor. This file contains lots of information, but you should really only be looking for two things: Verify that the usage events are logged correctly. Verify that different users have generated the usage event. In About Usage analytics in a cross-site publishing scenario we explained that for Usage analytics to work, the usage event must be recorded on the URL of the item. In the Event store file, you'll see many URLs. Look for URLs that end in dispform.aspx?id= followed by a number. In our Contoso version of this file, we see there are many entries with such URLs. This means that the usage events are being recorded correctly. To verify that the URLs actually belong to one of our catalog items, copy one of the URLs from this file, and paste it into your browser. To verify that different users have generated the usage event, look in the third column of the file. In our scenario, we can see that we have at least three user IDs. Now that we have verified that the usage events are correctly logged, you might be tempted to think that we are ready to run the Usage analytics job. But remember, by using Microsoft PowerShell to start Usage analytics, we are actually starting timer jobs. When the Usage analytics timer job starts, it'll take the usage events from yesterday and process them. Since we want to process the files from today, we'll use a simple trick so that the correct files can be processed by Usage analytics. Prepare usage events files before you start Usage analytics with Windows PowerShell In your EventStore folder, create a folder named myevents. Copy the usage event files that you want Usage analytics to process into your myevents folder. In our Contoso scenario, copy all files from the View usage events in the Event store folder into myevents. Right-click your myevents folder and select Properties. In the Attributes section, select Read-only (Only applies to files in folder), and then click OK. In the Confirm Attribute Changes dialog, select Apply changes to this folder, subfolder and files and then click OK. Now you are ready to start the Usage analytics job. Start the Usage analytics job with Microsoft PowerShell At the Microsoft PowerShell command prompt, type the following commands: powershell $job = get-sptimerjob -type microsoft.office.server.search.analytics.usageanalyticsjobdefinition $job.DisableTimerJobSchedule() $job.StartAnalysis("\\\Analytics_\EventStore\myevents") $job.EnableTimerJobSchedule() Notice that one command contains two placeholders: host name and guid. The host name is the name of the server where SharePoint Server is installed. You can see the GUID in the file path of your EventStore. Check the status of the Usage analytics job by entering the following command: powershell $job.GetAnalysisInfo() The Usage analytics job is finished when State is Stopped and Status is 100. Now that Usage analytics have processed the usage events, the next step is to display the results of the analysis on our Publishing site. To do that, we'll add and configure two Web Parts. Next article in this series Add and configure the Recommended Items and Popular Items Web Part in SharePoint Server

OfficeDocs-SharePoint/SharePoint/SharePointServer/administration/change-the-content-search-web-part-display-template-and-use-windows-powershell-t.md/0

Change the Content Search Web Part display template and use Windows PowerShell to start Usage analytics in SharePoint Server

OfficeDocs-SharePoint/SharePoint/SharePointServer/administration/change-the-content-search-web-part-display-template-and-use-windows-powershell-t.md

OfficeDocs-SharePoint

title: "Configure digest authentication for a claims-based web application in SharePoint Server" ms.reviewer: ms.author: serdars author: SerdarSoysal manager: serdars ms.date: 8212017 audience: ITPro f1.keywords: - NOCSH ms.topic: article ms.service: sharepoint-server-itpro ms.localizationpriority: medium ms.collection: - IT_Sharepoint_Server - IT_Sharepoint_Server_Top ms.assetid: de49a030-60bc-49aa-979e-8b76678b63f0 description: "Learn how to configure digest authentication for a web application that uses claims-based authentication in SharePoint Server." Configure digest authentication for a claims-based web application in SharePoint Server [!INCLUDEappliesto-2013-2016-2019-SUB-xxx-md] You can configure digest authentication for one or more zones in a SharePoint Server claims-based web application. A web application is an Internet Information Services (IIS) web site that SharePoint Server creates and uses. Zones represent different logical paths for gaining access to the same web application. Within each web application, you can create up to five zones. A different web site in IIS represents each zone. Use zones to enforce different access and policy conditions for large groups of users. To configure digest authentication for one or more zones in a SharePoint Server web application, use IIS Manager console, instead of SharePoint Server Central Administration. Unlike basic authentication, digest authentication encrypts user credentials to increase security. User credentials are sent as an MD5 message digest in which the original user name and password cannot be determined. Digest authentication uses a challengeresponse protocol that requires the authentication requestor to present valid credentials in response to a challenge from the server. To authenticate against the server, the client has to supply an MD5 message digest in a response that contains a shared secret password string. The MD5 Message-Digest Algorithm is described in RFC 1321. For access to RFC 1321, see The Internet Engineering Task Force (https:go.microsoft.comfwlinkp?LinkId=159913). Before you begin Before you perform this procedure, confirm the following: Your system is running SharePoint Server. The user and IIS server must be members of, or trusted by, the same domain. Users must have a valid Windows user account stored in Active Directory Domain Services (AD DS) on the domain controller. The domain must use a Windows Server 2008 or Windows Server 2008 R2 domain controller. [!NOTE] For SharePoint Server 2016, the domain must use a Windows Server 2012 R2 or Windows Server 2016 domain controller You understand digest authentication for web traffic. For more information, see What is Digest Authentication? (previous-versionswindowsit-prowindows-server-2003cc778868(v=ws.10)). Configure IIS to enable digest authentication Use IIS Manager console to configure IIS to enable digest authentication for one or more of the following zones for a claims-based web application: Default Intranet Extranet The Default zone is the zone that is first created when a web application is created. The other zones are created by extending a web application. For more information, see Extend claims-based web applications in SharePoint. To configure IIS to enable digest authentication Verify that you are a member of the Administrators group on the server on which you are configuring IIS. Click Start, point to Administrative Tools, and then click Internet Information Services (IIS) Manager to start IIS Manager console. Expand Sites in the console tree, and then click the IIS web site that corresponds to the web application zone on which you want to configure digest authentication. In Features View, in IIS, double-click Authentication. In Features View, in Authentication, right-click Digest Authentication, and then click Enable. Right-click Digest Authentication, and then click Edit. In the Edit Digest Authentication Settings dialog, in the Realm text box, type the appropriate realm, and then click OK. The realm is a DNS domain name or an IP address that will use the credentials that have been authenticated against your internal Windows domain. You must configure a realm name for digest authentication. The web site is now configured to use digest authentication. See also Concepts Configure Basic authentication for a claims-based Web application Other Resources Plan for user authentication methods in SharePoint Server Extend claims-based web applications in SharePoint

OfficeDocs-SharePoint/SharePoint/SharePointServer/administration/configure-digest-authentication-for-a-claims-based-web-application.md/0

Configure digest authentication for a claims-based web application in SharePoint Server

OfficeDocs-SharePoint/SharePoint/SharePointServer/administration/configure-digest-authentication-for-a-claims-based-web-application.md

OfficeDocs-SharePoint

ms.date: 03132018 title: "Configure backup and restore permissions in SharePoint Server" ms.reviewer: ms.author: serdars author: SerdarSoysal manager: serdars audience: ITPro f1.keywords: - NOCSH ms.topic: article ms.service: sharepoint-server-itpro ms.localizationpriority: medium ms.collection: - IT_Sharepoint_Server - IT_Sharepoint_Server_Top ms.assetid: 3a25437a-e994-42c7-b4df-ac9fa29f38f5 description: "Learn how to configure permissions for backup and restore operations in SharePoint Server." Configure backup and restore permissions in SharePoint Server [!INCLUDEappliesto-2013-2016-2019-SUB-xxx-md] You can configure backup and restore permissions for SharePoint Server by using the SharePoint Central Administration website or Microsoft PowerShell. The backup tool that you use depends on the kind of environment that you have deployed, your backup schedule requirements, and service level agreements that you have made with your organization. Before you begin Before you back up or restore SharePoint Server, you must make sure that the timer service account, SQL Server service account, and users who run the backup or restore operations have the correct permissions or are members of the correct Windows security groups or SharePoint groups. You must configure these permissions and group memberships when you first deploy SharePoint Server. You have to update permissions and group memberships when you add new farm components to the environment and if you want to add users who will perform backup and restore operations. Permissions for the SharePoint Timer service and SQL Server account in SharePoint Server The SharePoint Timer Server and the SQL Server service account in SharePoint Server perform backup and restore operations on behalf of users. These service accounts require Full Control permissions on any backup folders. Group memberships required to run backup and restore operations in Central Administration You must make sure all user accounts that use Central Administration to back up or restore your farm and farm components have the group memberships that are described in the following table. Farm componentMember of Administrators group on the local computerMember of Farm Administrators SharePoint group :-----:-----:----- Farm Yes No Service Application Yes No Content Database Yes No Site Collection No Yes Site, list, document library No Yes Setting permissions to run SharePoint backup and restore operations by using PowerShell You must make sure that all user accounts that use PowerShell to back up or restore your farm and farm components are added to the SharePoint_Shell_Access role for a specified database and have the permissions described in the table later in this section. You can run the Add-SPShellAdmin cmdlet to add a user account to this role. You must run the command for each user account. Moreover, you must run the command for all databases to which you want to grant access. [!NOTE] You only have to grant a user account access to back up and restore a specific farm component one time. You will have to perform this task again only when you add new farm components to your environment or when you want to add users to perform backup and restore operations. [!IMPORTANT] The Add-SPShellAdmin cmdlet grants the SPDataAccess role but this is not enough to complete the restore operation. This is because the restore-spsite cmdlet uses direct insert statements to add content rather than stored procedures which accommodate other interactions. The Add-SPShellAdmin cmdlet worked fine in SharePoint 2010 because as part of the SPDataAccess schema it added dbo permissions. For SharePoint Servers 2019, 2016 and 2013 the db_owner fixed database role permissions are required to complete restore operations from the SharePoint Management Shell. To add a user to or remove a user from the SharePoint_Shell_Access role by using PowerShell Verify that you have the following memberships: securityadmin fixed server role on the SQL Server instance. db_owner fixed database role on all databases that are to be updated. Administrators group on the server on which you are running the PowerShell cmdlets. An administrator can use the Add-SPShellAdmin cmdlet to grant permissions to use SharePoint Server cmdlets. [!NOTE] If you do not have permissions, contact your Setup administrator or SQL Server administrator to request permissions. For additional information about PowerShell permissions, see Add-SPShellAdmin. Start the SharePoint Management Shell. At the PowerShell command prompt, type the following command: powershell Add-SPShellAdmin -Username -Database Where: \ is the GUID assigned to the database. To add a user account to all the databases in the farm, type the following command: powershell ForEach ($db in Get-SPDatabase) {Add-SPShellAdmin -Username -Database $db} Where: \ is the user whose account you want to add. To remove a user account from all the databases in the farm, type the following command: powershell ForEach ($db in Get-SPDatabase) {Remove-SPShellAdmin -Username -Database $db} Where: \ is the user whose account you want to remove. To view the user accounts currently added to the databases in the farm, type the following command: powershell ForEach ($db in Get-SPDatabase) {Get-SPShellAdmin -Database $db} For more information, see Add-SPShellAdmin. [!NOTE] We recommend that you use Microsoft PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions. You might also have to grant additional permissions to the users who run the backup or restore operation by using PowerShell. The following table shows the permissions that are required. Farm componentMember of Administrators group on the local computerMember of Farm Administrators SharePoint groupFull control on backup folder :-----:-----:-----:----- Farm Yes No Yes Service Application Yes No Yes Content Database Yes No Yes Site Collection No Yes Yes Site, list, document library Yes No Yes See also Concepts Plan for backup and recovery in SharePoint Server Prepare to back up and restore farms in SharePoint Server Overview of backup and recovery in SharePoint Server

OfficeDocs-SharePoint/SharePoint/SharePointServer/administration/configure-permissions-for-backup-and-restore.md/0

Configure backup and restore permissions in SharePoint Server

OfficeDocs-SharePoint/SharePoint/SharePointServer/administration/configure-permissions-for-backup-and-restore.md

OfficeDocs-SharePoint