Azure Security Logins to Office 365 and Splunk

Eric Adler 

Hello,

If you are experiencing slow event logging for logon events in Office 365/Azure AD via Splunk, there could be several factors contributing to this issue. Here are a few potential explanations and suggestions to consider:

Network or connectivity issues: Slow event logging can sometimes be caused by network problems or connectivity issues between Office 365/Azure AD and Splunk. Ensure that there are no network interruptions or latency problems that could be affecting the data transfer between these systems.

Splunk configuration: Review your Splunk configuration settings to ensure that they are optimized for handling and processing logon events. Check if there are any performance-related configurations or limitations that may be impacting the ingestion speed.

Data volume and retention: If you are dealing with a large volume of logon events or have a long data retention policy, it can strain the resources of Splunk and lead to slower logging. Consider adjusting the retention period or implementing data filtering to reduce the load on Splunk.

Splunk deployment architecture: Evaluate your Splunk deployment architecture to ensure that it is designed for scalability and performance. Consider distributing the workload across multiple indexers or leveraging additional hardware resources to improve event logging speed.

Splunk add-ons: Verify if you have the latest versions of the Splunk add-ons for Office 365/Azure AD. Updates to these add-ons may address known issues or improve performance.

Splunk support and community: Reach out to the Splunk community, experienced professionals having Splunk certification, or engage with the Splunk community forums to seek assistance. Other Splunk users may have encountered similar issues and can provide valuable insights or troubleshooting tips.

It is important to investigate the specific circumstances of your environment and evaluate these factors to identify the root cause of the slow event logging. By addressing the underlying issues, you can improve the timeliness and reliability of logon event data in Splunk.

I hope this information helps, and I wish you success in resolving the issue with your event logging.

Best regards.