Sign-in activity reports in the Azure Active Directory portal
The reporting architecture in Azure Active Directory (Azure AD) consists of the following components:
- Sign-ins – Information about the usage of managed applications and user sign-in activities.
- Audit logs - Audit logs provide system activity information about users and group management, managed applications, and directory activities.
This article gives you an overview of the sign-ins report.
Who can access the data?
- Users in the Security Administrator, Security Reader, and Report Reader roles
- Global Administrators
- Any user (non-admins) can access their own sign-ins
What Azure AD license do you need to access sign-in activity?
- Your tenant must have an Azure AD Premium license associated with it to see the all up sign-in activity report. See Getting started with Azure Active Directory Premium to upgrade your Azure Active Directory edition. It will take a couple of days for the data to show up in the reports after you upgrade to a premium license with no data activities before the upgrade.
The user sign-ins report provides answers to the following questions:
- What is the sign-in pattern of a user?
- How many users have signed in over a week?
- What’s the status of these sign-ins?
Start with Azure portal. To access the sign-ins report select Sign-ins, continue to the Monitoring. It may take up to two hours for some sign-in records to show up in the portal.
The sign-ins report only displays the interactive sign-ins, that is, sign-ins where a user manually signs in using their username and password. Non-interactive sign-ins, such as service-to-service authentication, are not displayed in the sign-ins report.
A sign-ins log has a default list view that shows:
- The sign-in date
- The related user
- The application the user has signed in to
- The sign-in status
- The status of the risk detection
- The status of the multi-factor authentication (MFA) requirement
You can customize the list view by clicking Columns in the toolbar.
Displays additional fields or remove fields that are already displayed.
Select an item in the list view to get more detailed information.
Customers can now troubleshoot Conditional Access policies through all sign-in reports. By clicking on the Conditional Access tab for a sign-in record, customers can review the Conditional Access status and dive into the details of the policies that applied to the sign-in and the result for each policy. For more information, see the Frequently asked questions about CA information in all sign-ins.
Filter sign-in activities
First, narrowing down the reported data to a level that works for you. Second, filter sign-ins data using date field as default filter. Azure AD provides you with a broad range of additional filters you can set.
The User filter enables you to specify the name or the user principal name (UPN) of the user you care about.
The Application filter enables you to specify the name of the application you care about.
The Sign-in status filter enables you to select:
The Conditional Access filter enables you to select the CA policy status for the sign-in:
- Not Applied
The Date filter enables to you to define a timeframe for the returned data.
Possible values are:
- One month
- 7 days
- 24 hours
- Custom time interval
When you select a custom timeframe, you can configure a start time and an end time.
If you add additional fields to your sign-ins view, these fields are automatically added to the list of filters. For example, by adding Client App field to your list, you also get another filter option that enables you to set the following filters:
This filter shows all events where sign-in attempts were attempted using browser flows.
Exchange ActiveSync (supported)
This filter shows all sign-in attempts where the Exchange ActiveSync (EAS) protocol has been attempted from supported platforms like iOS, Android, and Windows Phone.
Exchange ActiveSync (unsupported)
This filter shows all sign-in attempts where the EAS protocol has been attempted from unsupported platforms like, Linux distros.
Mobile Apps and Desktop clients The filter shows all sign-in attempts that were not using browser flows. For example, mobile apps from any platform using any protocol or from Desktop client apps like Office on Windows or MacOS.
A legacy mail client using IMAP to retrieve email.
Office 2013, where ADAL is enabled and it is using MAPI.
- Old Office clients
Office 2013 in its default configuration where ADAL is not enabled and it is using MAPI, or Office 2016 where ADAL has been disabled.
A legacy mail client using POP3 to retrieve email.
A legacy mail client using SMTP to send email.
Download sign-in activities
Click the Download option to create a CSV or JSON file of the most recent 250,000 records. Start with download the sign-ins data if you want to work with it outside the Azure portal.
The number of records you can download is constrained by the Azure Active Directory report retention policies.
Sign-ins data shortcuts
Azure AD and the Azure portal both provide you with additional entry points to sign-ins data:
- The Identity security protection overview
- Enterprise applications
Users sign-ins data in Identity security protection
The user sign-in graph in the Identity security protection overview page shows weekly aggregations of sign-ins. The default for the time period is 30 days.
When you click on a day in the sign-in graph, you get an overview of the sign-in activities for this day.
Each row in the sign-in activities list shows:
- Who has signed in?
- What application was the target of the sign-in?
- What is the status of the sign-in?
- What is the MFA status of the sign-in?
By clicking an item, you get more details about the sign-in operation:
- User ID
- Application ID
- IP address
- MFA Required
- Sign-in status
IP addresses are issued in such a way that there is no definitive connection between an IP address and where the computer with that address is physically located. Mapping IP addresses is complicated by the fact that mobile providers and VPNs issue IP addresses from central pools that are often very far from where the client device is actually used. Currently in Azure AD reports, converting IP address to a physical location is a best effort based on traces, registry data, reverse look ups and other information.
On the Users page, you get a complete overview of all user sign-ins by clicking Sign-ins in the Activity section.
Usage of managed applications
With an application-centric view of your sign-in data, you can answer questions such as:
- Who is using my applications?
- What are the top three applications in your organization?
- How is my newest application doing?
The entry point to this data is the top three applications in your organization. The data is contained within the last 30 days report in the Overview section under Enterprise applications.
The app-usage graphs weekly aggregations of sign-ins for your top three applications in a given time period. The default for the time period is 30 days.
If you want to, you can set the focus on a specific application.
When you click on a day in the app usage graph, you get a detailed list of the sign-in activities.
The Sign-ins option gives you a complete overview of all sign-in events to your applications.
Office 365 activity logs
You can view Office 365 activity logs from the Microsoft 365 admin center. Consider the point that, Office 365 activity and Azure AD activity logs share a significant number of the directory resources. Only the Microsoft 365 admin center provides a full view of the Office 365 activity logs.
You can also access the Office 365 activity logs programmatically by using the Office 365 Management APIs.