{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-16T13:36:43.315Z",
  "record_id": "VXI-EXT-PROCUREMENT-AZURE-POLICY-MODE-01-v1",
  "record_kind": "external_reference",
  "title": "Azure Policy: Evaluation and enforcement modes",
  "system": "Azure Policy",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does an assigned Azure policy prove non-compliant changes are blocked?",
  "near_questions": [
    "Is the assignment in DoNotEnforce mode?",
    "Does it still evaluate compliance?",
    "Is Disabled a different effect?",
    "Can a remediation task still run?",
    "Which child scopes are excluded?",
    "Do overrides change the effect?",
    "Is the definition version fixed?",
    "Does a compliance result prove a change was blocked?",
    "Which activity was actually denied?",
    "Are staged enrollment settings relevant?",
    "What evidence proves effective policy scope?",
    "Can I save the policy-mode distinction?"
  ],
  "supported_claims": [
    {
      "claim": "DoNotEnforce evaluates compliance without enforcing the policy effect. Disabled effect is different because it avoids evaluation. Assignment exclusions and scoped overrides also matter. Remediation tasks for deployIfNotExists can still be started in DoNotEnforce mode; that mode is not a blanket no-change guarantee.",
      "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": "DoNotEnforce evaluates compliance without enforcing the policy effect. Disabled effect is different because it avoids evaluation. Assignment exclusions and scoped overrides also matter. Remediation tasks for deployIfNotExists can still be started in DoNotEnforce mode; that mode is not a blanket no-change guarantee.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Azure Policy assignment structure",
    "source_url": "https://learn.microsoft.com/en-us/azure/governance/policy/concepts/assignment-structure",
    "checked_on": "2026-10-16",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-AZURE-POLICY-MODE-01-v1",
    "candidate_record_sha256": "e5193f1203db0c11fde3dea5c4b35ad391e5578a7d0cc23a21dfd25e463cb819",
    "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": "DoNotEnforce evaluates compliance without enforcing the policy effect. Disabled effect is different because it avoids evaluation. Assignment exclusions and scoped overrides also matter. Remediation tasks for deployIfNotExists can still be started in DoNotEnforce mode; that mode is not a blanket no-change guarantee.",
    "required_buyer_context": "Assignment mode, definition version, scope, overrides and remediation. Effective configuration and dated operational evidence have not been 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-16",
    "claim_to_check": "A policy assignment proves blocking, or DoNotEnforce prevents every change.",
    "documented_statement": {
      "status": "documented",
      "statement": "DoNotEnforce evaluates compliance without enforcing the policy effect. Disabled effect is different because it avoids evaluation. Assignment exclusions and scoped overrides also matter. Remediation tasks for deployIfNotExists can still be started in DoNotEnforce mode; that mode is not a blanket no-change guarantee.",
      "source_ids": [
        "azure-policy"
      ]
    },
    "buyer_evidence_required": [
      "Assignment mode, definition and effect.",
      "Scope exclusions and overrides.",
      "Remediation tasks and actual enforcement evidence."
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Check evaluation, enforcement and remediation separately before describing the control."
    },
    "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-policy",
        "url": "https://learn.microsoft.com/en-us/azure/governance/policy/concepts/assignment-structure",
        "final_url": "https://learn.microsoft.com/en-us/azure/governance/policy/concepts/assignment-structure",
        "title": "Azure Policy assignment structure",
        "checked_on": "2026-10-16",
        "sha256": "aad8c906cd0bb6dfc441119b1679d3b878f81a024622a600e61712243c227e03",
        "bytes": 74940
      }
    ],
    "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": "Preserve the evidence boundary between a compliance report and enforced prevention.",
      "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": "Assignment mode, definition version, scope, overrides and remediation."
    }
  },
  "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-policy-assignment-enforcement-mode-boundary",
  "machine_readable_record": "/varexis-index/records/azure-policy-assignment-enforcement-mode-boundary.json"
}