"Customer access review" here means the periodic review of which employees, contractors and service accounts can reach customer environments or customer data, plus the remediation of whatever that review flags. Many SaaS and services companies run it because customers ask for it. The remediation trail is the part worth preserving: it records a judgment, an action and a checked result, and a tenant merger is one of the few events that can quietly erase it.
What should be inventoried before an identity tenant merger affects customer access review remediation history?
Inventory record classes, time coverage, the owning system and the real access deadline for each class. The deadline that matters is the day admin access to the source tenant ends, which is often earlier than the project's go-live date.
Tenant consolidations are usually scoped around moving users, groups and app assignments. Review decisions, their justifications and the audit events that prove a removal happened are easy to leave behind, and several of them sit on short retention clocks by default.
| Record class | Typical home | Clock to check | Metadata to note |
|---|---|---|---|
| Review decisions and justifications | Identity provider review campaigns (Microsoft Entra access reviews, Okta Identity Governance) | Entra review history reports stay downloadable for 30 days after each report is created | Date range, number of review cycles, whether reports were saved |
| Directory audit events (owner changes, role removals) | Identity provider audit log | Entra audit logs: 30 days on P1 or P2; Okta System Log: 90 days | Whether logs stream to a SIEM or storage, and since when |
| Findings and remediation status | GRC tool | The company's own tool settings and contract | Finding count, years covered, status values used |
| Change tickets for each removal | Ticketing system such as Jira or ServiceNow | The company's retention policy | Whether findings cite ticket keys |
| Owner assignments and departures | HR system | The company's retention policy | Whether leaver dates can be matched to account owners |
Two points keep this inventory on the right side of the line. First, ask what exists and when it disappears; do not recommend that anyone keep data longer than their policies, contracts and privacy obligations allow. Second, the company's security and legal owners decide what is preserved. The wind-down preservation brief and the post-merger data migration guide cover the general pattern; the admin access guide covers what to do when nobody can still sign in to the old tenant.
Why do quarterly reviews outlive the logs that prove them?
Because the cadences do not match. Many companies review customer-facing access quarterly, but Microsoft Entra keeps audit logs for 30 days on P1 and P2 (7 days on Free), and Okta does not return System Log data older than 90 days to queries. By the time the next review asks whether last quarter's removals actually happened, the identity provider may no longer hold the events, unless they were routed to storage or a SIEM. Microsoft states that expired audit data cannot be recovered if it was not archived first.
That is why the inventory asks a second question for every identity source: was it exported or streamed, since when, and where does that copy live now? A merger adds a third: will that copy stay readable once the source tenant's subscriptions and admin roles are retired? The GRC tool and change tickets usually hold years, but they only record that someone said a removal was done. The audit event is the independent check, and it is the record most likely to be missing.
How should the inventory be sequenced against the merger plan?
Work backwards from the date admin access to the source tenant ends, not from go-live. The plan below is Illustrative: a fictional mid-size SaaS company with quarterly reviews and an eight-week consolidation.
| Week (Illustrative) | Inventory step | Who answers |
|---|---|---|
| Week 1 | List review campaigns in the source tenant, with first and last cycle dates | Identity administrator |
| Week 2 | Confirm whether audit logs stream to storage or a SIEM, and the earliest date held there | Security operations head |
| Week 3 | Note whether review history reports were saved in past cycles, or must be generated now within their 30-day download window | Identity administrator |
| Week 4 | Count GRC findings by year and check whether they cite ticket keys | GRC owner |
| Week 5 | Confirm HR leaver dates can be matched to account and service account owners | HR systems lead |
| Week 6 | Record the contract and subscription end dates for the source tenant | IT procurement |
| Week 8 | Source tenant admin access ends | Merger program lead |
Each answer is a count, a date range or a yes or no. Nothing in the plan requires a partner to see a review decision, a log line or a ticket. If an answer is "we do not know", that is recorded as an unknown for SourceX and the company to resolve later.
Does the company qualify, and what stays unknown?
The introduced company needs 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license the records, and an authorized contact who can discuss a license. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English.
Until SourceX reviews the opportunity with the company, nobody knows whether there is dataset demand for these records, what the rights review will conclude, what must be removed or de-identified, or what the company would be offered. The security operations head or identity administrator knows coverage; the company's counsel decides what customer contracts and privacy obligations allow; the CEO authorizes a licensing discussion, often with the CTO or general counsel advising. Customer names inside review records are one reason rights review comes first. SourceX licenses approved business data directly from companies for AI training and evaluation and manages the agreement, rights review, data preparation, delivery and payout; partners never handle the records. Partners sign the Channel Partner Agreement before submitting introductions, and the first valid introduction within the 90-day window is credited when the company submits a verified application. Whether a license needs board sign-off is covered in does licensing data require board approval; browse more sectors on the industries hub.
Go deeper on customer access review remediation
- Referral brief template for customer access review remediation: a fill-in brief for the note you send with the introduction.
- Customer access review remediation exception examples: worked cases showing which records explain how a flagged exception was handled.
- Customer access review remediation records across systems: a system map of the keys that join identity, GRC, ticketing and HR records.
- Who can license customer access review remediation records: a short answer on which decision-maker to introduce.
Next step
Refer a company. No cap on rewards. Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.
If the merger date is real and the inventory shows years of review history still reachable, register as a partner, check the company against who qualifies, and read the program terms and reward rules before you send the handoff.