An attempt was made to modify an object to include an attribute that is not legal for its class I have found that this is due to the vast majority of our AD user objects ... if I try Set-ADUser ...

So for the last few years, I've had some various powershell scripts that I've been running as scheduled tasks to set different attributes of our user objects in AzureAD (We have an on-premises AD ...