Azure App Services当前组成咨询：Logic Apps与Function Apps是否独立

Great question—this is a common point of confusion since Azure's service lineup has evolved over time. Let me break this down clearly:

Current Azure App Service Core Offerings #

Azure App Service now centers on these specialized, closely integrated offerings (all built on the same underlying App Service infrastructure):

• Web Apps: The foundational service for hosting web applications, static sites, and general-purpose web workloads. This is the primary entry point you'll see in official docs since many other App Service offerings are optimized variants of this.
• Web Apps for Containers: A dedicated flavor of Web Apps that lets you deploy and run applications packaged in Docker containers (supporting both single-container and multi-container setups via Docker Compose or Kubernetes).
• API Apps: Optimized for building, hosting, and managing RESTful APIs. While listed as a distinct offering, it's essentially a Web Apps instance pre-configured with API-focused features like API Management integration, Swagger support, and CORS configuration.
• Mobile Apps: Built to power backend services for mobile applications, including features like push notifications, user authentication, offline data sync, and mobile-specific SDKs. Like API Apps, it's built on the Web Apps infrastructure with mobile-optimized tooling.

Status of Logic Apps & Function Apps #

You're absolutely right—both Logic Apps and Function Apps have moved to become standalone service categories in Azure:

• Azure Functions (Function Apps): Now a fully independent serverless compute service focused on event-driven, on-demand code execution. While it originated as part of App Service, it now has its own dedicated management plane, pricing models (Consumption, Premium, Dedicated), and feature set tailored for serverless workloads.
• Azure Logic Apps: A low-code/no-code integration service for building automated workflows that connect apps, data, and services. It also started under App Service but is now a standalone service, with two deployment options: Consumption plan (serverless, pay-per-execution) and Standard plan (runs on App Service infrastructure but managed as a separate service).

The reason you might see the official App Service page linking directly to Web Apps is that Web Apps is the core of the App Service platform, and the other offerings are specialized use cases built on top of it—so consolidating the docs there makes sense for consistency.

内容的提问来源于stack exchange，提问作者Nashmár