Skip to content

Commit fc72a37

Browse files
authored
Update plan-monitoring-and-reporting.md
1 parent 59f4987 commit fc72a37

File tree

1 file changed

+36
-49
lines changed

1 file changed

+36
-49
lines changed

articles/active-directory/reports-monitoring/plan-monitoring-and-reporting.md

Lines changed: 36 additions & 49 deletions
Original file line numberDiff line numberDiff line change
@@ -60,7 +60,7 @@ Learn more about:
6060
* An Azure Event Hubs namespace to integrate with SIEM solutions
6161
* An Azure Log Analytics workspace to send logs to Azure Monitor logs
6262

63-
## Azure reporting and monitoring deployment project
63+
## Stakeholders, communications, and documentation
6464

6565
Use the following sections to define the users who consume and monitor reports, and your Azure AD monitoring architecture.
6666

@@ -70,7 +70,7 @@ Successful projects align expectations, outcomes, and responsibilities. See, [Az
7070

7171
### Communications plan
7272

73-
Tell your users how and when the experience will change. Provide contact information for support.
73+
Tell your users when, and how, their experience will change. Provide contact information for support.
7474

7575
### Document current infrastructure and policies
7676

@@ -100,87 +100,74 @@ Business use cases:
100100

101101
### Monitoring solution architecture
102102

103-
With Azure AD monitoring, you can route Azure AD activity logs and retain them for long-term reporting and analysis to gain insights into your environment, and integrate it with SIEM tools.
103+
With Azure AD monitoring, you can route Azure AD 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.
104104

105-
Decision flow chart![An image showing what is described in subsequent sections](media/reporting-deployment-plan/deploy-reporting-flow-diagram.png)
105+
![Decision matrix for business-need architecture.](media/reporting-deployment-plan/deploy-reporting-flow-diagram.png)
106106

107107
#### Archive logs in a storage account
108108

109-
By routing logs to an Azure storage account, you can keep them for longer than the default retention period outlined in our [retention policies](./reference-reports-data-retention.md). Use this method if you need to archive your logs, but don't need to integrate them with an SIEM system, and don't need ongoing queries and analysis. You can still do on-demand searches.
109+
You can keep logs longer than the default retention period by routing them to an Azure storage account.
110110

111-
Learn how to [route data to your storage account](./quickstart-azure-monitor-route-logs-to-storage-account.md).
111+
> [!IMPORTANT]
112+
> 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.
112113
113-
#### Send logs to Azure Monitor logs
114+
Learn more:
114115

115-
[Azure Monitor logs](../../azure-monitor/logs/log-query-overview.md) consolidate monitoring data from different sources. It also provides a query language and analytics engine that gives you insights into the operation of your applications and use of resources. By sending Azure AD activity logs to Azure Monitor logs, you can quickly retrieve, monitor, and alert on collected data. Use this method when you don't have an existing SIEM solution that you want to send your data to directly but do want queries and analysis. Once your data is in Azure Monitor logs, you can then send it to event hub, and from there to a SIEM if you want to.
116+
* [How long does Azure AD store reporting data?](./reference-reports-data-retention.md)
117+
* [Tutorial: Archive Azure AD logs to an Azure storage account](./quickstart-azure-monitor-route-logs-to-storage-account.md)
118+
119+
#### Send logs to Azure Monitor logs
116120

117-
Learn how to [send data to Azure Monitor logs](./howto-integrate-activity-logs-with-log-analytics.md).
121+
[Azure Monitor logs](../../azure-monitor/logs/log-query-overview.md) consolidate monitoring data from different sources. Use the query language and analytics engine for insights on application operation and resource usage. Retrieve, monitor, and alert on collected data by sending Azure AD activity logs to Azure Monitor logs.
118122

119-
You can also install the pre-built views for Azure AD activity logs to monitor common scenarios involving sign-in and audit events.
123+
> [!IMPORTANT]
124+
> Use this logging method if there is no SIEM solution for receiving data. You can conduct queries and analysis. After data is in Azure Monitor logs, you can send it to your event hub, and then to a SIEM.
120125
121-
Learn how to [install and use log analytics views for Azure AD activity logs](./howto-install-use-log-analytics-views.md).
126+
Learn more:
122127

123-
#### Stream logs to your Azure event hub
128+
* [Integrate Azure AD logs with Azure Monitor logs](./howto-integrate-activity-logs-with-log-analytics.md).
129+
* [Analyze Azure AD activity logs with Azure Monitor logs](/MicrosoftDocs/azure-docs/blob/main/articles/active-directory/reports-monitoring/howto-analyze-activity-logs-log-analytics.md).
124130

125-
Routing logs to an Azure event hub enables integration with third-party SIEM tools. This integration allows you to combine Azure AD activity log data with other data managed by your SIEM, to provide richer insights into your environment.
131+
#### Route logs to your Azure event hub
126132

127-
Learn how to [stream logs to an event hub](./tutorial-azure-monitor-stream-logs-to-event-hub.md).
133+
Routing logs to an Azure event hub enables integration with SIEM tools. For more insights, combine Azure AD activity log data with other data managed by your SIEM.
128134

129-
## Plan Operations and Security for Azure AD reporting and monitoring
135+
Learn more: [Tutorial: Stream Azure Active Directory logs to an Azure event hub](./tutorial-azure-monitor-stream-logs-to-event-hub.md).
130136

131-
Stakeholders need to access Azure AD logs to gain operational insights. Likely users include security team members, internal or external auditors, and the identity and access management operations team.
137+
## Roles
132138

133-
Azure AD roles enable you to delegate the ability to configure and view Azure AD Reports based on your role. Identify who in your organization needs permission to read Azure AD reports and what role would be appropriate for them.
139+
Stakeholders need access to Azure AD logs. These users likely are the security teams, auditors (internal or external), identity and access management operations teams, etc.
134140

135-
The following roles can read Azure AD reports:
141+
Use Azure AD roles to delegate configuration and permit who views or reads Azure AD Reports. The following roles read Azure AD reports:
136142

137143
* Global Admin
138-
139144
* Security Admin
140-
141145
* Security Reader
142-
143146
* Reports Reader
144147

145-
Learn More About [Azure AD Administrative Roles](../roles/permissions-reference.md).
146-
147-
*Always apply the concept of least privileges to reduce the risk of an account compromise*. Consider implementing [Privileged Identity Management](../privileged-identity-management/pim-configure.md) to further secure your organization.
148+
Learn more: [Azure AD built-in roles](../roles/permissions-reference.md)
148149

150+
> [!NOTE]
151+
>To increase account security, apply the concept of least privileges.
152+
>Learn more: [What is Azure AD Privileged Identity Management?](../privileged-identity-management/pim-configure.md).
149153
150-
## Deploy Azure AD reporting and monitoring
151-
152-
Depending on the decisions you have made earlier using the design guidance above, this section will guide you to the documentation on the different deployment options.
153-
154-
### Consume and archive Azure AD logs
155-
156-
[Find activity reports in the Azure portal](./howto-find-activity-reports.md)
154+
## Deployment options
157155

158-
[Archive Azure AD logs to an Azure Storage account](./quickstart-azure-monitor-route-logs-to-storage-account.md)
156+
Use the following guidance to review deployment options.
159157

160158
### Implement monitoring and analytics
161159

162-
[Send logs to Azure Monitor](./howto-integrate-activity-logs-with-log-analytics.md)
163-
164-
[Install and use the log analytics views for Azure Active Directory](./howto-install-use-log-analytics-views.md)
165-
166-
[Analyze Azure AD activity logs with Azure Monitor logs](./howto-analyze-activity-logs-log-analytics.md)
167-
168-
* [Interpret audit logs schema in Azure Monitor](./overview-reports.md)
169-
170-
* [Interpret sign in logs schema in Azure Monitor](./reference-azure-monitor-sign-ins-log-schema.md)
171-
172-
* [Stream Azure AD logs to an Azure event hub](./tutorial-azure-monitor-stream-logs-to-event-hub.md)
160+
* [What are Azure Active Directory reports?](./overview-reports.md)
173161

174-
* [Integrate Azure AD logs with Splunk by using Azure Monitor](./howto-integrate-activity-logs-with-splunk.md)
162+
* [Interpret the Azure AD sign-in logs schema in Azure Monitor](./reference-azure-monitor-sign-ins-log-schema.md)
175163

176-
* [Integrate Azure AD logs with SumoLogic by using Azure Monitor](./howto-integrate-activity-logs-with-sumologic.md)
164+
* [How to: Integrate Azure Active Directory logs with Splunk using Azure Monitor](./howto-integrate-activity-logs-with-splunk.md)
177165

178-
166+
* [Integrate Azure Active Directory logs with SumoLogic using Azure Monitor](./howto-integrate-activity-logs-with-sumologic.md)
179167

180-
181168

182169
## Next steps
183170

184-
Consider implementing [Privileged Identity Management](../privileged-identity-management/pim-configure.md)
171+
[What is Azure AD Privileged Identity Management?](../privileged-identity-management/pim-configure.md)
185172

186-
Consider implementing [Azure role-based access control](../../role-based-access-control/overview.md)
173+
[What is Azure role-based access control (Azure RBAC)?](../../role-based-access-control/overview.md)

0 commit comments

Comments
 (0)