Can I get help better understand this statement - 'Only SDE-schema EGDBs are allowed in cloud solutions ?'

[MuneerMajid]

Hi All,

I have been working with Azure SQL Database's in IaaS and PaaS form and have had plenty of Enterprise Geodatabases working full throttle in these environments. I have had plenty of success hosting IaaS SQL Enterprise Geodatabases and have also done plenty of migrations from On-Premises EGDBs over the years. 

I recently stumbled upon this statement (screenshot below) at this article - 
https://enterprise.arcgis.com/en/system-requirements/latest/windows/databases-in-the-cloud.htm

My general practice anyways has been to create the Enterprise GDB in SSMS, create SDE login, user, alter role, grant it the right permissions and schema, and then head over to Pro to enable the EGDB. 

And I believe the Create EGDB in Pro isnt a preferred option anyways (ever since ArcMap started to be faded out). Having said that, I can still pretty much create DBO-schema owned databases on Azure Cloud Databases just fine. I dont see any issues with doing it one way or the other. To summarize, you can still have DBO and SDE owned DBs on Azure SQL, and it depends on the way you do it. 

So can you please explain what is the content of the above statement in the documentation, what are the reservations again DBO owned EGDBs in Azure SQL databases and Azure Managed cloud instances ?

Thank you for reading the long post and your inputs are really appreciated. 

[simoxu]

I had the same question and I was told that sde-schema has a better security gesture and it's always the preferred schema.

To be honest, I installed EGDBs using both dbo-schema and sde-schema in MS Azure SQL MI, both EGDBs seemingly work fine... but I didn't do an exhaustive test.

Since it's explicitly listed as "Limitations" in 11.4 document now, I won't risk using dbo-schema for production in any cloud-based MS SQL database. This will make sure I'll get the tech support if anything happens.