@Vincent Walker I had discussion internally and below is the response I got :
Currently we do not have any MS web site that gives that definition that the customer might be looking for but we will consider it as feedback for our documentation.
The perspective on when to define a service as IaaS, PaaaS and SaaS is based on the degree of responsibility that the customer takes vs. the provider of the service.
Based on that, our definition is:
Azure VMs: IaaS
Azure Virtual Desktop (the service itself): PaaS
Windows 365: SaaS (DaaS)
While all of those services can consist of various components that might be IaaS on their own, what makes up the definition is the service that is provided.
With AVD, MS provides a managed service to connect securely to VMs and Apps. The customer is responsible to manage the VMs, but is not responsible to manage e.g. the Broker infrastructure, Gateways, licensing, Web Access etc.
With Windows 365, even the VM is itself is not running in the customer subscription and is provisioned by MS. The customer only takes care about installing apps and updates.
If you would call Windows 365 a DaaS service is really depending on what definition for DaaS you like to follow.
Some would say, W365 is DaaS as it offer a subscription based access to a Desktop incl. flexible monthly billing, a pre-configured environment and management tools to deploy the apps.
Some might say, W365 is not DaaS, as the customer would still need to install the apps & updates via MEM themselves and the end user cannot call MS directly if they have an issue using their Cloud PC.
Hope it helps!!!
Please "Accept as Answer" if it helped so it can help others in community looking for help on similar topics.