This message was deleted.

You’re referring to non-persistent/pooled desktops right? You could run

dsregcmd /join

there shouldn’t be an issue with that, but keep in mind that a new machine account could take up to an hour by default to be synchronised to Azure AD

I am, yes. Joining also fails, which is why I think this issue is on the MS side of things. The article that they provided when they told me “Citrix says to do something else” doesn’t even apply to us, and was more of an “you can also do it this way” article.

I just rely on BIS-F to take care of the leave on the master image and join on deployed machines. I have had issues previously with a non BIS-F client where the Scheduled Task didn't always seem to work and an extra startup script was added to explicitly run the /join.