You can open Azure AD (now Microsoft Entra ID) reports if you hold at least the Reports Reader role and sign in to the Entra admin center. The main condition is the license: audit logs work on a free tenant, but sign-in logs need an Entra ID P1 or P2 license. The portal is only half the job, though. Once you can read the reports, the next question is how to get them to the people who need them without exporting a file by hand every week. We cover both below.
A quick naming note. Microsoft renamed Azure Active Directory to Microsoft Entra ID, so you will see both names in documentation, scripts and old internal wikis. They refer to the same service.
Table of Contents
- The scenario we will use
- What counts as an Azure AD report
- Which role and license you need
- How to open the reports in the admin center
- Other ways to reach the same data
- Retention: the limit that catches teams
- When access fails or the data looks wrong
- Getting the report to the auditor without the Monday export
- What PBRS does in this workflow
- Your existing tools are enough when
- Put the weekly report on a schedule
- FAQ
- Your next step
The scenario we will use
To keep this concrete, we will follow one illustrative situation. It is not a customer story.
A mid-sized finance company has an IT manager, a BI analyst and an internal auditor. The auditor wants a Monday morning summary of failed and interrupted sign-ins to the finance reporting apps, plus a list of role changes made the previous week. The IT manager must grant access without handing out Global Administrator. The analyst wants to stop pasting numbers into a spreadsheet. Each section returns to this same weekly report.
What counts as an Azure AD report
Entra ID produces several kinds of activity logs. The three most people mean are:
- Sign-in logs: who signed in, to which application, from which IP address, and whether it succeeded, failed or was interrupted.
- Audit logs: changes made in the directory, such as role assignments, group changes and app registrations.
- Provisioning logs: records of users and groups being synced to or from other apps.
There are also object reports, such as a view of a user account and where its permissions come from. Those are for access reviews rather than activity monitoring, and the steps below focus on the activity logs your auditor is asking about.
Which role and license you need
Microsoft's monitoring operations documentation sets the access rules. Sign-in logs require Reports Reader, Security Reader, Security Administrator or Global Reader, together with an Entra ID P1 or P2 license. Audit logs accept those roles, or Global Administrator, on a free license. Provisioning logs are free for seven days and then need P1.
| Log type | Minimum role | License |
|---|---|---|
| Sign-in logs | Reports Reader (or Security Reader, Security Administrator, Global Reader) | Entra ID P1 or P2 |
| Audit logs | Same roles, or Global Administrator | Free works |
| Provisioning logs | Same roles | Free for 7 days, then P1 |
Reports Reader is the least privileged role for activity logs, according to Microsoft's guide to accessing activity logs. For the finance company, that is the role the IT manager assigns to the auditor. It shows the logs and nothing more, so the auditor cannot change a policy or a user.
The MFA sign-in report has a slightly higher bar. To see the sign-in activity report with authentication details, you sign in as at least an Authentication Policy Administrator and go to Entra ID > Users > Sign-in logs. That view shows MFA prompts and any Conditional Access policies that applied.
A separate point for individual users: anyone can see their own sign-in history at mysignins.microsoft.com, which Microsoft's filtering documentation notes. That is useful for a help desk ticket, but it is not a tenant-wide report.
How to open the reports in the admin center
- Assign the role. In the Entra admin center, give the auditor's account Reports Reader. Use a role assignment on that one account rather than adding them to a broad admin group.
- Confirm the license. If the auditor needs sign-in logs, check that the tenant has P1 or P2. Without it, the sign-in page will not give them the data.
- Sign in and browse. Go to Entra ID > Monitoring & health and choose Audit logs, Sign-in logs or Provisioning logs, as described in Microsoft's access guide.
- Filter before you read. The audit log filters include Service, Category, Activity, Status, Target, Initiated by and Date range. Sign-in logs add Request ID, Correlation ID, User, Application, Status, Resource, IP address and Conditional Access. The full list is in the filter documentation.
- Download if you need a file. Per the download guide, downloading is available in all editions. Files come as CSV or JSON with UTC timestamps, capped at 100,000 sign-in or provisioning records and 250,000 audit records per file. Programmatic download through Graph needs a premium license.
For the Monday report, the auditor's filters would be: status Failure or Interrupted, applications limited to the finance reporting apps, and a seven-day date range. For role changes, they would use the audit log with the category set to role management.
Reading a sign-in row
Each row carries the date, a Request ID, the user principal name (the sign-in name, usually an email address), the application, the status, the IP address, an estimated location, the resource and the Conditional Access result. An "Interrupted" status commonly means the user still had to finish something such as MFA setup or a password change, according to one practitioner guide. The Request ID is the value to give Microsoft Support if you open a case.
Other ways to reach the same data
The portal is fine for investigation. It is a poor fit for a weekly deliverable, because every run depends on a person remembering to click. Microsoft documents several other routes: the Microsoft Graph API, streaming to an event hub, Azure Monitor logs and real-time monitoring with Microsoft Sentinel.
For scripting, the usual cmdlet is Get-MgAuditLogSignIn from the Microsoft Graph PowerShell module. Querying through Graph needs the AuditLog.Read.All permission and a P1 or P2 license, as Gatera's guide on MFA audit logs lays out. Plan for pagination and filter on the server side where you can, since returning every sign-in for a large tenant is slow.
The analyst has a decision to make here:
- A script on a schedule is cheap to start. It also becomes something one person owns, with its own credentials, error handling and formatting to maintain.
- Logs routed to a workspace and reported in Power BI gives you a proper report with visuals, filters and a data model that anyone can reuse.
For anything the auditor reads every week, we recommend the second route, and then automating delivery of that report.
Retention: the limit that catches teams
The logs do not last forever. As of September 2026, Entra keeps audit and sign-in logs for seven days on a free license and 30 days on P1 or P2, and an upgrade does not bring back anything that has already expired. Longer history exists only where something was already archiving it, for example diagnostic settings that send logs to a storage account or Log Analytics.

That changes the finance company's plan. If the auditor needs a quarter of history, the IT manager has to route logs out of Entra before they age out. Check Microsoft's current retention page before you commit to an audit schedule, because retention terms can change.
When access fails or the data looks wrong
Most problems come from a short list:
- The page is empty or blocked. Check the license first for sign-in logs, then the role. A Global Reader without P1 or P2 will not see sign-in data.
- Events are missing. Look at the date range and your retention window. Anything older than seven or 30 days is gone unless it was exported.
- A user shows hundreds of entries. One person can generate many rows because background token refreshes and app activity each produce sign-ins. Filter by application and status before concluding something is wrong.
- A download looks cut off. The per-file caps of 100,000 sign-in and 250,000 audit records apply. Narrow the date range and download in pieces.
- A Graph call returns an authorization error. Confirm the app or account has AuditLog.Read.All with admin consent.
Getting the report to the auditor without the Monday export
Here the problem changes. Giving the auditor Reports Reader solves access to the logs. It does not solve delivery. Suppose the weekly summary lives in a Power BI report, built on logs you have routed out of Entra. Someone still has to open it, export it as PDF or Excel, and email it. That is the repetitive step that falls apart during vacations and audits.
Power BI's own scheduling can cover a simple case: one report, one audience, one format. The point where it stops being enough is when you need different recipients to receive different filtered versions, several formats, delivery to a folder or collaboration tool, or a log of what went out and when. For our scenario, the IT manager wants the auditor to get the sign-in summary and the compliance lead to get only the role-change page. That is personalization, and it is where a dedicated tool earns its place.
There is a permissions side as well. A report that lists sign-in activity is sensitive, and the people receiving it should see only what their role allows. Our guide to Power BI report access permissions walks through how to structure that, and our post on exporting while keeping row-level security covers keeping each recipient inside their own data slice.
If your Power BI tenant enforces MFA or a custom sign-in method, the scheduler has to authenticate too. We document how to connect PBRS when Power BI uses MFA, 2FA or custom organization authentication.

What PBRS does in this workflow
PBRS handles Power BI and SSRS reports. In the finance company example, it takes the finished sign-in summary report and does the work the analyst was doing by hand: it schedules the run, personalizes it for each recipient, exports it to a format such as PDF or Excel, and delivers it securely to licensed or external recipients. It supports dynamic, data-driven schedules and event-triggered workflows, so the report can go out on Monday morning or when a condition is met, and it has automated error handling.
If your team runs a self-hosted dashboard instead, IntelliFront BI gives centralized access to dashboards, KPIs and reports. It supports Microsoft single sign-on through Microsoft Graph, so viewers sign in with their existing Microsoft identities.
Your existing tools are enough when
We would not add software for every case. The Entra admin center plus a saved filter is enough when one or two people review logs occasionally and nothing needs to be delivered. Native Power BI subscriptions are enough when a single report goes to a stable list in one format. Consider another approach when you can answer yes to any of these:
- Recipients need different filtered versions of the same report.
- You need PDF, Excel and a file-share copy for the same run.
- Delivery has to follow an event or data condition, not a clock.
- Someone must be able to prove what was sent, to whom and when.
- Help desk tickets asking for a manual export keep landing on the same two people.
Our view
We build report automation, so we see the same pattern often in access conversations: a team solves who may open the report, then forgets that a report nobody delivers on time is still a missed deadline. Get the Entra role and license right first, because that is the foundation of an audit-ready process.
Then treat delivery as its own requirement. A scheduled, personalized, monitored export is easier to defend to an auditor than a manual one, and it frees the analyst for analysis. PBRS is designed for exactly that step for Power BI and SSRS, and we think of it as the layer that makes an access decision visible in the inbox of the right person.
Christian Ofori-Boateng
Put the weekly report on a schedule
If your sign-in and role-change report already exists in Power BI, PBRS can schedule and deliver it for you. See how it works on the PBRS Power BI report scheduler page and start from the trial or demo.

PBRS is available under a subscription or perpetual license. If you manage subscriptions already, our guide to managing and auditing Power BI report subscriptions shows what to review first.
FAQ
What is the minimum role to view Azure AD sign-in logs?
Reports Reader is the least privileged role for activity logs. Security Reader, Security Administrator and Global Reader also work. Sign-in logs additionally need an Entra ID P1 or P2 license.
Do I need a paid license to see audit logs?
No. Audit logs are available on a free license to the roles listed above, including Global Administrator. Programmatic download through Graph is the part that requires a premium license.
How far back can I see Entra ID logs?
The portal keeps audit and sign-in logs for seven days on a free license and 30 days on P1 or P2, per the retention guidance linked above. For longer history, send the logs to a storage account or Log Analytics before they expire.
Can I schedule an Entra report to email itself?
Not from the admin center alone. A common approach is to route the logs to a workspace, build a Power BI report, and use a scheduler such as PBRS to export and deliver it on a recurring schedule to the right recipients.
Your next step
This week, do two things. Assign Reports Reader to the person who needs the logs, and check whether your tenant has P1 or P2 for sign-in data. Then decide whether the report that follows should still depend on someone clicking Export on Monday morning.
