Menu
Region
Ready to get started? Contact us.

Aurion validation

Validate Aurion lifecycle workflows before production rollout.

A successful UNIFYConnect/Aurion implementation needs prepared test environments, representative Aurion data, agreed acceptance scenarios, and production validation before go-live.

Review solution scope Read FAQs
Prepare confirm Aurion and identity test environments
Validate test onboarding, updates, and offboarding scenarios
Promote complete production checks before go-live
UNIFYConnect Home UNIFYConnect automates identity lifecycle management between authoritative sources, Microsoft Entra ID, Active Directory, applications, and downstream …

Explore UNIFYConnect Aurion

UNIFYConnect Aurion UNIFYConnect can use Aurion People & Payroll as an authoritative source for automated onboarding, offboarding, account updates, and manager … FAQ Frequently asked questions about UNIFYConnect and Aurion integration. Solution UNIFYConnect provides automated identity lifecycle management for organisations using Aurion People & Payroll as an authoritative HR source. Testing Guidance on testing a UNIFYConnect/Aurion implementation before production rollout.
Testing objective

Testing should prove the workflow before production data starts moving.

Customers need access to a suitable Aurion test environment for integration and functional testing.
A dedicated UAT environment with Aurion and Microsoft Entra ID or Active Directory helps validate expected outcomes and identify remediation before production.
Employee onboarding
Add a new employee in Aurion and confirm the expected account, attributes, and access outcomes.
Employee updates
Change name, phone, title, position, or manager details and verify target identities are updated correctly.
Employee offboarding
Terminate an employee in Aurion and confirm account disablement and access removal at the right time.
Development testing

Start by confirming connectivity and data-readiness.

Integration testing confirms the required components can connect. A data load test then analyses expected changes, highlights data inconsistencies, and helps confirm whether the UAT system is ready for acceptance testing.
  1. Integration test Confirm Aurion, UNIFYConnect, and target-system connectivity after infrastructure setup.
  2. Data load test Run a controlled data load to identify expected changes and flag data issues.
  3. UAT readiness Confirm remediation actions before asking HR and IT teams to perform acceptance scenarios.
Acceptance testing

HR and IT teams should validate the lifecycle scenarios they will rely on.

Acceptance testing should cover new starters, existing employee changes, manager relationship changes, and terminated employees. The goal is to prove both identity outcomes and the operational evidence needed for production approval.
Expected account state Confirm accounts are created, updated, disabled, or left unchanged according to the agreed rule set.
Data integrity Confirm names, titles, contact details, manager relationships, and other mapped attributes are correct.
Access outcomes Confirm group memberships, access removal, and downstream controls behave as expected.
Production validation

Final checks should happen before the go-live schedule is confirmed.

Before production activation, UNIFY confirms required components are connected and performs a final data load test to validate expected changes. Any remaining data issues should be corrected before go-live.
Production connectivity Confirm all production components are reachable and configured as expected.
Final data load Validate expected system changes and flag remaining data corrections.
Go-live coordination Coordinate timing and acceptance once testing evidence is complete.