{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-24T16:34:01.009Z",
  "record_id": "VXI-EXT-PROCUREMENT-AZURE-BLOB-VERSIONING-OVERWRITE-RESIDUAL-01-v1",
  "record_kind": "external_reference",
  "title": "Azure blob overwrites and previous versions",
  "system": "Microsoft Azure",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does overwriting an Azure blob remove the data stored in its previous versions when versioning is enabled?",
  "near_questions": [
    "Can old Azure blob content survive an overwrite?",
    "Does deleting the current Azure blob remove previous versions?",
    "How are Azure blob version IDs relevant to offboarding?",
    "Does Azure blob versioning protect a deleted storage account?"
  ],
  "supported_claims": [
    {
      "claim": "Azure Blob versioning preserves previous versions as immutable content and assigns version IDs to changes. Earlier versions can remain available after modification or deletion of the current blob. Microsoft recommends separate lifecycle or storage-action cleanup for old versions. Versioning itself does not protect against deletion of the storage account or container.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Removal of historical content from an overwrite alone",
    "The number and state of retained versions are not inspected.",
    "Buyer deployment testing, live runtime enforcement, certification or permission to act",
    "Expanded capabilities or licences for existing INDEX executables"
  ],
  "public_summary": "Azure Blob versioning preserves previous versions as immutable content and assigns version IDs to changes. Earlier versions can remain available after modification or deletion of the current blob. Microsoft recommends separate lifecycle or storage-action cleanup for old versions. Versioning itself does not protect against deletion of the storage account or container.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Blob Versioning in Azure Storage - Azure Storage | Microsoft Learn",
    "source_url": "https://learn.microsoft.com/en-us/azure/storage/blobs/versioning-overview",
    "checked_on": "2026-10-24",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-AZURE-BLOB-VERSIONING-OVERWRITE-RESIDUAL-01-v1",
    "candidate_record_sha256": "5857008da99779dc32737d194947c06a74710cd1d7d53252104609e3059a3369",
    "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": "Azure Blob versioning preserves previous versions as immutable content and assigns version IDs to changes. Earlier versions can remain available after modification or deletion of the current blob. Microsoft recommends separate lifecycle or storage-action cleanup for old versions. Versioning itself does not protect against deletion of the storage account or container.",
    "required_buyer_context": "Account versioning state and blob version inventory; Overwrite/deletion events and old-version cleanup configuration; Container/account protection and required deletion boundary. 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 overwriting an Azure blob remove the data stored in its previous versions when versioning is enabled?",
    "documented_statement": {
      "status": "documented",
      "statement": "Azure Blob versioning preserves previous versions as immutable content and assigns version IDs to changes. Earlier versions can remain available after modification or deletion of the current blob. Microsoft recommends separate lifecycle or storage-action cleanup for old versions. Versioning itself does not protect against deletion of the storage account or container.",
      "source_ids": [
        "azure-versioning"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "Reconcile all version identities and cleanup settings rather than inspect only the current blob.",
      "source_ids": [
        "azure-versioning"
      ]
    },
    "buyer_evidence_required": [
      "Account versioning state and blob version inventory",
      "Overwrite/deletion events and old-version cleanup configuration",
      "Container/account protection and required deletion boundary"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Do not declare prior content erased from a successful overwrite of the current blob."
    },
    "unknowns": "The number and state of retained versions are not inspected.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "The number and state of retained versions are not inspected."
    },
    "evidence_sources": [
      {
        "source_id": "azure-versioning",
        "url": "https://learn.microsoft.com/en-us/azure/storage/blobs/versioning-overview",
        "final_url": "https://learn.microsoft.com/en-us/azure/storage/blobs/versioning-overview",
        "status": 200,
        "captured_at_utc": "2026-10-24T16:04:00.821Z",
        "sha256": "72526d28a08887a15a80f0599d168725f61c83ec73b2dfb2c590c50f80f50f9b",
        "bytes": 82953,
        "title": "Blob Versioning in Azure Storage - Azure Storage | 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,
        "version_context": "Rolling official vendor documentation captured on 2026-10-24; account tier, service version, enabled features and buyer configuration require separate verification.",
        "reviewed_sections": [
          "Immutable previous versions",
          "Cleanup and account/container exclusions"
        ]
      }
    ],
    "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 historical data that remains after an application replaces its live blob.",
      "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 historical data that remains after an application replaces its live blob.",
    "refusal_conditions": [
      "Do not declare prior content erased from a successful overwrite of the current blob."
    ]
  },
  "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 historical data that remains after an application replaces its live blob.",
    "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-blob-versioning-overwrite-residual",
  "machine_readable_record": "/varexis-index/records/azure-blob-versioning-overwrite-residual.json"
}
