Reboot script not working for Azure VMs

Issue: For a subscription with Automation-Account configured, a schedule is configured which stops all servers at 6pm EST on Sundays and then starts them back up on a schedule at 630pm EST.  These schedules execute a set of runbooks which stop and start all servers in this subscription. All servers appeared to have stopped, but it appears the server XYZSQLServer appears to have had issues stopping.  It was believed this to be due to Windows update which have been applied to this server during the stopping process.  The last activity on the server (windows event viewer) was at 6:08pm and then no activity (including and starting or stopping of services) until after 9pm on the 12th was seen.  It shows in the jobs in the automation account, XYZSQLServer starting at 6:32pm but there is no other jobs showing any other server started during this time.

Analysis: It can be seen there is no issue with the Automation environment since runbook ran multiple times but did not fail to execute instead it might be the code in the runbook. Runbooks stop the servers and restart them. It’s weekly reboot of the multiple servers in that subscription. It starts with the SQL database server first giving it time to stop and start. Seems the error is not related to automation environment but to allocation in Azure in that specific moment where it tried to start the SQL server but there were not enough resources as stated by the error message. Based on the information provided in the runbook it seems to be an allocation issue that Azure had in that moment.

Cause Identified: Failed due to allocation issues with Azure in a specific time range. The Region this VM is associated with did not have enough capacity for the requested VM size at the time of provisioning to support its allocation.

Resolution/Recommendation:

Please review the recommendations above to understand alternative sizes or regions. In addition, try starting the VM again as the issue might have been temporary and there now could be sufficient resources for the allocation.

To determine sizes by ...	Do the following
Azure portal	Select the VM in the Azure portal. Under Settings, choose Size. On the Size blade, you can view available sizes and use filter options.
PowerShell	Use the Get-AzComputeResourceSku command and filter for a region: Get-AzComputeResourceSku | where {$_.Locations.Contains("<<insert-region>>")}
Azure CLI	Use the az vm list-skus command with the --location parameter to filter for a region and the --size parameter to match the size name: az vm list-skus --location <<insert-region>> --size <<insert-size>> --output table
REST API	Use the Resource SKUs - List operation.

You can also peruse Products available by region to see which products are available in all the regions.

Reference: Created by troubleshooting provided by Microsoft Azure Support