People-reference anatomy

The diagram shows the universal three-step shape of any people-reference in Power Automate: the field as Power Automate displays it, the raw identifier stored underneath, and the Office 365 Users lookup that resolves it to a profile with a real email. Dataverse uses a GUID, a SharePoint Person column uses an object, Salesforce uses a Lookup ID, and a plain text column just holds the address. Same three boxes, different labels.

Drumlin's Contracts list is the easy case: ResponsiblePartner already holds the address, so there is nothing to resolve. The pattern matters the moment a source stores an identifier instead.

The right-hand box is an Office 365 Users lookup. When can a flow skip it?