Customer access review remediation: what to inventory before an identity tenant merger

Short answer

Before an identity tenant merger, inventory customer access review remediation as record classes with clocks: review decisions and justifications, directory audit events, GRC findings, change tickets and owner assignments. For each, note which system holds it, how far back it reaches today, who owns it and the date admin access to the source tenant ends. Some identity logs reach back weeks, not years. Record only metadata, then introduce the security operations head and the executive who can authorize a licensing discussion.

Visual briefFull-size diagram
Lookback bars measured back from today against three quarterly review cycles: Entra audit logs reach back 30 days, Okta System Log queries 90 days, while GRC findings, change tickets and HR records reach back as far as company policy keeps them.
Illustrative: the identity logs that prove a removal reach back weeks, while the review cycles they evidence run quarterly. Retention periods are the vendors' published defaults.

"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 classTypical homeClock to checkMetadata to note
Review decisions and justificationsIdentity provider review campaigns (Microsoft Entra access reviews, Okta Identity Governance)Entra review history reports stay downloadable for 30 days after each report is createdDate range, number of review cycles, whether reports were saved
Directory audit events (owner changes, role removals)Identity provider audit logEntra audit logs: 30 days on P1 or P2; Okta System Log: 90 daysWhether logs stream to a SIEM or storage, and since when
Findings and remediation statusGRC toolThe company's own tool settings and contractFinding count, years covered, status values used
Change tickets for each removalTicketing system such as Jira or ServiceNowThe company's retention policyWhether findings cite ticket keys
Owner assignments and departuresHR systemThe company's retention policyWhether 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 stepWho answers
Week 1List review campaigns in the source tenant, with first and last cycle datesIdentity administrator
Week 2Confirm whether audit logs stream to storage or a SIEM, and the earliest date held thereSecurity operations head
Week 3Note whether review history reports were saved in past cycles, or must be generated now within their 30-day download windowIdentity administrator
Week 4Count GRC findings by year and check whether they cite ticket keysGRC owner
Week 5Confirm HR leaver dates can be matched to account and service account ownersHR systems lead
Week 6Record the contract and subscription end dates for the source tenantIT procurement
Week 8Source tenant admin access endsMerger 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

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.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Is a customer access review the same as an auditor's management letter point?

No. An access review is the company's own control: it decides who keeps access and records why. A management letter point is raised by an outside auditor. The company's review decisions, responses and tickets are its own records; auditor workpapers are not.

Should I tell the client to keep its identity logs longer so they can be licensed?

No. Retention is the company's decision under its own policies, contracts and privacy obligations. A partner can point out that some exports expire on a short clock and leave the decision to the people with authority.

What if the source tenant is already read-only?

Then the inventory still helps: note what can still be reported on, what was streamed to storage or a SIEM before the change, and what only survives in the GRC tool and tickets. Gaps are recorded as unknowns, not reconstructed from memory.

Sources

  1. refer.sourcex.si/terms
  2. learn.microsoft.com/en-us/entra/id-governance/access-reviews-dow…
  3. learn.microsoft.com/en-us/entra/identity/monitoring-health/refer…
  4. developer.okta.com/docs/reference/system-log-query

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment