teams
1570 TopicsTime tracking woven into Microsoft 365, simple, secure, and proven
From Web to Teams, Outlook, and now M365 Copilot, Klynke time tracking is fully woven into the Microsoft 365 fabric. For partners, this isn’t just another feature. It’s a value-added service you can recommend, bundle, or build into your existing offerings. The payoff: clients stay inside the tools they already know and trust, while you strengthen your Microsoft 365 practice with a solution that’s proven, secure, and seamless. With a tried and tested approach, partners can confidently deliver integrated experiences that feel natural to end users. No extra training. No steep adoption curve. Microsoft even spotlighted this in the Tech Community interview Building Secure SaaS on Microsoft Cloud Let’s explore how integrated solutions like time tracking can open new doors for collaboration. If you’re building on Microsoft 365, we’d love to connect and share ways to create more value together.26Views1like0CommentsGetting a 401 when trying to create a conversation
Hello ! Using the node botbuilder SDK, I am trying to setup my bot to proactively create a conversation in a public channel on Teams. However, I keep getting 401 responses from the API, with no further details. You can find my code attached bellow: const adapter = new CloudAdapter( new ConfigurationBotFrameworkAuthentication( { MicrosoftAppId: process.env.MS_BOT_APP_ID, MicrosoftAppTenantId: process.env.MS_CLIENT_ID, }, new ConfigurationServiceClientCredentialFactory({ MicrosoftAppId: process.env.MS_BOT_APP_ID, MicrosoftAppPassword: process.env.MS_BOT_CLIENT_SECRET, MicrosoftAppTenantId: process.env.MS_CLIENT_ID, }), ), ); await adapter.createConversationAsync( process.env.MS_BOT_APP_ID!, Channels.Msteams, "https://smba.trafficmanager.net/teams/", null, { activity: { type: "message", text: "This is a test message", textFormat: "markdown", }, bot: { id: `28:${process.env.MS_BOT_APP_ID}`, name: "Zygon" }, isGroup: true, tenantId: process.env.MS_TENANT_ID, channelData: { channel: { id: channelId } }, }, console.log, );454Views0likes9CommentsAzureADSharedMode - Teams without PIN
I prepared in Intune profile for Samsung devices in kiosk mode with a multi-app setting. I added Teams, Outlook, Egde and Managed Home Screen as apps. In addition, I also created a configuration profile for the Managed Home Screen application in which I set that it is necessary to configure a PIN for the session. I also set the Require PIN code after returning from screen saver option. Everything works great until the user leaves the Teams app on or someone calls the user logged into Teams. At this point, no PIN is needed to unlock the device. You can easily access Teams of the logged-in user. The user is asked for the session PIN only when he wants to switch to another app. I didn't set screen lock in android settings because in my opinion it's pointless since the device is in shared mode. Have you encountered anything like this? It poses a potential security risk if a logged-in user leaves the Teams app open, puts the phone down and walks away from it, and at that moment someone calls the phone and the person who picks it up without probelm gets access to the logged-in user's teams.256Views1like2CommentsNew To The Community
Hello ISV Success Community, As a new member to the community, I decided to start with an introduction. I’m Aubin Bakana, Founder and CTIO (Chief Technology & Innovation Officer) of Baobab Logix LTD, now based in Leeds, UK. I lead technology and innovation, driving solutions that are secure, ethical, and intelligent. At Baobab Logix, we’re building future-ready platforms that empower businesses to thrive. One of our flagship innovations is KeepComm Intel, a next-generation contact center solution that combines AI-driven automation with human-in-the-loop architecture for speed, accuracy, and trust. As a Microsoft Azure Solutions Architect Expert, Harvard CS50 certified, and full-stack developer, I bring deep technical expertise and a vision for sustainable innovation. I’m here to connect, collaborate, and share insights with fellow innovators who believe in shaping technology for good. Looking forward to engaging with this amazing community and exploring opportunities to build impactful solutions together! thank you.14Views1like0CommentsNew Teams Interface – can't pin /favorite entire teams
CoPilot wrote this post... in fact its proposed title was New Teams Interface – Missing Basic Functionality & Creating Chaos for Admins, so I think it's sensing a bit of annoyance at the new UI... I’m posting this out of sheer frustration after wrestling with the new Microsoft Teams layout. I'm an IT admin responsible for managing Teams across multiple users, and the recent interface update has made that nearly impossible. Key issue: You can no longer pin or favourite entire teams—only individual channels. This is a huge regression in usability. For power users and admins, being able to organize entire teams was essential. Now, everything’s buried under scattered views, vague icons, and non-intuitive menus. I’ve gone through every menu and setting imaginable. “Show,” “Pin,” “Back to classic”—none of it helps because Microsoft simply removed the feature. Even Copilot (Microsoft's own AI tool) couldn’t make sense of what was missing until we both realized the function was outright gone. That’s saying something. This change is actively hurting productivity for both end users and those of us tasked with supporting them. Updates should make things better—not hide or remove critical features without proper notice or alternatives. Microsoft, please rethink this. Stop redesigning without considering the real-world implications for businesses trying to stay organized. — If others are feeling the same pain, let’s get this some visibility. The more upvotes and replies, the louder the message648Views3likes3CommentsProblem with Teams and Exchange Integration
Hi everyone, My goal is to integrate Exchange Server (Exchange 2016 CU23) with Teams so that the Teams calendar can be used. I have set up Hybrid Configuration (Classic Full Hybrid) and completed the setup without any errors. I have also checked Entourage, and it shows that Exchange has been registered, but the Teams calendar is still not working. Check items: 1. Get-AuthServer 2. Get-IntraOrganizationConnector → Confirm the "Enabled" status. 3. Get-PartnerApplication → Confirm it's enabled. 4. External resolution of the Autodiscover and EWS virtual directories 5. Run Teams Exchange Integration → The only thing that works is "Verifying if the user's mailbox is discoverable by the Teams service," and everything else is fine.The user's mailbox is not discoverable by the Teams service. Please ask your administrators to verify the user has a mailbox and to confirm the connectivity between Teams and Exchange. Does anyone have any other ideas or suggestions to help me? Thanks!137Views0likes2Comments