Aug 22 2017 04:39 PM
Is there a way to email a SharePoint Group from a Flow? (not an O365 Group, not an AD group, but a legit SharePoint group)
Or do I have to define and maintain an actual Distribution Group for flow to send to?
Sep 11 2017 09:26 AM
I'm also looking for this... this is a major step back for one of our projects.
Oct 06 2017 08:49 AM
Your group should have an email assigned to it like GROUPNAME@groups.yourorg.com to which you can send any normal email through your outlook connector
Oct 31 2017 01:40 PM
Dec 04 2017 01:34 PM
May 14 2018 02:22 AM
This will not work. Tested but no success
May 14 2018 04:13 AM
Jul 11 2018 07:11 AM
Hi,
Can i know how to use Active Directory Security group or Distribution group on Microsoft flow Approval Process.
Please let me know if there is any direct step or any work around to fix this requirement.
Sep 06 2018 09:28 AM
Is there a way to do this? I am running into this now and need to email to all users in a SharePoint Group.
Oct 03 2018 09:37 AM
@Terry Hagan If I use this, where does it store the information for me to be able use it later?
Oct 03 2018 12:54 PM - edited Oct 03 2018 12:55 PM
Here is what I do for this (I am using this pattern for sending emails and assigning Flow tasks):
1) Initialize a variable of type string called "SendEmailTo"
2) Use the SharePoint HTTP call (i try to do everything using the Group ID)
3) Use the Parse Json action against the body of the SharePoint Http using the schema in the attached file
4) Do an Apply to Each on the body of the Parse Json action, and append the email (IMPORTANT with a semi colon) to your variable. This is will built you a string of email addresses that can be used in the send email action.
SCHEMA FOR PARSE JSON ACTION
{
"type": "object",
"properties": {
"d": {
"type": "object",
"properties": {
"results": {
"type": "array",
"items": {
"type": "object",
"properties": {
"__metadata": {
"type": "object",
"properties": {
"id": {
"type": "string"
},
"uri": {
"type": "string"
},
"type": {
"type": "string"
}
}
},
"Alerts": {
"type": "object",
"properties": {
"__deferred": {
"type": "object",
"properties": {
"uri": {
"type": "string"
}
}
}
}
},
"Groups": {
"type": "object",
"properties": {
"__deferred": {
"type": "object",
"properties": {
"uri": {
"type": "string"
}
}
}
}
},
"Id": {
"type": "number"
},
"IsHiddenInUI": {
"type": "boolean"
},
"LoginName": {
"type": "string"
},
"Title": {
"type": "string"
},
"PrincipalType": {
"type": "number"
},
"Email": {
"type": "string"
},
"IsEmailAuthenticationGuestUser": {
"type": "boolean"
},
"IsShareByEmailGuestUser": {
"type": "boolean"
},
"IsSiteAdmin": {
"type": "boolean"
},
"UserId": {
"type": "object",
"properties": {
"__metadata": {
"type": "object",
"properties": {
"type": {
"type": "string"
}
}
},
"NameId": {
"type": "string"
},
"NameIdIssuer": {
"type": "string"
}
}
}
},
"required": [
"__metadata",
"Alerts",
"Groups",
"Id",
"IsHiddenInUI",
"LoginName",
"Title",
"PrincipalType",
"Email",
"IsEmailAuthenticationGuestUser",
"IsShareByEmailGuestUser",
"IsSiteAdmin",
"UserId"
]
}
}
}
}
}
}
Oct 04 2018 01:48 AM
It doesn't store anything, the information, user title and email, is already stored in the SharePoint Group for you to use when you retrieve it.
Oct 04 2018 03:28 PM
I figured out how to do this some time ago. Since there's still interest in this I wrote up a blog post showing how to do it: https://techcommunity.microsoft.com/t5/PowerApps-Flow/Email-a-SharePoint-Group-from-Flow/m-p/266744#...
Dec 10 2018 10:30 PM
The link to the blog is broken - it takes me back to the post. Anyone managed to solve this? SharePoint Designer Workflow were so much easier.
Jun 10 2019 04:29 PM
I also didn't get this to run with the provided JSON.
I had a successful run after I changed it to this:
Sep 10 2019 08:57 AM
Microsoft, if you expect people to be moving away from Workflows to Flow, they're going to need BASIC functionality like this, not some hacky REST API calls done out of desperation.
Sep 23 2019 07:49 AM - edited Sep 23 2019 07:58 AM
I wouldn't suggest that using a REST call is a "hacky" technique out of desperation, although I understand your frustration if you are a power user. Most things for a web developer or software engineer are done via REST calls to a database, so this technique is very familiar. Brent's answer works perfectly fine for me and was well documented. The only thing he forgot to include was adding the variable, but once again, this is a familiar thing for a web dev.
Modifications from Brent's answer:
I removed "Title" from the filter to just return only emails since that's all that's required.
/_api/Web/SiteGroups/GetById(29)/users?$select=Email
Here's what I used for my schema, if you use this as sample payload it'll just convert the values such as "some text" to it's data type "String".
{
"d": {
"results": [
{
"__metadata": {
"id": "Some text",
"uri": "Some text",
"type": "SP.User"
},
"Email": "Some text"
},
{
"__metadata": {
"id": "Some text",
"uri": "Some text",
"type": "SP.User"
},
"Email": "Some text"
},
{
"__metadata": {
"id": "Some text",
"uri": "Some text",
"type": "SP.User"
},
"Email": "Some text"
}
]
}
}