Related to this post, we'll look at how to run a database sync in an Azure instance and also an on premise instance. Below is an example of how to import a license file in an Azure based environment, like a development environement.

k:\AosService\PackagesLocalDirectory\Bin\Microsoft.Dynamics.AX.Deployment.Setup.exe -- setupmode sync --syncmode FullTablesAndViews --metadatadir k:\AosService\PackagesLocalDirectory --bindir k:\AosService\PackagesLocalDirectory --sqlserver . --sqldatabase AXDBTEST --sqluser axdbadmin --sqlpwd password

First, we'll need to refer to this post to know where to look for the specific locations to execute the command. Once we have it, we can simply replace the values in the example below.

C:\ProgramData\SF\AOS_233\Fabric\work\Applications\AXSFType_App84\AXSF.Code.1.0.20180405130633\bin\Microsoft.Dynamics.AX.Deployment.Setup.exe --setupmode sync --syncmode FullTablesAndViews --metadatadir C:\ProgramData\SF\AOS_233\Fabric\work\Applications\AXSFType_App84\AXSF.Code.1.0.20180405130633\Packages --bindir C:\ProgramData\SF\AOS_233\Fabric\work\Applications\AXSFType_App84\AXSF.Code.1.0.20180405130633\Packages --sqlserver sqlserver.domain.com --sqldatabase AXDBTest --sqluser axdbadmin --sqlpwd password

In order to not get an error when interacting with SQL, the name by which you refer to the server in this script should match exactly the name in the cert used for SQL that was installed on the AOS. If you use localhost or ".", you will get a SQL related error.