Same wizard, reversed — you type the identity you expect, and the regular expressions and the formula are worked out for you.
Follows learn.microsoft.com/microsoft-365/copilot/connectors/map-non-entra-id and /map-entra-id
1Identity source
How the data source stores its user identities.
2Microsoft Entra user property
The Entra property the mapped identity has to match. Suggested from the identity you type in step 4 — change it if you need a different one.
3Non-Microsoft Entra user properties to map
Add one or more. The sample value is what that property normally holds — replace it with a real value from your data source.
4Expected result
Instead of writing the formula, type the identity this mapping has to produce.
5Generated configuration & preview
Enter these values in the wizard, field by field. The preview runs the formula forward against your sample values.
✎Summary to copy
Every field of the wizard, in order.
—
!Before you publish
One mapping applies to every user. Conditional mappings are not supported.
You cannot change the mapping after the connection is published.
Regular expressions extract, they never transform. They cannot change case, reorder characters, or add anything that is not already in the value — so if what you expect is not literally inside the property, no expression can produce it.
Regular expressions are not supported on the ME-ID path. Microsoft Entra user properties go into the formula whole.
Replace the sample values with data your connector really returns. Service accounts, contractors and merged domains are where a mapping usually breaks.
The wizard Preview shows five random users. Green there does not prove every user maps.