Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Bring Your Agent to Teams

microsoft.github.io

Post reply on HN
Print view View original

51–60 of 89 posts

Re: Bring Your Agent to Teams

#51

Post by bob1029 »

theshrike79 wrote: post #36
SV_BubbleTime wrote: post #20

Earlier quoted context omitted.

I know it’s NerdCool to hate on Teams, but I really don’t get it. I’m in Linux with portal for teams (electron app)… and it’s fine. Like, we moved to it from slack and I just don’t see much of a difference. I type stuff, and people see it. I set up a call and people join, we talk. What is it that is so broken, or is it just cool to hate?

Try being a consultant who needs to have access to 2+ Teams accounts simultaneously. On Slack I can just press command - and I'm switching between client Slack accounts. On Teams? Nope. Nope. Nope.

I have 3 accounts in teams. Two are in client tenants and one is my personal. I haven't had any issues because I can't work on more than one customer at a time. I still get notifications from the other clients when I'm not actively staring at things. I could leave teams off all day and still be fine. The business requirements don't change that quickly in my part of the world. If you are doing 1099 for multiple customers, you should not let them dance you around with instant messages in real time. That will wear you out very quickly.

Re: Bring Your Agent to Teams

#52

Post by high_na_euv »

leosanchez wrote: post #13
GorsyGentle wrote: post #12

> Your users live in Teams. No, I assure you, we do not. Nobody wants to live in hell. Even at my current company, we are mandated solely to use Teams for meetings. But nobody uses it for chat. Thankfully we have Slack to save us from that hell. Even if giphy is disabled because it might have R rated content whatever the hell that means.

IMO Only thing good about Teams is Emojis

Calendar

Re: Bring Your Agent to Teams

#53

Post by high_na_euv »

userbinator wrote: post #31
SV_BubbleTime wrote: post #20

Earlier quoted context omitted.

I know it’s NerdCool to hate on Teams, but I really don’t get it. I’m in Linux with portal for teams (electron app)… and it’s fine. Like, we moved to it from slack and I just don’t see much of a difference. I type stuff, and people see it. I set up a call and people join, we talk. What is it that is so broken, or is it just cool to hate?

I suspect those who honestly think Teams is fine have never used anything better.

Ive used

Ventrilo, teamspeak, discord, mumble, skype, teams, slack

And id say teams are okayish, nothing wrong about them

Discord is #1

Re: Bring Your Agent to Teams

#55

Post by ramon156 »

Underphil wrote: post #30
jordemort wrote: post #21

Was this written by an agent? It’s giving me a pain by the second paragraph.

I also found it truly brutal to read and got fed around the same spot. I hate this style so much.

I'm not saying its not, but I have always found MS articles / docs to be insufferable to read. 300 words to explain something that's nothing more than an API call

Re: Bring Your Agent to Teams

#56

Post by nerdjon »

GorsyGentle wrote: post #12

> Your users live in Teams. No, I assure you, we do not. Nobody wants to live in hell. Even at my current company, we are mandated solely to use Teams for meetings. But nobody uses it for chat. Thankfully we have Slack to save us from that hell. Even if giphy is disabled because it might have R rated content whatever the hell that means.

I really hate that Teams has basically taken over. It has so many poor design decisions that I regularly feel like I am fighting it.

My single biggest pet peeve, how it handles chats from meetings when you are not in the meeting. I have lost so many chats (or never got responses) because they were hidden in meeting chats that for some reason don't appear in your normal chat list.

Sure Slack had its own issues, but I don't remember ever feeling like I was actively fighting it and loosing.

Re: Bring Your Agent to Teams

#57

Post by plaidfuji »

> Teams is where most enterprise work happens: decisions get made, customers get answered, and projects move forward there.

… and Teams is where it will stay! Microsoft’s piss-poor integrability across its productivity suite is the single biggest reason agentic AI will fail to deliver its promised productivity benefits. You probably could build an agent to do a lot of people’s jobs, provided it had unfettered access to Teams, Outlook, Word, Excel, and PPT. But I can’t think of an organization who would want to grant that access today, and even if they wanted to, the solution here is to expose a self-managed HTTP endpoint for all your Teams traffic? Seriously?

Re: Bring Your Agent to Teams

#59

Post by mexicocitinluez »

theshrike79 wrote: post #36
SV_BubbleTime wrote: post #20

Earlier quoted context omitted.

I know it’s NerdCool to hate on Teams, but I really don’t get it. I’m in Linux with portal for teams (electron app)… and it’s fine. Like, we moved to it from slack and I just don’t see much of a difference. I type stuff, and people see it. I set up a call and people join, we talk. What is it that is so broken, or is it just cool to hate?

Try being a consultant who needs to have access to 2+ Teams accounts simultaneously. On Slack I can just press command - and I'm switching between client Slack accounts. On Teams? Nope. Nope. Nope.

> On Teams? Nope. Nope. Nope.

What? https://techcommunity.microsoft.com/blog/nonprofittechies/ho...

Re: Bring Your Agent to Teams

#60

Post by mexicocitinluez »

crote wrote: post #37

I just want Teams to have a proper webhook API! Why do I have to create a weird "workflow" to receive webhooks in a chat channel? Why does it have such complicated ownership permissions? Why is it automatically deleted if it doesn't see "enough" use? Why do I need to send the message in some weird "adaptive card" format - for which there are barely any ready-made libraries? Heck, why can't I create a new chat channel…

> Why do I have to create a weird "workflow" to receive webhooks in a chat channel?

Create the webhook in Microsoft Flow and connect it to Teams. You get observability and monitoring out-of-the-box.

Post reply on HN