{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-29T21:43:00.943093Z",
  "record_id": "VXI-EXT-ICE06-AZURE-BACKUP-SOFTDELETE-ROLLOUT-API-SCOPE-01-v1",
  "record_kind": "external_reference",
  "title": "Azure backup softdelete rollout api scope",
  "system": "Microsoft",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does an Azure Backup delete operation have the same retention effect in every region and API version?",
  "near_questions": [
    "Azure Backup soft delete preview GA API version",
    "backup delete regional secure by default scope",
    "Recovery Services deletion retention rollout",
    "Azure backup delete response recoverable state"
  ],
  "supported_claims": [
    {
      "claim": "Microsoft's reviewed secure-by-default guidance distinguishes preview-region behaviour from GA Recovery Services vault enforcement. Preview behaviour depends on client/API versions and prior configuration, while GA enforcement spans API versions. Soft-deleted data remains recoverable for the configured period. The region, vault type, rollout stage and request version are necessary to interpret a delete result.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Do not apply one rollout's behaviour globally or equate a delete response with permanent deletion. Recheck the current regional matrix before reliance.",
    "Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.",
    "No expanded capabilities or licences for existing INDEX executables."
  ],
  "public_summary": "Microsoft's reviewed secure-by-default guidance distinguishes preview-region behaviour from GA Recovery Services vault enforcement. Preview behaviour depends on client/API versions and prior configuration, while GA enforcement spans API versions. Soft-deleted data remains recoverable for the configured period. The region, vault type, rollout stage and request version are necessary to interpret a delete result.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Microsoft: Enhanced soft delete for Azure Backup",
    "source_url": "https://learn.microsoft.com/azure/backup/backup-azure-enhanced-soft-delete-about",
    "checked_on": "2026-10-29",
    "candidate_record_id": "VXI-EXT-ICE06-AZURE-BACKUP-SOFTDELETE-ROLLOUT-API-SCOPE-01-v1",
    "candidate_record_sha256": "42abad253a646f56b0acb911fe7f1a697f0c509a2764bae7a3a16c9cd3fa7516",
    "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's reviewed secure-by-default guidance distinguishes preview-region behaviour from GA Recovery Services vault enforcement. Preview behaviour depends on client/API versions and prior configuration, while GA enforcement spans API versions. Soft-deleted data remains recoverable for the configured period. The region, vault type, rollout stage and request version are necessary to interpret a delete result.",
    "required_buyer_context": "region and rollout status; vault type; soft-delete setting; client or API version; backup-item state and retention. 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-29",
    "claim_to_check": "Does an Azure Backup delete operation have the same retention effect in every region and API version?",
    "documented_statement": {
      "status": "documented",
      "statement": "Microsoft's reviewed secure-by-default guidance distinguishes preview-region behaviour from GA Recovery Services vault enforcement. Preview behaviour depends on client/API versions and prior configuration, while GA enforcement spans API versions. Soft-deleted data remains recoverable for the configured period. The region, vault type, rollout stage and request version are necessary to interpret a delete result.",
      "source_ids": [
        "azure-softdelete"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "An exit workflow upgrades its API or moves regions without revisiting deletion assumptions. The same nominal delete action can retain recoverable data under different rules. Adds Azure rollout- and interface-dependent deletion semantics, rather than AWS lock settings. This is an operational review inference, not an observed deployment outcome.",
      "source_ids": [
        "azure-softdelete"
      ]
    },
    "buyer_evidence_required": [
      "region and rollout status",
      "vault type",
      "soft-delete setting",
      "client or API version",
      "backup-item state and retention"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Do not apply one rollout's behaviour globally or equate a delete response with permanent deletion. Recheck the current regional matrix before reliance."
    },
    "unknowns": "The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "No buyer deployment or transaction was observed."
    },
    "evidence_sources": [
      {
        "source_id": "azure-softdelete",
        "url": "https://learn.microsoft.com/azure/backup/backup-azure-enhanced-soft-delete-about",
        "final_url": "https://learn.microsoft.com/en-us/azure/backup/secure-by-default",
        "captured_at_utc": "2026-10-29T19:18:24.077742+00:00",
        "status": 200,
        "content_type": "text/html",
        "bytes": 67223,
        "sha256": "511de4ef4a167399fcba059270326c174fbfc447317a90211797fed412c8c507",
        "publisher": "Microsoft",
        "version_context": "Rolling official documentation; applicability is limited to the exact captured response and its stated service, API and feature constraints. Recheck present support before current reliance. Source captured 2026-10-29T19:18:24.077742+00:00.",
        "rights_review": "Public original factual paraphrase and attributed source metadata only. Captured documentation bodies, code examples, images and vendor marks remain private. No vendor software licence, certification or buyer deployment assurance is granted.",
        "capture_integrity_verified": true,
        "source_assertion_reviewed": true,
        "title": "Microsoft: Enhanced soft delete for Azure Backup",
        "checked_on": "2026-10-29",
        "capture_status": 200,
        "claim_review_completed": true,
        "hash_basis": "SHA-256 of captured HTTP response body bytes",
        "reviewed_sections": [
          "API considerations for soft delete",
          "Soft delete of recovery points"
        ]
      }
    ],
    "observed_deployment": false,
    "commercial_reliance_boundary": "Documentation supports only the stated boundary. Existing licensed checkers analyse supported supplied declarations locally; they do not inspect provider accounts, verify live behaviour, enforce decisions or certify compliance.",
    "paid_value": {
      "decision_context": "An exit workflow upgrades its API or moves regions without revisiting deletion assumptions. The same nominal delete action can retain recoverable data under different rules.",
      "free": "Complete source review, questions, provenance and limitations; free to read and save locally.",
      "single_request": "Unavailable for this publication-only record; historical saved retrieval is unchanged.",
      "evidence_receipt": "Unavailable for this publication-only record; no paid retrieval entitlement is added.",
      "excluded": [
        "Fresh source research",
        "Native provider integration or schema support",
        "Live inspection or runtime enforcement",
        "Payment settlement or verified deletion",
        "Certification or expanded licences"
      ],
      "integrity": "Hashes identify content versions; they do not prove factual truth or provide a signature."
    },
    "revalidation": {
      "trigger": "Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included.",
      "specific_watch": "API considerations for soft delete"
    },
    "buyer_relevance": "An exit workflow upgrades its API or moves regions without revisiting deletion assumptions. The same nominal delete action can retain recoverable data under different rules.",
    "refusal_conditions": [
      "Do not apply one rollout's behaviour globally or equate a delete response with permanent deletion. Recheck the current regional matrix before reliance.",
      "Do not infer deployment conformance, authority or successful outcomes from source documentation."
    ],
    "decision_context": {
      "operator": "Data custody and recovery operator",
      "scenario": "An exit workflow upgrades its API or moves regions without revisiting deletion assumptions.",
      "consequence": "The same nominal delete action can retain recoverable data under different rules.",
      "confidence": "Primary documentation assertion supported; deployment applicability unverified"
    },
    "novelty_review": {
      "candidate_id": "ICE06-DB7CCC2E84E6",
      "disposition": "EXTENSION",
      "nearest_record_id": "VXI-EXT-PROCUREMENT-AWS-BACKUP-VAULT-LOCK-GRACE-RETENTION-BOUNDARY-01-v1",
      "nearest_record_url": "/varexis-index/records/aws-backup-vault-lock-grace-retention-boundary.json",
      "nearest_record_sha256": "7373f9cabaf311d1ea0f62d83a0fbd4b42f6d84b57ff6e52f72398cd4dc71deb",
      "material_distinction": "Adds Azure rollout- and interface-dependent deletion semantics, rather than AWS lock settings.",
      "independent_challenge": "PASS"
    },
    "optional_selection": {
      "guide_id": "data-exit-audit-evidence",
      "guide_url": "/index-guides/data-exit-audit-evidence",
      "guide_manifest": "/varexis-index/decision-guides.json",
      "checker": {
        "product_id": "agent-data-exit",
        "price_gbp_excluding_vat": 79,
        "purchase_url": "/index-access?route=agentic_pack_data_exit_v1",
        "licence_scope": "Existing separate internal-use licence; subscriptions do not include the executable.",
        "benefit": "Optional local analysis of supported supplied declarations only; no native provider integration or verification is added."
      },
      "boundary": "Optional adjacent workflow only. This review does not extend a checker input schema or implement native provider validation. Preserve the six canonical guides unchanged."
    },
    "exact_access": {
      "endpoint": "/mcp/catalogue",
      "tool": "get_publication_record",
      "arguments": {
        "record_id": "VXI-EXT-ICE06-AZURE-BACKUP-SOFTDELETE-ROLLOUT-API-SCOPE-01-v1"
      },
      "record_url": "/varexis-index/records/azure-backup-softdelete-rollout-api-scope.json",
      "original_mcp_search": false,
      "paid_saved_retrieval": false
    }
  },
  "niche": {
    "niche_id": "ice06-custody",
    "label": "AI Data Custody, Retention & Exit Assurance",
    "classification_id": "custody",
    "classification_label": "AI Data Custody, Retention & Exit Assurance",
    "topic_id": "custody",
    "buyer_intent": "An exit workflow upgrades its API or moves regions without revisiting deletion assumptions. The same nominal delete action can retain recoverable data under different rules.",
    "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-backup-softdelete-rollout-api-scope",
  "machine_readable_record": "/varexis-index/records/azure-backup-softdelete-rollout-api-scope.json"
}