For SQL Server I did some testing on this and yes, no obstacles, for the App Service probably yes, but never tried.

Thank you Martins.

Sage X3 expects a named SQL instance, how you managed this? Also what path you provided for DBMS & ODBC tools?

Yes, that would be very interesting. and please take a note of this conversation here in Chatter. The SQL-Server as a Service in Azure ist not supported.   https://sagegroup.my.salesforce.com/_ui/core/chatter/groups/GroupProfilePage?g=0F924000000HjJ4&fId=0D51o00006jO2ey

Thank you Markus.

Would it be possible to share a screenshot of the page you mentioned? Looks like I need an account and login to see the content.

Hi James,

I was wondering if you finally got clarity on the SQL server issue in Azure. Can we create a named instance as expected by Sage X3?

Is this still an issue to be concerned about?

Hi Leonard,

In this case, I have concluded that Azure SQL instance is not supported. We cannot have a named instance and database tools path. Hence my customer procured SQL Server core-based licenses and we proceeded with normal installation in the Azure VMs.

I am not sure how Martins de Almeida managed this.

Hi James,

Thank you for the update. I guess we will also have to go with Azure VMs instead of Azure SQL instances.

Hi everyone,

I know this discussion happened a while ago, but it might server other people:
AZURE is not a supported platform for Sage X3 at the moment, even in 2021R3. It doesn't mean it won't work, it means that if you need support from Sage while using Azure VMs that you have an issue with something that is Azure specific (driver, azure services, etc.) Sage won't be able to assist you. Normal support for X3 will be OK though (functionality issue, development, etc.).
I hope this will help.
Kind regards,

Bruno