Azure cannot send the manager's name or email there, and the value '1234' is correct by design. It is Qmarkets' user ID (UID) echoed back, not an Azure id.
Why it is Qmarkets' UID?
- The SCIM standard defines manager.value as "the id of the SCIM resource representing the user's manager".
That id is whatever the SCIM server returned when the manager was provisioned. Referencing the manager by
the server's id is the whole design of the attribute.
- Qmarkets endpoint returns the user's id as the SCIM id. The id is set from the user's account .
Azure learned "1234" from Qmarkets when it created or matched that manager, and sends it back.
- An Entra object id is a GUID, so "1234" could not have come from Azure's side anyway.
Why it is a bare string and not {value, $ref, displayName} ?
That part is a known Microsoft deviation. In the Microsoft Q&A thread on this exact payload, Microsoft
employees said the service sends only the id as a simple string, that there is "no way to achieve" anything
else, that customised referential attributes are not supported, and that the manager's displayName is not on
the roadmap.
The thread still has unresolved complaints dated May 2026.
Important points:
- Azure sends the manager only once the manager is themself provisioned to Qmarkets' app. If the manager comes into
scope later, the reference stays empty until the customer restarts provisioning.
That is documented on the Entra known-issues page.
- There is no Azure mapping setting that switches this to email or UPN.
Qmarkets can setup a Supervisor/Manager value to appear as username/email address value (instead of the manager's
UID) in idea/s a user submits.
Please contact your CSM if you would like to use this functionality.