Hey folks,
I'm not sure where the idea that Azure Files doesn't support SMB Multichannel if the storage account has private endpoints, but it's not true. You can absolutely use private endpoints and SMB Multichannel together. If there's ever been any point in the documentation where we said otherwise, please let me know and I will promptly fix it.
I feel that the documentation for the Get-SmbMultichannelConnection cmdlet is confusing. I'm not sure why the screenshotted output from the documentation shows multiple entries for each server - I notice that screenshot seems to imply that there are multiple NICs, so perhaps that has something to do with it? I'm not an expert on what the cmdlet does, so I don't want to speculate much more than that.
With respect to a stock Azure VM, we only expect to see a single row per "server" if there's a SMB Multichannel connection. The returned objects from Get-SmbMultichannelConnection show the current and max channels of the mount. SMB will increase/decrease the current channel count as needed based on data transfer. You can see this with the following command:
Get-SmbMultichannelConnection | Select *
If SMB Multichannel is not enabled on this storage account, or is not negotiated on the client side (client negotiates by default), then you would see no results for the Get-SmbMultichannelConnection command.
Please let me know if you have any questions.
Thanks,
Will Gries
Principal Product Manager, Azure Files