{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-18T19:34:16.969Z",
  "record_id": "VXI-EXT-PROCUREMENT-DATABRICKS-EXTERNAL-LOCATION-UNBIND-EXISTING-TABLE-ACCESS-01-v1",
  "record_kind": "external_reference",
  "title": "Databricks: Unbinding a location can leave existing tables usable",
  "system": "Databricks",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does unbinding a Databricks external location from a workspace stop access through tables already created there?",
  "near_questions": [
    "Will Databricks external tables stop working after location unbinding?",
    "When does Databricks check an external-location workspace binding?",
    "Are Databricks catalog bindings the same as external-location bindings?",
    "What residual table access must be checked after restricting a location?"
  ],
  "supported_claims": [
    {
      "claim": "Databricks checks an external location's workspace binding when privileges against that location are exercised, such as creating an external table. Its GCP guide explicitly says that an external table continues to function if the location is subsequently unbound. Catalog bindings provide a separate way to control the workspaces in which catalog contents are available.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Universal revocation, direct cloud-storage denial or tested table isolation",
    "Buyer deployment testing, live runtime enforcement, certification or permission to act",
    "Expanded capabilities or licences for existing INDEX executables"
  ],
  "public_summary": "Databricks checks an external location's workspace binding when privileges against that location are exercised, such as creating an external table. Its GCP guide explicitly says that an external table continues to function if the location is subsequently unbound. Catalog bindings provide a separate way to control the workspaces in which catalog contents are available.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Manage external locations | Databricks on Google Cloud",
    "source_url": "https://docs.databricks.com/gcp/en/connect/unity-catalog/cloud-storage/manage-external-locations",
    "checked_on": "2026-10-18",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-DATABRICKS-EXTERNAL-LOCATION-UNBIND-EXISTING-TABLE-ACCESS-01-v1",
    "candidate_record_sha256": "18f01b5bd0a05e93d265e1821842af9c972414c6356be90a6e27bad1eb8ce1cf",
    "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": "Databricks checks an external location's workspace binding when privileges against that location are exercised, such as creating an external table. Its GCP guide explicitly says that an external table continues to function if the location is subsequently unbound. Catalog bindings provide a separate way to control the workspaces in which catalog contents are available.",
    "required_buyer_context": "Metastore, workspace, cloud and external-location binding state. Previously created external tables, catalog bindings and effective grants. Post-change access observations for each intended data path. 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": "Does unbinding a Databricks external location from a workspace stop access through tables already created there?",
    "documented_statement": {
      "status": "documented",
      "statement": "Databricks checks an external location's workspace binding when privileges against that location are exercised, such as creating an external table. Its GCP guide explicitly says that an external table continues to function if the location is subsequently unbound. Catalog bindings provide a separate way to control the workspaces in which catalog contents are available.",
      "source_ids": [
        "databricks-external"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "A location binding change is not sufficient evidence of universal data offboarding.",
      "source_ids": [
        "databricks-external"
      ]
    },
    "buyer_evidence_required": [
      "Metastore, workspace, cloud and external-location binding state.",
      "Previously created external tables, catalog bindings and effective grants.",
      "Post-change access observations for each intended data path."
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Refuse all-access-removed claims based only on the external-location binding."
    },
    "unknowns": "Buyer tables, cloud credentials and grants were not inspected; other cloud variants need their own source check.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "Buyer tables, cloud credentials and grants were not inspected; other cloud variants need their own source check."
    },
    "evidence_sources": [
      {
        "source_id": "databricks-external",
        "url": "https://docs.databricks.com/gcp/en/connect/unity-catalog/cloud-storage/manage-external-locations",
        "final_url": "https://docs.databricks.com/gcp/en/connect/unity-catalog/cloud-storage/manage-external-locations",
        "title": "Manage external locations | Databricks on Google Cloud",
        "checked_on": "2026-10-18",
        "captured_at_utc": "2026-10-18T19:20:55.189Z",
        "version_context": "Databricks GCP Unity Catalog documentation; other clouds not inferred.",
        "sha256": "90adbfc51a33598e9811b49eb40a7c5160df469c3135d39b73d49b67a2b69720",
        "bytes": 128713,
        "hash_basis": "Decoded HTTP response body bytes; identifies captured content, not truth or certification",
        "reviewed_sections": [
          "Assign an external location to specific workspaces",
          "Important behavior of workspace bindings"
        ],
        "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 which declared controls can support an agent authority 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 external-table behavior and catalog/location bindings after workspace or privilege changes."
    },
    "buyer_relevance": "Identify which declared controls can support an agent authority decision.",
    "refusal_conditions": [
      "Refuse all-access-removed claims based only on the external-location binding."
    ]
  },
  "niche": {
    "niche_id": "agent-authority-action-evidence",
    "label": "Agent Authority & Action Evidence",
    "classification_id": "governance",
    "classification_label": "Agent Governance & Policy Boundaries",
    "topic_id": "governance",
    "buyer_intent": "Identify which declared controls can support an agent authority 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#databricks-external-location-unbind-existing-table-access",
  "machine_readable_record": "/varexis-index/records/databricks-external-location-unbind-existing-table-access.json"
}
