Material Outsourcing Notification
The regulatory obligation to inform a supervisor before placing a critical function with a third party, which puts cloud adoption on a timeline architecture must respect.
In several regulated sectors, moving a material business function to a third party — which includes a cloud provider — triggers a notification or non-objection process with the supervisor, before the arrangement begins.
The architectural relevance is timing and content. The process takes weeks to months, and it requires artifacts that must therefore exist early: which service is being outsourced, where processing and data will be located, how the firm retains oversight and audit rights, what the exit plan is, and how substitutability has been assessed.
That last pair is where architecture is directly implicated. An exit plan asserting that workloads could be moved is not sufficient; supervisors increasingly expect evidence that it has been tested. And substitutability requires an assessment of what would actually be needed to run the function elsewhere, which is a design question about how much provider-specific capability the architecture has adopted.
The practical consequence is that a project plan which discovers this obligation after the technical design is complete has a delay of months that no engineering effort can compress. It belongs in the same early conversation as residency and data protection.