Call External API when a document is uploaded to Team general channel?

Hi @john john Pter ,

Thank you for reaching out to Microsoft Q & A !

You can extend your existing Azure Functions solution using Microsoft Graph change notifications. Files uploaded to a Team’s General channel are stored in the associated SharePoint site, so monitor the underlying document library rather than Teams messages. See Teams and SharePoint integration.

Recommended flow

File upload → Graph notification → HTTP-triggered Function → Queue → Worker Function → AI API → Summary saved to SharePoint

1. Identify the General channel folder

Use the Get filesFolder API to obtain the channel folder’s id and parentReference.driveId. Store these identifiers instead of hard-coding paths such as Shared Documents/General.

2. Create a change-notification subscription

For this design, subscribe to /drives/{drive-id}/root with changeType set to updated, then filter processing to the General channel folder.

Point notificationUrl to a publicly accessible HTTPS endpoint hosted by an HTTP-triggered Azure Function.

• During subscription validation, return the URL-decoded validationToken as text/plain with HTTP 200 within 10 seconds.
• For regular notifications, validate clientState, persist the notification to a queue, and return HTTP 202 Accepted promptly. Keep document processing in the worker Function.

See Create a subscription and Receive notifications through webhooks.

3. Identify uploaded files using delta queries

Establish an initial baseline during provisioning, then run a catch-up delta query after creating the subscription.

In the worker Function, call /drives/{drive-id}/root/delta, follow each @odata.nextLink, and save the final @odata.deltaLink. On subsequent notifications, resume from the saved delta link.

Filter the results to new files in the General channel folder, skipping folders, deleted items, previously processed files, and generated summaries.

See Track changes with driveItem delta.

4. Process the document asynchronously

The worker Function should:

• Download the uploaded file from SharePoint.
• Send its content to the external AI summarization endpoint.
• Upload the generated summary to SharePoint.
• Use durable processing state keyed by drive ID and item ID to handle repeated notifications without creating duplicate summaries.
• Explicitly exclude generated summaries from processing to prevent repeated AI calls.

Store AI credentials in Azure Key Vault or secured Function App settings, and grant only the Microsoft Graph permissions required for your design.

5. Renew subscriptions and reconcile changes

Renew the subscription before its expirationDateTime. The documented maximum lifetime for driveItem subscriptions is 42,300 minutes (under 30 days). Periodic delta reconciliation can recover changes missed during notification interruptions.

See the Microsoft Graph subscription reference.

Validation test: Upload a document to General and confirm that one summary is generated, repeated notifications do not create duplicates, generated summaries are skipped, and the saved delta link advances after successful processing.

Please "Upvote the Answer" if this information helped you. This will help us and others in the community as well.

Hi @john john Pter

Thank you for reaching out to Microsoft Q&A. I would implement this as a Microsoft Graph change-notification workflow for the SharePoint folder behind the Team's General channel. The notification endpoint should only validate and queue work; a separate Function should download the file, call the AI service, and upload the generated document.

Implementation Approach

When your provisioning Function creates the Team, retain the Team ID and obtain the General channel's file location:

GET https://graph.microsoft.com/v1.0/teams/{team-id}/channels/{general-channel-id}/filesFolder

This returns the channel's SharePoint-backed driveItem including the drive and folder identifiers needed for subsequent file operations. Get filesFolder

Then create a Microsoft Graph subscription for file changes in that Drive/DriveItem. Point its notificationUrl at a public HTTPS HTTP-triggered Azure Function. Graph validates that endpoint by sending validationToken as a query parameter; the Function must return the URL-decoded token as text/plain with 200 OK within 10 seconds or the subscription is not created. Receive change notifications through webhooks

For each ordinary notification, I would use this flow:

1. Check that the received clientState matches the random value supplied when the subscription was created. Receive change notifications through webhooks
2. Put the drive item ID and notification metadata on Azure Storage Queue or Service Bus, then return 202 Accepted promptly. Graph recommends queueing when processing cannot finish within three seconds; it can retry notifications, so the handler should be idempotent. Receive change notifications through webhooks
3. In a queue-triggered Function, obtain the current item metadata and download its content with GET /drives/{drive-id}/items/{item-id}/content. Downloading a file with application permissions requires at least Files.Read.All. Download driveItem content
4. Check the file type and size against the AI endpoint's supported inputs, send the content to that endpoint, and generate a distinct result name such as original-name-summary.docx so that the result upload does not retrigger processing of itself.
5. Upload the result to the same folder, or another designated folder, through Graph. A simple content upload supports files up to 250 MB and requires Files.ReadWrite.All for application permissions; use an upload session for larger results. Upload or replace the contents of a driveItem

Persist the Graph subscription ID, monitored resource, expiration time, and clientState. Subscriptions expire and must be renewed. I would also configure lifecycle notifications and a timer-triggered renewal/reconciliation job, because notifications can be delayed, duplicated, or missed. subscription resource type Reduce missing subscriptions and change notifications

From my experience, keep the AI endpoint credential in Key Vault or Function app settings, never in source code or a SharePoint document. Grant only the Graph permissions needed for the selected read/write design, and restrict which file extensions and folders the worker accepts before content leaves Microsoft 365.

Please 'Upvote' (Thumbs-up) and 'Accept' as answer if the response was helpful. This will benefit other community members who face the same issue.

Best regards, Andrew S Taylor

The comment's mentioned is right that you watch SharePoint, not Teams. But there's no SharePoint trigger for Azure Functions. You want Graph change notifications.

1. Create a Graph subscription on the drive root of the Team's site. Not the General folder- on OneDrive for Business you can only subscribe to the root.
2. Point it at an HTTP-triggered Function. That Function has to echo back the validation token when the subscription is created, or Graph rejects it.
3. When a notification arrives, call /drives/{drive-id}/root/delta. The notification only tells you something changed, not what.
4. Filter the delta results to the General path, download the file, POST it to your AI endpoint.
5. Add a timer Function to renew the subscription. They expire, and it stops silently when they do.

If you'd rather not host and validate your own endpoint (step 2), Event Grid can receive Graph events directly.

Help make this community better for everyone: if this answer resolved your issue, please accept it or leave an upvote. If not, share more details in a comment so we can continue the discussion and find the right solution.