Power Platform Community Forum Thread Details

Hi Everyone,

I’m working on a Power Automate flow to integrate Microsoft Teams with Salesforce. The flow starts with the Teams trigger "When a transcript is available", followed by:

HTTP – Get Salesforce Token
Parse JSON
HTTP – Call Salesforce Apex REST

I selected the scope "User (all meetings for a user)" and provided the User ID. However, when I run the flow, it fails immediately at the trigger step with the following error:

- Action 'When_a_transcript_is_available' failed
- NotificationUrl must use the https scheme. (Parameter 'input')

The flow does not even proceed to the HTTP actions.

I’m not sure where Power Automate is expecting this NotificationUrl or which configuration is causing the issue. Has anyone faced this issue before? Is there any additional setup required for Teams transcripts, webhook URLs, or trigger configuration?

I am also attaching the flow screenshot for more details. please have a look.

Any guidance would be appreciated.

power_automate_er...

Your file is currently under scan for potential threats. Please wait while we review it for any viruses or malicious content.

Categories:

Power Automate Desktop

Hi,

That error is being raised by Microsoft Graph, not by Power Automate. The Teams trigger "When a transcript is available" creates a Graph change-notification subscription behind the scenes (on the /communications/onlineMeetings/getAllTranscripts resource). Graph requires that the subscription’s notificationUrl be an HTTPS URL it can reach — and because transcripts contain meeting content, Graph also requires the subscription to use resource data with encryption. If either the encryption prerequisite or the user/scope reference isn’t valid, the platform passes an empty / non-https notificationUrl to Graph and you see exactly the message you’re getting.

What to fix, in order

Validate the User scope value. "User (all meetings for a user)" expects the Azure AD object ID (GUID) of the target user — not their UPN, email, or display name. Get it from Entra admin center → Users → [user] → Object ID, or via Graph: GET https://graph.microsoft.com/v1.0/users/{upn}. A wrong/empty user ID is one of the known reasons the connector falls back to an invalid notificationUrl. See Microsoft Teams connector reference.
Confirm the trigger is allowed for that user. Transcript change notifications require the user to have a Teams license that includes meeting recording/transcription, and the meeting policy must allow transcription. Without it Graph won’t accept the subscription. See Configure transcription and captions for Teams meetings.
Set up the encryption certificate (the most common root cause). Transcript notifications return resource data, so Graph requires the subscription to be created with includeResourceData=true plus an encryptionCertificate and encryptionCertificateId. The first-party Teams trigger handles this for you only when the tenant has a valid Graph notification encryption setup. Follow Set up change notifications that include resource data and Microsoft Graph change notifications overview. If you’ve never registered an X.509 cert with Graph for resource-data notifications, transcript triggers will fail at the subscription-creation step exactly as you’re seeing.
Check tenant prerequisites for online-meetings notifications. The OnlineMeetings.Read.All and OnlineMeetingTranscript.Read.All permissions must be granted (admin consent) to the connector’s app, and your tenant must have the Application Access Policy in place if the connection account isn’t the same user as the one whose meetings you’re subscribing to. See Configure application access policy for online meetings.
Re-create the connection and re-pick the trigger. Once 1–4 are in place, delete the existing Teams connection used by the flow, sign back in, and re-add the trigger from scratch (don’t just save the existing one). This forces the connector to mint a fresh subscription with the now-valid prerequisites.

Why the error wording is what it is

When Graph receives a subscription create request whose notificationUrl is missing or non-https, it returns "NotificationUrl must use the https scheme. (Parameter ‘input’)" — that exact string surfaces verbatim through the Power Automate trigger. It’s almost always a downstream symptom of one of the prerequisites above being unmet (most commonly the encryption certificate for resource-data notifications). Reference: Create subscription – Microsoft Graph.

If after step 3 the issue persists, the fastest confirmation is to try creating the same subscription directly via Graph Explorer using the same user/scope — if Graph rejects it there too, you’ve isolated the problem to the encryption-cert / tenant-policy side, not Power Automate.

Found this helpful? Please mark ✅ "Does this answer your question?" so others searching for the same issue can find it quickly. A 👍 on "Was this reply helpful?" or a ♥ Like is also much appreciated!

Raghav Mishra — LinkedIn | PowerAI Labs