Security

AI Activity Investigations: New Microsoft Playbook

2 min read

Summary

Microsoft has published a new investigator playbook to help security teams reconstruct AI-related activity across Microsoft 365 Copilot and Azure AI services. The guidance brings together telemetry, KQL queries, schema references, and detection logic across Purview, Defender, and Sentinel so investigators can move from isolated signals to a clear incident timeline.

Need help with Security?Talk to an Expert

Introduction

As AI tools become part of daily business workflows, security teams need reliable ways to investigate what happened inside them. Microsoft’s new playbook for Microsoft 365 Copilot and Azure AI services is designed to help incident responders reconstruct AI activity using telemetry already available across Microsoft security tools.

What’s new

Microsoft has released an AI investigation playbook that provides a structured methodology for analyzing AI-related activity. The playbook is built around a scope → context → signal model:

  • Scope: Identify who interacted with the AI system, when the activity occurred, and which service was involved.
  • Context: Determine what resources were accessed, what data may have been exposed, and whether the behavior matched expected usage.
  • Signal: Evaluate alerts and detections such as prompt injection attempts, anomalous usage, or credential exposure within the full activity chain.

The playbook also consolidates practical investigation resources into one model, including:

  • Schema references
  • KQL queries
  • Detection patterns and logic
  • Configuration guidance across Microsoft security products

Microsoft says this approach works across Microsoft Purview, Microsoft Defender, and Microsoft Sentinel, helping teams reduce ad hoc pivots between tools.

Why this matters for security teams

AI interactions generate metadata-rich telemetry, including identity, timestamps, and resource access details. That makes it possible to reconstruct events—but only if teams have a repeatable process.

For security operations and incident response teams, this playbook helps answer critical questions:

  • Who used the AI system?
  • What data was accessed during the interaction?
  • Was the activity authorized?
  • Does the behavior indicate normal use, a policy violation, or a possible compromise?

The guidance also extends to agent-based systems, where investigators may need to review which agents are deployed, how they are configured, and what data they are permitted to access.

Next steps

IT and security administrators should review the playbook and validate that the required telemetry and configurations are enabled across their Microsoft security stack. Teams using Microsoft 365 Copilot or Azure AI services should also consider updating investigation procedures to include AI-specific signals and response workflows.

As AI adoption grows, the ability to reconstruct AI activity is becoming a core incident response capability—not a nice-to-have. Microsoft’s playbook is a practical step toward making those investigations more consistent and defensible.

Need help with Security?

Our experts can help you implement and optimize your Microsoft solutions.

Talk to an Expert

Stay updated on Microsoft technologies

AI securityMicrosoft 365 CopilotAzure AIMicrosoft Sentinelincident response

Related Posts

Security

Microsoft Sentinel Named a 2026 SIEM Leader

Microsoft has been named a Leader in the 2026 Gartner Magic Quadrant for SIEM, highlighting the continued momentum behind Microsoft Sentinel. The announcement also underscores Microsoft's push toward integrated, AI-powered security operations through deep Sentinel integration with the new Integrated Security Operations Center in Microsoft Defender.

Security

Microsoft Perception GA: Agentic Security at Ignite

Microsoft has made Microsoft Perception generally available, introducing an agentic security platform that coordinates red, blue, and green team agents through automated playbooks. Announced at Ignite 2026, the update also expands Defender and Sentinel capabilities to help security teams detect, investigate, and remediate AI-speed threats while keeping administrators in control.

Security

Device Code Phishing Risks for AI Coding Agents

Microsoft warns that device code phishing can be used against AI coding agents such as GitHub Copilot CLI, not just user mailboxes or cloud apps. In a controlled lab, a single approved device code sign-in could enable remote session steering, memory poisoning, synced session exposure, and private repository access depending on account permissions and enabled features.

Security

Microsoft 365 Outage Phishing Campaign Targets Users

Microsoft Threat Intelligence reported a high-volume phishing campaign that impersonates Microsoft 365 service-health notifications to trick users into clicking malicious links. The campaign matters because it uses outage-themed urgency and recipient-specific tracking to target multiple industries, increasing the risk of credential theft and follow-on account compromise.

Security

SCKit ScreenConnect Attack: MSPs Must Hunt Now

Microsoft Threat Intelligence confirmed a campaign abusing ConnectWise ScreenConnect to deploy unauthorized remote-access clients and the SCKit worm on MSP-managed endpoints. The activity can also target technician sessions, making this a high-priority incident for defenders because removing a rogue client alone does not eliminate persistence or invalidate exposed sessions.

Security

AI Agent Supply Chain Attacks Target Coding Tools

Microsoft Security researchers detailed two post-training supply chain attack paths that can backdoor coding and terminal agents: dataset poisoning and model poisoning. The findings matter because compromised agents can misuse tools, execute commands, and access sensitive environments even when prompts appear benign, reinforcing the need for stronger controls around training data, model provenance, and tool permissions.