CODEWITHSUNDEEP
azureazure-active-directorymicrosoft-graph-apipostmanbearer-token
spanky762
spanky762

Reputation: 171

Create onlineMeeting Fails with 403 Forbidden following Microsoft instructions for Postman

Attempting to create an online meeting via Postman following instructions here and here.

I have signed up for a free developer account at Microsoft Azure Portal. I have successfully created an additional user. I have successfully registered a test application: Azure Registered Application

I have created Bearer tokens with scope User.Read.All, OnlineMeetings.ReadWrite, Calendars.ReadWrite using both the TenantID ( login.microsoftonline.com/{{TenantID}}/oauth2/v2.0/authorize ) and the organizations path ( login.microsoftonline.com/organizations/oauth2/v2.0/authorize ) patterns, Postman Configure New Token, and have verified the API permissions in Azure. enter image description here

I have set up my Microsoft Graph environment for Postman (I believe) correctly, setting ClientID, ClientSecret, TenantID, UserPassword, and UserName. MS Graph environment

I have been able to connect via Postman and query both users (Get Users) and my user profile (Get My Profile), and have successfully received responses for both.

I believe I have configured my POST headers correctly. POST Headers

I am posting the following JSON content:

{
"startDateTime": "2021-01-22T14:30:34.2444915-05:00",
"endDateTime": "2021-01-22T15:00:34.2464912-05:00",
"subject": "User Token Meeting"
}

The problem here is that regardless of Token used (either the generated {{UserAccessToken}} when using {{TenantID}} or copy/pasting the token from the ../organizations/.. pattern), and whether I post to https://graph.microsoft.com/v1.0/me/onlineMeetings or https://graph.microsoft.com/beta/me/onlineMeetings, I am receiving a 403 Forbidden Status response. Status 403 Forbidden

I'm honestly not sure if this is due to something I have done wrong or if there is a problem with Azure "free" developer accounts not having the rights to create meetings. Status 403 with response headers

Does anybody have a solution for this? Or a link to instructions on creating a Teams meeting via Postman that works?

Thanks.

Upvotes: 0

Views: 496

Answers (2)

spanky762
spanky762

Reputation: 171

Must LOG INTO TEAMS AT LEAST ONCE before creating meetings via API.

Please refer to @Joy Wang's answer regarding Licenses, as I believe that was also necessary.

Once I set my licenses correctly I still could not get it to work until after I logged into Teams using the test Developer credentials. I had never logged in before, just went directly to API work. After I did the initial login the API calls from Postman began to return a 201 - Created response. enter image description here

Upvotes: 0

Joy Wang
Joy Wang

Reputation: 42123

I can reproduce your issue with an Azure AD Free tenant, I suppose you also use that.

enter image description here

And it works in an Azure AD Premium P2 tenant.

enter image description here

Looks the issue should be related to the Azure AD Pricing tier(maybe related to the Microsoft Teams License more specific, not an expert about that, not say much here), so to solve this issue, you could upgrade your Azure AD License, if you have not used the Free trial before, you could navigate to the Azure Active Directory -> Licenses, active the Premium P2 to have a try.

enter image description here

Upvotes: 1

Related Questions