{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-24T18:06:09.388Z",
  "record_id": "VXI-EXT-PROCUREMENT-AZURE-LOG-RETENTION-QUERY-MODE-BOUNDARY-01-v1",
  "record_kind": "external_reference",
  "title": "Azure retained logs and query availability",
  "system": "Microsoft Azure",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does total Azure Log Analytics retention guarantee the same interactive query window for every table plan?",
  "near_questions": [
    "Can Azure long-term retained logs require a search job?",
    "How does Auxiliary query retention differ from Basic?",
    "Does total retention equal interactive query availability?",
    "What should be checked before declaring old Azure logs missing?"
  ],
  "supported_claims": [
    {
      "claim": "Azure distinguishes analytics retention from long-term retention. Analytics and Basic long-term data is retrieved through search jobs, while Auxiliary data remains queryable throughout its total retention period. The table plan and retention state therefore determine the available retrieval method; retained data is not always available through the same query path.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Universal interactive access throughout every retention period",
    "The buyer’s retained rows and successful recovery are unknown.",
    "Buyer deployment testing, live runtime enforcement, certification or permission to act",
    "Expanded capabilities or licences for existing INDEX executables"
  ],
  "public_summary": "Azure distinguishes analytics retention from long-term retention. Analytics and Basic long-term data is retrieved through search jobs, while Auxiliary data remains queryable throughout its total retention period. The table plan and retention state therefore determine the available retrieval method; retained data is not always available through the same query path.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Manage Data Retention in a Log Analytics Workspace - Azure Monitor | Microsoft Learn",
    "source_url": "https://learn.microsoft.com/en-us/azure/azure-monitor/logs/data-retention-configure",
    "checked_on": "2026-10-24",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-AZURE-LOG-RETENTION-QUERY-MODE-BOUNDARY-01-v1",
    "candidate_record_sha256": "6c2779931cb2d6ddf83dc0a05f2eba48f964ca7c39ddc5b72d978fd98cb4e1f7",
    "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 distinguishes analytics retention from long-term retention. Analytics and Basic long-term data is retrieved through search jobs, while Auxiliary data remains queryable throughout its total retention period. The table plan and retention state therefore determine the available retrieval method; retained data is not always available through the same query path.",
    "required_buyer_context": "Table plan and analytics/total retention settings; Requested time range and query or search-job mode; Retrieval result and coverage assessment. 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 total Azure Log Analytics retention guarantee the same interactive query window for every table plan?",
    "documented_statement": {
      "status": "documented",
      "statement": "Azure distinguishes analytics retention from long-term retention. Analytics and Basic long-term data is retrieved through search jobs, while Auxiliary data remains queryable throughout its total retention period. The table plan and retention state therefore determine the available retrieval method; retained data is not always available through the same query path.",
      "source_ids": [
        "azure-retention"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "Verify table plan, time range and retrieval mode before treating an empty interactive query as missing evidence.",
      "source_ids": [
        "azure-retention"
      ]
    },
    "buyer_evidence_required": [
      "Table plan and analytics/total retention settings",
      "Requested time range and query or search-job mode",
      "Retrieval result and coverage assessment"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Do not infer deletion solely from an inappropriate query path."
    },
    "unknowns": "The buyer’s retained rows and successful recovery are unknown.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "The buyer’s retained rows and successful recovery are unknown."
    },
    "evidence_sources": [
      {
        "source_id": "azure-retention",
        "url": "https://learn.microsoft.com/en-us/azure/azure-monitor/logs/data-retention-configure",
        "final_url": "https://learn.microsoft.com/en-us/azure/azure-monitor/logs/data-retention-configure",
        "status": 200,
        "captured_at_utc": "2026-10-24T17:45:38.044Z",
        "sha256": "aac422ae6058ae6aa08c13112d9671628b9d34fd25458541891c5f8a9a3b7500",
        "bytes": 90557,
        "title": "Manage Data Retention in a Log Analytics Workspace - Azure Monitor | 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": [
          "Analytics, long-term and total retention",
          "Table plan differences"
        ],
        "version_context": "Rolling official documentation captured 2026-10-24; verify the applicable deployment, API edition and configuration before reliance."
      }
    ],
    "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": "Choose the correct retrieval path during an audit or recovery investigation.",
      "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": "Choose the correct retrieval path during an audit or recovery investigation.",
    "refusal_conditions": [
      "Do not infer deletion solely from an inappropriate query path."
    ]
  },
  "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": "Choose the correct retrieval path during an audit or recovery investigation.",
    "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-log-retention-query-mode-boundary",
  "machine_readable_record": "/varexis-index/records/azure-log-retention-query-mode-boundary.json"
}
