Request for Proposal For Microsoft Fabric Implementation Partner To Co-Design And Co-Develop

Request for proposals for Microsoft Fabric Implementation Partner to Co-Design and Co-Develop Closing Date: 25 Sep 2026 Type: Consultancy REQUEST FOR PROPOSAL (RFP) Issued on: September 07, 2026 Solicitation Number: 51450 For: Professional Services for qualified Microsoft Fabric implementation partner to co- design and co-develop. Bids Deadline: September 25, 2026 Background Pathfinder is driven by the conviction that all people, regardless of where they live, have the right to decide whether and when to have children, to exist free from fear and stigma, and to lead the lives they choose. Since 1957, we have partnered with local governments, communities, and health systems to remove barriers to critical sexual and reproductive health services. Together, we expand access to contraception, promote healthy pregnancies, save womens lives, and stop the spread of new HIV infections, wherever the need is most urgent. Our work ensures millions of women, men, and young people are able to choose their own paths forward. Pathfinder is issuing this Request for Proposal to establish a contract with a qualified offeror for the co-design, setup, and initial co-development of a Microsoft Fabric-based data warehouse and lakehouse environment. This initiative is part of Pathfinders commitment to strengthening our data governance, security, and performance standards through improved data management capabilities, using a medallion architecture, with Microsoft Purview providing data governance and cataloguing. Scope of Work Overview Pathfinder is seeking a qualified Microsoft Fabric implementation partner to co-design and co-develop, working directly alongside our internal data engineering staff, the target-state architecture, governance model, and an initial reference implementation for our unified enterprise data analytics platform. This is a co-design and co-development engagement, not a design-then-handoff or full build engagement. Pathfinders Data Engineer will work side by side with the offerors consultant(s) throughout delivery, so that the collaborative process itself serves as the primary route to internal capability, rather than a training exercise added on afterward. The offeror remains fully responsible for every phase deliverable meeting its agreed acceptance criteria, regardless of how jointly it was produced. Ongoing build responsibility beyond what is listed below should not be assumed. Detailed Scope of Work Architecture co-design and documentation Co-design and validate Pathfinders proposed domain-based, medallion architecture (OneLake foundation; Fabric Domains at the top level; one workspace per medallion layer per domain), with Pathfinders Data Engineer an active participant in design sessions, not a reviewer of pre-formed conclusions. Confirm Lakehouse versus Warehouse usage per layer and domain jointly, with the reasoning behind each decision documented as it is made. Document the final architecture in sufficient detail that Pathfinders team can build against it without ongoing offeror involvement. Governance model co-design (Microsoft Purview) Co-design the Purview collection structure, classification approach, and business glossary framework, aligned to Pathfinders business domains. Co-design the sensitivity label taxonomy, with particular attention to the domains carrying the most sensitive data. Configure initial Purview scanning for Azure SQL and Power Platform sources jointly, with Pathfinders Data Engineer performing configuration steps alongside the consultant. Document the governance model, including current platform limitations relevant to Pathfinders architecture, so Pathfinders team understands what is automated versus what requires manual process. Metadata-driven ingestion framework: co-design and reference implementation Co-design the control-table schema and parameterised pipeline pattern for ingestion (API, database, and file-based sources), extending Pathfinders existing metadata-driven approach into Fabric Data Pipelines. Co-develop one working reference implementation per source type against a real Pathfinder source (one API-based source, one database source, and one file-based source, to be confirmed with the selected offeror), with Pathfinders Data Engineer authoring alongside the consultant, sufficient for Pathfinders team to replicate the pattern against the remaining priority sources without further offeror involvement. Environment and CI/CD co-configuration Co-configure the Dev/Test/Prod environment strategy for the Platform Foundation and one pilot domain. Set up Fabric Deployment Pipelines integrated with Pathfinders existing Azure DevOps Git repositories, with Pathfinders Data Engineer performing the configuration under the consultants direction. Document the promotion process so Pathfinders team can operate it independently. Security model co-design Co-design and configure the Entra ID security group structure, workspace-level and item-level permission model, and the row-level security pattern for the domains carrying the most sensitive data. Knowledge transfer and handoff Structured knowledge transfer sessions with Pathfinders internal team, supplementing rather than substituting for the co-design and co-development approach used throughout the engagement. Written documentation sufficient to stand alone as an operational reference after the engagement ends. A defined handoff acceptance step confirming Pathfinders team can operate independently before the engagement is considered complete. Explicitly Out of Scope The following are not included in this engagement and should not be assumed or informally added during delivery. Any of these requiring offeror involvement would be handled through a separate, explicitly scoped change order, not absorbed into the fixed fee. Full build-out of all domain integrations beyond the reference implementations. The offeror co-develops one reference implementation per source type (three total); Pathfinders team replicates the pattern across the remaining domains and sources. Power BI report rebuilding. Evaluating and rebuilding Pathfinders existing reporting estate against the new governed platform is Pathfinder-owned work, to be sequenced separately from this engagement. Ongoing pipeline maintenance, Silver or Gold model building beyond the reference implementations, or production support after handoff. Full multi-domain rollout of the Dev/Test/Prod and CI/CD pattern beyond the Platform Foundation and one pilot domain. Purview Wave 2 scope (sensitivity labelling enforcement, DLP configuration, access policy integration). Engagement Structure: Phases and Fee Allocation Phase Focus Indicative Duration Fee Allocation Phase 1- Architecture co-design and validation; confirm workspace and domain structure (1-2 weeks) -15% Phase 2- Governance model co-design (Microsoft Purview); security model; CI/CD and environment co-configuration (2-3 weeks) -30% Phase 3- Co-development of the three source-type reference pipelines against real Pathfinder sources (2-3 weeks) -35% Phase 4- Documentation, structured knowledge transfer sessions, handoff acceptance (1 week) -20% Total indicative timeline: 6-9 weeks. Payment terms Fixed Price: Pathfinder anticipates entering into a fixed-price contract with the selected contractor. Payment will be made according to the milestones and fee allocation set out in the Engagement Structure table above, tied to Pathfinders formal acceptance of each phases deliverables, not hours logged. Acceptance Criteria Each phase is considered complete only when its deliverables are reviewed and formally accepted by Pathfinders Project Lead. Acceptance considers both the quality of the deliverable and evidence of genuine co-design/co-development participation. Final engagement acceptance (Phase 4) requires: All architecture, governance, and pattern documentation delivered and reviewed. The three reference pipeline implementations functioning correctly against live Pathfinder sources, with Pathfinders Data Engineer able to demonstrate active authorship of the co-developed work. Knowledge transfer sessions completed, with Pathfinders internal team able to demonstrate independent understanding of the delivered architecture and patterns, for example by extending the ingestion pattern to a fourth source under the offerors observation, without offeror-led implementation. Warranty and Payment Holdback The offeror will provide a warranty period of 30 to 60 days following final acceptance, during which the offeror must remedy defects in delivered work at no additional cost. Critical defects must be acknowledged within 2 business days and resolved or worked around within 10 business days; other severities follow proportionate, mutually agreed response times. A holdback of 10-15% of the total fee will be withheld and released only after the warranty period concludes with no unresolved critical defects. All deliverables, architecture documentation, configuration, and associated code become Pathfinders property outright upon payment. Proposal Guidelines and Instructions Offerors will be required to submit two proposals, electronically, one a technical proposal and the other a cost proposal. All proposals must be signed and valid for a minimum of sixty (60) days. Your proposal should provide basic information about your Company/Individual and relevant service offerings. It should have a section addressing each of the following areas: Company/Individual Profile Past Performance Technical Approach References Relationship disclosure and mitigation plan Key Personnel Other (optional) Responses should include the following information: A. Technical Proposal (100 Points) a. References - pass/fail Submit two (2) client references for e Tender Link : https://reliefweb.int/job/4228696/rfp-microsoft-fabric-implementation-partner-co-design-and-co-develop