Getting error while creating Microsoft Graph Distribution list of beta version

Question

Getting error while creating Microsoft Graph Distribution list of beta version

Baljeet Kaur 0

I tried to create a distribution list using example at url https://learn.microsoft.com/en-us/graph/api/user-post-distributionlists?view=graph-rest-beta&tabs=http

I tried in Postman with method => POST /users/{id | userPrincipalName}/distributionLists

URL=> https://graph.microsoft.com/beta/users/{userPrincipalName}/distributionLists

Content-Type: application/json

Authorization: Bearer {token}

Body=> same as in url example

The user is having Application-Contacts.ReadWrite permission
My postman request details are

ms-ags-diagnostic{"ServerInfo":{"DataCenter":"Central India","Slice":"E","Ring":"3","ScaleUnit":"002","RoleInstance":"PN2PEPF000007D0"}}DateTue, 21 Jul 2026 08:30:32 GMT

and I am getting this error

{
    "error": {
        "code": "RequestBroker--ParseUri",
        "message": "Resource not found for the segment 'distributionLists'."
    }
}

Could you please correct me if I am doing something wrong.

0 comments

2 answers

Your answer

Answer 1

/distributionLists is a Microsoft Graph beta-only mailbox API. The documented create endpoint is:

POST /me/distributionLists
POST /users/{id | userPrincipalName}/distributionLists

The error:

{
  "error": {
    "code": "RequestBroker--ParseUri",
    "message": "Resource not found for the segment 'distributionLists'."
  }
}

indicates Microsoft Graph is not resolving that path in the request being sent.

Check these points:

Use the beta endpoint exactly:

   https://graph.microsoft.com/beta/users/{id-or-userPrincipalName}/distributionLists

or:

   https://graph.microsoft.com/beta/me/distributionLists

Ensure the token includes Contacts.ReadWrite permission. For create, the least-privileged permission is:
- Delegated: Contacts.ReadWrite
- Application: Contacts.ReadWrite
Send the required headers:
- Authorization: Bearer {token}
- Content-Type: application/json
Ensure the JSON body includes at least the required property:
```
   {
     "displayName": "My Distribution List"
   }
```
members is optional.
If using an SDK, note that Microsoft Graph SDKs use v1.0 by default. For this API, the request must target beta.

A minimal HTTP example is:

POST https://graph.microsoft.com/beta/me/distributionLists
Authorization: Bearer {token}
Content-Type: application/json

{
  "displayName": "My Distribution List"
}

If the request still returns Resource not found for the segment 'distributionLists', switch from /users/{userPrincipalName}/distributionLists to /me/distributionLists with a delegated token and verify the request is actually going to graph.microsoft.com/beta/... rather than v1.0. This API is documented only under beta, and beta APIs are subject to change and not supported for production use.

Answer 2

Michelle-N 20,735 Microsoft External Staff Moderator

Please note that Q&A forum is a public platform, and moderators will modify the question to hide personal information in the description. Kindly ensure that you hide any personal or organizational information the next time you post an error or other details to protect personal data.

Hi @Baljeet Kaur

Based on the error, I do not think the issue is with the JSON body. The error Resource`` ``not`` ``found`` ``for`` ``the`` ``segment`` ``'distributionLists' indicates that Microsoft Graph is not resolving the distributionLists segment in the request URI.

Please make sure you are not using the literal placeholder {userPrincipalName} in the URL. Replace it with the actual user principal name, for example:

POST`` ``https://graph.microsoft.com/beta/users/******@domain.com/distributionLists

or test first with:

POST`` ``https://graph.microsoft.com/beta/me/distributionLists

Also confirm that the token has the required Contacts.ReadWrite permission. Since this API is currently under Microsoft Graph /beta, it may be subject to change and may not be available in all environments. I would also suggest testing GET`` ``https://graph.microsoft.com/beta/me/distributionLists. If that returns the same Resource`` ``not`` ``found error, the endpoint is likely not currently available for your tenant/mailbox path rather than being a request body issue.

If the requirement is to create a tenant-level Exchange Online distribution group, the recommended and stable approach is to use Exchange Admin Center or Exchange Online PowerShell with New-DistributionGroup.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Baljeet Kaur 0 Reputation points

2026-07-21T15:11:16.5666667+00:00

Now I tried it in C# with nuget package Microsoft.Graph.Beta version 6.2.0 preview but I am not able to find DistributionList class in Microsoft.Graph.Beta.Models

The documentation clearly states that its available in latest version of Microsoft.Graph.Beta nuget package
Michelle-N 20,735 Reputation points Microsoft External Staff Moderator

2026-07-22T11:52:47.11+00:00
Hi @Baljeet Kaur

Thank you for your update. After researching, please refer the following idea:

Short-term (if you need personal distribution lists / contact groups now)

If you need to create personal distribution lists (Outlook contact groups) immediately, the best option is to wait for Microsoft Graph support if your timeline allows. In the meantime, Exchange Web Services (EWS) remains a viable workaround for many tenants. Although EWS is in maintenance mode, it still supports creating distribution lists by using CreateItem in the Contacts folder and setting the appropriate distribution list properties. Another possible approach is the legacy Outlook REST API, but this is not recommended because the API is being retired. If you want to stay within Microsoft Graph, your options are currently limited: you can create individual contacts and contact folders, but you cannot create a true expandable Outlook distribution list (the type that Outlook recognizes and manages as a contact group) through the stable Graph APIs today.

If the real requirement is a tenant-level Distribution Group (classic DL)

This is a completely different object. Use one of these stable methods:

Option A – Microsoft Graph (recommended for pure Graph solutions)

POST https://graph.microsoft.com/v1.0/groupsContent-Type: application/json{ "displayName": "My Distribution Group", "mailEnabled": true, "mailNickname": "my-dl", "securityEnabled": false, "groupTypes": []}

Option B – Exchange Online PowerShell (most reliable)

New-DistributionGroup -Name "My Distribution Group" -Alias "my-dl" -Type Distribution

Regarding the C# SDK issue

Even if the DistributionList model appears in a future Microsoft.Graph.Beta package, the call will still fail with the same RequestBroker--ParseUri error until the service actually supports the segment. The model generation is driven by the OpenAPI description, which can be updated before the runtime endpoint is live

Thank you for your patience.