Understand data storage and workspaces

This article helps you understand how data is stored in Microsoft Defender for Cloud, and when you need a Log Analytics workspace.

Defender for Servers is one of the paid plans provided by Microsoft Defender for Cloud.

Before you begin

This article is the fifth article in the Defender for Servers planning guide. Before you begin, review the earlier articles:

  1. Start planning your deployment.
  2. Review Defender for Servers access roles.
  3. Select a Defender for Servers plan
  4. Understand how Defender for Servers collects data for assessment and when you need a workspace.

Understand data residency

Before you deploy Defender for Servers, learn how Defender for Cloud stores data.

  • Review general Azure data residency considerations.
  • Posture data collected by Defender for Cloud is stored in the Defender for Cloud backend. Data is routed based on the tenant location. European tenants are stored in a Europe location.
  • Defender for Cloud's threat protection data including security alerts might be processed in the same region as the cloud resource, and later routed to the MDC backend.
  • Data collected by the Defender for Endpoint agent for file integrity monitoring is stored for access and analysis in a Log Analytics workspace.
  • You can export data to a Log Analytics workspace using continuous export.

Next steps

Learn how to scale a Defender for Server deployment.