deployment failing in MariaDb and ScaleSet Templates

"code": "Conflict",
"message": "{\r\n \"status\": \"Failed\",\r\n \"error\": {\r\n \"code\": \"ResourceDeploymentFailure\",\r\n \"message\": \"The resource operation completed with terminal provisioning state 'Failed'.\",\r\n \"details\": [\r\n {\r\n \"code\": \"DeploymentFailed\",\r\n \"message\": \"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-debug for usage details.\",\r\n \"details\": [\r\n {\r\n \"code\": \"Conflict\",\r\n \"message\": \"{\\r\\n \\\"status\\\": \\\"Failed\\\",\\r\\n \\\"error\\\": {\\r\\n \\\"code\\\": \\\"ResourceDeploymentFailure\\\",\\r\\n \\\"message\\\": \\\"The resource operation completed with terminal provisioning state 'Failed'.\\\",\\r\\n \\\"details\\\": [\\r\\n {\\r\\n \\\"code\\\": \\\"OSProvisioningTimedOut\\\",\\r\\n \\\"message\\\": \\\"OS Provisioning for VM 'dbabcmoodlevm1' did not finish in the allotted time. The VM may still finish provisioning successfully. Please check provisioning state later.\\\"\\r\\n }\\r\\n ]\\r\\n }\\r\\n}\"\r\n }\r\n ]\r\n }\r\n ]\r\n }\r\n}"

No template path or test is provided. Start by locating the MariaDB and Scale Set templates in the repository, then reproduce the Azure deployment and inspect the provisioning state and deployment-operation details for the reported OSProvisioningTimedOut error. Done means identifying and fixing the template cause, with a deployment that completes successfully.

Written by the indexing model from the issue text.