I figured you were being genuine, but there’s usually a few people who point at Microsoft’s “embracing” of Linux as the first step in the “embrace, extend, extinguish” trope, and see any involvement by Microsoft as nefarious. When the reality is just that Microsoft’s Azure cloud services are a much larger share of their annual revenue than Windows, and Linux is a major part of their cloud offerings.

If you browse the LKML (Linux Kernel Mailing List) for 5 minutes, you’ll probably see a bunch of microsoft.com email addresses, and it’s been that way for years. I understand why it bothers some people, but also Linus (and a couple others) approve everything that actually gets merged, whether it’s from a microsoft employee, or a redhat employee, or anyone else. Even if microsoft wanted to pay employees to submit patches that would hurt the kernel, the chance that they’d actually be approved is so low it wouldn’t be worth their time.

There are some differences between distros as to whether TRIM is enabled by default or not (I’ve read Ubuntu enables it by default, but Debian does not). That said, depending on what file-system your ssd is formatted with it may be enabled by default at that level. The most-often recommended file-systems for SSDs are Btrfs and F2FS, both of which support and enable TRIM by default (as of Linux 6.2 for Btrfs, so if you are running an older kernel version you might need to manually enable it). I think most distro installers support using Btrfs as the main file-system, but F2FS is a bit more hit and miss I think. Safest bet would be to investigate once you settle on a distro, but support should be pretty standard, even if it’s not enabled by default.