Enabling a Microsoft Azure SQL Database with Hebrew_CI_AS Collation as an enterprise geodatabase in ArcGIS Pro and ArcMap fails with ERROR: Cannot resolve the collation conflict between "Hebrew_CI_AS" and "SQL_Latin1_General_CP1_CI_AS" in the equal to operation.

Workaround

The ArcGIS (Desktop, Engine, Server) 10.7.1 Azure SQL Database Collations General Patch is now live on the support site. The URL is: https://support.esri.com/en/download/7798

1. Create a new database from SQL Server Management Studio under a SQL Server Instance with a Hebrew_CI_AS collation. Change the default Collation from (SQL_Latin1_General_CP1_CI_AS to Hebrew_CI_AS) within the database properties options in Management Studio.
2. Once created, enable that database as an enterprise geodatabase from ArcGIS Pro or ArcMap running the Enable Enterprise Geodatabase geoprocessing tool.
3. From SQL Server Management Studio, restore the enabled geodatabase with Hebrew Collation from the SQL Server instance to an Azure SQL instance referencing the workflow from the link below: https://stackoverflow.com/questions/33436344/restoring-sql-server-backup-to-azure-sql-databasehttps://stackoverflow.com/questions/33436344/restoring-sql-server-backup-to-azure-sql-database
4. Based on the workflow from the link above, after successfully deploying the existing geodatabase from a SQL Server instance with the preferred collation (Hebrew_CI_AS) to an existing Azure instance, connect to it using direct connection via ArcCatalog from ArcGIS Pro or ArcMap. (Make sure to remove the Windows Authentication user name from the Security settings of the SQL database from Management Studio before proceeding with the deployment to Azure SQL) https://github.com/Microsoft/azuredatastudio/issues/3337https://github.com/Microsoft/azuredatastudio/issues/3337

Steps to Reproduce