Introduction
In SharePoint, sometimes we need to select more than one person for a record, like adding multiple team members or approvers. But updating a multi-select Person or Group column can be a bit tricky in Power Automate. In this article, we will learn a simple way to create or update this multi-select people field so you can use it easily in your flows.
Use Case
Sometimes a single record needs to have multiple users assigned to it, like approvers or reviewers. When updating this through a Power Automate flow , extra handling is needed so the multi-select Person or Group column works as expected. For this article, we will keep it simple by storing the user's email in a single variable and then using it to create the multi-select Person or Group column.
Below are the steps
Step 1
Go to your SharePoint list, create a new column of type Person or Group, and make sure Allow multiple selections is turned on.

Step 2
Go to make.powerautomate.com , open Power Automate, and create a new Manually triggered flow.
(As per your requirement, you can choose any trigger that fits your scenario.)

Step 3
Add a variable in your flow and give the name as "varMultipleUserEmails" and type as Array, then add emails in array format like ["[email protected]","[email protected]"].
You can add actual Office 365 user emails; here I am are just using these as a showcase.

Step 4
Add a Select action, set From as variables('varMultipleUserEmails') and map Claims as concat('i:0#.f|membership|', item()).

Step 5
Add a Create or Update item action, select your SharePoint site address and list name, make sure the Person or Group field is set to Switch to input entire array , and then add the Select action output.

Step 6
The above steps work fine when all users are already available in Office 365. But in real scenarios, data can come from multiple sources, and some records may contain email IDs that do not exist in the Office 365 tenant (as shown in the image).
To handle this, we need to change the approach. Before creating or updating the multi-select Person field, we should first verify whether the user exists in Office 365. Only if the user exists should we create or update the field; otherwise, the user should be skipped.










Join the conversation! Your thoughts help the community grow.