@Reg ,
Firstly, Just to provide you a good understanding on hosting website on Azure. The term compute refers to the hosting model for the resources that your application runs on.
As a starting point reference ( it's for all websites), you may take a look at the criteria and flow chart (Decision tree for Azure compute services), weigh the platform strengths based on your organizational requirement and then chose the best platform.
Azure offers several ways to host websites: Azure App Service WebApps (PAAS solution), Virtual Machines (IAAS), Azure Static WebApps, Service Fabric and Static website hosting in Azure Storage. You can leverage the service that best suits your requirement.
- Azure Storage allows you to serve static content like HTML, CSS, JavaScript, and images from a
$web
storage container. This setup supports serverless architectures, including Azure Functions and other PaaS services, eliminating the need for a web server.
However, static websites on Azure have certain limitations. For instance, header configuration is only possible through Azure CDN, not directly within the static website feature. Also, authentication and authorization (AuthN and AuthZ) aren’t supported.
2.If these (above) features are crucial for your use case, Azure Static Web Apps is a viable alternative. It supports header configuration, AuthN, and AuthZ. Plus, it offers a fully managed CI/CD workflow from GitHub to global deployment.
3.For scenarios requiring a web server to render content, Azure App Service is recommended.
Migration:
Azure Storage migration overview -This article focuses on storage migrations to Azure and provides guidance on the following storage migration scenarios.
For more specific product migration scenarios, you can refer to the Cloud Adoption Framework.
If my answer helped (pointed, you in the right direction) > please click Accept Answer - it will benefit the community/users to find the answer quickly.