Skip to content

Guest Sign-ins by Home Tenant

The question it answers: Which external organisations’ guests signed in during the last 7 days, how many of them, and to which apps?

Which partner organisations actually use the access you granted them in the last 7 days, how many of their people, and to which apps. Organisations with guests but no sign-ins are candidates for the Guest Lifecycle clean-up; the most active ones deserve a cross-tenant partner configuration.

Where in the appEntra ID › Sign-in Analytics › Guest Sign-ins by Tenant
WorkloadEntra ID
KindTable
DataBuilt from the tenant data IntensiveReports keeps in memory and refreshes in the background, so it opens at once.
LicenceMicrosoft Entra ID P1.
Report id (API and MCP)entra.sign-ins.guest-sign-ins-by-tenant
ColumnKeyType
OrganisationNameText
SettingsCategoryStatus
GuestsDistinctUsersText
Sign-insCountText
AppsDetailText
ResultFindingText
Last sign-inLastSeenDateTime
Tenant IDSecondaryText

Licence: Microsoft Entra ID P1.

Application permissions on the IntensiveReports app registration (all permissions):

PermissionAPIWhat it allowsNote
AuditLog.Read.AllMicrosoft GraphRead all audit log data
Policy.Read.AllMicrosoft GraphRead your organization’s policies
Data sources it reads
  • GET /beta/auditLogs/signIns (7 days; userType, homeTenantId)
  • GET /v1.0/policies/crossTenantAccessPolicy/partners (names)
GET /ir-api/v1/reports/entra.sign-ins.guest-sign-ins-by-tenant?size=100

An AI assistant reads it with the MCP tool get_report and the id entra.sign-ins.guest-sign-ins-by-tenant. The client needs the Read grant for Entra ID. See Using the API.