Microsoft Entra monitoring and health deployment dependencies

Your Microsoft Entra reporting and monitoring solution depends on legal, security, operational requirements, and your environment's processes. Use the following sections to learn about design options and deployment strategy.

Benefits of Microsoft Entra reporting and monitoring

Microsoft Entra ID reporting has a view, and logs, of Microsoft Entra activity in your environment: sign-in and audit events, also changes to your directory.

Use data output to:

  • determine how your apps and services are used.
  • detect potential risks affecting the health of your environment.
  • troubleshoot issues preventing your users from getting their work done.
  • gain insights by seeing audit events of changes to your Microsoft Entra directory.

Microsoft Entra monitoring enables you to route your logs generated by Microsoft Entra ID reporting to different target systems. You can then either retain it for long-term use or integrate it with third-party Security Information and Event Management (SIEM) tools to gain insights into your environment.

With Microsoft Entra monitoring, you can route logs to:

  • an Azure storage account for archival purposes.
  • Azure Monitor logs, where you can analyze the data, create dashboards, and alert on specific events.
  • an Azure event hub where you can integrate with your existing SIEM tools such as Splunk, Sumologic, or QRadar.


You'll need a Microsoft Entra ID P1 or P2 license to access the Microsoft Entra sign-in logs.

For detailed feature and licensing information, see the Microsoft Entra pricing guide.

To deploy Microsoft Entra monitoring and health, you'll need a user who is a Security Administrator for the Microsoft Entra tenant.

Plan and deploy a Microsoft Entra monitoring and health deployment project

Reporting and monitoring are used to meet your business requirements, gain insights into usage patterns, and increase your organization's security posture. In this project, you'll define the audiences that will consume and monitor reports, and define your Microsoft Entra monitoring architecture.

Stakeholders, communications, and documentation

When technology projects fail, they typically do so due to mismatched expectations on effect, outcomes, and responsibilities. To avoid these pitfalls, ensure that you're engaging the right stakeholders. Also ensure that stakeholder roles in the project are well understood by documenting the stakeholders and their project input and responsibilities.

Stakeholders need to access Microsoft Entra logs to gain operational insights. Likely users include security team members, internal or external auditors, and the identity and access management operations team.

Microsoft Entra roles enable you to delegate the ability to configure and view Microsoft Entra reports based on your role. Identify who in your organization needs permission to read Microsoft Entra reports and what role would be appropriate for them.

The following roles can read Microsoft Entra reports:

  • Security Administrator
  • Security Reader
  • Reports Reader

Learn More About Microsoft Entra Administrative Roles. Always apply the concept of least privileges to reduce the risk of an account compromise. Consider implementing Privileged Identity Management to further secure your organization.

Engage stakeholders

Successful projects align expectations, outcomes, and responsibilities. See, Microsoft Entra deployment plans. Document and communicate stakeholder roles that require input and accountability.

Communications plan

Tell your users when, and how, their experience will change. Provide contact information for support.

  • What, if any, SIEM tools you're using.
  • Your Azure infrastructure, including existing storage accounts and monitoring being used.
  • Your organizational retention policies for logs, including any applicable compliance frameworks required.

Business use cases

To better prioritize the use cases and solutions, organize the options by "required for solution to meet business needs," "nice to have to meet business needs," and "not applicable."


  • Retention - Log retention: store audit logs and sign in logs of Microsoft Entra longer than 30 days
  • Analytics - Logs are searchable with analytic tools
  • Operational and security insights - Provide access to application usage, sign-in errors, self-service usage, trends, etc.
  • SIEM integration - Integrate and stream Microsoft Entra sign-in logs and audit logs to SIEM systems

Monitoring solution architecture

With Microsoft Entra monitoring, you can route Microsoft Entra activity logs and retain them for long-term reporting and analysis to gain environment insights, and integrate it with SIEM tools. Use the following decision flow chart to help select an architecture.

Decision matrix for business-need architecture.

Archive logs in a storage account

You can keep logs longer than the default retention period by routing them to an Azure storage account.


Use this archival method if there is no need to integrate logs with a SIEM system, or no need for ongoing queries and analysis. You can use on-demand searches.

Learn more:

Stream logs to storage and SIEM tools

Next steps