SharePoint Created By user has no email associated

[irondinges]

Good day,

I have a flow that generates an email alert when a list item is created.

This uses the "Created By - Email" dynamic content item from the trigger body.

One of my users has an issue where they do not receive emails when creating items. The flow works fine for other users (I have used this same pattern on dozens of flows with success).

Upon closer inspect of the flow's run, I noticed that the "Email" field for the "Created By" user is null. See below:

Some background information on my company's structure.

We have two tenants:

Tenant 1 - This is the tenant in which the flow lives. I have an account in this tenant.

Tenant 2 - This is the tenant of the user above who is having the issue.

The SharePoint site that the flow is connected to is a Team site created in Tenant 1. The user is part of this Team ("guest" user).

I investigated a bit further by querying the "User Information List" using Power BI, where indeed this user's email field is blank.

Note that other users from Tenant 2 do have an Email address, and presumably the flow would work fine for them.

I am not sure if this issue is beyond the scope of this forum, and where I should go if this is more a SharePoint related issue.

Is there a way to "edit" the user on the SharePoint user information list to resolve this?

Or will I have to split the Created By - Claims field to "build" the email address?

I want to avoid this as it adds unnecessary complexity for what I believe should be a simple system.

[v-bacao-msft · Accepted solution]

Hi @irondinges ,

You can complete the corresponding user information in the Office 365 admin center.

Or you can split the Created By-Claims field to get the email address. Like:

last(split(triggerOutputs()?['body/Author/Claims'],'|'))

Best Regards,

[irondinges]

Hi @v-bacao-msft ,

Thank you for the suggestion.

I did have to extent the split logic a little bit.

The claims string is in the following structure:

"i:0#.f|membership|name.surname_tenant2.com#ext#@tenant1.com"

So I did a split by |, then by #, and finally replaced the _ with @.

[jvdlinden]

I have found that this could also happen when there is no Exchange plan enabled for the user account that had created the item. That also causes the Email property to be null.

In my scenario, the user was assigned a Office 365 E3 license, but Exchange Online (Plan 2) within it, was not enabled.