{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-14T20:21:57.226Z",
  "record_id": "VXI-EXT-PROCUREMENT-AZURE-LOCK-PLANE-01-v1",
  "record_kind": "external_reference",
  "title": "Azure locks: Resource protection does not cover every data operation",
  "system": "Azure Resource Manager",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does an Azure read-only resource lock prevent changes to stored data?",
  "near_questions": [
    "Does a cloud resource lock make its data immutable?",
    "Can database rows change under an Azure read-only lock?",
    "Which API plane does a resource lock protect?",
    "Does a storage lock stop blob deletion through every endpoint?",
    "What evidence distinguishes resource deletion from data deletion?",
    "Can inherited locks cover management actions only?",
    "Which permissions govern the unprotected data plane?",
    "Does a failed management request prove the data is protected?",
    "What should procurement ask about immutable storage claims?",
    "Can a lock also block unexpected management reads?",
    "When should a data-protection claim remain qualified?",
    "Can I save an Azure lock-scope review?"
  ],
  "supported_claims": [
    {
      "claim": "Resource locks apply to control-plane operations. The documentation explicitly separates data-plane activity, including changes to database or storage contents that a resource lock does not prevent. Identify the actual operation and endpoint before accepting a claim that the locked resource is entirely immutable.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Verified buyer configuration or effective access rights",
    "Independent execution, completeness or security testing",
    "Vendor certification, legal compliance or guaranteed suitability"
  ],
  "public_summary": "Resource locks apply to control-plane operations. The documentation explicitly separates data-plane activity, including changes to database or storage contents that a resource lock does not prevent. Identify the actual operation and endpoint before accepting a claim that the locked resource is entirely immutable.",
  "related_record_ids": [
    "VXI-EXT-PROCUREMENT-KUBERNETES-SECRET-LIST-01-v1",
    "VXI-EXT-PROCUREMENT-IAM-BOUNDARY-GRANTS-01-v1",
    "VXI-EXT-PROCUREMENT-CIRCLECI-CONTEXT-RESTRICTION-01-v1"
  ],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Azure resource lock scope",
    "source_url": "https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/lock-resources",
    "checked_on": "2026-10-14",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-AZURE-LOCK-PLANE-01-v1",
    "candidate_record_sha256": "343e5c9c81c5823d292a465d991e02d42c6dbf610dd9148cd7ee45c06d8904f0",
    "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": "Resource locks apply to control-plane operations. The documentation explicitly separates data-plane activity, including changes to database or storage contents that a resource lock does not prevent. Identify the actual operation and endpoint before accepting a claim that the locked resource is entirely immutable.",
    "required_buyer_context": "Locked resource, operation, control/data plane and effective data permissions.",
    "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-14",
    "claim_to_check": "A resource lock prevents all changes or deletion of the data inside it.",
    "documented_statement": {
      "status": "documented",
      "statement": "Resource locks apply to control-plane operations. The documentation explicitly separates data-plane activity, including changes to database or storage contents that a resource lock does not prevent. Identify the actual operation and endpoint before accepting a claim that the locked resource is entirely immutable.",
      "source_ids": [
        "azure-lock"
      ]
    },
    "buyer_evidence_required": [
      "Lock type and inherited resource scope.",
      "The actual operation and service endpoint used.",
      "Data-plane authorisation and separate retention/deletion controls."
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Qualify immutability claims that rely solely on a management lock."
    },
    "unknowns": "The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.",
    "evidence_sources": [
      {
        "source_id": "azure-lock",
        "url": "https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/lock-resources",
        "final_url": "https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/lock-resources",
        "title": "Azure resource lock scope",
        "checked_on": "2026-10-14",
        "sha256": "6ee71614609f2c0c331c423a4724aef966e9b40fc0635da6a3d1e1fef952be7c",
        "bytes": 82612
      }
    ],
    "observed_deployment": false,
    "commercial_reliance_boundary": "Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.",
    "paid_value": {
      "decision_context": "Save why a management-lock screenshot was insufficient evidence for data immutability.",
      "free": "Complete review, practical questions, sources 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": "Lock scope, operation paths and separate data controls."
    }
  },
  "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-resource-lock-data-plane",
  "machine_readable_record": "/varexis-index/records/azure-resource-lock-data-plane.json"
}