Notatka
Dostęp do tej strony wymaga autoryzacji. Może spróbować zalogować się lub zmienić katalogi.
Dostęp do tej strony wymaga autoryzacji. Możesz spróbować zmienić katalogi.
The Viva Glint integration with Microsoft 365 Organizational Data Service is available to all customers, including customers with multiple Viva Glint instances, customers in GCC Moderate (GCC-M) environments, and customers with multitenant organization (MTO), cross-tenant synchronization (CTS), or business-to-business (B2B) policies set up in Microsoft Entra ID.
For new customers, Microsoft 365 Organizational Data Service is enabled by default. Existing customers with employee data already configured in Viva Glint must complete a one-time onboarding process to map Organizational data attributes to Viva Glint attributes before Viva Glint can import employee data from Microsoft 365 Organizational Data Service.
Organizational data attributes in Viva Glint
When employee data is imported through Microsoft 365 Organizational Data Service, the Organizational data attributes available to Viva Glint fall into two categories:
- Reserved attributes
- Custom attributes
Reserved attributes
Reserved attributes are a set of Organizational data attributes with predefined meanings in Microsoft 365 Organizational Data Service. Reserved attributes can further be classified as public or non-public.
Public reserved attributes are shared with Profile and used by other Microsoft 365 experiences that consume Profile data, including Microsoft 365, Copilot, People card, Viva Amplify, and Viva Engage.
Non-public reserved attributes can be shared with supported apps and Microsoft experiences based on the access chosen by the Organizational data source admin during connector setup. These experiences can include Viva Glint, Viva Insights, Copilot Dashboard, Skills, and Agents.
Most Organizational data attributes must be explicitly mapped to corresponding Viva Glint attributes before Viva Glint can import their values. Viva Glint-specific reserved attributes are mapped automatically.
The following public reserved attributes can be imported into Viva Glint:
| Attribute | Description | Data type | Example |
|---|---|---|---|
| Microsoft_PersonEmail | Unique identifier for an employee record. It can be the employee's primary SMTP address or email alias. | person.name@contoso.com | |
| Microsoft_ManagerEmail | Unique identifier for an employee's manager. It can be the manager's primary SMTP address or email alias. For CEOs, this can be left blank. | manager.name@contoso.com | |
| Microsoft_Organization | The internal organization or department name that an employee belongs to. | String | Financial Planning and Analysis |
| Microsoft_LevelDesignation | Level that represents an employee's experience, management level, or seniority within the organization. This is whatever public level designation your company uses. | String | Director |
| Microsoft_JobDiscipline | The discipline that an employee belongs to. For more actionable insights, avoid using too few or too many unique Job disciplines. This is the public job discipline. | String | Finance management |
| Microsoft_Layer | An employee's position within the organizational hierarchy, expressed as their distance from the top leader of the organization. For example, the CEO is at Layer 0. Avoid using too few or too many unique layers. This is the layer that is publicly available in your company. | Integer | 2 |
| Microsoft_FirstName | First name of the employee. | String | Alexa |
| Microsoft_LastName | Last name of the employee. | String | Smith |
| Microsoft_DisplayName | Preferred name of employee to display. This is the public display name an employee chooses to list. | String | Alexa Smith |
| Microsoft_JobTitle | The public facing job title of the employee. | String | Software engineer |
| Microsoft_CompanyOfficeLocation | An employee’s company office location. This is a location code, like a building number, floor, or room. This shouldn't be an employee's home office or personal address. | String | 2N |
| Microsoft_CompanyPostOfficeBox | This is the publicly available company office box number. | String | PO Box 12 |
| Microsoft_CompanyOfficeStreet | This is the publicly available company office street address. | String | NE 12th Street |
| Microsoft_CompanyOfficeCity | This is the publicly available office address city. | String | Redmond |
| Microsoft_CompanyOfficeState | This is the publicly available company office state. | String | Washington |
| Microsoft_CompanyOfficeCountryOrRegion | This is the publicly available company office country or region. It's a free-format string value, for example, "United States". | String | United States |
| Microsoft_CompanyOfficePostalCode | The publicly available company office postal code. | String | 98004 |
| Microsoft_Company | The company name. | String | Contoso |
| Microsoft_CompanyCode | The legal entity number of the company or its subdivision. | String | A2518 |
| Microsoft_EmploymentType | Used to classify employees based on their employment type. | String | Regular |
| Microsoft_HireDate | The date an employee began employment. If an employee has multiple hire dates, it's best to use the most recent hire date. Viva Glint uses Hire Date to derive Tenure groups. | DateTime | 12/31/2021 |
| Microsoft_EmployeeID | A unique identifier assigned to each employee. | String | E123456 |
| Microsoft_CostCenter | The financial cost center to which the employee is assigned. | String | CC-7890 |
| Microsoft_Division | The division or business unit the employee belongs to. | String | Human Resources |
| Microsoft_Phone | The employee's work phone number. | String | 123-456 |
The following Organizational data attributes aren't currently imported into Viva Glint:
Microsoft_SecondaryJobTitleMicrosoft_HourlyRateMicrosoft_WeeklyBadgeOnsiteDaysMicrosoft_UserSkillNamesMicrosoft_EmploymentStatusMicrosoft_DotLineManagersEmailAndLabelMicrosoft_AssistantsEmail
Note
Microsoft_GlintEmploymentStatus corresponds to the Viva Glint Status attribute and only accepts ACTIVE or INACTIVE values.
Custom attributes
Custom attributes are Organizational data attributes that are unique to your organization's employee data and aren't predefined as reserved attributes in Microsoft 365 Organizational Data Service.
Custom attributes don't automatically become available to every app or service. During connector setup, the Organizational data source admin chooses which custom attributes are shared with each supported app or service.
Viva Glint imports custom Organizational data attributes only when a corresponding Viva Glint attribute already exists and the custom Organizational data attribute is shared with Viva Glint. The custom Organizational data attribute name must exactly match the Viva Glint attribute name, including letter casing.
Important
Custom attribute mapping is case sensitive.
Note
If Viva Glint receives a custom Organizational data attribute that doesn't match an existing Viva Glint attribute, the attribute is ignored and an advisory message is included in the error messages provided after the upload completes. To import a new custom attribute into Viva Glint, first create the corresponding attribute in Viva Glint.
Customer onboarding to Microsoft 365 Organizational Data Service
Customers who already have employee data in Viva Glint People must complete a one-time mapping exercise before Viva Glint can import employee data from Microsoft 365 Organizational Data Service. After the one-time mapping is complete, the Viva Glint attribute update flow (People > Import > New User Schema or Attribute Updates) includes a Configure Organizational data step that you can use to add or update mappings between Viva Glint attributes and reserved attributes. New customers are automatically onboarded to Microsoft 365 Organizational Data Service during the first-time attribute setup flow.
Step 1: An onboarding banner will appear in the People page. Select View more to open the wizard.
Note
Organizational data in Microsoft 365 is being released in phases. If you don't see the onboarding banner, the feature isn't available yet in your tenant.
Step 2: Review Onboarding readiness requirements.
Review these key onboarding readiness information and related documentation articles to understand what is Microsoft 365 Organizational Data Service. When ready, select Get Started.
- Import employee data from Microsoft 365 Organizational Data Service
- Microsoft 365 Organizational Data Service
- Microsoft 365 Organizational Data Service - Attribute reference
- Import and manage your organizational data with a .csv file
- Import and manage your organizational data with a .csv file (existing link; keep the current URL)
Step 3a: Map Organizational data attributes to Viva Glint attributes
This setup flow enables existing Viva Glint attributes to be linked to Organizational data attributes from Microsoft 365 Organizational Data Service.
Required Viva Glint attributes are automatically mapped to corresponding reserved Organizational data attributes and can't be modified. Additional mappings, including Manager ID, Hire Date, custom attributes, and hierarchy groups can be added, removed, or updated at any time.
Attribute mappings determine which Viva Glint attributes receive values from Organizational data attributes. Mapping attributes that contain the same employee data ensures a consistent attribute structure across import methods, including Microsoft 365 Organizational Data Service, SFTP imports, and People page imports. This helps prevent duplicate attributes from being created in Viva Glint.
The required Viva Glint attributes are automatically mapped to corresponding reserved Organizational data attributes. These mappings are visible during onboarding but can't be changed or removed. Required Viva Glint attributes include First Name, Last Name, Email, Employee ID, and Status.
Additional Viva Glint attributes can be mapped to reserved Organizational data attributes. This step is optional.
Reserved Organizational data attributes have predefined meanings that can be understood across Microsoft experiences and services. Mapping a Viva Glint attribute to a reserved Organizational data attribute allows employee data associated with that reserved Organizational data attribute to be imported into the selected Viva Glint attribute.
For example, if your Organizational data import includes the reserved attribute Microsoft_SupervisorIndicator, you can map it to a Viva Glint attribute named People Manager. After the mapping is configured, Viva Glint imports the Microsoft_SupervisorIndicator values into the People Manager attribute. If no mapping is configured, the Microsoft_SupervisorIndicator attribute isn't imported into Viva Glint.
Attributes that aren't explicitly mapped to reserved Organizational data attributes continue to support custom attribute imports. When Viva Glint receives a custom Organizational data attribute, Viva Glint looks for an existing attribute with the same name. If an exact name match exists, including letter casing, the attribute and its values are imported. If no matching Viva Glint attribute exists, the custom Organizational data attribute isn't imported.
For example, if Organizational data includes a custom attribute named Supervisor Indicator and Viva Glint already contains a custom attribute named Supervisor Indicator, the attribute and its values are imported automatically. If Viva Glint doesn't contain a matching Supervisor Indicator attribute, the data isn't imported.
Note
If you want to keep the Viva Glint Manager Hierarchy distinct from the Profile or Entra Manager Hierarchy then don’t map Microsoft_ManagerID to Viva Glint’s attribute used for Manager hierarchy derivation.
Step 3b: Rename attributes that don't adhere to naming requirements
This step appears only when existing Viva Glint attribute names don't meet the naming requirements used by Viva Glint and Microsoft 365 Organizational Data Service.
Before onboarding can continue, Viva Glint validates existing attribute names against the naming requirements used by both Viva Glint and Microsoft 365 Organizational Data Service. Any attributes that don't meet these requirements must be renamed.
Important
If you rename an attribute during onboarding, update any employee data files or import processes that reference the previous attribute name. Future imports must use the renamed attribute.
Step 4: Review your changes and save
Review the summary of changes, including reserved Organizational data attribute mappings and any attribute renames, and then select Save changes.
After the onboarding process is completed, Viva Glint is configured to import employee data from Microsoft 365 Organizational Data Service. The Organizational data imports setting is automatically set to Yes.
Managing imports from Microsoft 365 Organizational Data Service
Enable and disable imports from Microsoft 365 Organizational Data Service
Completing onboarding automatically enables imports from Microsoft 365 Organizational Data Service in Viva Glint.
You can enable or disable imports from Microsoft 365 Organizational Data Service at any time from General settings > Technical configuration. When imports are disabled, Viva Glint stops importing employee data from Microsoft 365 Organizational Data Service, and uploads return the ORG_UPLOAD_SWITCHED_OFF advisory. If onboarding hasn't been completed, the Organizational data imports setting remains set to No. You can also configure email notifications for imports from Microsoft 365 Organizational Data Service. Up to 10 Viva Glint admins can receive these notifications.
If onboarding hasn't been completed, the Organizational data imports setting remains set to No.
Note
This toggle must be Yes for Viva Glint to appear as an optional end point for your connection in the Microsoft Admin Center at Setup > Migration and imports > Organizational data in Microsoft 365.
Remove an Microsoft 365 Organizational Data Service attribute mapping from a Viva Glint attribute
You can remove a Viva Glint attribute’s mapping to an Organizational data reserved attribute at any time from People > Actions > Manage User Attributes. After the mapping is removed, Viva Glint no longer updates that attribute from Organizational data reserved attributes. The unmapped Viva Glint attribute remains a custom attribute in Viva Glint and continues to be updated from Organizational data custom attributes when the attribute name matches with the Viva Glint attribute name.
Steps to remove the Organizational Data mappings
In the People > Actions > Manage User Attributes page, select on Manage mapping for organizational data.
On the Manage Organizational Data mapping page, remove the reserved attribute tags under Viva Glint attribute names and select Save.
In the review screen, review the set of attributes for which the reserved attribute mappings will be removed and select “Remove attribute mappings”.
Add an Organizational data attribute mapping
You can create or update Organizational data attribute mappings at any time from Settings > People > Actions > Manage User Attributes.
Follow the same mapping process described in the onboarding flow to map Viva Glint attributes to reserved Organizational data attributes.
Monitoring Microsoft 365 Organizational Data Service in Viva Glint
All Organizational data imports are audited to support easier review, troubleshooting and data reconciliation. Each audit event includes key import details, such as the original file Viva Glint received from Organizational data in Microsoft 365, any advisories generated for that file, and a processed file with an ingestion summary showing rows ingested, ignored, and skipped.