Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

To extract and index documents stored in Microsoft SharePoint, the Locator SharePoint connector needs to be configured with a user that has access to all the documents that are to be extracted. This user is referred to as the index user.

...

  • If any of the "Include Office 365..."-checkboxes in wizard is used for specific site collection templates
  • If "Include other site templates" is checked in the wizard and some of the templates were selected.

Note 3: Global admins and SharePoint admins don't have automatic access to Group Sites. That means they can not manage permissions inside Group Sites. However global admins still have option to add members and owners to Group Sites.

...

  1. To execute the Set-AdminOnSites.ps1 the SharePont Online Client Components SDK is required >> SharePointOnlineClientComponentsSDK
  2. You can run this script with IndexUser parameter set to index user's LoginName or Email. It is important to add i:0#.f|membership| prefix if LoginName is used.
  3. Multiple index users can be provided in the IndexUser parameter..
  4. Each time a new site collection is added to SharePoint, the SharePoint administrator will need to rerun this script or manually add index user permissions on newly created site collections.
  5. Before running this script you have to replace domain in SPOAdminURL with your tenant name.
  6. Before running this script you have to change SPOAdminUser value to your Index User nameIf you run this script without IndexUser parameter then this script will only preview the changes it would have made.
  7. You can provide list of site collections to be excluded in the SkipSiteCollections parameter. It works with both full and relative URLs.
  8. If you run this script with Remove switch then it will remove index user from Site Collection Administrator on each site collection.
  9. This script will prompt you for credentials, you have to provide SharePoint Admin Administrator credentials otherwise the script will fail.
  10. At the end you will have option to perform retry on all site collections the script had failed. AutoRetry switch can be used to do this automatically.

Adding Permissions to the Index User for MySites, OneDrive for Business and Delve Blogs

...

Excerpt

   

Configuring Windows Azure Active Directory

Locator uses the Windows Azure Graph API.  The Office 365 Global Administrator will need to configure an application, called a "service principal" in Windows Azure terminology, to be authorized to read Windows Azure Active Directory information.

Setting up the Windows Azure Graph API for Locator 

Setting up the Windows Azure Graph API for Locator is required in order to configure either an Exchange Online or a SharePoint online connection.  This need only be done one time, as the client ID and secret key obtained through these steps can be used for both the Exchange Online connector and the SharePoint Online connector.


To create and obtain an Azure AD Client App Id and a Client Secret, sign into https://portal.azure.com/#blade/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/RegisteredApps using the global administrator account for your Office 365 organization and do the steps indicated in red below. The two values that are to be extracted are circled in green:






The screenshot above has the application Id we need. The two menu options that are to be used for creating and obtaining the client secret, are circled in red and will be used in the following screenshots:

Image Modified