The company is designing a new interdepartmental ticketing system to centralize requests and communication. The system aims for an intuitive interface integrated with SharePoint Online and Microsoft Teams. The proposed architecture uses SPFx web parts for the frontend, delivering a native Microsoft 365 experience. Azure Database for PostgreSQL will manage relational data, audit logs, and SLA metrics due to anticipated data volume and complexity. A custom integration layer with REST APIs hosted on Azure Functions or App Service will connect the frontend and backend securely.This choice is driven by the desire for a seamless user experience and PostgreSQL's superior capabilities for complex data models and granular access control compared to SharePoint Lists. The team is questioning the long-term viability of SPFx as a frontend for external REST APIs. They are also deliberating whether the overhead of a custom API and PostgreSQL is justified over Dataverse or native SharePoint Lists. Specific concerns exist regarding securing SPFx calls to Azure APIs using Microsoft Entra ID for data segregation. Finally, the team seeks advice on potential maintenance, governance, and performance bottlenecks of this hybrid architecture.