Appearance
Interview Lookback reviews the interviews your team has already held in Microsoft Teams and flags candidates who show signs of fraud - proxies, masked networks, injected video, and different operators behind the same name. It runs on data already in your Microsoft 365 tenant, so you see results from your own hiring pipeline within a week, without changing how your recruiters work.
Interview Lookback is a light, partial evaluation of imper.ai for Hiring. It shows what was already happening in your interviews, using only the data Microsoft records about each call. A full deployment embeds imper.ai in your interview flow, where it runs a much wider suite of checks on every candidate.
At a Glance
| Integration | Microsoft 365 only (Calendar and Teams), read-only |
| Setup time | About 15 minutes - one admin consent |
| Results | A findings report and walk-through within one week |
| Lookback | Interviews from the last 30 days |
| Workflow change | None - nothing is installed, and recruiters and candidates do nothing differently |
How It Works
Find the interviews. Interview Lookback reads your recruiters' calendars and keeps the events that are interviews: not cancelled, with an external attendee, and with a Teams meeting link. An interview that appears on several recruiters' calendars is counted once.
Check how each candidate joined. For each interview, Interview Lookback reads the Teams call record of the meeting and examines every session the candidate opened: the network they connected from, and the device and software they used.
Correlate. Interview Lookback compares the same candidate across interview rounds, and different candidates against each other. A candidate whose location or device changes between rounds, or several candidates sharing the same infrastructure, points to handoffs and organized fraud rings.
What Interview Lookback Looks For
Masked networks - VPNs, residential proxies, and datacenter or tunneling IP addresses
Inconsistency between rounds - a candidate whose location, network, or device changes from one interview to the next
Video and remote-control tools - virtual cameras, phone-as-webcam software, remote desktop tools, and virtual display adapters on a machine with no monitor attached
Shared infrastructure - the same network or device behind different candidates
Required Permissions
Interview Lookback uses an Entra application with these Microsoft Graph application permissions. All of them are read-only.
| Permission | Used for |
|---|---|
Calendars.Read | Reading your recruiters' calendars to find interviews with external candidates and their Teams meeting links |
CallRecords.Read.All | Reading the Teams call record of each interview: when each participant joined, their network, and their device |
User.ReadBasic.All | Identifying your recruiters and interviewers, so they are told apart from candidates |
Organization.Read.All | Reading your tenant's verified domains, so that colleagues on any of your domains are never treated as external candidates |
Group.Read.All | Reading the membership of your recruiting team's group, so Interview Lookback knows which recruiters' calendars to scan |
Interview Lookback cannot send, change, or delete anything in your tenant.
NOTE
Microsoft keeps Teams call records for 30 days, and offers no way to retrieve older ones. Interview Lookback therefore covers interviews from the last 30 days.
Setting Up Interview Lookback
Choose one of two ways to grant the permissions. Both require a Global Administrator or Privileged Role Administrator in your Microsoft Entra tenant, since Microsoft reserves admin consent for Graph application permissions to these roles.
Option 1 - One-click consent (recommended)
imper.ai sends you an admin consent link.
Open the link and sign in with an administrator account.
Review the permissions listed above, and click Accept.
That is the whole setup - about 15 minutes, including review.
Option 2 - PowerShell, for more control
If your organization prefers to grant permissions manually, imper.ai provides a PowerShell script that grants the same permissions and can limit calendar access to your recruiters' mailboxes. Contact support@imper.ai to receive it.
NOTE
CallRecords.Read.All applies to the whole tenant - Microsoft does not support scoping it to a group. Interview Lookback only reads the call records of meetings it found on your recruiters' calendars.
Timeline
| When | What happens | Who |
|---|---|---|
| Day 1 | Grant consent (about 15 minutes) | Your Microsoft 365 administrator |
| Within one week | imper.ai scans your past interviews and prepares the findings report | imper.ai |
| End of week 1 | A walk-through of the findings: a ranked list of risky candidates, each with the evidence behind it | imper.ai with your HR, Talent Acquisition, and security teams |
What a Full Deployment Adds
Interview Lookback is limited to what Microsoft already records about each call. When imper.ai is embedded in your interview flow, a full deployment of imper.ai for Hiring runs a wider suite of checks:
Far deeper signals - imper.ai's verification flow collects device, browser, and network evidence that is not in a Teams call record. Some candidates hide their network from Teams entirely by joining through a browser, which Interview Lookback cannot see past.
Identity, not just connection data - imper.ai confirms that the person is the candidate they claim to be, rather than only flagging suspicious behavior.
Your recruiting platform's context - connecting your ATS (such as Workday, Greenhouse, or Ashby) lets imper.ai compare where a candidate actually is with where they say they are, and link candidates across applications.
Every interview, continuously - no 30-day window and no one-off report: each interview is covered as it happens, with results on the Hiring Dashboard and the Candidates page.
To move from Interview Lookback to a full deployment, see the Quickstart or contact support@imper.ai.
Related
Quickstart - moving to a full deployment