{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-24T17:38:21.804Z",
  "record_id": "VXI-EXT-PROCUREMENT-PURVIEW-EDISCOVERY-HOLD-LOCATION-STATUS-01-v1",
  "record_kind": "external_reference",
  "title": "Purview hold scope and location outcomes",
  "system": "Microsoft Purview",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does naming a custodian in a Purview eDiscovery hold establish that every intended location is successfully held?",
  "near_questions": [
    "How can a Purview hold miss an intended location?",
    "Which report shows eDiscovery hold processing failures?",
    "Does a distribution group represent an eligible hold location?",
    "What evidence confirms scope after creating an eDiscovery hold?"
  ],
  "supported_claims": [
    {
      "claim": "Purview process reports use Locations.csv to expose included locations, processing status and errors. Hold failures can include ineligible objects; the guide distinguishes eligible mailbox and site locations from objects such as distribution groups. A hold action must therefore be reconciled with actual location outcomes.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Legal advice about the adequacy of a hold",
    "Unlisted locations and the actual hold state of buyer data are not independently observed.",
    "Buyer deployment testing, live runtime enforcement, certification or permission to act",
    "Expanded capabilities or licences for existing INDEX executables"
  ],
  "public_summary": "Purview process reports use Locations.csv to expose included locations, processing status and errors. Hold failures can include ineligible objects; the guide distinguishes eligible mailbox and site locations from objects such as distribution groups. A hold action must therefore be reconciled with actual location outcomes.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Process reports in eDiscovery | Microsoft Learn",
    "source_url": "https://learn.microsoft.com/en-us/purview/edisc-process-report",
    "checked_on": "2026-10-24",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-PURVIEW-EDISCOVERY-HOLD-LOCATION-STATUS-01-v1",
    "candidate_record_sha256": "af01f914d023764d097f100e3c136d2904863d6c2566945bf550676c2fd17e6d",
    "method": "Primary documentation reviewed for the published bounded statement.",
    "deployment_tested_by_varexis": false,
    "revalidation": "The delivered snapshot preserves the review date shown. Recheck current primary documentation and deployment context before relying on present applicability; payment does not trigger fresh research."
  },
  "answer_policy": {
    "classification": "DOCUMENTED_WITH_DEPLOYMENT_BOUNDARY",
    "bounded_answer": "Purview process reports use Locations.csv to expose included locations, processing status and errors. Hold failures can include ineligible objects; the guide distinguishes eligible mailbox and site locations from objects such as distribution groups. A hold action must therefore be reconciled with actual location outcomes.",
    "required_buyer_context": "Expected mailbox and site inventory; Hold process Locations.csv and error details; Remediation evidence for omitted or failed locations. Buyer deployment not inspected.",
    "missing_evidence": "A broader claim needs evidence matching the intended use. Payment does not upgrade the evidence state."
  },
  "private_boundary": "Raw logs, thresholds, private paths, source code, protected mechanisms and reconstruction-level details are excluded from public and paid delivery.",
  "decision_profile": {
    "schema": "varexis-vendor-evidence-review/1",
    "review_status": "documentation_review_only",
    "checked_on": "2026-10-24",
    "claim_to_check": "Does naming a custodian in a Purview eDiscovery hold establish that every intended location is successfully held?",
    "documented_statement": {
      "status": "documented",
      "statement": "Purview process reports use Locations.csv to expose included locations, processing status and errors. Hold failures can include ineligible objects; the guide distinguishes eligible mailbox and site locations from objects such as distribution groups. A hold action must therefore be reconciled with actual location outcomes.",
      "source_ids": [
        "purview-reports"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "Match the intended custody locations to successful hold records and resolve failures.",
      "source_ids": [
        "purview-reports"
      ]
    },
    "buyer_evidence_required": [
      "Expected mailbox and site inventory",
      "Hold process Locations.csv and error details",
      "Remediation evidence for omitted or failed locations"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Do not claim complete hold coverage from the custodian label or submitted request alone."
    },
    "unknowns": "Unlisted locations and the actual hold state of buyer data are not independently observed.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "Unlisted locations and the actual hold state of buyer data are not independently observed."
    },
    "evidence_sources": [
      {
        "source_id": "purview-reports",
        "url": "https://learn.microsoft.com/en-us/purview/edisc-process-report",
        "final_url": "https://learn.microsoft.com/en-us/purview/edisc-process-report",
        "status": 200,
        "captured_at_utc": "2026-10-24T17:21:14.703Z",
        "sha256": "28ccf07ae9b1086e1a4b7d5c043e3158fdf92efb192773213a9e4995aad565a5",
        "bytes": 68065,
        "title": "Process reports in eDiscovery | Microsoft Learn",
        "hash_basis": "Decoded HTTP response body bytes",
        "rights_review": "Factual paraphrase and source metadata only; raw source retained privately and not redistributed.",
        "checked_on": "2026-10-24",
        "capture_status": 200,
        "claim_review_completed": true,
        "reviewed_sections": [
          "Understanding search result counts",
          "Missing items",
          "Settings and Locations reports",
          "Hold failures"
        ],
        "version_context": "Rolling official documentation captured 2026-10-24; current model/API version, account settings and applicable billing or retention terms require verification."
      }
    ],
    "observed_deployment": false,
    "commercial_reliance_boundary": "Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.",
    "paid_value": {
      "decision_context": "Find location-level preservation gaps before relying on a hold.",
      "free": "Complete review, sources, practical questions and limitations; may be saved locally.",
      "single_request": "Existing server-saved version-bound route snapshot for later authenticated retrieval.",
      "evidence_receipt": "The same snapshot plus the existing unsigned delivery receipt.",
      "excluded": [
        "Fresh vendor research",
        "Continuous monitoring or change alerts",
        "Testing the buyer configuration",
        "Private evidence or vendor certification"
      ],
      "integrity": "Hashes identify content versions; they do not prove truth or provide a signature."
    },
    "revalidation": {
      "trigger": "A saved purchase does not recheck the source or buyer configuration.",
      "specific_watch": "Recheck the documented behavior, product version and buyer evidence before relying on a current outcome."
    },
    "buyer_relevance": "Find location-level preservation gaps before relying on a hold.",
    "refusal_conditions": [
      "Do not claim complete hold coverage from the custodian label or submitted request alone."
    ]
  },
  "niche": {
    "niche_id": "enterprise-ai-data-custody-exit-assurance",
    "label": "Enterprise AI Data Custody & Exit Assurance",
    "classification_id": "custody",
    "classification_label": "AI Data Custody, Retention & Exit Assurance",
    "topic_id": "custody",
    "buyer_intent": "Find location-level preservation gaps before relying on a hold.",
    "comparison_role": "supplementary_discovery"
  },
  "paid_access_note": "The full published answer and boundaries are free. Paid access saves the selected route and source versions, with an unsigned receipt when purchased. Preview coverage before paying. Fresh research, bespoke assessment and protected evidence are excluded.",
  "service_route": {
    "request_guide": "/varexis-index/request.html",
    "request_workflow": "/varexis-index/request-workflow.json",
    "service_id": "single_request",
    "service_routes_url": "/varexis-index/service-routes.json",
    "payment_required": true,
    "availability_endpoint": "/api/index/capabilities",
    "operational_status": "AUTOMATIC_SERVICE_CAPABILITIES_GATED",
    "checkout_url": "/index-access"
  },
  "authority_boundary": "VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.",
  "human_page": "/varexis-index/catalog.html#purview-ediscovery-hold-location-status",
  "machine_readable_record": "/varexis-index/records/purview-ediscovery-hold-location-status.json"
}
