Azure VM Drive size configuration for MS-SQL

I have run into a scenario for a production server where **I was recommended to create a separate drive for each one of the bigger clients** (based on database sizes) whereas all other smaller clients can be placed on the same drive in Azure VM for better performance. Eg: - Client 1 has 800GB size (data file) - Client 2 has 900GB size (data file) - Client 3 has 50GB size (data file) - Client 4 has 40GB size (data file) We already have - 1 separate drive ****D:** for temp db** (both .ldf and .mdf are stored on drive D) - and 1 separate **drive E: for log files** (all .ldf file for all clients is stored here on E:) - and I was recommended to create a Drive F: for Client 3 and Client 4 (to store data files whereas their log files are already stored in E:), - Drive G: for Client 1 (to store data files whereas their log files are already stored in E:) - and Drive H: for Client 2 (to store data files whereas their log files are already stored in E:). Can this increase performance? Also, if I need to add a disk (Premium SSD) for 1 TB, would it be good if we use 256*4 or 512*2 or a single 1 TB disk? Please let me know if anyone has any experience with this.