(SQL Server) MS Teamwork: Update an Online Meeting

See more Microsoft Teams Examples

Demonstrates how to update a Microsoft Teamwork Online Meeting

Note:If using Application access (i.e. client credentials) which is what this example is doing, then you'll need to "Configure application access to online meetings or virtual events" See https://learn.microsoft.com/en-us/graph/cloud-communication-online-meeting-application-access-policy#configure-application-access-policy

For example, here's our Powershell session to setup the policy.

Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.
Try the new cross-platform PowerShell
https://aka.ms/pscore6 

PS C:\WINDOWS\system32> Install-Module -Name PowerShellGet -Force -AllowClobber
PS C:\WINDOWS\system32> Install-Module -Name MicrosoftTeams -Force -AllowClobber
PS C:\WINDOWS\system32> Connect-MicrosoftTeams

Account              Environment Tenant                               TenantId
-------              ----------- ------                               --------
admin@chilkat365.com AzureCloud  112d7ed6-71bf-4eba-a866-738364321bfc 112d7ed6-71bf-4eba-a866-738364321bfc

PS C:\WINDOWS\system32> New-CsApplicationAccessPolicy -Identity Test-Teams-policy -AppIds "e1cd2318-298b-4916-bfd6-78cae9938835" -Description "Want App to be able to work with Teams for a User"

Identity    : Tag:Test-Teams-policy
AppIds      : {e1cd2318-298b-4916-bfd6-78cae9938835}
Description : Want App to be able to work with Teams for a User

PS C:\WINDOWS\system32> Grant-CsApplicationAccessPolicy -PolicyName Test-Teams-policy -Identity "4ee732c3-322e-4a6b-b729-2fd1eb5c6004"
PS C:\WINDOWS\system32>

Note: This example uses the new "Integrated OAuth2 Client Credentials" feature introduced in Chilkat v9.5.0.96.

For more information, see https://learn.microsoft.com/en-us/graph/api/onlinemeeting-update?view=graph-rest-1.0&tabs=http

Chilkat ActiveX Downloads ActiveX for 32-bit and 64-bit Windows

// Important: See this note about string length limitations for strings returned by sp_OAMethod calls.
//
CREATE PROCEDURE ChilkatSample
AS
BEGIN
    DECLARE @hr int
    DECLARE @iTmp0 int
    DECLARE @sTmp0 nvarchar(4000)
    -- This requires the Chilkat API to have been previously unlocked.
    -- See Global Unlock Sample for sample code.

    DECLARE @success int

    DECLARE @http int
    EXEC @hr = sp_OACreate 'Chilkat_9_5_0.Http', @http OUT
    IF @hr <> 0
    BEGIN
        PRINT 'Failed to create ActiveX component'
        RETURN
    END

    -- Provide the information needed for Chilkat to automatically fetch the OAuth2.0 
    -- access token as needed.
    -- This is the new "Integrated OAuth2 Client Credentials" feature introduced in Chilkat v9.5.0.96.  
    DECLARE @jsonOAuthCC int
    EXEC @hr = sp_OACreate 'Chilkat_9_5_0.JsonObject', @jsonOAuthCC OUT

    -- --------------------------------------------------------------------------------------------------------
    -- You'll need to have registered an app in Azure beforehand.
    -- 
    -- Note: Creating an online meeting requires the following Application permission:  OnlineMeetings.ReadWrite.All
    -- 
    -- See How to Create an Azure App Registration for OAuth 2.0 Client Credentials
    -- --------------------------------------------------------------------------------------------------------

    -- Use the values from your App Registration in Azure.
    EXEC sp_OAMethod @jsonOAuthCC, 'UpdateString', @success OUT, 'client_id', 'e1cd2318-xxxx-4916-bfd6-xxxxxxxxxxxx'
    EXEC sp_OAMethod @jsonOAuthCC, 'UpdateString', @success OUT, 'client_secret', 'K.d8Q~RoJxxxxvCj_u_xxxxxxxxxxxxxxxxxxxxx'

    -- You'll always use this scope for client credentials, because the allowed actions
    -- are determined by the App Permissions defined when you registered the app in Azure.
    EXEC sp_OAMethod @jsonOAuthCC, 'UpdateString', @success OUT, 'scope', 'https://graph.microsoft.com/.default'

    -- The token endpoint includes your tenant ID.  Use your tenant ID (not the tenant ID shown here).
    EXEC sp_OAMethod @jsonOAuthCC, 'UpdateString', @success OUT, 'token_endpoint', 'https://login.microsoftonline.com/112d7ed6-71bf-4eba-a866-738364321bfc/oauth2/v2.0/token'

    -- Provide the OAuth2 information. Chilkat will use this information to automatically fetch the OAuth2 access token as needed,
    EXEC sp_OAMethod @jsonOAuthCC, 'Emit', @sTmp0 OUT
    EXEC sp_OASetProperty @http, 'AuthToken', @sTmp0

    -- -------------------------------------------------------------------------------------------
    -- The following JSON is sent in the request body.

    -- {
    --   "startDateTime": "2023-12-14T14:33:30-07:00",
    --   "endDateTime": "2023-12-14T15:03:30-07:00",
    --   "subject": "Patch Meeting Subject"
    -- }

    DECLARE @json int
    EXEC @hr = sp_OACreate 'Chilkat_9_5_0.JsonObject', @json OUT

    EXEC sp_OAMethod @json, 'UpdateString', @success OUT, 'startDateTime', '2023-12-14T14:33:30-07:00'
    EXEC sp_OAMethod @json, 'UpdateString', @success OUT, 'endDateTime', '2023-12-14T15:03:30-07:00'
    EXEC sp_OAMethod @json, 'UpdateString', @success OUT, 'subject', 'Patch Meeting Subject'

    DECLARE @sbRequestBody int
    EXEC @hr = sp_OACreate 'Chilkat_9_5_0.StringBuilder', @sbRequestBody OUT

    EXEC sp_OAMethod @json, 'EmitSb', @success OUT, @sbRequestBody

    -- To update an online meeting, send a PATCH request like this:
    -- 
    -- PATCH https://graph.microsoft.com/v1.0/users/{userId}/onlineMeetings/{meetingId}
    -- Content-Type: application/json 
    -- 
    -- {
    --   "startDateTime": "2020-09-09T14:33:30.8546353-07:00",
    --   "endDateTime": "2020-09-09T15:03:30.8566356-07:00",
    --   "subject": "Patch Meeting Subject"
    -- }

    DECLARE @userId nvarchar(4000)
    SELECT @userId = '4ee732c3-322e-4a6b-b729-2fd1eb5c6004'
    DECLARE @meetingId nvarchar(4000)
    SELECT @meetingId = 'MSo0ZWU3MzJjMy0zMjJlLTRhNmItYjcyOS0yZmQxZWI1YzYwMDQqMCoqMTk6bWVldGluZ19OemMwT0RGa1pESXRNV1ZoTkMwME9UQXpMV0psWXpJdFkyRXdNR0kzTVdNME5qTmpAdGhyZWFkLnYy'

    DECLARE @sbUrl int
    EXEC @hr = sp_OACreate 'Chilkat_9_5_0.StringBuilder', @sbUrl OUT

    EXEC sp_OAMethod @sbUrl, 'Append', @success OUT, 'https://graph.microsoft.com/v1.0/users/{userId}/onlineMeetings/{meetingId}'
    DECLARE @numReplaced int
    EXEC sp_OAMethod @sbUrl, 'Replace', @numReplaced OUT, '{userId}', @userId
    EXEC sp_OAMethod @sbUrl, 'Replace', @numReplaced OUT, '{meetingId}', @meetingId

    DECLARE @resp int
    EXEC sp_OAMethod @sbUrl, 'GetAsString', @sTmp0 OUT
    EXEC sp_OAMethod @http, 'PTextSb', @resp OUT, 'PATCH', @sTmp0, @sbRequestBody, 'utf-8', 'application/json', 0, 0
    EXEC sp_OAGetProperty @http, 'LastMethodSuccess', @iTmp0 OUT
    IF @iTmp0 = 0
      BEGIN
        EXEC sp_OAGetProperty @http, 'LastErrorText', @sTmp0 OUT
        PRINT @sTmp0
        EXEC @hr = sp_OADestroy @http
        EXEC @hr = sp_OADestroy @jsonOAuthCC
        EXEC @hr = sp_OADestroy @json
        EXEC @hr = sp_OADestroy @sbRequestBody
        EXEC @hr = sp_OADestroy @sbUrl
        RETURN
      END

    -- ----------------------------------------------------------------------------------------
    -- IMPORTANT: 

    -- If using Application access, you will get the following error unless you configure your application
    -- to manage online meetings on behalf of the user.  (Note that the user ID is in the URL shown above.)
    -- See  https://learn.microsoft.com/en-us/graph/cloud-communication-online-meeting-application-access-policy#allow-applications-to-access-online-meetings-on-behalf-of-a-user 
    -- 
    -- {
    --   "error": {
    --     "code": "General",
    --     "message": "No application access policy found for this app.",
    --     "innerError": {
    --       "request-id": "1c9bd09a-a089-4afd-add4-eec2334135c8",
    --       "date": "2023-11-17T16:26:53",
    --       "client-request-id": "1c9bd09a-a089-4afd-add4-eec2334135c8"
    --     }
    --   }
    -- }
    -- ----------------------------------------------------------------------------------------

    DECLARE @jsonResp int
    EXEC @hr = sp_OACreate 'Chilkat_9_5_0.JsonObject', @jsonResp OUT

    EXEC sp_OAGetProperty @resp, 'BodyStr', @sTmp0 OUT
    EXEC sp_OAMethod @jsonResp, 'Load', @success OUT, @sTmp0
    EXEC sp_OASetProperty @jsonResp, 'EmitCompact', 0
    EXEC sp_OAMethod @jsonResp, 'Emit', @sTmp0 OUT
    PRINT @sTmp0

    DECLARE @statusCode int
    EXEC sp_OAGetProperty @resp, 'StatusCode', @statusCode OUT

    PRINT 'response status code = ' + @statusCode

    EXEC @hr = sp_OADestroy @resp

    IF @statusCode <> 200
      BEGIN

        PRINT 'Failed.'
        EXEC @hr = sp_OADestroy @http
        EXEC @hr = sp_OADestroy @jsonOAuthCC
        EXEC @hr = sp_OADestroy @json
        EXEC @hr = sp_OADestroy @sbRequestBody
        EXEC @hr = sp_OADestroy @sbUrl
        EXEC @hr = sp_OADestroy @jsonResp
        RETURN
      END

    -- Here is a sample response:

    -- Use the following online tool to generate parsing code from sample JSON: 
    -- Generate Parsing Code from JSON

    -- Use the following online tool to generate parsing code from sample JSON: 
    -- Generate Parsing Code from JSON


    PRINT 'Success.'

    EXEC @hr = sp_OADestroy @http
    EXEC @hr = sp_OADestroy @jsonOAuthCC
    EXEC @hr = sp_OADestroy @json
    EXEC @hr = sp_OADestroy @sbRequestBody
    EXEC @hr = sp_OADestroy @sbUrl
    EXEC @hr = sp_OADestroy @jsonResp


END
GO