ManageEngine identity products: selection, implementation and support
Several ManageEngine products address identity, but they do not do the same job. An administrator trying to standardise account changes has a different requirement from a security team investigating a privileged action. Choosing well begins by separating those responsibilities.
Fristine helps assess identity product implementation against your directory environment, business applications and operating model. Use the distinctions below to prepare a requirements discussion, then validate the exact edition, supported integration and delivery scope before committing to a rollout.
ADManager Plus: account administration and delegated work
ADManager Plus addresses Active Directory and Microsoft 365 administration and reporting. In an implementation workshop, focus on account templates, delegated tasks and approval ownership. The useful test is whether the right operator can perform an approved action without receiving broader permissions than the job requires.
Choose the identity job first
ADAudit Plus: evidence of changes and activity
ADAudit Plus addresses change auditing and related activity visibility across supported identity and file environments. Begin with the events your reviewers need to investigate. Agree collection coverage, timestamps, report access and alert ownership. An audit trail is only useful when the team can interpret its scope and recognise missing evidence.
ADSelfService Plus: recovery and authentication experience
ADSelfService Plus addresses password self service, MFA and SSO requirements. Design enrolment and recovery alongside the normal sign in journey. Include a user who loses a device, an account that cannot complete enrolment and an application with different authentication requirements. These cases determine whether the support process is usable.
Exchange Reporter Plus: messaging visibility
Exchange Reporter Plus focuses on reporting, auditing and monitoring for supported Exchange environments. Identify the questions the messaging team needs answered and the permissions needed to obtain the evidence. Confirm current platform compatibility before a migration or coexistence project; an Exchange related product name does not establish support for every environment.
Identity360: workforce identity in a cloud platform
Identity360 is a cloud based workforce IAM platform. Evaluate directory sources, application access and lifecycle responsibilities together. Decide which source owns an identity and what happens when attributes conflict. Validate the integration and region requirements for the proposed design rather than assuming cloud deployment removes those decisions.
M365 Manager Plus: Microsoft 365 administration and reporting
M365 Manager Plus addresses management, auditing and reporting across supported Microsoft 365 services. Define tenant access, administrator roles and reporting needs before authorising connections. Test the scope of a delegated operator and confirm which required data is available under the selected product and Microsoft licensing arrangements.
Identity Access: a separate access management evaluation
ManageEngine also lists Identity Access for cloud based access management requirements, including MFA and SSO. Treat it as a distinct product evaluation. Compare the required login surfaces and policies with Identity360, ADSelfService Plus and existing access tools before deciding whether it adds useful capability or duplicates an established control.
Choose a combination by responsibility
Create a simple selection record: the problem, the responsible team, the required action or report, the candidate product and any overlap. This makes the reason for each product visible. It also prevents a broad identity programme from becoming a bundle of tools with unclear ownership.
Start configuration with a small representative group. Test permitted actions, denied actions, partial failures and recovery. Record what the pilot established and what remains outside scope. Expansion should depend on that evidence and the ability of the team to operate the result.
Scope implementation separately from licences
The proposal should identify installation or tenant setup, permissions, templates, workflows, integrations, training and handover. Include upgrade and support responsibilities if required. Do not assume every product shares the same deployment model, commercial unit or maintenance process.
Bring your current directories and identity tools, the tasks that consume administrator time and the evidence your reviewers need. We can use that information to narrow the product assessment without starting with seven separate deployments.
Frequently asked questions
001Do we need every product listed on this page?
No. The page separates product roles so you can avoid buying overlapping tools without a clear reason. Start with the required administration, authentication or audit outcome. Compare existing capabilities and validate editions. A suitable scope may involve one product, a selected combination or changes to tools you already operate.
002What is the difference between ADManager Plus and ADAudit Plus?
The principal distinction for evaluation is administration versus audit visibility. ADManager Plus addresses account management work, while ADAudit Plus focuses on evidence of changes and activity in supported environments. Your requirements may involve both, but define the operator actions and reviewer questions separately before assuming either product satisfies the other's purpose.
003Can ADSelfService Plus replace every authentication control?
That cannot be assumed. Review supported applications, devices, authentication methods and recovery requirements against the current edition. Existing identity providers or access policies may remain necessary. Test the intended login and recovery journeys, including exceptions, before changing production authentication for a broad group of employees or contractors.
004How should Identity360 and Identity Access be compared?
Begin with the identity and access responsibilities you need to cover, then compare the current products against that list. Confirm directory sources, application support, lifecycle needs and policy requirements. Their names alone do not establish equivalent scope. A product specific evaluation should document both useful coverage and any gaps or overlap.
005Can these tools work with more than one tenant or directory?
Multi environment requirements need validation for each product, edition and licensing model. Provide the number of tenants or directories, the relationship between them and the required separation of administration. Test cross environment visibility and permissions explicitly. Do not infer supported scale or isolation from a successful single environment demonstration.
006What should an identity product pilot demonstrate?
It should show the required action or report using representative accounts and permissions, including a denied action and a failure scenario. For authentication, include enrolment and recovery. For auditing, check evidence completeness and interpretation. The pilot should leave a clear record of validated behaviour and unresolved dependencies before wider deployment.
007Are implementation and vendor support the same service?
No. Implementation concerns your configuration, workflows, integrations and handover. Vendor support addresses the product under its applicable support terms. An ongoing service may help coordinate both, but responsibilities and escalation should be explicit. Confirm who owns upgrades, configuration changes, access administration and operational incidents after the initial project ends.
008Can we obtain a fixed price immediately?
A useful price requires product scope, environment counts, integrations, migration needs and acceptance expectations. Begin with broad information and a representative use case. The quotation should separate software, implementation and any ongoing service. Publishing a generic price before understanding those dependencies would make unlike requirements appear directly comparable.
Review your delivery requirements
Discuss access, information handling and operational responsibilities as part of the proposed scope.
Explore related services
ManageEngine Implementation Services India · ManageEngine Identity & Access Services
Discuss this implementation