Error in ProcessTeamRequest - failed to get license information for the user

[ChristianHoffmannn]

Description

Since 3 weeks we are having an issue with new created teams from the request a team app. The service user is not removed from new teams. In the logic app from ProcessTeamRequest i saw that there is an error at the step post welcome message to general channel: { "error": { "code": "Forbidden", "message": "Failed to get license information for the user. Ensure user has a valid Office365 license assigned to them.", "innerError": { "date": "2022-03-17T09:12:34", "request-id": "9bbb0587-5a17-4f78-b437-51af0f516184", "client-request-id": "9bbb0587-5a17-4f78-b437-51af0f516184" } } }

We have one service user, which with who, we created the app via powershell and in keyvault we have another user saved as sausername.

I checked both users and both users got an active license (Azure AD Premium P1 and the other one got an O365 E3 license) I do not really unterstand, why this error appears.

Does anyone have an idea?

Kind regards Christian

Steps to reproduce

1. checked service user for active license
2. created new team with request a team app

Expected results

With an active license for the service user, new teams should be created and all steps from Processteamrequest should be successfull.

Actual Results

New teams are created but Processteamrequest logic fails at step posting welcome message to new team.

Solution component

Logic Apps

Operating system (environment)

Windows

Additional Info

No response

[ChristianHoffmannn]

@alexc-MSFT do you have an idea,why this error happens?

[alexc-MSFT]

@ChristianHoffmannn your service account - does this have an O365 license or only AD P1? The service account is used to post the welcome message so if that doesn't have an O365 license then the step will fail.

[zaaj]

I'm getting the same error just on "Get-MgBetaTeamworkDevice" after connecting with a TeamsAdmin account - my admin account doesn't have any licenses, none of the other admin powershell modules seem to require one, and I wouldn't expect a retrieval request to need one when the ROP account can use the MicrosoftTeams module with no licensing issues.