Got follow error when using graph API create chat: "Failed to get license information for the user. Ensure user has a valid Office365 license assigned to them"

Question

Got follow error when using graph API create chat: "Failed to get license information for the user. Ensure user has a valid Office365 license assigned to them"

Yi Huang 黃懿 11

Currently using the delegated permission with an AAD account logged in to create chat for Teams users.

What have done are the belows

The user is able to login to MS Teams.
My app client have got the follwing permissions:
User.ReadBasic.All,
TeamsActivity.Send,
Chat.ReadWrite,
ChannelMessage.Send
User.Read.All
My AAD account have been granted the Teams administration role.
The test is made on Postman, and have gotten a token from OAuth2.

(1) My first question is , according to this page permissions-reference, the API will do if granted the suited permission.
However, the error that recieved from Postman tells that the User.Read.All permission, which is not mentioned needed for the create chat API, is also needed.
It's important for me to know associated information since applying for permission in the company that I worked for required great efforts and careful look.

(2) My second question is, the error message tells that there is still needed to "consent as user or Grant admin consent in portal".
But I've already signed in OAuth through my AAD account and passwd and gave the app secrets, id.

(3) The last question, is O365 essential for creating Teams chat?
Since the error message also tells this.
Should the O365 be added on the AAD account, the app client or the target Teams user?

It's quite urgent, please help.
Thank you so much for reading this issue.

JimmyYang-MSFT 58,641 Reputation points Microsoft External Staff

2022-10-10T02:49:18.14+00:00

Hi @Yi Huang 黃懿

Teams tag is mainly focused on the general issue of Microsoft Teams troubleshooting. According to your description, your question is more relaterd to Teams API developoment, which is not in our support scope. So we will also add office-teams-app-dev tag to your thread. Thanks for your understanding!
Meghana-MSFT 4,116 Reputation points Microsoft External Staff

2022-10-10T10:19:23.623+00:00

We are looking into this, we will get back to you.
Yi Huang 黃懿 11 Reputation points

2022-10-11T07:34:27.297+00:00

still got the same error after turning on o365 of the target user account

Here is the request id => "client-request-id": "c9bfdba7-0f94-4ec8-8d81-3a19a3882de4"
Yi Huang 黃懿 11 Reputation points

2022-10-11T07:34:53.27+00:00

Thank you so much

3 answers

Your answer

JimmyYang-MSFT 58,641 Reputation points Microsoft External Staff

2022-10-10T02:49:18.14+00:00

Hi @Yi Huang 黃懿

Teams tag is mainly focused on the general issue of Microsoft Teams troubleshooting. According to your description, your question is more relaterd to Teams API developoment, which is not in our support scope. So we will also add office-teams-app-dev tag to your thread. Thanks for your understanding!
Meghana-MSFT 4,116 Reputation points Microsoft External Staff

2022-10-10T10:19:23.623+00:00

We are looking into this, we will get back to you.
Yi Huang 黃懿 11 Reputation points

2022-10-11T07:34:27.297+00:00

still got the same error after turning on o365 of the target user account

Here is the request id => "client-request-id": "c9bfdba7-0f94-4ec8-8d81-3a19a3882de4"
Yi Huang 黃懿 11 Reputation points

2022-10-11T07:34:53.27+00:00

Thank you so much

Answer 1

CarlZhao-MSFT 46,366

Hi @Yi Huang 黃懿

Does the signed-in user have an O365 license? Please check:

Go to Azure AD>Users > find your users> Licenses make sure your users have been granted O365 licenses.

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
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.

CarlZhao-MSFT 46,366 Reputation points

2022-10-12T02:19:25.283+00:00

Hi @Yi Huang 黃懿
Would you please provide us with an update on the status of your issue?
Yi Huang 黃懿 11 Reputation points

2022-10-14T01:27:28.427+00:00

Thank you so much.
The information offered has been sent to the department in the office that manage associated configurations.
Currently waiting for the verification process, will test the result and immediately update whether the issue fixed as soon as test avilable.
Sorry for the late reply due to mine absence from the office yesterday.
Really appreciate your help.
CarlZhao-MSFT 46,366 Reputation points

2022-10-14T01:38:19.093+00:00

Looking forward to your reply.

Thanks,
Carl Zhao
CarlZhao-MSFT 46,366 Reputation points

2022-10-17T01:49:38.043+00:00

Hi @Yi Huang 黃懿

If the answer is helpful, please click Accept Answer and kindly upvote. If you have any further questions about this answer, please click Comment.

Thanks,
Carl Zhao
Yi Huang 黃懿 11 Reputation points

2022-10-18T02:43:29.053+00:00

Really grateful for the help.
Sorry, still got the same error messages on postman after turning on the mentioned settings, still looking for methods to solve the issue.
CarlZhao-MSFT 46,366 Reputation points

2022-10-18T02:51:08.623+00:00

The image you shared seems to be invalid, please check.
CarlZhao-MSFT 46,366 Reputation points

2022-10-18T02:52:27.463+00:00

Your users are already assigned an O365 license, right?
Yi Huang 黃懿 11 Reputation points

2022-10-18T04:05:49.73+00:00

Yes. the O365 license is assigned.
Thank you for reminding, the correct scrennshot images are updated.
CarlZhao-MSFT 46,366 Reputation points

2022-10-19T10:20:31.39+00:00

Are you using a user who has been granted an O365 license? Please check.
Yi Huang 黃懿 11 Reputation points

2022-10-20T01:30:20.403+00:00

Pardon.
May I asked the difference between assigning a O365 license and granting a license,
not familiar about the difference and haven't found associated info from google.

Login in through the testing-use user account to microsoft word and teams have tested and are both success as shown in the follow image.

(Sorry for not attaching an image of login into teams since mine currently in a teams meeting therefore couldn't login to another account)

Howerver the the error message of postman remain the same.

Am wondering whether the problem is associated to this documentation, and is considering to test through code instead of postman
https://learn.microsoft.com/en-us/azure/active-directory/develop/v2-permissions-and-consent#admin-restricted-permissions
Yi Huang 黃懿 11 Reputation points

2022-10-20T01:54:06.517+00:00

Pardon.
May I asked the difference between assigning a O365 license and granting a license,
not familiar about the difference and haven't found associated info from google.

Login in through the testing-use user account to microsoft word and teams have tested and are both success as shown in the follow image.

(Sorry for not attaching an image of login into teams since my currently in a teams meeting therefore couldn't login to another account)

Howerver the the error message of postman remain the same.

Am wondering whether the problem is associated to this documentation which tells "These types of permissions are used only by daemon services and other noninteractive applications that run in the background." at the bottom of the paragraph,
and is considering to test through code instead of postman, however the process may take longer time for me since it requires applications in my office to access the egress to azure endpoints for my coding projects.
Would it be possible to ask for your suggestion, whether you consider this a probable cause. Thank you.
https://learn.microsoft.com/en-us/azure/active-directory/develop/v2-permissions-and-consent#admin-restricted-permissions
CarlZhao-MSFT 46,366 Reputation points

2022-10-20T03:07:13.527+00:00

There is no difference between assigning an O365 license and granting an O365 license, it is just a different expression.

As long as your users have an O365 license then you can definitely create group chats. Can you use JWT.ms to parse your access token and then take a screenshot and share it?
Yi Huang 黃懿 11 Reputation points

2022-10-20T04:42:10.58+00:00

Here's the screenshot. Really grateful for the help.
CarlZhao-MSFT 46,366 Reputation points

2022-10-21T10:13:13.847+00:00

Can you provide a screenshot of your latest error message? If you have an O365 license then you can definitely create chats.
CarlZhao-MSFT 46,366 Reputation points

2022-10-21T10:18:09.547+00:00

Also, call https://graph.microsoft.com/v1.0/me/licenseDetails?$select=skuId,skuPartNumber endpoint and provide a screenshot.
Yi Huang 黃懿 11 Reputation points

2022-10-24T01:41:28.433+00:00

Ohhh, the user that been used to login to the delegated permission hasn't been granted the O365 license.
May I confirm again, so, not only the user to be added to the newly-created chat has to be granted o365 license, but the user that logged into the delegated permission should also be granted a O365 license.

The following images is the screenshot of the current error.
So grateful for the information and help, will inform the team that manage the license to add one for the delegated user, and update the results after tested.
CarlZhao-MSFT 46,366 Reputation points

2022-10-24T02:05:29.04+00:00

Of course, you must grant an O365 license to the logged-in user.
Yi Huang 黃懿 11 Reputation points

2022-10-24T05:43:32.657+00:00

Sorry but still got the same error messages as below after granting license to all users.
CarlZhao-MSFT 46,366 Reputation points

2022-10-24T06:12:21.27+00:00

Hi @Yi Huang 黃懿
Call the https://graph.microsoft.com/v1.0/me/licenseDetails?$select=skuId,skuPartNumber endpoint and share the screenshot.
Yi Huang 黃懿 11 Reputation points

2022-10-24T06:22:01.987+00:00

Here it is .
CarlZhao-MSFT 46,366 Reputation points

2022-11-11T10:29:08.737+00:00

Hi @Yi Huang 黃懿
I noticed that you turned off most of the services including Teams services when you grant the O365 license, now please enable these services and call the API endpoint again.

Answer 2

Meghana-MSFT 4,116 Microsoft External Staff

The API would work if the permissions mentioned in the doc are given. I tried creating chat in postman using application permissions. As mentioned in Create Chat, Chat.Create application permission is sufficient.
Admin needs to consent to the permissions and then you can get the token.
O365 license is required. As mentioned by CarlZhao-MSFT please verify the user's license.

Yi Huang 黃懿 11 Reputation points

2022-10-18T02:43:38.737+00:00

Really grateful for the help.
Sorry, still got the same error messages on postman after turning on the mentioned settings, still looking for methods to solve the issue.

Answer 3

Ivelk 1

Hello @Yi Huang 黃懿 ,

Check Apps under E3 License. I had same issue and somehow MS Teams was not checked.
After that i got it working.

Share via

Got follow error when using graph API create chat: "Failed to get license information for the user. Ensure user has a valid Office365 license assigned to them"

3 answers

Your answer