{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-24T18:06:09.388Z",
  "record_id": "VXI-EXT-PROCUREMENT-AZURE-DIAGNOSTIC-DESTINATION-NETWORK-BOUNDARY-01-v1",
  "record_kind": "external_reference",
  "title": "Azure diagnostic destination network access",
  "system": "Microsoft Azure",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Can an Azure diagnostic setting deliver to a firewalled Storage or Event Hubs destination without the required network allowance?",
  "near_questions": [
    "Can a destination firewall block Azure diagnostic exports?",
    "What network setting supports firewalled diagnostic Storage destinations?",
    "Does creating a diagnostic setting prove delivery?",
    "What evidence detects broken Azure diagnostic routing?"
  ],
  "supported_claims": [
    {
      "claim": "Azure diagnostic guidance requires the trusted Microsoft services network bypass for supported Storage or Event Hubs destinations with firewalls enabled. Creating a diagnostic setting does not itself establish reachable, authorized delivery. These destination-specific rules should not be generalized to every Log Analytics configuration.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "A blanket bypass requirement for every Azure destination",
    "The buyer’s network path and delivered data are untested.",
    "Buyer deployment testing, live runtime enforcement, certification or permission to act",
    "Expanded capabilities or licences for existing INDEX executables"
  ],
  "public_summary": "Azure diagnostic guidance requires the trusted Microsoft services network bypass for supported Storage or Event Hubs destinations with firewalls enabled. Creating a diagnostic setting does not itself establish reachable, authorized delivery. These destination-specific rules should not be generalized to every Log Analytics configuration.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Diagnostic Settings in Azure Monitor - Azure Monitor | Microsoft Learn",
    "source_url": "https://learn.microsoft.com/en-us/azure/azure-monitor/platform/diagnostic-settings",
    "checked_on": "2026-10-24",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-AZURE-DIAGNOSTIC-DESTINATION-NETWORK-BOUNDARY-01-v1",
    "candidate_record_sha256": "0c901a00a6676eb8d09f47390444e839b6e9ddd24c0fb9fa0d6e362390632e34",
    "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 diagnostic guidance requires the trusted Microsoft services network bypass for supported Storage or Event Hubs destinations with firewalls enabled. Creating a diagnostic setting does not itself establish reachable, authorized delivery. These destination-specific rules should not be generalized to every Log Analytics configuration.",
    "required_buyer_context": "Diagnostic setting and destination type; Destination firewall and trusted-services setting; Delivery errors and received records. 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": "Can an Azure diagnostic setting deliver to a firewalled Storage or Event Hubs destination without the required network allowance?",
    "documented_statement": {
      "status": "documented",
      "statement": "Azure diagnostic guidance requires the trusted Microsoft services network bypass for supported Storage or Event Hubs destinations with firewalls enabled. Creating a diagnostic setting does not itself establish reachable, authorized delivery. These destination-specific rules should not be generalized to every Log Analytics configuration.",
      "source_ids": [
        "azure-diagnostics"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "Check destination network settings and actual incoming evidence after configuration changes.",
      "source_ids": [
        "azure-diagnostics"
      ]
    },
    "buyer_evidence_required": [
      "Diagnostic setting and destination type",
      "Destination firewall and trusted-services setting",
      "Delivery errors and received records"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Do not claim continuous export from the setting alone when destination access is unresolved."
    },
    "unknowns": "The buyer’s network path and delivered data are untested.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "The buyer’s network path and delivered data are untested."
    },
    "evidence_sources": [
      {
        "source_id": "azure-diagnostics",
        "url": "https://learn.microsoft.com/en-us/azure/azure-monitor/platform/diagnostic-settings",
        "final_url": "https://learn.microsoft.com/en-us/azure/azure-monitor/data-collection/diagnostic-settings",
        "status": 200,
        "captured_at_utc": "2026-10-24T17:45:38.101Z",
        "sha256": "0f64710aeaf8d7e5d02470aadedc68ea44b34b379d2575177871b7ef6ac82151",
        "bytes": 77834,
        "title": "Diagnostic Settings in Azure Monitor - 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": [
          "Destination limitations",
          "Storage and Event Hubs firewall trusted-services access"
        ],
        "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": "Identify a concrete failure mode in configured audit delivery.",
      "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": "Identify a concrete failure mode in configured audit delivery.",
    "refusal_conditions": [
      "Do not claim continuous export from the setting alone when destination access is unresolved."
    ]
  },
  "niche": {
    "niche_id": "agent-authority-action-evidence",
    "label": "Agent Authority & Action Evidence",
    "classification_id": "audit",
    "classification_label": "Audit, Provenance & Evidence Accountability",
    "topic_id": "audit",
    "buyer_intent": "Identify a concrete failure mode in configured audit delivery.",
    "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-diagnostic-destination-network-boundary",
  "machine_readable_record": "/varexis-index/records/azure-diagnostic-destination-network-boundary.json"
}
