Hello @Dan Goodson ,
Thanks for reaching out.
No, "Device authentication failed" (error 50155) could happen for several reasons like device is disabled or pending on AAD.
You could verify device status from Azure portal --> Azure AD --> Devices --> All devices
Disabling : Disabling a device prevents it from authenticating via Azure AD
Pending : Pending devices indicates that the device has been synchronized successfully using Azure AD connect form
your on-premise Active Directory and it is ready for device registration, but is not registered to Azure AD yet.
If it is Azure AD join kindly remove the device from Azure AD and try joining back then check whether you were receiving error message again. To fix the problem, unregister the device by running dsregcmd /debug /leave
and dsregcmd /debug /join
at an elevated command prompt.
or if it is an Hybrid Azure AD join then Verify that the device is synced from cloud to on-premises or is not disabled. Sync cycles may be delayed since it syncs the Key after the object is synced.
Hope this helps.
------
Please "Accept the answer" if the information helped you. This will help us and others in the community as well.