1. They need to implement a disaster solution for user mistake. If a user mistakenly has deleted/modified some data, and they find it out after 28 days (the length of backup-in-time provided by MS) they need to be able to restore from backup and access this data.
2. They are after a ‘handsfree’ automated solution, may be using some APIs if possible
3. They are open to storing the backup in a Azure Blob storage for longer retention as long as solution enables ‘handsfree’ option.

https://github.com/microsoft/BCTech/tree/master/samples/ExtractData#extracting-data-from-business-central

BC admin portal allows for the storing of back ups in Azure. Then create a Flow and call the API on schedule and that is it (up to 10 times a month).

https://community.dynamics.com/blogs/post/?postid=05472d7a-751f-49b6-8092-0aab91e368ea

The process involve copying the full automated backups to blob storage, then restore this (when needed) to an on-prem instance BC. From here the client can either migrate data using config packages (BC functionality) or follow the process of “Migrate to BC Online” to the latest version. Shared this with client as well, they just don’t want to touch it and have it working ‘handsfree’ (doesn’t look like we have such a ‘handsfree’ solution in the offering)

I’ve seen theres an open source tool to get info into Data Lake from BC https://github.com/microsoft/bc2adls

When a record is deleted from BC, it also by default gets deleted in theData Lake