{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-30T15:17:58.235744+00:00",
  "record_id": "VXI-EXT-ICE09-ENTRA-AGENT-SINGLE-TENANT-BLUEPRINT-MULTITENANCY-01-v1",
  "record_kind": "external_reference",
  "title": "Can a multitenant Entra blueprint make one child identity valid across tenants",
  "system": "Microsoft",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Can a multitenant Entra blueprint make one child identity valid across tenants?",
  "near_questions": [
    "Does a multitenant blueprint share one agent account?",
    "Must each customer tenant create its own agent identity?",
    "Can an agent token reach another tenant's API?",
    "Which local identity belongs in a cross-tenant deployment review?"
  ],
  "supported_claims": [
    {
      "claim": "No. Agent identities remain single-tenant. A multitenant blueprint can be installed elsewhere and create separate tenant-local identities; it does not make an existing child identity cross-tenant.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Require the destination tenant identity and authorization evidence.",
    "Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.",
    "No expanded capabilities or licences for existing INDEX executables."
  ],
  "public_summary": "No. Agent identities remain single-tenant. A multitenant blueprint can be installed elsewhere and create separate tenant-local identities; it does not make an existing child identity cross-tenant.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Microsoft primary documentation: entra agent identities",
    "source_url": "https://learn.microsoft.com/en-us/entra/agent-id/agent-identities?view=entra-agent-id",
    "checked_on": "2026-10-30",
    "candidate_record_id": "VXI-EXT-ICE09-ENTRA-AGENT-SINGLE-TENANT-BLUEPRINT-MULTITENANCY-01-v1",
    "candidate_record_sha256": "fd694c569bdf74938bbb5655eb46964be9b1687b92d8d791063206122111e774",
    "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": "No. Agent identities remain single-tenant. A multitenant blueprint can be installed elsewhere and create separate tenant-local identities; it does not make an existing child identity cross-tenant.",
    "required_buyer_context": "source/destination tenants; local agent IDs; blueprint installations; resource tenant. 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",
    "applicability_status": "Existing documented requirement; captured 2026-10-30; deployed behaviour unverified.",
    "checked_on": "2026-10-30",
    "claim_to_check": "Can a multitenant Entra blueprint make one child identity valid across tenants?",
    "documented_statement": {
      "status": "documented",
      "statement": "No. Agent identities remain single-tenant. A multitenant blueprint can be installed elsewhere and create separate tenant-local identities; it does not make an existing child identity cross-tenant.",
      "source_ids": [
        "entra-agent-identities"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "Can a multitenant Entra blueprint make one child identity valid across tenants? Require the destination tenant identity and authorization evidence. Separates distributed blueprints from tenant-local agents rather than generic exchange policy. This is an operational review inference, not an observed deployment outcome.",
      "source_ids": [
        "entra-agent-identities"
      ]
    },
    "buyer_evidence_required": [
      "source/destination tenants",
      "local agent IDs",
      "blueprint installations",
      "resource tenant"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Require the destination tenant identity and authorization evidence."
    },
    "unknowns": "The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "No buyer deployment or transaction was observed."
    },
    "evidence_sources": [
      {
        "source_id": "entra-agent-identities",
        "url": "https://learn.microsoft.com/en-us/entra/agent-id/agent-identities?view=entra-agent-id",
        "final_url": "https://learn.microsoft.com/en-us/entra/agent-id/agent-identities?view=entra-agent-id",
        "captured_at_utc": "2026-10-30T14:22:29.798244+00:00",
        "status": 200,
        "content_type": "text/html",
        "bytes": 54582,
        "sha256": "272ad070ed434546efbb8601cc8d87b090efe5755bbd9c06ecf5ffce0259fc8c",
        "title": "Microsoft primary documentation: entra agent identities",
        "publisher": "Microsoft",
        "checked_on": "2026-10-30",
        "capture_status": 200,
        "claim_review_completed": true,
        "hash_basis": "SHA-256 of captured HTTP response-body bytes; not a signature or factual guarantee.",
        "version_context": "Existing documented requirement; captured 2026-10-30; deployed behaviour unverified.",
        "rights_disposition": "Original bounded paraphrase with source attribution. Captured source body remains private; no source-body redistribution. Vendor documentation rights, code licences and marks are not transferred.",
        "reviewed_sections": [
          "Credentials",
          "single-tenant",
          "different"
        ]
      }
    ],
    "observed_deployment": false,
    "commercial_reliance_boundary": "Documentation supports only the stated boundary. Existing licensed checkers analyse supported supplied declarations locally; they do not inspect provider accounts, verify live behaviour, enforce decisions or certify compliance.",
    "paid_value": {
      "decision_context": "Can a multitenant Entra blueprint make one child identity valid across tenants? Require the destination tenant identity and authorization evidence.",
      "free": "Complete source review, questions, provenance and limitations; free to read and save locally.",
      "single_request": "Unavailable for this publication-only record; historical saved retrieval is unchanged.",
      "evidence_receipt": "Unavailable for this publication-only record; no paid retrieval entitlement is added.",
      "excluded": [
        "Fresh source research",
        "Native provider integration or schema support",
        "Live inspection or runtime enforcement",
        "Payment settlement or verified deletion",
        "Certification or expanded licences"
      ],
      "integrity": "Hashes identify content versions; they do not prove factual truth or provide a signature."
    },
    "revalidation": {
      "trigger": "Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included.",
      "specific_watch": "single-tenant"
    },
    "buyer_relevance": "Can a multitenant Entra blueprint make one child identity valid across tenants? Require the destination tenant identity and authorization evidence.",
    "refusal_conditions": [
      "Require the destination tenant identity and authorization evidence.",
      "Do not infer deployment conformance, authority or successful outcomes from source documentation."
    ],
    "decision_context": {
      "operator": "Identity administrator or delegated-access reviewer",
      "scenario": "Can a multitenant Entra blueprint make one child identity valid across tenants?",
      "consequence": "Require the destination tenant identity and authorization evidence.",
      "confidence": "High for the explicitly bounded captured clause; conflicts and version limits retained; deployment untested."
    },
    "novelty_review": {
      "candidate_id": "ICE09-003",
      "disposition": "EXTENSION",
      "nearest_record_id": "VXI-EXT-PROCUREMENT-OAUTH-TOKEN-EXCHANGE-SUBJECT-ACTOR-POLICY-01-v1",
      "nearest_record_url": "/varexis-index/records/oauth-token-exchange-subject-actor-policy.json",
      "nearest_record_sha256": "20777a8702cf1334f7f595689e87426725ba04ee1867690e816077ced7bb0d2e",
      "material_distinction": "Separates distributed blueprints from tenant-local agents rather than generic exchange policy.",
      "review_status": "PASS: source qualification plus independent reviewer challenge and resolved corrections"
    },
    "optional_selection": {
      "guide_id": "delegated-agent-identity-continuity",
      "guide_url": "/index-guides/delegated-agent-identity-continuity",
      "guide_manifest": "/varexis-index/decision-guides.json",
      "checker": {
        "product_id": "agent-tool-admission",
        "price_gbp_excluding_vat": 49,
        "purchase_url": "/index-access?route=agentic_pack_tool_admission_v1",
        "licence_scope": "Existing separate internal-use licence; subscriptions do not include the executable.",
        "benefit": "Optional local analysis of supported supplied declarations only; no native provider integration or verification is added."
      },
      "boundary": "Optional existing checker analyses its supported supplied declarations locally. It does not connect to the documented provider, import native provider exports, verify tokens, establish live outcomes or extend its schema or licence."
    },
    "exact_access": {
      "endpoint": "/mcp/catalogue",
      "tool": "get_publication_record",
      "arguments": {
        "record_id": "VXI-EXT-ICE09-ENTRA-AGENT-SINGLE-TENANT-BLUEPRINT-MULTITENANCY-01-v1"
      },
      "record_url": "/varexis-index/records/entra-agent-single-tenant-blueprint-multitenancy.json",
      "original_mcp_search": false,
      "paid_saved_retrieval": false
    }
  },
  "niche": {
    "niche_id": "ice09-identity",
    "label": "Agent Identity, Credentials & Delegation",
    "classification_id": "identity",
    "classification_label": "Agent Identity, Credentials & Delegation",
    "topic_id": "identity",
    "buyer_intent": "Can a multitenant Entra blueprint make one child identity valid across tenants? Require the destination tenant identity and authorization evidence.",
    "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#entra-agent-single-tenant-blueprint-multitenancy",
  "machine_readable_record": "/varexis-index/records/entra-agent-single-tenant-blueprint-multitenancy.json"
}