Issue: EntraID accounts not showing in landscape's user page

### Is there an existing issue for this?

- [X] I have searched the existing issues and found none that matched mine

### Describe the issue

The title says it all. Customer logs in the desktop with an EntraID account (which works), and expects that that user is now part of the accounts on the machine, but Landscape server does not reflect that in its user list.

This may be important to allow for script execution as the user or other user-specific operations.

While this initially may seem like a Landscape issue, I think it makes sense that the discussion start here because it may be something in the middle, something that authd is doing different from the traditional way and what landscape client expects.

### Steps to reproduce

1. Register a machine in a landscape server
2. Log in locally with an authd account (in this case, EntraID)
3. Check if landscape will add that user to its user list

### System information and logs

_No response_

### Double check your logs

- [X] I have redacted any sensitive information from the logs

No files or tests are named. Start by reproducing the three listed steps, then trace how authd-created EntraID users are discovered and reported to Landscape compared with traditional local users. Done means the expected EntraID account appears in Landscape's machine user list, with behavior suitable for user-specific operations.

Written by the indexing model from the issue text.