I have no explicit source for this scenario, but I am a 365 admin and extrapolated from my knowledge of Intune.
The way I see it, there is nothing actually preventing Microsoft from blocking computers from using personal 365.
Just look at the autopilot service in intune, you add a machine to it using either a machine ID or a serial number, then it is locked to that tenant and can’t be used outside of that with windows.
There is no checking of actual ownership of the device, and once a device is added to autopilot, it will prompt for a tenant logon even after a complete reinstall.
This means that MS will check any computer that checks in with their servers for their ID and s/n, and against a blocklist.
I have no explicit source for this scenario, but I am a 365 admin and extrapolated from my knowledge of Intune.
The way I see it, there is nothing actually preventing Microsoft from blocking computers from using personal 365.
Just look at the autopilot service in intune, you add a machine to it using either a machine ID or a serial number, then it is locked to that tenant and can’t be used outside of that with windows.
There is no checking of actual ownership of the device, and once a device is added to autopilot, it will prompt for a tenant logon even after a complete reinstall.
This means that MS will check any computer that checks in with their servers for their ID and s/n, and against a blocklist.