Unable to add webhook to channel

%3CLINGO-SUB%20id%3D%22lingo-sub-106586%22%20slang%3D%22en-US%22%3EUnable%20to%20add%20webhook%20to%20channel%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-106586%22%20slang%3D%22en-US%22%3E%3CP%3EWhen%20Microsoft%20Teams%20was%20originally%20released%2C%20we%20were%20able%20to%20define%20Incoming%20Webhooks%20for%20individual%20channels.%20We%20also%20added%20a%20Jenkins%20connector%20(using%20the%20webhooks)%20for%20notifications.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAt%20the%20start%20of%20August%2C%20this%20functionality%20has%20disappeared%20(and%2For%20become%20extremely%20limited).%20We%20only%20have%20a%20limited%20set%20of%20connectors%20available%20for%20a%20channel%20(VSTS%2C%20Yammer%2C%20Wunderlist%2C%20Dynamics%2C%20TFS)%2C%20but%20none%20of%20the%20items%20displayed%20in%20the%20%3CA%20href%3D%22https%3A%2F%2Fmsdn.microsoft.com%2Fen-us%2Fmicrosoft-teams%2Fconnectors%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Edocumentation%3C%2FA%3E.%20No%20Trello%2C%20Github%2C%20Asana.%20More%20importantly%2C%20we%20do%20not%20have%20the%20ability%20to%20define%20a%20normal%20Incoming%20Webhook%20connector.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOur%20existing%20Jenkins%20connector%20appears%20under%20the%20%22Configured%22%20option%2C%20but%20posting%20to%20the%20URL%20defined%20there%20gives%20a%20HTTP%20403%20error.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20there%20O365%20administration%20capabilities%20to%20define%20exactly%20which%20connectors%20are%20available%20for%20teams%2C%20or%20is%20there%20a%20setting%20somewhere%20that%20controls%20which%20items%20we%20have%20available%3F%20%26nbsp%3BOur%20O365%20admins%20cannot%20find%20any%20setting%20anywhere%20that%20controls%20the%20connectors.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-106586%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EActivity%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EAdministrator%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EHow-to%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESettings%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-178709%22%20slang%3D%22en-US%22%3ERe%3A%20Unable%20to%20add%20webhook%20to%20channel%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-178709%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20exactly%20the%20same%20problem%3B%20only%204%20connectors%20are%20available%3B%20nothing%20else.%20How%20and%20Why%3F%20Has%20anyone%20discovered%20the%20reason%20yet%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-106610%22%20slang%3D%22en-US%22%3ERe%3A%20Unable%20to%20add%20webhook%20to%20channel%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-106610%22%20slang%3D%22en-US%22%3EStrange...I'm%20seeing%20the%20same%20connectors%20in%20two%20different%20tenants...in%20one%20of%20the%20tenants%20I%20have%20also%20enabled%20Teams%20Developer%20Preview%20that%20give%20access%20to%20more%20Teams%20Apps...Have%20you%20tried%20to%20enable%20Teams%20Developer%20Preview%20to%20see%20if%20the%20situation%20is%20the%20same%3F%20By%20the%20way%2C%20it%20seems%20that%20this%20is%20something%20that%20could%20be%20related%20to%20your%20tenant.%20In%20regards.%20In%20regards%20of%20your%20question%20about%20how%20to%20enable%20%2F%20disable%20Connectors%2C%20this%20is%20something%20that%20can%20be%20done%20only%20by%20means%20of%20PowerShell%3A%20%3CA%20href%3D%22https%3A%2F%2Fsupport.office.com%2Fen-us%2Farticle%2FConnect-apps-to-your-groups-in-Outlook-ed0ce547-038f-4902-b9b3-9e518ae6fbab%3Fui%3Den-US%26amp%3Brs%3Den-US%26amp%3Bad%3DUS%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.office.com%2Fen-us%2Farticle%2FConnect-apps-to-your-groups-in-Outlook-ed0ce547-038f-4902-b9b3-9e518ae6fbab%3Fui%3Den-US%26amp%3Brs%3Den-US%26amp%3Bad%3DUS%3C%2FA%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Visitor

When Microsoft Teams was originally released, we were able to define Incoming Webhooks for individual channels. We also added a Jenkins connector (using the webhooks) for notifications.

 

At the start of August, this functionality has disappeared (and/or become extremely limited). We only have a limited set of connectors available for a channel (VSTS, Yammer, Wunderlist, Dynamics, TFS), but none of the items displayed in the documentation. No Trello, Github, Asana. More importantly, we do not have the ability to define a normal Incoming Webhook connector.

 

Our existing Jenkins connector appears under the "Configured" option, but posting to the URL defined there gives a HTTP 403 error.

 

Is there O365 administration capabilities to define exactly which connectors are available for teams, or is there a setting somewhere that controls which items we have available?  Our O365 admins cannot find any setting anywhere that controls the connectors. 

2 Replies
Highlighted
Strange...I'm seeing the same connectors in two different tenants...in one of the tenants I have also enabled Teams Developer Preview that give access to more Teams Apps...Have you tried to enable Teams Developer Preview to see if the situation is the same? By the way, it seems that this is something that could be related to your tenant. In regards. In regards of your question about how to enable / disable Connectors, this is something that can be done only by means of PowerShell: https://support.office.com/en-us/article/Connect-apps-to-your-groups-in-Outlook-ed0ce547-038f-4902-b...
Highlighted

I have exactly the same problem; only 4 connectors are available; nothing else. How and Why? Has anyone discovered the reason yet?