Deployment failing at VM stage.

Template:
301-sql-alwayson-md-ilb-zones

Error:
{
"status": "Failed",
"error": {
"code": "ResourceDeploymentFailure",
"message": "The resource operation completed with terminal provisioning state 'Failed'.",
"details": [
{
"code": "DeploymentFailed",
"message": "At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.",
"details": [
{
"code": "NotFound",
"message": "{\r\n \"error\": {\r\n \"code\": \"PlatformImageNotFound\",\r\n \"message\": \"The platform image 'MicrosoftSQLServer:SQL2017-WS2016-BYOL:SQLDEV:latest' is not available. Verify that all fields in the storage profile are correct. For more details about storage profile information, please refer to https://aka.ms/storageprofile\",\r\n \"target\": \"imageReference\"\r\n }\r\n}"
}
]
}
]
}
}

#

and:
{"code":"DeploymentFailed","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.","details":[{"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/DeployOperations for usage details.\",\r\n \"details\": [\r\n {\r\n \"code\": \"NotFound\",\r\n \"message\": \"{\\r\\n \\\"error\\\": {\\r\\n \\\"code\\\": \\\"PlatformImageNotFound\\\",\\r\\n \\\"message\\\": \\\"The platform image 'MicrosoftSQLServer:SQL2017-WS2016-BYOL:SQLDEV:latest' is not available. Verify that all fields in the storage profile are correct. For more details about storage profile information, please refer to https://aka.ms/storageprofile\\\",\\r\\n \\\"target\\\": \\\"imageReference\\\"\\r\\n }\\r\\n}\"\r\n }\r\n ]\r\n }\r\n ]\r\n }\r\n}"},{"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/DeployOperations for usage details.\",\r\n \"details\": [\r\n {\r\n \"code\": \"NotFound\",\r\n \"message\": \"{\\r\\n \\\"error\\\": {\\r\\n \\\"code\\\": \\\"PlatformImageNotFound\\\",\\r\\n \\\"message\\\": \\\"The platform image 'MicrosoftSQLServer:SQL2017-WS2016-BYOL:SQLDEV:latest' is not available. Verify that all fields in the storage profile are correct. For more details about storage profile information, please refer to https://aka.ms/storageprofile\\\",\\r\\n \\\"target\\\": \\\"imageReference\\\"\\r\\n }\\r\\n}\"\r\n }\r\n ]\r\n }\r\n ]\r\n }\r\n}"}]}

and:

Start by locating the 301-sql-alwayson-md-ilb-zones template and the VM imageReference using MicrosoftSQLServer:SQL2017-WS2016-BYOL:SQLDEV:latest. Check whether that platform image is still available and identify the supported image value; done means the template deployment completes past the VM stage without PlatformImageNotFound.

Written by the indexing model from the issue text.