This article defines how Office 365 fields are mapped to IT Glue fields. Learn more about integrating with Office 365 in our Office 365 Integration article.
A summary of the sync behaviour:
- Tenants —> IT Glue Organizations
- Users —> IT Glue Contacts
Organizations
| IT Glue: Organizations |
Office 365: Tenants |
| Name |
Tenant Name |
| Location Name (use organization name) |
Tenant Name |
| Address |
Address |
| State/Province |
State/Province |
| City |
City |
| Postal / Zip Code |
Postal / Zip Code |
| Location Phone |
Phone |
Contacts
| IT Glue: Contacts |
Office 365: Users |
| Name |
First Name + Last Name |
| Title |
Job Title |
| Office Phone |
Phone |
| Mobile Phone |
Mobile |
| Primary Email |
User Name |
| Mailbox Aliases |
Alias |
Matching logic
Standard matching rules are used to match records within IT Glue when pulling data from Office 365. The sync will discover Tenants and Contacts in Office 365 and match them to data in IT Glue using the Office 365 fields shown in the table below:
| IT Glue: Asset |
IT Glue Field |
Office 365 Field |
| Organizations |
Name |
Tenant Name |
| Contacts |
Email |
- Attempt match on any alias of the Microsoft user.
- Attempt match on the username value (e.g. the @onmicrosoft.com domain).
- Attempt match on combination of First Name + Last Name.
|
Location
Location information is a one-time push into IT Glue and does not sync. If the location is updated in Office 365, then IT Glue creates another location for the Organization.
The matching logic for the initial sync of locations is that Address 1, City, State/Province, and Country all must match between the Office 365 tenant and a location within IT Glue. If there is a match, there will be no location created in IT Glue, but the existing location will be updated.
After the initial sync, any updates to the location of the Office 365 tenant will result in another location created in IT Glue. If Address 1, City, State/Province, and Country do not match, then a new location is created.