Every customer has their own personality. Some customers come from different industries, while other customers espouse different visions and atmospheres. One customer may request Satisfaction Survey Analysis and yet another may request Sales Channel Analysis, or Competitor Analysis.
However, there is at least one trait that all customers have in common. Every customer needs to believe that their company resources ($$$) are being used in an efficient and financially responsible manner.
It is out of this common desire to always improve efficiency and enforce financial responsibility that the value of Azure (Cloud) comes into clear light. Features such as elasticity, scalability, and compute pause all help organizations reduce on-premises infrastructure, maintenance, and personnel costs.
One example where Azure cloud saves a customer money is by only charging for what is stored and what is computed. Server waste (under-utilization) is shown on this page's title diagram. In the Azure cloud, a customer is not charged for this waste.
Customers may decide to lift and shift current on-premises environments to the Azure cloud, or may intend on taking a more future, features driven approach, that strategically embraces a new Enterprise Data Architecture that relies entirely on Azure integration tools (not on-premises tools).
More aggressive approaches include moving on-premises SQL Servers to the cloud, while making sure all of the new Enterprise Data Architecture relies on data sources only in the cloud. Hybrid approaches of migrating some SQL Servers to the cloud, while other servers use a data Gateway and remain on-premises are often incorporated.
Do you need to Lift and Shift existing SQL Server(s) to the Cloud, or Implement a Modern Azure Cloud Data (Storage) Architecture including a Data Lake, a Data Warehouse, and an Analytics / Analysis platform with analyst visualizations?