Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

Microsoft Retiring Office365 Connectors to move to Power Automate Workflows - has anyone done anything with this yet?

https://devblogs.microsoft.com/microsoft365dev/retirement-of-office-365-connectors-within-microsoft-teams/#comments

We just found out that Microsoft is going to be retiring O365 Connectors in favor of Power Automate Workflows. I have not had time to dig into this really deep yet but was wondering if anyone else has? I use webhooks for various alerts to various Teams and am hoping this might be a simple easy conversion.

Thanks,
Dave

Find more posts tagged with

Teams Alerting

Alerting

webhooks

Accepted answers

bubowski42

I hope I'm understanding correctly and I can still use webhooks with the Workflows app, b/c I just spent 2 days getting this working. If so, here's how I set it up.

Final product:

Here's how I got there:

- Right click your team or chat and select "Workflows"

- Select "Post to a chat when a webhook request is received"

- Name it and click Next

- Add workflow

- Navigate to your new workflow and edit. Below is what my flow looks like:

- Then copy the URL from the top flow and paste this in your alert httpPost along with your JSON:

Here is the JSON code I used:

{
"type": "Application/JSON",
"attachments": [{
"contentType": "object",
"content": {
"type": "AdaptiveCard",
"version": "1.4",
"body": [{
"type": "TextBlock",
"text": "***Solarwinds Alert***",
"isSubtle": false,
"wrap": false,
"size": "Large",
"weight": "Bolder",
"spacing": "None"
}, {
"type": "TextBlock",
"text": "Node **${NodeName}** is ***DOWN***",
"isSubtle": false,
"wrap": false,
"spacing": "None"
}, {
"type": "TextBlock",
"text": "IP ADDRESS: ${N=SwisEntity;M=IP_Address}",
"isSubtle": false,
"wrap": false,
"spacing": "None"
}, {
"type": "TextBlock",
"text": "Alert Trigger Time: ${N=Alerting;M=AlertTriggerTime;F=DateTime}",
"isSubtle": false,
"wrap": false,
"spacing": "None"
}, {
"type": "TextBlock",
"text": "OP LOC: ${N=SwisEntity;M=CustomProperties.OP_LOC}",
"isSubtle": false,
"wrap": false,
"spacing": "None"
}, {
"type": "TextBlock",
"text": "**Please acknowledge ownership and investigate**",
"isSubtle": false,
"wrap": false,
"spacing": "None"
}

]
}
}
]
}

EDIT: I also had to allow a firewall rule outbound from Solarwinds server to the specific Azure FQDN you're sending your POST to.

All comments

lynchnigel

Likewise, Ive configured the workflow as that seems pretty simple from the message, but they dont work and Im trying to figure out why, if its authentication its not giving me a clue, the message in Solarwinds says yes its gone.... but nothing in Teams.

A link to help if you are struggling https://office365itpros.com/2024/06/17/teams-post-to-channel-workflow/

martian_monster

We have made some progress and I can get Solarwinds to Teams but the formatting is off. Hopefully will get some time to read up on this and get some adjustments done so it works.

rdavidsoncca

Martian, curious on what you learn/find on the formatting. Having similar issues and working with my internal Teams administrator to figure this out. Like you mention...the O365 connectors work perfect, but the Power Automate flow does not. Curious if you have ran this by support yet. I have dug around THWACK and attempted to locate anything but no luck.

martian_monster

If you are not happy with this move let Microsoft know - feedbackportal.microsoft.com/.../80ed6877-b642-ef11-b4ad-000d3a7aba8b

bubowski42

I hope I'm understanding correctly and I can still use webhooks with the Workflows app, b/c I just spent 2 days getting this working. If so, here's how I set it up.

Final product:

Here's how I got there:

- Right click your team or chat and select "Workflows"

- Select "Post to a chat when a webhook request is received"

- Name it and click Next

- Add workflow

- Navigate to your new workflow and edit. Below is what my flow looks like:

- Then copy the URL from the top flow and paste this in your alert httpPost along with your JSON:

Here is the JSON code I used:

{
"type": "Application/JSON",
"attachments": [{
"contentType": "object",
"content": {
"type": "AdaptiveCard",
"version": "1.4",
"body": [{
"type": "TextBlock",
"text": "***Solarwinds Alert***",
"isSubtle": false,
"wrap": false,
"size": "Large",
"weight": "Bolder",
"spacing": "None"
}, {
"type": "TextBlock",
"text": "Node **${NodeName}** is ***DOWN***",
"isSubtle": false,
"wrap": false,
"spacing": "None"
}, {
"type": "TextBlock",
"text": "IP ADDRESS: ${N=SwisEntity;M=IP_Address}",
"isSubtle": false,
"wrap": false,
"spacing": "None"
}, {
"type": "TextBlock",
"text": "Alert Trigger Time: ${N=Alerting;M=AlertTriggerTime;F=DateTime}",
"isSubtle": false,
"wrap": false,
"spacing": "None"
}, {
"type": "TextBlock",
"text": "OP LOC: ${N=SwisEntity;M=CustomProperties.OP_LOC}",
"isSubtle": false,
"wrap": false,
"spacing": "None"
}, {
"type": "TextBlock",
"text": "**Please acknowledge ownership and investigate**",
"isSubtle": false,
"wrap": false,
"spacing": "None"
}

]
}
}
]
}

EDIT: I also had to allow a firewall rule outbound from Solarwinds server to the specific Azure FQDN you're sending your POST to.

rdavidsoncca

Testing this out now. The JSON payload is working. I think I have something blocking stuff between our Azure and SolarWinds. Working with our Azure and FW folks to validate. Thanks for sharing this @bubowski42

bubowski42

Yeah, I had to create a policy allowing our Solarwinds primary server to the specific URL on port 443 - example: "prod-35.westus.azure.com" or something like that.

bubowski42

I am not a JSON code expert by any means, in fact I know very little... but the examples they give on the power automate website do not work and I kept getting "NULL" errors for attachments and body. I finally found a forum online where someone had figured out the right format. I posted my adaptation below and it's working for me. I hope it helps you also, b/c I spent a couple of days trying to figure it out.

martian_monster

Thank you. I am learning that there are different ways to get work flows from Solarwinds to Teams. This helps quite a bit and I finally am getting time to read and digest all of the work flow items.

martian_monster

Do you only put the JSON code in the alert side in Solarwinds? Or does it go into the work flow as well? I have one work flow kind of working but it is setup differently and the JSON files are in the workflow as well as the alert.

bubowski42

I only put the JSON code in Solarwinds Alert. I didn't put any code on the workflow side.

bubowski42

fyi... here is the forum I found that has the correct format:

community.atlassian.com/.../2749257

martian_monster

Thanks! I deleted my first attempt at this and re-created it and it is working. I was asking about the JSON in the workflow because I have a different workflow setup that we put the JSON in the flow and the alert.

I like what you did because the JSON is not in the flow it is in the alert.

lynchnigel

Do we know if Microsoft are still pushing for this to be changed for the 15 August? The notifications appear to have disappeared....

using the above and adding a bit of code (factset) Ive been able to get something but would be nice to have it a bit neater. Ive also found im having to send the messages as me! so a service account will be needed by the looks as it wont send via the bot.

{
"attachments": [{
"contentType": "object",
"content": {
"type": "AdaptiveCard",
"$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
"version": "1.5",
"body": [{
"style" : "expanded",
"color": "attention",  
"type": "TextBlock",
"text": "======== SOLARWINDS TEST WORKFLOWS ======",
"isSubtle": false,
"wrap": false,
"size": "Large",
"weight": "Bolder",
"spacing": "None"
}, {
"type": "TextBlock",
"text": "Node **${NodeName}** is ***DOWN***",
"isSubtle": false,
"wrap": false,
"spacing": "None"
}, {
"type": "TextBlock",
"text": "IP ADDRESS: ${N=SwisEntity;M=IP_Address}",
"isSubtle": false,
"wrap": false,
"spacing": "None"
}, {
"type": "TextBlock",
"text": "Alert Trigger Time: ${N=Alerting;M=AlertTriggerTime;F=DateTime}",
"isSubtle": false,
"wrap": false,
"spacing": "None"
},
        {
            "type": "FactSet",
    "facts": [{
        "name": "Building",
        "value": "${N=SwisEntity;M=CustomProperties.Building1} "
    }, {
        "name": "Node Room",
        "value": " ${N=SwisEntity;M=CustomProperties.NodeRoom65}"
    }, {
        "name": " Alert date / Time",
        "value": "${N=Generic;M=ShortDate} ${N=Generic;M=ShortTime} "
    }, {
        "name": "Status",
        "value": " ${N=SwisEntity;M=Status;F=Status}"
	}, {
	  "name": "Alert details",
	  "Value": "${N=Alerting;M=AlertName}.${N=Alerting;M=AlertDetailsUrl}"

    }],
    "markdown": true
},




]
}