Creating Microsoft Teams Shared Channel fails with the message Failed to execute GetLicenseTypeAsync

Question

Creating Microsoft Teams Shared Channel fails with the message Failed to execute GetLicenseTypeAsync

SanderS 61

Hi, since Yesterday we see on multiple tenants an issue with creating Microsoft Teams Shared Channels. When creating the Shared Channel it fails with the following message:

Failed to execute GetLicenseTypeAsync.

This was working on all tenants before Yesterday but now failing without any change on our side on the calling code.

We are using the Graph URL teams/82d9ec5e-8d98-4141-8d23-xxxxxx/channels with a POST call to add the channel. The POST call contains the following body shown below. I also tried with different owners and with and without members, all with the same results.

{
	"membershipType": "shared",
	"members": [
		{
			"******@odata.bind": "https://graph.microsoft.com/v1.0/users('******@Domain.onmicrosoft.com')",
			"roles": [
				"owner"
			],
			"@odata.type": "#microsoft.graph.aadUserConversationMember"
		}
	],
	"@odata.type": "#Microsoft.Graph.channel",
	"description": "Shared channel provisioned by the automated regression tests",
	"displayName": "My Shared Channel"
}

The result of the call is als shown below.

{
	"error": {
		"code": "NotFound",
		"message": "Failed to execute GetLicenseTypeAsync.",
		"innerError": {
			"code": "Unknown",
			"message": "Failed to execute GetLicenseTypeAsync.",
			"date": "2025-06-17T07:21:53",
			"request-id": "99e76ecb-3b09-41b8-a711-20944e121ff7",
			"client-request-id": "99e76ecb-3b09-41b8-a711-20944e121ff7"
		}
	}
}

Does anyone have an idea what is going on and if there is a work around before Microsoft fixes this issue?

Nivedipa-MSFT 3,646 Reputation points Microsoft External Staff Moderator

2025-06-17T11:52:15.55+00:00

@SanderS - Thanks for bringing this issue to our attention. We will check and update you soon.
Jeremy Beatson 5 Reputation points

2025-06-17T23:23:27.28+00:00

We are seeing the same exact error in our tenant too for flows that include Graph API posts that have previously been working without error.

3 answers

Your answer

Nivedipa-MSFT 3,646 Reputation points Microsoft External Staff Moderator

2025-06-17T11:52:15.55+00:00

@SanderS - Thanks for bringing this issue to our attention. We will check and update you soon.
Jeremy Beatson 5 Reputation points

2025-06-17T23:23:27.28+00:00

We are seeing the same exact error in our tenant too for flows that include Graph API posts that have previously been working without error.

Answer 1

Benjamin 5

we have the same issue on multiple Tenants. It seems to be a bug in the Graph

SanderS 61 Reputation points

2025-06-18T07:25:46.1766667+00:00

Thank you @Gabriel-N and @Nivedipa-MSFT for your reactions.
I tried to add some example code here but I am not able to post it while it is getting removed everytime due to violation of the Code of Conduct.

I will send the code as private message, maybe that will work.
SanderS 61 Reputation points

2025-06-18T07:28:43.9666667+00:00

Not sure how to send a private message... If someone wants to receive the code just send me a provate mesage and I guess I can reply on that with the sample code.
Gabriel-N 1,715 Reputation points Microsoft External Staff Moderator

2025-06-18T08:17:20.44+00:00

Hi SanderS if you see a notification like this, please click “View Message”. I just sent you a PM!
Benjamin 5 Reputation points

2025-06-18T08:34:06.0833333+00:00

We have found out that it fails with App Only permissions (which are used in 99% of the cases). If you use delegated Permission it can create the shared channel.

Hopefully we will a quick fix from Microsoft. To change auth from App to Delegated will cost work and make no sense to use Delegated Permissions
Gabriel-N 1,715 Reputation points Microsoft External Staff Moderator

2025-06-18T12:41:34+00:00

Hi SanderSI found a suggestion from Benjamin, who faced the same issue as you, and I think it could be quite helpful. You might want to try running the code using delegated permissions, this approach worked well for Ben and could potentially resolve your issue too. Big thanks to Benjamin for sharing the solution, it’s been a great help to the community dealing with similar problems. Hope this works out for you as well!

Answer 2

Gabriel-N 1,715 Microsoft External Staff Moderator

Hi @SanderS

Thank you for posting your question in the Microsoft Q&A forum, and for reaching out regarding the issue you're encountering with creating a shared channel in Microsoft Teams. I'm sorry to hear you're facing these challenges and it’s completely understandable how frustrating and confusing this situation can be.

I appreciate you sharing part of your main code. To assist you more effectively, could you please provide the complete code, maybe via private message? This will allow me to conduct a more thorough review and offer more accurate guidance.

SanderS 61

Hi @Gabriel-N , sure.
I cannot give you the original code, while it contains several of our own PS Functions, but instead I created a small example code which gets the same error.

I will write a private message with the username and teamid we are using.


$groupId = "7b3ff276-3cb2-4592-a979-XXXXX"
$ownerName = "******@DOMAIN.onmicrosoft.com"
$body = @"
{
    "membershipType":  "shared",
    "members":  [
                    {
                        "******@odata.bind":  "https://graph.microsoft.com/v1.0/users('$ownerName')",
                        "roles":  [
                                      "owner"
                                  ],
                        "@odata.type":  "#microsoft.graph.aadUserConversationMember"
                    }
                ],
    "@odata.type":  "#Microsoft.Graph.channel",
    "description":  "Shared channel provisioned by the automated regression tests",
    "displayName":  "My Shared Channel"
}
"@

$uri = "https://graph.microsoft.com/v1.0/teams/$groupId/channels"
$headers = @{"Authorization" = $graphApiAccessToken }
$payload = [System.Text.Encoding]::UTF8.GetBytes($body) 

try {
    $apiResult = Invoke-RestMethod -Uri $uri -Headers $headers -Method "Post" -Body $payload -ContentType "application/json" -Verbose
}
catch [System.Exception] {
    $ex = $_

    $exception = $ex.Exception
    $exceptionMessage = $exception.Message
    $detailsMessage = $ex.ErrorDetails.Message
    $scriptStackTrace = $ex.ScriptStackTrace

    #Retrieve additional information from the exception
    if (! $detailsMessage -and $exception.Response) {
        try {
            Write-Verbose "Reading response stream"
            $postReader = New-Object System.IO.StreamReader($exception.Response.GetResponseStream())
            $detailsMessage = $postReader.ReadToEnd()
            $postReader.Close()
            if (! $ex.PSobject.Properties.Name -contains "ErrorDetails") {
                $ex | Add-Member -MemberType NoteProperty -Name ErrorDetails -Value $null -Force
            }
            $ex.ErrorDetails = New-Object System.Management.Automation.ErrorDetails($detailsMessage)
        } 
        catch {
            #ignore, failed retrieving additional information so skip it
        }
    }
}

$ex.ErrorDetails

SanderS 61 Reputation points

2025-06-18T07:09:34.72+00:00

< duplicate >
SanderS 61 Reputation points

2025-06-18T07:11:46.99+00:00

< duplicate >
SanderS 61 Reputation points

2025-06-18T07:13:40.45+00:00

< duplicate >
SanderS 61 Reputation points

2025-06-18T07:16:36.0333333+00:00

< duplicate >
SanderS 61 Reputation points

2025-06-18T07:21:23.2833333+00:00

< duplicate >
christian zuellig 26 Reputation points

2025-06-20T14:51:43.21+00:00

I have tested same with beta and v1.0 endpoint and both come back with same error when we do call App-Only. The App i test with does have Application Group.ReadWrite.All permission.
If i make the same call by using delegate permission Group.ReadWrite.All (OBO-Token for User with Teams-License) the call is successfull.

Looking at the Error it seems like the teams-license check is done based on the authentication token and not on the owner specified in the body-json.

Answer 3

Dear SanderS and all community members concerned with this issue,

First and foremost, thank you for your continued engagement and for sharing your valuable feedback regarding the challenges encountered with Microsoft Teams, specifically around the creation of shared channels via Microsoft Graph API. Your contributions have been instrumental in helping others navigate this issue, and we’d like to extend special thanks to Benjamin and christian zuellig for their thorough testing and insights.

Benjamin and Christian have tested the creation of shared channels using both the v1.0 and beta endpoints with App-Only permissions (Group.ReadWrite.All). Unfortunately, all attempts resulted in failure due to an error associated with the GetLicenseTypeAsync function. Their analysis indicates that the license check is being performed against the authentication token of the app, rather than the user specified in the request body. Interestingly, when the same request is executed using Delegated Permissions, on behalf of a user with a valid Teams license, the shared channel is created successfully.

We sincerely apologize for the inconvenience and truly appreciate your patience. Please note that, as forum moderators, we are not able to escalate or directly implement a fix. In the meantime, for urgent scenarios, using Delegated Permissions may serve as a temporary workaround.

Thank you once again for your collaboration and ongoing support. Please continue to share any additional findings or suggestions, your input is invaluable to the community.

Share via

Creating Microsoft Teams Shared Channel fails with the message Failed to execute GetLicenseTypeAsync

3 answers

Your answer