Jenkins Teams app no longer posting to Teams - Connector app missing from MS Teams Store

[marcjay]

Jenkins and plugins versions report

N/A. Plugin version 4.18.0 used

What Operating System are you using (both controller, and any agents involved in the problem)?

N/A

Reproduction steps

With the Jenkins Connector historically set up in MS Teams, and previously working, Jenkins jobs that would normally post to MS Teams no longer post. No errors in Jenkins build log or server log

Attempting to add the Connector to a new Teams Channel, it does not appear to be available:

Expected Results

Jenkins to be able to send notifications into MS Teams using the Jenkins Connector, as was working previously

Actual Results

Notifications do not appear in Teams

Attempting to post to the Webhook URL of an existing Jenkins Connector returns a 200 HTTP status code, but the JSON response includes a 404:

{
    "version": "1.1",
    "content": {
        "headers": [
            {
                "key": "Content-Type",
                "value": [
                    "text/plain; charset=utf-8"
                ]
            }
        ]
    },
    "statusCode": 404,
    "reasonPhrase": "Not Found",
    "headers": [],
    "trailingHeaders": [],
    "requestMessage": null,
    "isSuccessStatusCode": false
}

Anything else?

No response

[jsaintyv]

Hello, We meet the same issue.

We replace Jenkins connector by new connector of Microsoft "Incoming Webhook" https://teams.microsoft.com/l/app/203a1e2c-26cc-47ca-83ae-be98f960b6b2?source=app-details-dialog

It solve our problem.

[danieldenbraven]

Have the same issue, I found it weird because the Jenkins app is there, but the connector is gone. Maybe this is actually an issue with Teams and not Jenkins, as the app has a "Microsoft Teams Ecosystem" as a "developer".

[andreasmuelhaupt]

Same issue here. Made a POST to the Jenkins Webhook URL https://<tenant>.webhook.office.com/webhookb2/<guid>/JenkinsCI/<guid>/<guid> with the result http/200 and content showing

    "statusCode": 404,
    "reasonPhrase": "Not Found",

Using https://<tenant>.webhook.office.com/webhookb2/<guid>/IncomingWebhook/<guid>/<guid> results in http/200 and content showing

    "statusCode": 200,
    "reasonPhrase": "OK",

while having the Incoming Webhook Connector not even configured or approved by administrators!

Using any other name does not work and results in the http/200 response 404 as above. Curious what the root cause might be then with teams not recognizing the webhook its connector created.

[ViliusS]

Same here. Is this plugin dead?

[jstolp]

Same issue here. Made a POST to the Jenkins Webhook URL https://<tenant>.webhook.office.com/webhookb2/<guid>/JenkinsCI/<guid>/<guid> with the result http/200 and content showing

    "statusCode": 404,
    "reasonPhrase": "Not Found",

Using https://<tenant>.webhook.office.com/webhookb2/<guid>/IncomingWebhook/<guid>/<guid> results in http/200 and content showing

    "statusCode": 200,
    "reasonPhrase": "OK",

while having the Incoming Webhook Connector not even configured or approved by administrators!

Using any other name does not work and results in the http/200 response 404 as above. Curious what the root cause might be then with teams not recognizing the webhook its connector created.

This answer worked for me. I've received:

"HTTP/2 404: Unknown Connector provider JenkinsCI"

After the change in the URL from JenkinsCI to IncomingWebhook it worked (200 OK!)

[DarkNormal]

We're also having the same issue, can't find the Jenkins connector when searching for it in the Teams, and no option to configure a new Jenkins connector in the channel with the existing Jenkins setup.

When I do a POST request to the Jenkins Webhook URL I get a 404 with the below message: "Unknown Connector provider JenkinsCI"

Above solutions work to restore functionality

[roennow]

Jenkins connector is scheduled for release on Feb 28, 2023.

https://learn.microsoft.com/en-us/microsoftteams/office-365-custom-connectors#considerations-when-using-connectors-in-teams

This is the only information I can find on it.

[ViliusS]

Jenkins connector is scheduled for release on Feb 28, 2023.

https://learn.microsoft.com/en-us/microsoftteams/office-365-custom-connectors#considerations-when-using-connectors-in-teams

This is the only information I can find on it.

Thanks! Great find.

[ViliusS]

For us messages from Jenkins started to arrive on Teams channels again yesterday. JenkinsCI connector on new channels is still not available though.

[ajbowler]

For my existing connector, I've started receiving messages again as of today, February 6th, 2023.