Unanswered

O365 connector replacement: I can't get power automate to work!

(2) Share

Report

Posted on by DB-19080937-0

As we all know, O365 connectors are being deprecated.

Currently, my workflow looks like this: Azure Automation creates some text, which is then output directly into a Teams channel using an O365 connectors webhook URL.

In the interest of avoiding the webhook use, I have tried both Power Automate and Teams Workflows to bridge this gap.

My changed setup is: An Azure Automation script that generates a message and sends it as a simple text payload to a Power Automate or Teams workflow via an HTTP request. The flow then tries to post the received message to the specified Teams channel.

The Power Automate version:

Triggers on an HTTP request and parses the incoming message.
Posts the parsed message directly to a Teams channel.

Despite setting up the workflow as described, I have encountered challenges in ensuring the message is posted to the Teams channel. I'm able to get "Hello World" messages being sent to the Teams channel from both Power Automate and Teams webhooks, but the automation triggering doesn't work. All the error messages I get are BadRequest.

Could anyone provide insights or recommendations on how to streamline this process or suggest alternative approaches for achieving the same goal without relying on deprecated O365 connectors?

Thanks in advance!

Categories:

Building flows

Screenshot 2024-0...

I have the same question (0)

All responses (2)

Answers (0)

Michael E. Gernaey 53,433 Super User 2025 Season 2 on at

Like (1)

Report

Hi,

I am not following all the for eaches in the flow when you said you are just trying to send it to Teams.

Can you please share a flow, where it failed. Please share the Inputs and Outputs of the Trigger and all the actions being done, as well as the one that is failing.

Then we can help you.

Was this reply helpful? Yes No
DB-19080937-0 16 on at

Like (0)

Report
Thanks for the reply @FLMike!

I had used a template, but now have simplified it:

A powershell script successfully triggers this flow, which should send a message built by the PS script to the Teams channel. The PS script is:
$WebhookUri = "https://prod-00.uksouth.logic.azure.com:443/workflows/xxxxxxxxx/triggers/manual/paths/invoke?api-version=2016-06-01&sp=%2Ftriggers%2Fmanual%2Frun&sv=1.0&sig=xxxxxxxxx" $Payload = @{ type = "message" content = "Hello World - custom message will go in here" } $JsonPayload = $Payload | ConvertTo-Json -Depth 10 Invoke-RestMethod -Method Post -Uri $WebhookUri -ContentType "application/json" -Body $JsonPayload

This currently send an empty message to the teams channel. Ideally it says Hello World - custom message will go in here.

The parameters in the Send action are:

Have I done something fundamentally wrong? I don't need to parse the input as the message will be used as a large string to output as-is.

The Flow isn't saying anything fails :

Your flow ran successfully.

The input for the trigger is:

{

"schema": {

"type": "object",

"properties": {

"type": {

"type": "string"

},

"attachments": {

"type": "array",

"items": {

"type": "object",

"properties": {

"contentType": {

"type": "string"

},

"content": {

"type": "object",

"properties": {

"$schema": {

"type": "string"

},

"type": {

"type": "string"

},

"version": {

"type": "string"

},

"body": {

"type": "array",

"items": {

"type": "object",

"properties": {

"type": {

"type": "string"

}

},

"required": [

"type"

]

}

}

}

}

},

"required": [

"contentType",

"content"

]

}

}

}

}

}

The outputs are:

{
"headers": {
"Host": "prod-00.uksouth.logic.azure.com",
"Max-Forwards": "10",
"User-Agent": "Mozilla/5.0,(Windows NT; Windows NT 10.0; en-GB),WindowsPowerShell/5.1.22621.3880",
"X-ARR-LOG-ID": "xxxxxxxx",
"CLIENT-IP": "xxxxxxxx",
"DISGUISED-HOST": "prod-00.uksouth.logic.azure.com",
"X-SITE-DEPLOYMENT-ID": "xxxxxxxx",
"WAS-DEFAULT-HOSTNAME": "xxxxxxxx",
"X-Forwarded-Proto": "https",
"X-AppService-Proto": "https",
"X-ARR-SSL": "xxxxxxxx",
"X-Forwarded-TlsVersion": "1.2",
"X-Forwarded-For": "xxxxxxxx",
"X-Original-URL": "/workflows/xxxxxxxx/triggers/manual/paths/invoke?api-version=xxxx",
"X-WAWS-Unencoded-URL": "/workflows/xxxxxxxx/triggers/manual/paths/invoke?api-version=xxxx",
"Content-Length": "78",
"Content-Type": "application/json"
},
"body": {
"content": "Hello World - Plain Text Test",
"type": "message"
}
}

Thank you so much!

Was this reply helpful? Yes No