Thank you for your interest in SQLCipher. The approach documented in the link you referenced for utilizing SEE with the Azure Mobile App Client SDK should work just as well with our commercial edition SQLCipher packages. The approach there basically relies on a project that links against a “custom” sqlite3.dll file, utilizing it along with any included cryptography. In fact, the documentation specifically notes that SQLCipher would be supported as well:
that SEE is not the only encryption option for Mobile Apps; For instance, you can define a local store that uses SQLCipher for encryption.
In order to use SQLCipher, you would need to obtain appropriate licenses for the target platforms, include the pre-built libraries, and then be sure to set the key using
PRAGMA key after creating your MobileServiceSQLiteStore instance.
Important Clarification: The approach described in the linked Azure Samples GitHub project describes using a completely custom build of Azure Mobile Services, coupled with custom builds of native SQLite libraries that support encryption for each target platform. While this is technically possible, it is not a trivial integration. Most importantly this solution does not work with the officially supported Azure Mobile library distributions, and is not supported as a direct integration by the SQLCipher team at this time.