People-reference anatomy

The diagram shows the universal three-step shape of any people-reference in Power Automate: the raw identifier the source row carries, the profile record it points to, and the actual email you reach via an Office 365 Users lookup. 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 middle box is an Office 365 Users lookup. When can a flow skip it?