{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-24T17:09:18.442Z",
  "record_id": "VXI-EXT-PROCUREMENT-EXCHANGE-APPLICATION-RBAC-ADDITIVE-ENTRA-GRANTS-01-v1",
  "record_kind": "external_reference",
  "title": "Exchange application RBAC and additive grants",
  "system": "Microsoft Exchange Online",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does a scoped Exchange application RBAC assignment restrict an existing unscoped Entra application grant?",
  "near_questions": [
    "Can Exchange application RBAC leave broader Entra permissions effective?",
    "Which grants must be checked before restricting an app to selected mailboxes?",
    "Do Exchange application permissions combine with Microsoft Entra grants?",
    "Does an Application Access Policy constrain both Exchange grant paths?"
  ],
  "supported_claims": [
    {
      "claim": "Microsoft describes Exchange application RBAC and Entra application permissions as additive. An unscoped Entra grant can therefore provide access beyond a scoped RBAC assignment. Application Access Policies constrain the Entra grant path; they do not turn the separate RBAC assignment into a restriction on all other grants.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Universal mailbox restriction from one scoped grant",
    "Effective grants and mailbox access in the buyer tenant are not inspected.",
    "Buyer deployment testing, live runtime enforcement, certification or permission to act",
    "Expanded capabilities or licences for existing INDEX executables"
  ],
  "public_summary": "Microsoft describes Exchange application RBAC and Entra application permissions as additive. An unscoped Entra grant can therefore provide access beyond a scoped RBAC assignment. Application Access Policies constrain the Entra grant path; they do not turn the separate RBAC assignment into a restriction on all other grants.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Role Based Access Control for Applications in Exchange Online | Microsoft Learn",
    "source_url": "https://learn.microsoft.com/en-us/exchange/permissions-exo/application-rbac",
    "checked_on": "2026-10-24",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-EXCHANGE-APPLICATION-RBAC-ADDITIVE-ENTRA-GRANTS-01-v1",
    "candidate_record_sha256": "296ef423ba0e90a026361f00dcf3e5dd69ac7b71dc766b8c5a639fff087aefea",
    "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": "Microsoft describes Exchange application RBAC and Entra application permissions as additive. An unscoped Entra grant can therefore provide access beyond a scoped RBAC assignment. Application Access Policies constrain the Entra grant path; they do not turn the separate RBAC assignment into a restriction on all other grants.",
    "required_buyer_context": "Application identity and Entra consented permissions; Exchange RBAC assignments and resource scopes; Applicable Application Access Policies and mailbox access evidence. 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 a scoped Exchange application RBAC assignment restrict an existing unscoped Entra application grant?",
    "documented_statement": {
      "status": "documented",
      "statement": "Microsoft describes Exchange application RBAC and Entra application permissions as additive. An unscoped Entra grant can therefore provide access beyond a scoped RBAC assignment. Application Access Policies constrain the Entra grant path; they do not turn the separate RBAC assignment into a restriction on all other grants.",
      "source_ids": [
        "exchange-rbac"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "Evaluate the union of effective grant paths before accepting a mailbox restriction.",
      "source_ids": [
        "exchange-rbac"
      ]
    },
    "buyer_evidence_required": [
      "Application identity and Entra consented permissions",
      "Exchange RBAC assignments and resource scopes",
      "Applicable Application Access Policies and mailbox access evidence"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Reject a least-privilege conclusion based on the scoped RBAC assignment alone."
    },
    "unknowns": "Effective grants and mailbox access in the buyer tenant are not inspected.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "Effective grants and mailbox access in the buyer tenant are not inspected."
    },
    "evidence_sources": [
      {
        "source_id": "exchange-rbac",
        "url": "https://learn.microsoft.com/en-us/exchange/permissions-exo/application-rbac",
        "final_url": "https://learn.microsoft.com/en-us/exchange/permissions-exo/application-rbac",
        "status": 200,
        "captured_at_utc": "2026-10-24T16:47:20.539Z",
        "sha256": "31a2b7bad0f4f65a66fbfedf901e5eb281a64c5801bad0012db349be8796ffee",
        "bytes": 65386,
        "title": "Role Based Access Control for Applications in Exchange Online | 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": [
          "Intersection and union of Entra and Exchange grants",
          "Application Access Policies"
        ],
        "version_context": "Rolling official documentation captured 2026-10-24; installed API/SDK version, account tier and buyer configuration require verification."
      }
    ],
    "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": "Avoid approving a mailbox integration whose other grant path remains broad.",
      "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": "Avoid approving a mailbox integration whose other grant path remains broad.",
    "refusal_conditions": [
      "Reject a least-privilege conclusion based on the scoped RBAC assignment alone."
    ]
  },
  "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": "Avoid approving a mailbox integration whose other grant path remains broad.",
    "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#exchange-application-rbac-additive-entra-grants",
  "machine_readable_record": "/varexis-index/records/exchange-application-rbac-additive-entra-grants.json"
}
