Storage pool configuration for SQL Server
Is [using a single pool] applicable to Always-On or just applicable to shared storage FCI.


FCI's in Azure use storage spaces direct for disk replication, which I imagine is the source of this requirement.  For AGs you can use multiple separate disks or pools.  You should ensure that the same logical volumes and paths are available on each node, otherwise AG replication will stop if you perform file and filegroup operations on the primary.  EG if you ad a file 'g:\sql\data\foo.ndf' to a database, that path needs to exist on all the other cluster nodes for that change to be replicated.  See Troubleshoot a Failed Add-File Operation (Always On Availability Groups).

Also, wherever you put Tempdb data files, put Tempdb log there too.  Splitting out tempdb's log is overkill as it's likely to be underutilized, and its IO access patterns are more like tembdb data files than user database log files.  In particular transaction commit doesn't flush the tempdb logs.