<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>Syladon Insights</title><link>https://syladon.com/insights</link><description>Notes from the field on Microsoft 365, security, and investigations.</description><item><title>Why Microsoft 365 Audit Logs Matter During an Investigation</title><link>https://syladon.com/insights/why-m365-audit-logs-matter</link><guid>https://syladon.com/insights/why-m365-audit-logs-matter</guid><pubDate>Tue, 27 May 2025 12:00:00 GMT</pubDate><description>When something goes wrong in Microsoft 365, the audit log is often the only impartial record of what happened. Understanding its reach, and its limits, is essential.</description></item><item><title>What Businesses Should Review Before an Employee Departure</title><link>https://syladon.com/insights/review-before-employee-departure</link><guid>https://syladon.com/insights/review-before-employee-departure</guid><pubDate>Tue, 22 Apr 2025 12:00:00 GMT</pubDate><description>Most employee departures are routine. For the ones that aren't, a short, consistent technical checklist protects the business without treating anyone as a suspect.</description></item><item><title>What to Preserve After a Microsoft 365 Security Incident</title><link>https://syladon.com/insights/preserve-after-m365-security-incident</link><guid>https://syladon.com/insights/preserve-after-m365-security-incident</guid><pubDate>Tue, 18 Mar 2025 12:00:00 GMT</pubDate><description>When a Microsoft 365 account is compromised, the first hours shape what you can later reconstruct. A practical guide to preserving evidence without making things worse.</description></item></channel></rss>