d, these are a starting point and would require manual work by someone with the ability to configure connection strings and user IDs within the scripts in order to successfully deploy. This is because: - Private data (e.g., account names, connection strings, URLs) has been removed from them and relevant local details would need to be provided for deployment - Currently some refer to email addresses/groups within North Yorkshire, and may fail on deployment The SQL database is available as a DAC Package (see Deploy a Data-tier Application - SQL Server | Microsoft Learn) [10] – this is a single .dacpac file, this would typically be deployed using SQL Server Management Studio. Appendix 5 (SQL DAC Package). Data Factory clone is available as an ARM template (see Copy or clone a data factory in Azure Data Factory - Azure Data Factory | Microsoft Learn – follow the steps for point 3: “Live Mode”) [11], the ARM template would be deployed via the Azure Portal. This is a small number of .json files. Appendix 6 (ARM template for Data Factory Clone Zip). Practice guidance A very early version of the prototype was introduced to users at Locality events. More details are included at Section 3.3 (Introducing the Prototype - CSC Locality Days) and Section 4.5.1 (Initial Feedback from CSC Locality Days). Feedback received at these events led to the inclusion of data governance considerations in the practice guidance. The project team worked to embed points from the impact assessment process into the practice guidance. The guidance was circulated to those attending pilot workshops and used as the basis for introducing the product to attendees at the workshops. Attendees had the opportunity to go through it in the workshop and provide feedback. Front door team: “This user-friendly format 