đź”” This article highlights the advanced parameters available for the Trombinoscope component. For instructions on basic parameters, I recommend referring to another article.
Â
1. Technical Information
Data Source
- UAP
The SharePoint user base is referred to as UPA, which stands for User Profile Application. It is also used by the Delve application, allowing each user to view and update their SharePoint profile.
The UPA base is managed by SharePoint administrators from its administration menu. Profiles can be updated by administrators, while users can update some of their information via Delve.
The UAP base synchronizes from Entra ID to update and retrieve newly created profiles.
- Entra ID
Azure Active Directory has recently been renamed Entra ID. You can access the Entra ID portal if you have the necessary rights.
Management and protection with Microsoft Entra ID are your new identity and security manager. Protect your organization with a cloud-based identity and access management solution that connects employees, customers, and partners to their applications, devices, and data.
Entra ID is therefore your reference point for all users accessing your Digital Workplace. It contains a lot of information about users that, except for the phone number, can only be updated by administrators.
Â
Consult the Entra ID documentation
Â
Entra ID and UAP Synchronization
Â
The Microsoft documentation describes the profile data synchronized between Azure AD and Microsoft 365.
This means:
- Your identity repository is Azure AD, and the main information will be updated from this reference.
- User-customizable profile fields are specific to SharePoint. These fields include education, a person's description, and their skills.
- You can add custom fields in Azure AD profiles by following Microsoft documentation on "What are custom security attributes in Azure AD?"
- To synchronize more than just the main information between your Azure AD and SharePoint UPA, we invite you to research available literature in Microsoft communities. Synchronization can be achieved through a PowerShell script.
Â
Language management
Â
The Employee directory component adapts the information available to the user's language whenever possible. The following information is translated for the user into the language of the page they are on:
Â
- the job: JobTitle property of the UPA profile and Entra ID
- the department: Department property of the UPA profile and Entra ID
- the office: Office property of the UPA profile only
This information is translated:
- In the user profile
- In the organisation chart
- In the results
- In the filters
This information is displayed in the correct language as soon as a translation is available in your SharePoint term bank.
As a reminder, all this information is centralized in the SharePoint term bank and can be translated. Information relating to people is grouped together in the "People" term set available by default in your term bank.
Â
Term bank for your users' profile sheets
Â
âť—It is not possible to use suggestions with translations. Suggestions will only work with the default language of the term shop.
âť—Jint currently supports up to 1000 free entries for each property. Above this limit, we do not guarantee the ability to translate these items.
Â
2 Search parameters
In this group, you can define the parameters for the people search.
The first element to define is the source of your search. You can choose between two sources : Entra ID or SharePoint-Delve Directory.
Â
How do you choose the source?
Â
This will depend on which source you keep most up to date according to your identity management policy, and the Employee directory features you are focusing on, as each of the sources offers different features:
| Functionality | SharePoint | Entra ID |
| Suggestion | Default and customised suggestions | No suggestion |
| Filter | Default and custom filters. Suggests only values containing results |
Filters only on Department and Function. List of fixed values proposed to the user may contain no results |
| Périmètre | Filtrer le Filtering the scope using SharePoint profile properties. à l’aide des propriétés de profil SharePoint |
Filtering using Entra ID properties: - Internal/External - Active/Inactive  - Filtering based on Entra ID groups |
Â
Â
- SharePoint Search Settings
Â
Defining a KQL Query
Â
This field allows you to enter a query in KQL format to specify the search query to be executed. More information on KQL queries can be found here.
By default, the component searches among all profiles available on your tenant. If you wish to limit the use of the directory to a group, a division, or to people with a certain skill, you should use the KQL query to restrict and define this search scope. The SharePoint properties to use are those from your SharePoint search schema.
Example: The KQL query "JobTitle:Developer Department:R&D" allows you to display only employees whose job title is "developer" in the Research and Development department.
Â
Defining Search Suggestions for Users
Â
The Employee directory component offers suggestions as users type, helping them quickly identify filters to find the right person.
Â
Enable Search Suggestions
Â
You have the option to enable or disable the use of search suggestions.
Â
Default Suggested Properties
Â
Default Suggested Properties
By default, the first name and last name are available suggestions. We also offer four commonly used SharePoint properties as additional suggestions:
Â
- Job Title
- Department
- Location
- Skills and Interests
Â
Suggestions for these properties can be disabled if needed.
Â
Custom Suggested Properties
Â
You can add additional properties as suggestions via the "Add Custom Property" button. These data can include default Office data as well as custom data you've added to your Office profiles!
To be used as a suggestion, the managed property must be "refinable" and linked to a "crawled property" from the SharePoint search engine so that it can be proposed in suggestions.
Â
Learn more about the SharePoint search schema.
Â
In the example above, the "School" field corresponding to the SPS-School property is added via "Add Custom Suggestion". All custom suggestions will be added under the separator below "Skills and Interests". They can be enabled/disabled, edited, or removed.
Â
Filters
Â
You can offer filters on different properties to suggest them directly without the need for manual input. This can assist the user in starting their search more easily.
The filters provide values from profiles available within the searched scope. They are displayed in descending order of occurrence, so the most frequent values are available first.
 You can provide up to three different filters.
Â
Â
The filtering feature requires a managed property that is "refinable" from the SharePoint search engine to function properly.
Â
To add a filter, follow these steps:
Â
- Identify the managed property ("crawled property") of the User Profile Application that contains the information you want to filter on.
- Find or create in the SharePoint search engine the "refinable" managed property linked to this crawled property so that it can be proposed in suggestions.
- Add this managed property in the configuration of the Employee directory.
Learn more about the SharePoint search schema
Â
There are default managed properties available in SharePoint. Here is a non-exhaustive list:
Â
- JobTitle
- Department
- BaseOfficeLocation
Â
Once this step is completed:
- To add a filter, use the "Add Filter" button
Â
Â
- To configure the filter:
Â
- Save the information
Â
- Entra ID Search Settings
Â
Groups
Â
When you opt to search your users in Entra ID, you can configure the following features:
- You can also select a scope of individuals defined by Azure AD groups to narrow down the hired individuals to display.
Â
- It is possible to include or exclude external accounts. By default, they are not included.
Â
- Additionally, you can manually add filters to customize the scope. The Newcomers component uses the "User" resource from the Microsoft Graph APIs. For example, if you want to display newcomers in a specific role such as Director, you should write "JobTitle eq 'Director'". You can click the "Run" button to ensure that your filter is correct and to receive a response from the API if it is not. Learn more
Â
Â
Error example
Â
Filters
You can add filters on Departments and Job Titles, for example, for your users by clicking on "Select Filters."
The people term catalog is then presented to you. It's up to you to choose the relevant filter values for your search. All selected values will then be offered to the user in one of the two categories.
Â
Comments
0 comments
Please sign in to leave a comment.