600 concurrent users report slow logons and sluggish Outlook performance. FSLogix Profile Containers are stored on an Azure Files Standard (GPv2) share in the same region as the session hosts. Network and CPU utilization on hosts are normal. Which two actions will most directly improve profile performance? (Choose two)

Slow logons and sluggish Outlook with normal host CPU/network often point to storage performance bottlenecks for FSLogix profiles. Azure Files Standard (GPv2) has IOPS and throughput limits that can be insufficient for 600 concurrent users. Migrating to FileStorage (Azure Files Premium) provides significantly higher, consistent IOPS and throughput, directly addressing the performance issue. Sizing the share appropriately ensures enough provisioned IOPS. Increasing the Azure Files share quota on a Standard tier account also increases its baseline IOPS and burst throughput, offering a cost-effective improvement if Premium is not immediately feasible or fully required. SMB Multichannel is beneficial but requires specific client and server configurations and might not be the primary bottleneck here. NFS 4.1 is not typically used for FSLogix Profile Containers on Azure Files. DFS Namespace provides abstraction and referral, not direct performance improvement for a single underlying share.