Could not create a Private Channel using Microsoft Graph API on a Targeted/First Release tenant

Sander 36

We are having issues creating a Teams Private Channel within Targeted Release M356 tenants when using Microsoft Graph API.

When we want to create a Private Channel the channel is created but the SharePoint folder backing up the channel is not created. When opening the Files tab of the private channel within the Teams client is also not creating the folder and only shows a white page.

The same functionality is working perfectly within a Standard Release tenant so this issue only applies to Targeted/First Release tenants. We see the issue happening on 3 of our tenants, all Targeted release.

We are creating the private channel using the following Graph API statement:

teams/{groupId}/channels

This Graph API is returning information about the newly created channel and looks ok.
It fails when executing the following Graph API query:
teams/{groupId}/channels/{channelId}/filesFolder

The message from that query is:
Folder location for this channel is not ready yet, please try again later. (NotFound)

Anyone has idea how to fix this issue?
@Microsoft

JimmyYang-MSFT 53,931 Reputation points Microsoft Vendor

2023-12-01T05:15:53.84+00:00

@Sander

Teams tag is mainly focused on the general issue of Microsoft Teams troubleshooting. According to your description, your question is related to Teams development, which is not in our support scope. So I will remove teams tag from your thread. Thanks for your understanding!
Rohit Varghese 1 Reputation point

2023-12-01T06:09:43.65+00:00

@Sander

Facing the same issue here. Have you found any solution? Or posted any new thread?
Sander 36 Reputation points

2023-12-01T06:58:54.5866667+00:00

Hi @Rohit Varghese we still see the issue at our tenants. We did not find any workaround untill now.
Also opening the Channel Files tab within Teams is not triggering the creation of a private site with SharePoint folder, so no luck there.
We are still investigating the options for a workaround but untill now no luck.
Also tried using both Application and Delegated permissions, but both are causing the same issue.
Rohit Varghese 1 Reputation point

2023-12-01T07:06:15.8933333+00:00

I agree. Kindly let us know if you find anything. We are also checking for any workaround. Thanks @Sander
Sander 36 Reputation points

2023-12-05T08:28:41.28+00:00

Hi @Rohit Varghese we found a workaround, but not a great one...

When the private channel has been created with only one owner, that same owner can open Microsoft Teams and click on the Files tab of that newly created Channel. In this case the SharePoint site and folder backing up the channel is created.
It is also created when using Microsoft Graph API and the following query with Delegated permissions of the current owner:
teams/{groupId}/channels/{channelId}/filesFolder

Again not a great solution, but maybe it works for your business case?

No one from @microsoft readering this post and have an idea about the issue and possible solution?
Sander 36 Reputation points

2023-12-12T08:25:16.8+00:00

Hi you all, we also found out the issue is not only regarding Microsoft Graph API but also exists when creating a Private Channel from within the Microsoft Teams Admin.
When a Private Channel is created from the Microsoft Teams Admin and the Private Channel Files tab is opened by a member of the Channel the content of the files tab is not shown and stays blank.
Only when the owner of the Private Channels opens the File tab the corresponding SharePoint site and folder is created and shown within the files tab. After this action it is also available for the members in the Channel.
Sander 36 Reputation points

2023-12-12T08:26:54.6733333+00:00

So @JimmyYang-MSFT , the issue is now also regarding Microsoft Teams itself while as explained above the issue also occurs when creating the Private Channel from Microsoft Teams Admin.
Could you please add the Microsoft Teams tag again, maybe it will help solving this issue. Thank you!
Steve 0 Reputation points

2023-12-24T18:39:16.2566667+00:00

I’m seeing the same issue in one of my tenants, but not the other.

Weirdly, everything was working fine up until the 12 December, but since then, I’m getting the issue seen in this thread despite the MS documentation describing that when this occurs, trigger the filesFolder endpoint to trigger the provisioning, which no longer works.

I’ve since built a custom function to check to see when the SharePoint site has been provisioned and then to continue a few custom actions.
Sander 36 Reputation points

2024-01-17T07:47:01.9566667+00:00

According to Microsoft Support they hope to have a fix by the end of January.
Jenny Pitts 0 Reputation points

2024-01-17T12:12:16.9466667+00:00

Sander you have mentioned a MS issue do you have any details about this I can look at as I believe this is impacting a few of our customers also?
Sander 36 Reputation points

2024-01-17T13:18:06.26+00:00

I guess I have added all details in the thread. What are you looking for additional details @jenny pitts?
Sander 36 Reputation points

2024-01-31T10:30:40.6833333+00:00

It really got worse tonight. Now we also see this problem on Standard Release tenants. So this problem is now happing on ALL tenants.
Microsoft reaction:
Sander 36 Reputation points

2024-01-31T10:34:11.7833333+00:00

It got even worse tonight. The issue with creating private channels is now seen on all tenants, so also on Standard Release tenants.
Reaction of MS:
Nelson, Joel 0 Reputation points

2024-02-28T16:05:02.97+00:00

We've had this working under automation for the last year or two and now suddenly it no longer is working and is causing us much pain. Have tried looping at the filesfolder endpoint for up to an hour on the general channel with no luck. Used to work in a couple minutes. Is Microsoft monitoring this thread? If so, please fix asap.
Sander 36 Reputation points

2024-02-29T07:03:31.8366667+00:00

Hi Nelson, Joel, at our environments this is working OK at the moment. Do you call the FilesFolder Graph endpoint of the Channel after creating the private channel? This should trigger the creation of the backend site, document library and folder.
URL: https://learn.microsoft.com/en-us/graph/api/channel-get-filesfolder?view=graph-rest-1.0&tabs=http

Annadurai, Sivakumar (EXT) 0

Same issue ,

Folder location for this channel is not ready yet, please try again later.

{
  "error": {
    "code": "NotFound",
    "message": "Folder location for this channel is not ready yet, please try again later.",
    "innerError": {
      "code": "ItemNotFound",
      "message": "Folder location for this channel is not ready yet, please try again later.",
      "details": [],
      "date": "2024-11-19T05:45:50",
      "request-id": "e8f35851-97f1-45cd-872e-e86bedbe1b85",
      "client-request-id": "e8f35851-97f1-45cd-872e-e86bedbe1b85"
    }
  }
}

https://graph.microsoft.com/v1.0/teams/7-9191-067e6e7abd80/channels/19:5f34d86625344a4c973e08@thread.tacv2/filesFolder?$select=weburl

1 answer

Sander 36 Reputation points

2024-02-05T11:14:43.58+00:00

We have seen that the issue has been resolved at the first of February. Microsoft also confirmed they have fixed this issue.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Could not create a Private Channel using Microsoft Graph API on a Targeted/First Release tenant

1 answer

Your answer