Sovereign SDWAN and Sovereign SASE

I am creating a solution for a MSP where they intent to build a multi-tenant platform of Sovereign SDWAN and Unified SASE together. We have proposed a unified solution comprising the following:

Unified Control and Management Plane:

FortiManager, FortiAnalyzer, FortiAuthenticator, FortiNAC, FortiPAM, FortiClient EMS, FortiPortal, FortiGuard FDN (country specific mirror)

!!!All the above components will be on-prem.

At the Data plane apart from regular FortiGates at HUBs, PoPs and Branches, SASE specific appliances and VMs like FortiProxy, FortiSandBox, FortiDDoS, FortiADC was also considered,

!!!

At the same time, we are also aware and also customer got some input from Fortinet reseller SE that that Fortinet sell an SKU named FortiSASE Sovereign which is productized solution where FortiSASE Sovereign Orchestrator, FortiSASE Sovereign Web Portal resides in country specific FortiCloud SaaS and that is mandatory.

So wanted some idea whether customer need to maintain split model or the original design I have created is technically correct and fully implementable.

• Orchestrator i.e. on-prem FortiManager for SDWAN), FortiSASE Sovereign Orchestrator (Fortinet-operated) for SASE
• Two consoles, two RBAC models, two onboarding workflows for the NOC team to operate.