{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-18T19:34:16.969Z",
  "record_id": "VXI-EXT-PROCUREMENT-AZURE-SEARCH-SOURCE-DELETE-INDEXER-POLICY-RESIDUAL-01-v1",
  "record_kind": "external_reference",
  "title": "Azure AI Search: Source deletion needs index-side evidence",
  "system": "Azure AI Search",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Can source document deletion leave retrievable copies in an Azure AI Search index?",
  "near_questions": [
    "Will deleting an Azure blob automatically remove its search document?",
    "Can adding Azure Search deletion detection later remove old orphans?",
    "Does Azure AI Search soft deletion cover one-to-many indexing?",
    "What indexer timing evidence is needed before closing source cleanup?"
  ],
  "supported_claims": [
    {
      "claim": "Microsoft requires a deletion-detection strategy from the first indexer run; adding one later and resetting the indexer does not remove documents deleted before the policy existed. Native blob soft deletion must remain detectable until the indexer processes it. The documented soft-delete policies do not cover one-to-many indexing, which requires explicit index deletion requests.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Verified index erasure, universal connector coverage or removal from external copies",
    "Buyer deployment testing, live runtime enforcement, certification or permission to act",
    "Expanded capabilities or licences for existing INDEX executables"
  ],
  "public_summary": "Microsoft requires a deletion-detection strategy from the first indexer run; adding one later and resetting the indexer does not remove documents deleted before the policy existed. Native blob soft deletion must remain detectable until the indexer processes it. The documented soft-delete policies do not cover one-to-many indexing, which requires explicit index deletion requests.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Changed and Deleted Blobs - Azure AI Search | Microsoft Learn",
    "source_url": "https://learn.microsoft.com/en-us/azure/search/search-how-to-index-azure-blob-changed-deleted",
    "checked_on": "2026-10-18",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-AZURE-SEARCH-SOURCE-DELETE-INDEXER-POLICY-RESIDUAL-01-v1",
    "candidate_record_sha256": "99764a97ff7878448aa766c522d01784ecfa64fcedf9691c370ea5b646383f05",
    "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": "Microsoft requires a deletion-detection strategy from the first indexer run; adding one later and resetting the indexer does not remove documents deleted before the policy existed. Native blob soft deletion must remain detectable until the indexer processes it. The documented soft-delete policies do not cover one-to-many indexing, which requires explicit index deletion requests.",
    "required_buyer_context": "Indexer/data-source type, key mapping and deletion policy from initial run. Soft-delete retention, deletion timestamps and successful indexer processing. Index inventory and explicit deletion results for orphaned or one-to-many documents. 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-18",
    "claim_to_check": "Can source document deletion leave retrievable copies in an Azure AI Search index?",
    "documented_statement": {
      "status": "documented",
      "statement": "Microsoft requires a deletion-detection strategy from the first indexer run; adding one later and resetting the indexer does not remove documents deleted before the policy existed. Native blob soft deletion must remain detectable until the indexer processes it. The documented soft-delete policies do not cover one-to-many indexing, which requires explicit index deletion requests.",
      "source_ids": [
        "azure-search-delete"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "Source absence alone does not establish removal from the search index.",
      "source_ids": [
        "azure-search-delete"
      ]
    },
    "buyer_evidence_required": [
      "Indexer/data-source type, key mapping and deletion policy from initial run.",
      "Soft-delete retention, deletion timestamps and successful indexer processing.",
      "Index inventory and explicit deletion results for orphaned or one-to-many documents."
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Refuse complete-index-cleanup claims without applicable policy and observed index-side results."
    },
    "unknowns": "Historical indexer configuration and residual search results are unobserved.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "Historical indexer configuration and residual search results are unobserved."
    },
    "evidence_sources": [
      {
        "source_id": "azure-search-delete",
        "url": "https://learn.microsoft.com/en-us/azure/search/search-how-to-index-azure-blob-changed-deleted",
        "final_url": "https://learn.microsoft.com/en-us/azure/search/search-how-to-index-azure-blob-changed-deleted",
        "title": "Changed and Deleted Blobs - Azure AI Search | Microsoft Learn",
        "checked_on": "2026-10-18",
        "captured_at_utc": "2026-10-18T19:20:55.815Z",
        "version_context": "Azure Storage indexer deletion guide; page last updated 2026-06-02.",
        "sha256": "aba0af57a1521ed9a3b177ed5231e1590f14b22684d2ad0f73822771fb63fe88",
        "bytes": 62045,
        "hash_basis": "Decoded HTTP response body bytes; identifies captured content, not truth or certification",
        "reviewed_sections": [
          "Deletion detection strategy from first run",
          "Native blob soft delete",
          "Limitations"
        ],
        "capture_status": 200,
        "rights_review": "Factual paraphrase and source metadata only; response body retained privately and not redistributed."
      }
    ],
    "observed_deployment": false,
    "commercial_reliance_boundary": "Documentation review only; no supplier clearance, configuration audit, observed execution or certification of the buyer's claim.",
    "paid_value": {
      "decision_context": "Identify residual resources before closing a data-retention or exit decision.",
      "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 indexer type, key mappings, one-to-many behavior and retention windows."
    },
    "buyer_relevance": "Identify residual resources before closing a data-retention or exit decision.",
    "refusal_conditions": [
      "Refuse complete-index-cleanup claims without applicable policy and observed index-side results."
    ]
  },
  "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": "Identify residual resources before closing a data-retention or exit decision.",
    "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#azure-search-source-delete-indexer-policy-residual",
  "machine_readable_record": "/varexis-index/records/azure-search-source-delete-indexer-policy-residual.json"
}
