Design around dependencies
Assess existing architecture, owners and critical integrations. Record sizing assumptions, prerequisites and acceptance criteria before product selection.
OpenText NetIQ Identity Manager supports provisioning and identity lifecycle management. We connect authoritative identity sources, application entitlements and approval workflows to reduce manual drift and improve evidence of access changes.

Architecture, implementation and an accountable operational handover.
Assess existing architecture, owners and critical integrations. Record sizing assumptions, prerequisites and acceptance criteria before product selection.
Pilot representative workloads, validate compatibility and stage production changes with agreed rollback criteria.
Deliver configuration records, test evidence and runbooks. Define support boundaries, escalation and lifecycle responsibilities.
Select the capabilities that meet your control objectives, application dependencies and operating model.
Define joiner, mover and leaver processes based on trusted sources and application ownership.
Validate connectors, entitlement mapping and reconciliation before automating account changes.
Establish approvals, exception handling and auditable records for lifecycle actions.
Technology supports a control programme; it does not establish compliance on its own. Validate policies, operating procedures and evidence alongside implementation.
Document account ownership, approved entitlements, approvals and verified removal or rotation.
Validate access evidence, exception handling and controlled emergency procedures.
Questions to resolve before committing to a platform or deployment scope.
Confirm authoritative sources, identity matching and entitlement owners. Resolve account exceptions and define reconciliation behavior before automation. Test joiner, mover and leaver cases, including failed connector operations and rollback, rather than validating only successful account creation.
We confirm the current product edition, supported versions, deployment options, integration prerequisites and license scope. Availability, subscription terms and required add-ons are checked for the proposed environment rather than inferred from portfolio branding.
Support and managed operations can be scoped around agreed assets, responsibilities, service windows and escalation arrangements. Monitoring, change authority and vendor escalation are documented in the service scope; they are not assumed to be included with a product license.
Regional delivery
IRIS Technology delivers OpenText (Micro Focus) architecture, implementation, migration and support scopes through established operations in Saudi Arabia and Jordan. Products, licensing and responsibilities are confirmed for each engagement.
Discuss architecture, delivery priorities, migration constraints and the operating model with our team.