# What's New in Veeam Intelligent ResOps for Microsoft 365

**Initial release**

# Introduction

Veeam Intelligent ResOps for Microsoft 365 adds data and AI context to Veeam Data Cloud. Discover the Microsoft 365 estate, understand which users and AI agents can reach data, identify obsolete content and protection gaps, and act on selected files through quarantine, sensitivity labels and Undo AI recovery.

The Veeam DataAI Command Platform supplies the inventory, relationship graph, analytics, administration and classification services behind these capabilities. This document describes the initial Veeam customer release, beginning with the platform capabilities and then the native Microsoft 365 functionality.

The Microsoft 365 experience connects discovery and investigation to operational decisions: what to retain, what to protect, which content needs tighter controls, and which agent changes to recover. Deployment tables describe where the control plane and content processing run, and the closing comparison shows the Microsoft 365 capabilities included in Foundation and Advanced.

# Veeam DataAI Command Platform capabilities

## Inventory discovery and search

Shared services provide a consistent way to find resources, investigate relationships and use the intelligence collected from connected environments. Inventory content and available operations depend on the connected workload.

**Connector management** --- Configure supported connections and review their synchronization and discovery status. A common management experience provides visibility into the connections that supply platform metadata and classification results.

**Unified inventory and discovery** --- View discovered resources, services, production data and protected objects in a common inventory. Correlate information from supported connectors to understand what exists in the connected environment and where further investigation is required.

**Global search and graph queries** --- Find supported inventory objects using properties, conditions and relationships. Build reusable queries to investigate resources, locate files and identify protection gaps when the connected workload supplies the required protection metadata.

**Business context with tags** --- Create custom tags and apply them to supported inventory objects. Use tags to carry business context into graph queries, dashboard filters and policy scope, helping teams organize resources around their own operational requirements.

**Operational activity and history** --- Review discovery scans, synchronization and other supported tasks, including their status, results and failures. Backup and recovery task visibility is defined by the connected workload. Operational history and platform audit logs provide separate views of activity.

**APIs and extensibility** --- Use supported APIs and graph-query access to retrieve platform metadata and integrate queries and analytics with operational tools. Service accounts provide a dedicated identity for non-human access. Available endpoints and actions follow the enabled workload, entitlement and assigned permissions.

## Dashboards reporting and notifications

Dashboards and reports allow teams to consume platform intelligence in the format that suits their work, from an operational overview to the individual objects behind a result.

**System and custom dashboards** --- Use provided dashboards or create custom dashboards organized into groups. Share dashboards with other authorized users so teams can work from a consistent view of the connected environment.

**Query-driven data widgets** --- Build data widgets from graph queries and open supported widget results to inspect the underlying inventory objects. Refine the result with additional filters to investigate the data behind a metric or chart.

**Configurable grids** --- Present query results in a table with selected columns. Rename and reorder columns, apply supported filters and adjust the grid presentation to focus on the attributes relevant to the investigation.

**Metrics and charts** --- Display supported counts and aggregations, including file counts, duplicate counts and file size. Configure metric colors and layouts, enable time-series views where available, and choose chart types such as columns, bars, donut charts, lines, splines and areas.

**Report generation and sharing** --- Generate dashboard reports in PDF or PowerPoint presentation format. Select available page sizes and portrait or landscape orientation, and use supported sharing options to distribute the report.

**Scheduled reporting** --- Select dashboards for recurring report generation and configure supported delivery options. Scheduled reports help operational teams and stakeholders review the same information on a regular basis.

**CSV export preferences** --- Choose the default compression format for supported CSV exports, using ZIP or GZIP. Organization-level preferences provide a consistent export format for users.

**Custom notification templates** --- Customize supported policy and discovery-scan email templates, including the subject, preview text, message body and available variables. Preview templates before publishing them to align notifications with organizational terminology and communication requirements.

## Identity access and tenant administration

Centralized administration provides consistent controls for people and integrations accessing the platform. Administrators can align permissions and tenant preferences with the way their organization operates.

**User and group management** --- Create and manage users, import users from CSV and organize users into groups. Assign roles to users or groups to manage access by job function and reduce repetitive permission administration.

**Predefined and custom roles** --- Use predefined roles or create custom roles with permissions for enabled modules and platform capabilities. Role-based access control determines which information and operational actions a user can access within the permissions available for that module.

**Service accounts and API credentials** --- Create service accounts for scripts, agents and other integrations that require access independently of human users. Generate API credentials and assign the permissions needed for supported metadata queries and operations.

**Single sign-on** --- Integrate with a supported SAML identity provider to centralize authentication. Configure default user roles, enforce SSO for selected domains or user populations, and enable just-in-time user provisioning where required.

**Organizational domains** --- Configure primary and secondary domains to identify organizational users. Recognize additional organizational domains when administering user access.

**Homepage and organization logo** --- Set the default homepage and upload an organization logo to personalize the tenant experience. These settings help users enter the platform through the view most relevant to their work.

**Localized user interface** --- Select the interface language from English, Portuguese, French, Italian, Spanish, German, Japanese, Arabic and Indonesian. Interface localization is separate from the languages available for content classification.

## Security audit and support

Security settings give administrators control over platform sign-in, recorded activity and authorized support access.

**Login security** --- Configure password length, the treatment of repeated invalid sign-in attempts and multi-factor authentication requirements. Control concurrent user sessions and the maximum number of concurrent logins per user. Multi-Factor Authentication can be also enabled.

**Session timeout** --- Configure idle session timeout and enforce the setting across users. Tenant-level enforcement allows administrators to apply a consistent inactivity limit.

**IP access restrictions and masking** --- Restrict applicable sign-in and platform access paths to configured IP ranges, and enable IP masking in logs separately. Documented exclusions apply to IP restrictions, including support access; the setting does not cover every access path.

**Searchable audit logs** --- Investigate recorded platform events using filters for time, user, activity and object type. Audit records provide visibility into supported administrative and system activity, including account changes and sign-in events.

**Configurable audit retention** --- Set the retention period for platform audit logs to meet organizational requirements. The configured retention period applies to recorded events; supported values and event coverage are defined in the product documentation.

**Customer-controlled support access** --- Grant support access with a customer-selected role and expiration date and time. Restrict access to a specified support identity where required and review the support audit trail. Customers control when access is enabled and the permissions granted.

**Partner tenant access** --- Allow authorized partner users to select and access the customer tenants assigned to them from a central tenant selector. Access remains subject to each tenant authorization and the applicable partner permissions.

## Graph intelligence AI assistance and policies

The relationship graph connects inventory, access, activity and protection context so teams can investigate impact and define policies against the data affected. AI assistance helps users explore that context and build supported analytical views.

**Veeam DataAI Command Graph** --- Connect discovered data, identities, systems and AI context through their observed relationships. Use graph queries and interactive views to investigate dependencies, correlate protection information and assess potential impact where the required workload metadata is available.

**Precision protection and recovery** --- Use sensitivity, relationships and protection context to identify objects that require protection or recovery. The connected workload defines available actions and version selection. Microsoft 365 protection context and Undo AI recovery are described in the workload section.

**AI-assisted investigation** --- Ask questions about the observed environment to help investigate issues, find gaps, and explore and explain relationships. AI assistance can generate supported queries and analytical views, helping users move from a question to the data needed to assess it.

**Resilience Agents** --- Use platform agents to assist with supported resilience investigations and analytical tasks. Agent capabilities follow the connected workload and the user's permissions.

**AI-assisted dashboards** --- Use the dashboard agent to help create analytical views and data widgets from a natural-language request. Review the resulting queries and underlying data before relying on the dashboard for operational decisions.

**Managed and customer-configured model providers** --- Use the Veeam-managed model service for platform agents, or configure a supported external model provider using customer-managed credentials. Provider choice allows organizations to align model use with their policies; supported providers and usage terms follow the release configuration.

**Agent execution traces** --- Super administrators can inspect agent conversations and execution details, including status, timing, model and tool calls, token usage and available response details. Traces help investigate agent behavior and distinguish an analytical response from a completed operational action.

**Context-aware policy evaluation** --- Define policy scope and evaluation conditions using supported graph relationships, classification results and business context. Evaluate requirements and initiate the notifications or enforcement actions available for the selected workload, helping apply policies more precisely and consistently.

## Data classification engine and catalog

Data classification examines the content of supported sources to identify sensitive values and recognize business documents. The engine combines pattern matching, language analysis and machine learning, with built-in definitions and organization-specific rules. Findings provide context for investigation, reporting and supported policy decisions.

**Contextual detection** --- The engine parses structured layouts and unstructured text, then evaluates candidate matches together with nearby terms and related detections. Named-entity recognition identifies values such as names and locations that do not follow a fixed numeric pattern. Contextual machine learning examines the collected detections to resolve ambiguous matches and filter likely false positives. These methods complement explicit rules and known-value matching.

**Built-in data elements** --- Start with a library of 209 data elements across 18 categories, covering personal identifiers, contact information, financial information, authentication and other sensitive values. Enable the definitions relevant to the organization and use their detections to locate and scope sensitive content in connected sources.

**Custom data elements and detection tuning** --- Extend the library with rules for internal identifiers and specialized data. Define regular expressions for recognizable patterns, dictionaries for maintained term lists, and keywords or anchors for supporting context. Combining a candidate value with surrounding terminology makes a rule more specific, helping distinguish organization-specific information from similar-looking content.

**Classification dictionaries** --- Use 73 dictionaries across 12 categories and five languages as reusable term lists in classification definitions. Add custom dictionaries for industry terminology, internal vocabulary or business processes. Reusing a maintained dictionary allows multiple definitions to share the same terminology as requirements evolve.

**Document categories and types** --- Classify business content using 73 document types across nine categories, including financial statements, employment agreements and medical forms. Machine learning and pattern matching identify what a document represents alongside the sensitive information it contains. Create custom types for organization-specific documents. This allows files with the same format to be distinguished by their business meaning.

**File-format recognition** --- The format catalog recognizes 2,103 file formats across 22 categories. Recognition identifies how a file is represented; supported extraction capabilities determine which content can be analyzed for classification. Use scan profiles to select relevant formats and file-name criteria, following the content-extraction coverage available for the connected workload.

## Classification profiles and risk context

Profiles combine individual detections into reusable classification criteria. Data risk settings add organizational priorities to those findings, using the sensitivity of the information, where it is held and how much is concentrated in a resource.

**Built-in and custom content profiles** --- Use a catalog of 54 content profiles or create custom profiles for organizational requirements. Profiles combine data elements and classification criteria with applicable locality, language and structured or unstructured content settings. A profile can identify combinations of financial, personal or health information relevant to a review, giving teams a reusable scope for investigation, reporting and supported policies.

**Exact data indexes and profiles** --- Locate known sensitive information by fingerprinting reference values in an exact data index and defining the required matches in an exact data profile. Profiles can match a primary identifier together with associated fields, such as a known customer identifier and name. This distinguishes records corresponding to the supplied reference data from values that merely fit a pattern.

**Configurable sensitivity and importance** --- Configure data risk profiles for data types, locations and concentrations. In Data Type settings, assign category sensitivity and set the importance of the data-type dimension using levels from Very Low to Very High. For example, authentication information can receive a different sensitivity from contact information. These controls align the assessment with the information identified by classification and the organization's priorities.

**Location and concentration context** --- Include data location and concentration when assessing which findings require attention. Location settings reflect the importance assigned to where information is held; concentration settings account for the amount of data gathered in a resource. These dimensions help teams consider sensitive-data concentrations alongside individual detections when prioritizing investigation.

**Findings for investigation and policies** --- Use classification results and risk context in supported graph queries, dashboards and data intelligence views. Locate objects containing selected information, inspect their relationships and refine the results for a particular investigation. Correlate findings with available identity, access and protection metadata to assess exposure and resilience requirements. Supported policies can use this context to define scope and evaluate conditions; operational actions follow the connected workload and entitlement.

## Scan configuration and evidence controls

Scan controls help teams tailor discovery and classification to their requirements, test definitions on sample content and govern access to scan evidence.

**Default and custom scan profiles** --- Use the default scan profile or create profiles for individual data systems. Configure supported file-type and file-name criteria to include or exclude content from scanning.

**Custom scan categories** --- Define custom scan categories using file-type and file-name exclusions. Reuse these categories in supported scan configurations to maintain consistent scope.

**Instant Classify** --- Upload a file, or a ZIP archive containing multiple files, select the classification scope and review the results. Test sample content without first connecting a data source or configuring a broader discovery scan.

**Evidence retrieval controls** --- Control whether users can download evidence from supported classification scans. Enforce signed headers for evidence validation when required; this limits evidence retrieval to in-application validation and prevents direct evidence downloads.

### Additional module configuration

**Data Maps reference lists** --- Manage the controlled values used to describe catalog records, such as asset ownership, managing organization and security measures. Create custom lists to reflect the terminology and metadata requirements of the organization.

# Native Microsoft 365 capabilities

## Discovery classification and access context

Veeam Intelligent ResOps for Microsoft 365 adds data and access context to the Veeam Data Cloud tenant. Discover the estate, understand which users and AI agents can reach sensitive information, identify protection gaps and take action on selected files. It is the first workload introduced to Veeam customers on the Veeam DataAI Command Platform.

**Microsoft 365 inventory** --- Discover users, groups, mailboxes, sites and files across SharePoint Online, OneDrive, Exchange Online and Microsoft Teams. Inventory brings together metadata for files, folders, mailbox messages and attachments, and supported Teams chat and channel resources. Representative file sampling adds a sensitivity signal during inventory; scan definitions provide full content classification separately. Entra identity and application context connects these resources to the people and applications that can access them, giving administrators a common view for investigating data location, access and protection.

**Content classification through scan definitions** --- Run full content scans separately from metadata inventory. The Veeam data plane opens supported SharePoint and OneDrive files and classifies selected Microsoft 365 content, including Outlook message bodies and attachments and supported Teams content. Findings connect data elements, content profiles and document types to resources. Per-file findings and available matched-value evidence with surrounding context help administrators assess content before targeting a policy.

**Focused scan scope and classification definitions** --- Focus supported scans on selected sites, libraries, folders, users or groups. Apply source-specific criteria such as filename, path, format, size, owner and dates to narrow eligible content. Choose enabled data elements, content profiles, document categories and dictionaries, including custom definitions for internal identifiers and business terminology. This aligns the scan with the information and locations relevant to the investigation.

**Recurring scans and content extraction** --- Use recurring scans with incremental analysis of new and changed content to keep classification findings current. Enable optical character recognition (OCR) for supported images and PDFs, and archive extraction where required. Review processed, skipped and failed items to assess actual scan coverage before relying on content-based policies.

**Sensitive data and access context** --- Combine classification findings with supported read, write and full-control relationships for users, groups, applications and agents. Find files containing personally identifiable information that are shared with the entire organization, or sensitive content within an agent's reach. Graph queries follow the relationships behind these toxic combinations, helping teams identify the relevant files, identities and sites and prioritize a sharing or protection review.

## Data lifecycle File Insights and protection

File intelligence helps administrators find cleanup opportunities, understand sensitive-data exposure and prioritize protection. Policies and dashboards connect the estate-level summary to the matching resources, so teams can review the data affected before choosing a response.

**Redundant obsolete and trivial data** --- Use native exact duplicate detection based on file checksums and File ROT policies to identify candidates for lifecycle cleanup. Built-in policies include duplicate files and retention review at one, three, five and seven years. Matching file counts, volume and storage cost estimates help assess the opportunity before choosing an action. Policy scope and configured quarantine settings control the response to matching files.

**Duplicate and lifecycle analysis** --- Review duplicate file groups and estimated reclaimable volume after discovery, and identify the sources, owners and folders contributing to duplication. Refine lifecycle queries using available creation, modification or last-access dates alongside other file properties. These views help teams quantify a cleanup opportunity and review retention needs; reclaimable volume and cost estimates describe potential savings before remediation.

**Default File Insights policies** --- Identify files using metadata, access and protection context, with classification findings adding content-based criteria. Built-in insights include broadly shared files, public files, personally identifiable information (PII), protected health information (PHI), and files matching CPRA or PIPEDA content criteria. Review the matching files and volume, then refine the scope for investigation or remediation. Content-based criteria use completed classification scans; regulation-related profiles help locate relevant information for review.

**Policy scope and impact review** --- Use graph conditions to combine file content, source, path and access context into a policy scope. Inspect the matching files and the scope's impact before configuring an action. File Insights flags resources for investigation; ROT and remediation policies can use their configured actions to address eligible files. This keeps the review criteria connected to the data affected.

**Backup intelligence** --- Combine Microsoft 365 inventory with Veeam Data Cloud protection context to identify data that lacks protection and prioritize what to protect first. Sensitive content, broad sharing and agent access add business context to the protection review. For example, investigate sensitive files within an agent's reach that also need protection, helping teams focus resilience decisions on the potential impact of losing or changing that data.

**Microsoft 365 Intelligence Overview dashboard** --- Start with file counts and volume, Entra users and groups, application registrations and AI agents. Widgets highlight sensitive findings, sensitive files accessible to the entire organization and agents modifying data. Explore classification distributions, agent-accessible volume by service, sites containing sensitive data with sharing enabled, and file formats. Follow an exposure finding to the underlying files and identities, review the affected sites, and refine a labeling, quarantine or protection review.

## Quarantine and Microsoft Purview labeling

Remediation policies use classification and graph context to target eligible SharePoint Online and OneDrive files. Administrators can automate a configured response or work with selected files directly, using workbench results and logs to review what happened.

**Automated file quarantine** --- Create File Quarantine policies using data elements, content profiles, source paths and other graph properties. For example, target OneDrive files containing email addresses within a selected resource path, or SharePoint files matching specified content profiles. Quarantine moves eligible files to a configured customer-managed SharePoint Online, OneDrive or Amazon S3 destination. Review the matching files and configure the response for that scope.

**Quarantine workbench and revert** --- Review matched, quarantined and reverted files, with separate totals for the selected policy and processing status for each file. Quarantine selected eligible files or revert them to their original location. Policy logs help identify completed operations and exceptions. Mark findings as remediated or remove that designation according to the workflow; this changes the finding status. Export the file list to support operational review.

**Microsoft Purview labeling policies** --- Import and synchronize existing Microsoft Purview Information Protection sensitivity labels. Map data elements and content profiles to those labels, or apply a chosen label to supported files within a precise scope. For example, map a Date of Birth finding or personal-data content profile to the organization's corresponding label. This connects the labeling decision to the information found in the file.

**Labeling controls and classification metadata** --- Configure automatic or scheduled labeling, replacement of existing labels, and options to skip manually labeled files or changes that would lower sensitivity. Attach classification metadata such as whether a file contains personal data, its data element categories and detected types. Add custom key/value metadata for organizational context. These settings help maintain consistent labeling and carry classification findings into file metadata.

**Data Labeling workbench** --- Compare existing and target labels, inspect labeling activity and track results for matched files. Totals distinguish files labeled by Veeam, files labeled externally and files labeled by the selected policy. Administrators can manually apply or remove labels, manage remediation status and export selected files when the operation is available. This provides a common place to investigate label differences, handle exceptions and review progress.

## AI agent discovery activity and Undo AI

AI agent intelligence connects agents and applications to the data they can reach and the activity observed in the tenant. Undo AI connects that investigation to recovery through Veeam Data Cloud, helping administrators respond to unwanted file changes with the relevant agent and file context in view.

**AI agent discovery and application context** --- Discover supported Microsoft 365 agents and applications identified as capable of acting as agents. Inspect associated identities, data systems and sites, together with available relationships to query agents, data loaders and user interfaces. These views help administrators investigate the application components connected to organizational data and understand how an agent reaches information alongside the users and applications already present in the tenant.

**Agent access to sensitive content** --- Follow an agent's relationships to accessible files, detected data elements and content profiles. For example, one agent view connects 821 files in a single SharePoint site to 28 data element types and eight content profiles. This exposes the scope and sensitivity of data within the agent's reach; recorded activity shows which files it actually touched.

**Agent Activity Timeline** --- Review access, create, modify, move and delete events by agent and data system, with hourly activity summaries and file-level event details. An initial seven-day activity backfill provides recent context. Select an event to inspect the agent, file, data system and time involved, then compare the activity with available restore points to investigate an unwanted change and identify a recovery path.

**Undo AI with Veeam Data Cloud** --- Recover supported agent file changes using available Veeam Data Cloud restore points. From the activity timeline, inspect the affected file and use the available Undo change action to initiate recovery, including restoration of a deleted file. Activity, affected files and restore points remain in the same investigation context, helping administrators connect a recovery decision to the specific agent change that prompted it.

**Prioritize agent exposure and impact** --- Use graph queries and dashboard findings to investigate agents that can reach sensitive data, broadly shared files or data requiring protection. Compare potential access with recorded modifications and deletions to distinguish exposure from observed impact. This context helps teams focus on a remediation or recovery review on the relevant files.

## Deployment models and processing ownership

Choose Veeam-managed Shared data plane with SaaS, or deploy your own data plane in your own AWS account with a hybrid approach (option reserved for large organizations). The deployment must match the purchased SKU. Both models retain a Veeam-hosted regional control plane; the model determines who hosts the content-processing data plane.

**Regional service control plane** --- The control plane coordinates Microsoft 365 connections, scan definitions, processing jobs and platform services. It runs in Ohio (us-east-2) for AMER, Stockholm (eu-north-1) for EMEA and Tokyo (ap-northeast-1) for APJ. Both deployment models use the regional service control plane; the choice of model determines where the Veeam data plane runs. 

**Veeam data plane** – A data plane performs the content-processing work: it opens supported Microsoft 365 content and scans it for data elements, content profiles and document types. The control plane coordinates that work, while the data plane runs the analysis. This distinction lets customers choose the processing environment separately from the regional platform service. 

**SaaS and Hybrid deployment comparison**

| Dimension | SaaS Shared data plane | Hybrid customer-hosted data plane |
|---|---|---|
| Control plane | Veeam-hosted regional platform service | Veeam-hosted regional platform service |
| Data plane | Veeam-managed Shared data plane | Data plane deployed in the customer AWS account |
| Content-processing location | Supported Veeam-hosted AWS region selected for the connector | Customer AWS region chosen for the data plane |
| Processing resources | Veeam-managed shared resources | Customer-owned AWS compute and storage |
| Infrastructure responsibility | Veeam operates the processing service | Customer deploys the AWS infrastructure; Veeam provides the data plane software |
| Deployment selection | Select SaaS in the connector Hosting Location | Select the deployed data plane in the connector Hosting Location |
| SKU requirement | Foundation SaaS or Advanced SaaS | Foundation Hybrid or Advanced Hybrid |
| Edition feature coverage | Defined by Foundation or Advanced | Defined by Foundation or Advanced |

## SaaS Shared data plane regions and connections

The following regions apply to the SaaS deployment model. Each geography has a regional service control plane and a set of Veeam-managed Shared  data-plane locations for Microsoft 365 content processing. In Hybrid Mode, processing instead runs through the data plane deployed in the customer's AWS account and region.

**SaaS control plane and data plane**

| Geography | Service control plane | Shared data plane |
|---|---|---|
| AMER | Ohio (us-east-2) | N. Virginia (us-east-1); Oregon (us-west-2); Montreal (ca-central-1); Ohio (us-east-2); N. California (us-west-1); São Paulo (sa-east-1) |
| EMEA | Stockholm (eu-north-1) | Frankfurt (eu-central-1); London (eu-west-2); Dublin (eu-west-1); Stockholm (eu-north-1); Milan (eu-south-1); Paris (eu-west-3); Zurich (eu-central-2); Spain/Aragón (eu-south-2); Cape Town (af-south-1) |
| APJ | Tokyo (ap-northeast-1) | Sydney (ap-southeast-2); Hong Kong (ap-east-1); Tokyo (ap-northeast-1); Mumbai (ap-south-1); Singapore (ap-southeast-1); Seoul (ap-northeast-2); Osaka (ap-northeast-3); Jakarta (ap-southeast-3) |

**Microsoft 365 connection** --- An authorized tenant administrator completes the Microsoft 365 connection. Inventory, identity and access analysis, activity collection and content scans provide the context used by the selected capability. Scan definitions control the content included in classification.

**Connected protection and remediation services** --- Use the Veeam Data Cloud connection settings supplied during automatic tenant provisioning and review authentication status. Undo AI requires the protection connection and an available restore point for the affected data. Connect Microsoft Purview for sensitivity labels and configure destination access for quarantine workflows.

## Microsoft 365 capabilities by edition

Veeam Intelligent ResOps for Microsoft 365 is an add-on for Veeam Data Cloud for Microsoft 365 customers. Foundation combines visibility, DataAI intelligence and remediation controls. Advanced adds sensitive-data context, exact duplicate detection and Microsoft Purview labeling.

**Microsoft 365 edition comparison**

| Capability | Foundation | Advanced |
|---|:-:|:-:|
| File Discovery across SharePoint, OneDrive, Teams and Exchange | Included | Included |
| AI Agent and User Discovery | Included | Included |
| Data Access Visibility and Access Activity | Included | Included |
| Contextual Data and AI Intelligence through the Command Graph | Included | Included |
| Intelligence Agent | Included | Included |
| Sensitive Data Discovery and Classification | Sampled signals during inventory | Full scans with evidence and OCR |
| Exact Duplicate File Detection | Not included | Included |
| Obsolete Data Detection and storage cost estimates | Included | Included |
| Backup Intelligence | Included | Included |
| Insight Policies | Metadata-based criteria | Metadata and classified content criteria |
| File Quarantine | Included | Included |
| Data Labeling with Microsoft Purview | Not included | Included |
| Undo AI using Veeam Data Cloud restore points | Included | Included |
| Dashboards and reports | Included | Included |