Hello John Johnson,
Welcome to the MS Q&A Forum.
There are numerous possible causes for your disconnection from the Azure VM. Based on your explanation, it appears that the current VM size does not have sufficient resources to support all the processes you are running. To address this issue, I suggest reviewing a checklist of best practices and guidelines to optimize the performance of your SQL Server on Azure Virtual Machines (VMs).
While running SQL Server on Azure Virtual Machines, continue using the same database performance tuning options that are applicable to SQL Server in on-premises server environments. However, the performance of a relational database in a public cloud depends on many factors, such as the size of a virtual machine, and the configuration of the data disks. There's typically a trade-off between optimizing for costs and optimizing for performance. This performance best practices series is focused on getting the best performance for SQL Server on Azure Virtual Machines. If your workload is less demanding, you might not require every recommended optimization. Consider your performance needs, costs, and workload patterns as you evaluate these recommendations. Overview: Checklist: Best practices for SQL Server on Azure VMs
Furthermore, you may consider utilizing PerfInsights on Azure VM to pinpoint the areas where resource utilization is constrained.
PerfInsights is a self-help diagnostics tool that collects and analyzes the diagnostic data, and provides a report to help troubleshoot Windows virtual machine performance problems in Azure. PerfInsights can be run on virtual machines as a standalone tool, directly from the portal by using Performance Diagnostics for Azure virtual machines, or by installing Azure Performance Diagnostics VM Extension.
Hope above answers your question and concern. Let me know if you need additional assistance. If the answer was helpful, please accept it and complete the quality survey so that others can find a solution.
Sincerely,
Olga Os.