A cloud-native SIEM solution that provides intelligent security analytics and threat detection across systems
Thank you for your reply.
Below is a RCA and resolution: -
Sentinel is NOT migrated fully into Defender
Data (SigninLogs) still comes ONLY from Log Analytics workspace
Defender portal does NOT replace ingestion pipeline
As per Microsoft:
Sentinel still runs on Log Analytics workspace
Workbooks, connectors, and tables remain workspace-dependent
2. Why your SigninLogs is NOT appearing ( Root Causes)
Cause 1 — You enabled Diagnostic settings but NOT the Sentinel connector properly
Requirement:
You must enable the Microsoft Entra ID data connector in Sentinel
Logs DO NOT appear just by enabling diagnostic settings alone [learn.microsoft.com]
What to check:
Go to:
Sentinel → Data connectors → Microsoft Entra ID
Ensure:
Connector is Connected
Shows data types (SigninLogs / AuditLogs)
For you reference: https://learn.microsoft.com/en-us/azure/sentinel/connect-azure-active-directory
Cause 2 — Workspace mismatch (Most Common)
Logs go to the Log Analytics workspace linked to Sentinel .
If:
Diagnostic settings → Workspace A
Sentinel attached → Workspace B
You will see:
No SigninLogs table
Connector = Disconnected
Resolution:
Go to:
Entra ID → Diagnostic settings
Verify:
Same workspace as Sentinel
Remove old config (optional)
Re-create diagnostic setting
https://learn.microsoft.com/en-us/azure/sentinel/connect-azure-active-directory'
Cause 3 — You are checking in Defender instead of Log Analytics
Critical point (very often missed):
SigninLogs table DOES NOT show in Defender UI like Sentinel logs
It is a Log Analytics table
Microsoft confirms:
Logs are stored in Log Analytics workspace [learn.microsoft.com]
Correct validation method:
Go to:
Azure Portal → Log Analytics Workspace → Logs
Run: SigninLogs
| take 10
Cause 4 — Data ingestion delay (longer than expected)
Logs may take 15–30 minutes to appear
In real scenarios, can take up to 1–2 hours (observed cases)
Cause 5 — Missing required roles / permissions
Required:
Sentinel Contributor on workspace
Security Admin in Entra ID
Why Connector shows “Disconnected”
“Disconnected” means:
Sentinel is NOT detecting data flow yet
NOT necessarily misconfiguration.
It flips to Connected only AFTER logs arrive.
Below is the resolution: -
Step 1 — Validate Workspace
- Check:
Sentinel workspace name
Diagnostic settings workspace name
- Must match EXACTLY
Step 2 — Reconfigure Entra diagnostic settings
Entra ID → Monitoring → Diagnostic settings
- Select:
SigninLogs
- AuditLogs
Destination:
SAME Log Analytics workspace
Step 3 — Re-enable connector
Sentinel → Data connectors → Entra ID
Open connector page
Click:
Disconnect (if stuck)
- Reconnect
Step 4 — Generate activity
Perform:
Portal login
MFA login
- Failed login attempt
Step 5 — Validate in Log Analytics (NOT Defender)
Run:SigninLogs
| sort by TimeGenerated desc
About “Sentinel Optimization Workbook” missing
This is expected behavior:
Workbooks are:
Stored as Azure resources in workspace
https://learn.microsoft.com/en-us/azure/sentinel/monitor-your-data?tabs=defender-portal
After moving to Defender:
They appear under:
Sentinel → Threat management → Workbooks
https://learn.microsoft.com/en-us/azure/sentinel/whats-new?tabs=defender-portal
If missing:
Install from Content Hub
Or import manually