We added a new feature to Addigy Identity: User Attributes. User Attributes provide another powerful way to manage devices using a user-centric approach that can reduce a lot of admin time and simplify workflows. Once an end-user signs into their identity provider account (Azure and Google are the first Identity Providers to support this feature), data returned from the provider is available within Addigy as device facts. Data such as Employee Department, Hire Date, Employee Type, etc., are very useful for automating Addigy in response to changes in your organization.
Links To Enable Collection of User Attributes:
What data does Addigy Identity fetch when the "Collect User Attributes" setting is turned on?
- Identity Email
- Identity Employee Department
- Identity Employee Hire Date
- Identity Employee Type
- Identity Mobile Phone
- Identity Provider Name
- Identity User Display Name
- Identity Username
- Identity Office Location *New*
- Identity Usage Location *New*
- Identity Password Set Date *New*
The following table lists the Addigy Identity attribute mappings and the corresponding cloud identity provider attributes:
|
Addigy Attribute Name |
Attribute Mapping Value |
Attribute Meaning |
Identity Providers That Collect Which Attributes |
|
Identity Email |
|
Email address for the user; for example: ["j@companyname.com"] NOTE: This property cannot contain accent characters. |
Azure and Google |
|
Identity Employee Department |
department |
The name of the department in which the user works. |
Azure and Google |
|
Identity Employee Hire Date |
employeeHireDate |
The date and time when the user was hired or will start work in case of a future hire. |
Azure and Google |
|
Identity Employee Type |
employeeType |
Captures enterprise worker type. For example, Employee, Contractor, Consultant, or Vendor. |
Azure and Google |
|
Identity Mobile Phone |
mobilePhone |
The primary cellular telephone number for the user. |
Azure and Google |
|
Identity Provider Name |
azure or google |
The name of the Identity Provider. |
Azure and Google |
|
Identity User Display Name |
displayName |
The name is displayed in the directory for the user. This is usually the combination of the user's first and middle initial and last names. This property is required when a user is created and cannot be cleared during updates. |
Azure and Google |
|
Identity Username |
userPrincipalName |
The UPN is an Internet-style login name for the user based on the Internet standard RFC 822. By convention, this should map to the user's email name. The general format is alias@domain, where the domain must be present in the tenant's collection of verified domains. This property is required when a user is created. |
Azure and Google |
|
Identity Office Location |
usageLocation
|
A two letter country code (ISO standard 3166). Examples include: US, JP, and GB.
|
Azure only |
|
Identity Usage Location |
officeLocation |
The office location in the user's place of business. |
Azure only |
|
Identity Password Set Date |
lastPasswordChangeDateTime |
The time when this Azure AD user last changed their password or when their password was created, whichever date the latest action was performed. |
Azure only |
FAQs
How often does this data refresh?
Answer: After the end-user successfully signs in each time.
Why does this feature only work with Azure and Google?
Answer: We are working on Okta to support user attributes in the future. Since Azure and Google currently support the feature, we wanted to allow Addigy Users that use either of these Identity Providers to have the ability to use it as we work on increasing feature capabilities.
What should I do with these attributes now?
Answer: We highly recommend utilizing these User Attribute device facts to filter devices using flex policies automatically.
Does this new feature cost extra?
Answer: Nope, this feature does not come with an additional cost.
Where do I go to see these populated fields?
Answer: There are multiple ways to see this data. One way is by going to the devices page > Click on Columns > Search for "Identity." Then select the attributes you would like to see.
I don't have this feature enabled. Does Addigy still collect the user data?
Answer: No, user information is only collected if the "Collect User Attributes" setting is enabled.
Why do some of my device facts show N/A?
Answer: It could mean the end-user still needs to sign in successfully or that the field in the Identity Provider directory is blank. It could also mean the feature is not enabled or configured properly.
How do I make a feature request for User Attributes?
Answer: Go to support.addigy.com to visit the Community Feedback section and create a new post. For more information, here are the Guidelines for Creating Feedback Posts.