| bfc1380b98f204f1… | Path A is quick to implement but does not satisfy the RFP governance threshold, making it insufficient for the stated governance requirements. | active | contextual | yes | |
| c3ad856509b5b7d4… | Under Path B, the organization must build and own runtime, orchestration, retrieval, provenance and citation governance, prompt-injection defenses, telemetry, frontend, and the associated integration, testing, security hardening, and lifecycle work. | active | contextual | yes | |
| 49e1ce0c5652d039… | Path B uses Foundry plus Agent Framework and a custom application to provide full flexibility for building custom agents on Azure AI Foundry runtime grounded on Fabric. | active | contextual | yes | |
| c94619247f88d3b9… | Path A is limited to structured Fabric data and lacks native PDF or Word grounding, durable multi-agent workflows, agent-level monitoring, citations, human-in-the-loop controls, and a business user interface. | active | contextual | yes | |
| 7e6832f4308d9ced… | Path A, Fabric Data Agents only, provides conversational natural-language question answering over governed Fabric data and honors Purview labels. | active | contextual | yes | |
| 6aa80d272881c05a… | Building agents directly in Fabric leads to two practical implementation paths, and IT should evaluate both honestly so that the tradeoffs are understood. | active | contextual | yes | |
| 770fdba610843395… | Pyrana provides agentic capabilities as a single governed and pre-integrated platform so that organizations do not need to assemble the equivalent Microsoft services themselves. | active | contextual | yes | |
| 9bf21ebf9aa65260… | On the Microsoft stack, agentic capabilities require assembling multiple services including Fabric, Foundry Agent Service, the Agent Framework SDK, and custom application code so that the full agent solution functions. | active | contextual | yes | |
| 3c30959c9feb3b92… | Pyrana and Microsoft Fabric operate at different solution layers because Fabric answers governed data questions while Pyrana uses that data plus documents, policies, and tribal knowledge to produce traceable and trusted recommendations. | active | contextual | yes | |
| b6106f8ae22ac403… | Under the proposed exception rationale, Pyrana adds agent-grade governance including source-to-AI citations, fact-versus-recommendation typing, human-in-the-loop approvals, and prompt protections so that AI outputs are governed beyond standard Fabric capabilities. | active | contextual | yes | |
| 26fe423b3f37e791… | Under the proposed exception rationale, Pyrana consumes governed data from OneLake and writes no data outside Azure so that data residency remains within approved Microsoft infrastructure. | active | contextual | yes | |
| 049b267a97d6c760… | The proposed written exception rationale defines the AI-agent capability as being delivered by Pyrana, an Azure-native agentic-application platform deployed in the organization's tenant so that the exception remains within the Azure environment. | active | contextual | yes | |
| cd156ce4396e03db… | Pyrana is intended to be the single platform IT documents and approves rather than a sprawl of external tools so that governance and vendor management remain centralized. | active | contextual | yes | |
| 5614bb26c6a11fd7… | Pyrana performs no model training on Summer Fridays data and instead uses private inference with per-tenant isolation so that customer data remains isolated and not used for training. | active | contextual | yes | |
| d51a9f382fb4e7fb… | Pyrana reads from governed Fabric data, and raw confidential or customer-level data is never exposed through dashboards or agents unless explicitly approved so that sensitive data access remains controlled. | active | contextual | yes | |
| d640b2ca6d171327… | Pyrana runs in Summer Fridays' Azure tenant using Azure OpenAI or Foundry models, Azure Postgres, Entra ID, and AKS so that the platform remains inside the Microsoft estate. | active | contextual | yes | |
| c4cf1f3d31a5e02e… | The agentic layer is the narrow, documented exception so that the non-Fabric portion of the solution is limited and explicitly identified. | active | contextual | yes | |
| 50bfada05b4fc010… | Purview continues to own catalog, lineage, sensitivity labels, and data loss prevention so that governance responsibilities remain with Microsoft's governance tooling. | active | contextual | yes | |
| ada9501547d98d61… | Dashboards reconcile to approved Fabric logic and Power BI reports so that reporting remains aligned with sanctioned business logic. | active | contextual | yes | |
| 0d9cf125dea42781… | The governed data model and business-metrics layer live in the Fabric lakehouse, warehouse, and semantic models so that governed analytical logic remains in Fabric-managed assets. | active | contextual | yes | |
| e0d25226425a91b5… | Ingestion, transformation, refresh, and reconciliation run in Fabric pipelines so that core data-processing operations stay within Fabric. | active | contextual | yes | |
| f0a2ed37bc601f29… | Company data remains in OneLake as the system of record so that Fabric continues to host the authoritative enterprise data store. | active | contextual | yes | |
| c6f96f4c382434eb… | Pyrana is designed to satisfy the Fabric mandate rather than circumvent it so that its deployment aligns with the RFP's Microsoft-environment requirements. | active | contextual | yes | |
| f5085a6d111e6aa7… | Any platform used outside Fabric must be documented and approved by Summer Fridays IT before use so that external platform adoption is controlled through formal review. | active | contextual | yes | |
| 4e0e080fafae36ff… | The RFP requires the solution to be built within Summer Fridays' approved Microsoft Fabric environment unless IT approves a written exception so that non-Fabric deployment needs explicit authorization. | active | contextual | yes | |
| 516e28d17020e8e2… | Pyrana is effectively Path B already built, governed, and supported so that the organization can obtain Path B capabilities without running its own integration program. | active | contextual | yes | |
| d8a6b74f9f7a73e3… | Path B can meet the governance bar, but it becomes a build-it-yourself integration program on top of the data project so that scope, timeline, and maintenance risk increase. | active | contextual | yes | |
| 7984e02af3270c37… | Path A is fast but insufficient for the RFP governance bar so that speed alone does not satisfy the stated governance expectations. | active | contextual | yes | |
| 7703b0d4885f73dd… | Under Path B, the organization owns integration, testing, security hardening, and lifecycle responsibilities so that operational and maintenance accountability remains internal. | active | contextual | yes | |
| 07064e21d8bd2dd5… | Under Path B, the organization must build and own runtime, orchestration, retrieval, provenance and citation governance, prompt-injection defenses, telemetry, and a custom frontend so that the full agent stack is self-assembled. | active | contextual | yes | |
| 2800fc0ca6a863ea… | Path B uses Foundry plus Agent Framework plus a custom application to provide full flexibility for building custom agents on Azure AI Foundry runtime orchestrated with Microsoft Agent Framework and grounded on Fabric. | active | contextual | yes | |
| d7045792ac23109f… | Path A does not provide agent-level monitoring, citations, human-in-the-loop capabilities, or a business user interface so that these governance and usability features must be obtained elsewhere. | active | contextual | yes | |
| e1bf54b5d8beb2c6… | Path A supports single-turn question answering rather than durable multi-agent workflows so that it does not provide persistent multi-agent process execution. | active | contextual | yes | |
| 26955eaf83eabad9… | Path A is limited to structured Fabric data with no native PDF or Word grounding so that unstructured document grounding is not available in the Fabric Data Agents-only approach. | active | contextual | yes | |
| 6c3e1d358c2823e0… | Path A, Fabric Data Agents only, provides conversational natural-language question answering over governed Fabric data while honoring Purview labels so that users can query structured governed data conversationally. | active | contextual | yes | |
| 734b4baa4287b4ae… | Building agents directly in Fabric means choosing between two practical paths, and IT should evaluate both honestly so that the implementation tradeoffs are fully understood. | active | contextual | yes | |
| e54d9691cef1d2cd… | Pyrana delivers agentic capabilities as one governed, pre-integrated platform so that organizations avoid assembling separate Microsoft services and custom code to achieve the same outcome. | active | contextual | yes | |
| 5f55665a64d3b2bd… | On the Microsoft stack, agentic capabilities are assembled from multiple services including Fabric, Foundry Agent Service, the Agent Framework SDK, and custom application code so that equivalent functionality is not delivered as a single integrated product. | active | contextual | yes | |
| 77a7586fac23ec02… | Pyrana and Microsoft Fabric operate at different solution layers because Fabric answers governed-data questions while Pyrana determines recommended actions using data, documents, policies, and tribal knowledge so that recommendations can be traced and trusted. | active | contextual | yes | |
| 6d29cb3fdb50a551… | The written exception rationale says Pyrana adds agent-grade governance including source-to-AI citations, fact-versus-recommendation typing, human-in-the-loop approvals, and prompt-related controls. | active | contextual | yes | |
| bdf8f9d1d2a275ee… | The written exception rationale states that Pyrana consumes governed data from OneLake and writes no data outside Azure. | active | contextual | yes | |
| 57e434a2437f7c80… | The proposed written exception rationale states that the AI-agent capability is delivered by Pyrana as an Azure-native agentic application platform deployed in the company's tenant. | active | contextual | yes | |
| 9a44fc9c38a4d496… | Pyrana is intended to be the single platform that IT documents and approves, avoiding a proliferation of external tools. | active | contextual | yes | |
| 7490c1883ffe47a8… | The platform does not train models on Summer Fridays data and instead uses private inference with per-tenant isolation. | active | contextual | yes | |
| fabd07ef67b31a4b… | Pyrana reads from governed Fabric data, and raw confidential or customer-level data is not exposed through dashboards or agents unless explicit approval is granted. | active | contextual | yes | |
| 1c0f795f8b2da274… | Pyrana runs inside Summer Fridays' Azure tenant using Azure OpenAI or Foundry models, Azure Postgres, Entra ID, and AKS, which keeps it inside the Microsoft estate. | active | contextual | yes | |
| 6aa20b728021d7c6… | The agentic layer is presented as the narrow, documented exception to the Fabric-only environment requirement. | active | contextual | yes | |
| 7fd61fe1214c439a… | Purview continues to own cataloging, lineage, sensitivity labels, and data loss prevention responsibilities in the proposed setup. | active | contextual | yes | |
| 27026d3c023c1cd5… | Dashboards are expected to reconcile to approved Fabric logic and Power BI reports so that reporting remains aligned with sanctioned calculations. | active | contextual | yes | |
| 1d5f51e360c5e353… | The governed data model and business metrics layer remain in the Fabric lakehouse, warehouse, and semantic models. | active | contextual | yes | |