Settings and activity
13 results found
-
4 votes
An error occurred while saving the comment An error occurred while saving the comment 
Eric Mesa
commented
We would like the ability to pull the Department attribute from Azure AD into Atera users' properties. We would like to use this for more granular reporting, but not seeing where this is set or if it is possible. The Attribute is coming over because it is mapping the user to a specific Site, but we would like to use the Department field to actually populate the Department in Atera user attributes also. Azure AD Department to Atera User Department field.
Eric Mesa
supported this idea
·
-
8 votesEric Mesa
supported this idea
·
-
217 votesEric Mesa
supported this idea
·
-
803 votesEric Mesa
supported this idea
·
-
871 votesEric Mesa
supported this idea
·
-
1,618 votes
Congratulations on helping shape Atera! The feature you requested is currently being considered for development. Please be patient as the process can take a while or even stall to make way for other features. We’ll update you once it’s been implemented and released!
Eric Mesa
supported this idea
·
-
973 votesEric Mesa
supported this idea
·
-
1,489 votesEric Mesa
supported this idea
·
-
81 votesEric Mesa
supported this idea
·
-
5 votesEric Mesa
supported this idea
·
-
6 votesEric Mesa
supported this idea
·
-
3 votesEric Mesa
supported this idea
·
-
12 votesEric Mesa
supported this idea
·
Atera’s Azure AD sync currently reads the Department attribute from Azure Active Directory for the purposes of site assignment, but it does not populate the Department field within the Atera user profile. We are requesting an enhancement that ensures the Department value pulled during Azure AD synchronization is also written to the Department field in Atera’s user properties.
Business Need / Problem Statement:
Our organization leverages the Department attribute extensively within Azure AD for identity management, reporting, and operational workflows. When users are synced into Atera, we expect this attribute to remain consistent across systems.
Currently, Atera is clearly consuming the Department attribute during sync—since it is used to place users into the appropriate Site—but the value is not displayed or stored in the Atera User Properties > Department field. This results in:
Incomplete user metadata inside Atera
Additional manual effort to maintain accurate department assignments
Loss of visibility for technicians who rely on role/department context when supporting users
Inconsistent data across platforms, reducing efficiency and accuracy in support processes
Requested Enhancement:
We request that Atera expands its Azure AD integration so that the Department attribute retrieved during sync is automatically populated into the Department field within Atera user profiles. Or at least given the option to select what attributes we want to sync and populate in Atera.
Expected Impact / Benefits:
Eliminates manual updates
Improves data consistency between Azure AD and Atera
Enhances technician visibility into user role/department
Strengthens automation, reporting, and ticket routing opportunities
Provides a more complete and accurate user directory within Atera
Conclusion:
This enhancement leverages data Atera is already retrieving and would materially improve accuracy and efficiency for Atera customers who utilize Azure AD–based identity synchronization. We appreciate your consideration and believe this update aligns with Atera’s goal of improving automation and simplifying IT operations.