Exchange Online Distribution List Onwership

[Trevor L]

Hello all-

I currently have a requirement to pull all cloud distribution list owners in from Exchange Online and make those available in the platform to use in catalog items and/or approvals for distribution list management.  In my research into the Exchange Online spoke and Entra ID spoke, neither provide the capability to look up group owners.

Has anyone done this before and if so could you point me in the right direction to satisfy this requirement?

Thanks community!

[Shreya Shah]

You can create a custom action to fulfil this use case. You can explore https://learn.microsoft.com/en-us/graph/api/group-list-owners?view=graph-rest-1.0&tabs=http to know about the REST API endpoint and required inputs and given outputs.

You can copy an existing action and replace the above API specific details to create your custom action.

Or you can explore Spoke Generator to know how to create spoke actions using either OpenAPI specifications or Postman collection or using product documentation. You can watch a short introduction to the same in this video - https://youtu.be/P17CtwyItpM?si=9iR25nE0xyRkaDVQ

[Trevor L]

Hello Shreya-

Thanks for the reply.  Your provided link to the graph API only applies to Entra ID security groups.  Distributions lists in Exchange Online are not supported -- "Owners are currently not available in Microsoft Graph for groups that were created in Exchange, distribution groups, or groups that are synchronized from an on-premises environment."

If you have any insight on how to get Exchange Online group owners, I would appreciate any tips you have!

[Aartii01]

Hi 

Any response on the same, since I am as also struggling to find solution

[Trevor L · Accepted solution]

I was unable to find anything to allow a ServiceNow spoke to do this natively.  Our solution was to:

1. Have our Exchange Admin set up a Azure Runbook to collect the dist list owners and provide the output in JSON.
2. Configure a flow to run a Azure Automation Run Job action to run the runbook on a recurring basis.
3. The flow then processes the JSON and updates or adds owner records as needed.

Not the ideal solution, but it did work for our use case to help automate request item flows.