I'm backtracking now on my statement of confidence that we can do this for 7.2.
An Azure App Service cannot be used to host the Jiwa API.
The Crystal Reports runtime must be installed in the environment hosting the Jiwa API - as it demands a certain registry key entry to be present (and possibly other requirements) - but as you cannot create registry keys on Azure App Services, it is not possible to have the Crystal libraries work at all.
What is required by Crystal Reports is the registry entry of
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Crystal Reports\Common Files to be the file path of the Crystal assemblies/files. On a Windows machine with Crystal Reports for Visual Studio, Developer Version installed that would typically be
C:\Program Files (x86)\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Common\SAP BusinessObjects Enterprise XI 4.0\win32_x86A Crystal Assembly checks that registry entry and if not present throws an exception upon instantiation:
"
An error has occurred while attempting to load the Crystal Reports runtime. Either the Crystal Reports registry key permissions are insufficient, or the Crystal Reports runtime is not installed correctly. Please install the appropriate Crystal Reports redistributable (CRRedist.msi) containing the correct version of the Crystal Reports runtime (x86, x64, or Itanium) required. Please go to http://www.businessobjects.com/support for more information"
We cannot add registry entries to Azure App Services, nor can we intercept application access to the registry to return a value as a proxy, and nor can we create the registry entry in code.
If you are hosting the Jiwa database in Azure SQL, then the API must be either the self hosted API service on a Windows VM in Azure, or an IIS site on a Windows VM.