Issue with Teams RSC Permission TeamMember.Read.Group
I want to use Teams RSC to allow a bot to add and remove members of (private) teams channels. https://learn.microsoft.com/en-us/microsoftteams/platform/graph-api/rsc/resource-specific-consent#supported-rsc-permissions the API scope ChannelMember.ReadWrite.Group is appropriate for that. -> "Read and write the members of this team's channels." I have created a teams app and added the RSC API application scope (ChannelMember.ReadWrite.Group) to the App manifest and published the app to my org. The app has the "team" scope. Then I installed the app in a team and tested the API access. I sign-in with the Application SP using app-only auth. What is working: I can read the members of a public channel in the team using: invoke-mggraphRequest -Uri https://graph.microsoft.com/v1.0/teams/[team id]/channels/[channel id]/members -Method Get I can also read the members of a shared channel in the team using the same request. What is not working: I cannot access a private channel in the team: The above request yields the response: "code":"Forbidden","message":"Caller does not have the required roles for accessing 'Private' channel data. To access 'Private' data, API requires one of 'ChannelMember.Read.All, ChannelMember.ReadWrite.All, Group.Read.All, Directory.Read.All, Group.ReadWrite.All, Directory.ReadWrite.All'. Roles on the request 'Group.Selected'." I cannot remove a member from a shared channel. The request: invoke-mggraphRequest -Uri https://graph.microsoft.com/v1.0/teams/[team id]/channels/[channel id]/members/[member id] -Method Delete yields the error: "code":"Forbidden","message":"Caller app is not enabled for requesting the channel of 'Shared' channel type. To access channel data app has to be enabled in the requesting channel." Has someone successfully used the RSC TeamMember.Read.Group in a shared or private channel? Why does the API not work in private channels and only for read in shared channel? The documentation says "of this team's channels", it does not mention any restriction to public channels. Also a write scope only to public channels does not make sense, as members of a public channel are inherited from the team and cannot be managed seperately. What do I need to do differently to be able to read and modify members of private and shared channels in a team using RSC permissions?In/Out Board on Teams
We have been requested to create a departmental automated In/Out Board listing all staff, capturing their presence from Outlook/Teams and displaying onto a SharePoint 2013 (on premise versus O365) page. To keep it simple we would like to display name and status (based upon presence). If we could capture information like "in a meeting" or "Busy" or "Away" or "On a call" that would be even better. I have already posted on the MS Tech Community and Earlier on Teams and was advised to check in here. Any advice or guidance would be most helpful...
Making Teams Updates Seamless: Smarter Delivery with Peer-to-Peer download and Scattered Rollouts
Updating Microsoft Teams is an important part of keeping collaboration smooth and secure. The latest Teams updater makes this process more efficient than ever by introducing two innovative strategies: Delivery Optimization and Scattered Update. These approaches work together to minimize bandwidth usage, reduce impact on networks, and ensure updates happen seamlessly—so users can stay productive without interruptions. Why Bandwidth Optimization Matters In large organizations, updates often need to reach thousands of devices. If they all download at the same time, it can put extra pressure on the network and slow down other important activities. By optimizing how updates are delivered, IT teams can keep everything running smoothly and ensure users stay connected without interruptions. It’s a simple step that makes a big difference for a seamless experience. Delivery Optimization in Detail Delivery Optimization is a built-in Windows feature designed to make updates more efficient by reducing redundant downloads. It works through several smart mechanisms: Peer-to-Peer Sharing Devices on the same network can share update files with each other, so not every device needs to download the update package from the internet. Customer should expect more than 30% of bandwidth savings from peer-to-peer sharing. More information on peering efficiency: Delivery Optimization Frequently Asked Questions | Microsoft Learn Microsoft Connected Cache Organizations can use a dedicated cache server to store update packages locally, enabling faster retrieval and reducing external bandwidth usage. Seeming-less leveraging standard HTTP sources as well as peers DO leverages standard HTTP sources seamlessly, ensuring update always complete. IT teams can manage Delivery Optimization settings through familiar tools like Intune, Configuration Manager. This approach helps significantly reduce bandwidth consumption for large packages such as Teams updates, making the process smoother and more reliable. Scattered Update Scattered Update is designed to prevent all devices from updating at the same time. Instead of a single, large wave of downloads, updates are distributed in smaller, controlled phases. Here’s how it helps: Intelligent Scheduling Teams updater assigns devices to different time windows, spreading the rollout over hours or days. Smart scheduling can redistribute up to 70% of update download attempts within the first two days of a new release. Background Update Teams updater checks for and downloads updates during its scheduled time slot, all without needing the main app to be running. Best Practices for IT Admins To get the most out of Delivery Optimization, consider configuring settings for your tenant to allow peer-to-peer sharing and connected cache. This ensures devices can leverage local sources before downloading from the internet. If you're already using Delivery Optimization peer-to-peer in your organization, and/or are using Microsoft Connected Cache with HTTPS support, no further action is required! Teams updates will seamlessly use your preferred method of bandwidth optimization. Please refer to Delivery Optimization documentations below for how to configure your tenant: Configure Delivery Optimization for Windows | Microsoft Learn. HTTPS Support for Microsoft Connected Cache Overview | Microsoft LearnIntune Android: Shared Device mode Teams calls
I am currently testing the shared device mode, we would also like to use Teams calls on the devices (Samsung). It rings but the interface does not appear. I can't even accept a call in the app. Do you have the same problem? And how did you solve it? I have already added the following ‘apps’. com.samsung.android.incallui com.android.server.telecom com.samsung.android.app.telephonyui
Unified Company Calendar for Mixed Microsoft 365 and Non-365 Users – 2025
Seeking a Shared Calendar Solution for Mixed Microsoft 365 and Non-365 Users I’m working on a solution to create a shared company calendar that everyone in our organization can view, while keeping editing permissions limited to a few selected individuals. The challenge: Some of our team members do not use Microsoft 365, and I’d like them to still be able to subscribe to or view the calendar and receive updates. Ideally, this should work without requiring full Microsoft accounts. I initially considered using an ICS-based calendar, but it seems Microsoft 365 Group calendars don’t support sharing via ICS links. I also explored creating a Group calendar as suggested in other threads, but ran into issues making it accessible to external users or those without 365 accounts. For context, I’m a Global Admin, so I have full access to configure settings in the Microsoft 365 Admin Center and Exchange if needed. We’re a small business, and our main goal is to have a centralized calendar for vacation schedules and company-wide events. It should be simple to access and maintain, with a focus on collaboration and accessibility across the board. What I’m looking for: A calendar that’s viewable by all, including non-M365 users Editable only by a few delegated team members Compatible with Microsoft 365, but not dependent on it for basic access Any tools, workarounds, or best practices that have worked for others in similar hybrid environments
Mouse button 'Back/Forward' not working in 'New Teams'
Though there are options to 'pop out' windows from Teams, Teams is a generally a single page app. As such, one of my most used features in 'Classic Teams' is switching back 'n forth between several 'tabs' I'm currently working with. Say I've got somebody on chat, but then have to quickly check something in Teams, then go back to chat. In Classic Teams this works just fine using the mouse's back & forward buttons. In 'New' Teams, this no longer registers any action at all. I assume the feature still exists, since left of the search bar there are still the back/forward UI buttons. But moving the mouse over for every time you need to switch back and forth is a lot slower and less intuitive than just using the mouse buttons. Current behavior: Mouse 'back'/'forward' buttons do not work in 'New Teams' Expected behavior: Mouse 'back/forward' buttons register the 'back' and 'forward' navigation commands as they did in 'Classic' TeamsDisplay Teams chat message with date stamp rather than relative day
Is there a way to force Teams Chat messages to display the date of a message rather than "yesterday" or "today"? e.g. display "27/08/2024" instead of displaying "yesterday 2:12 pm". (I'm creating this post on 28/08.) We use screenshots of Teams messages in our processes, and having to wait for the actual date to displayed invariably means taking the screenshot is forgotten. Immersive reader always shows the actual date, but not the recipient of the message. No help there.The Files tab in channels is now "Shared"
I've found this Roadmap article about this feature: https://www.microsoft.com/en-us/microsoft-365/roadmap?id=470597 The Microsoft 365 Admin Message Center Message ID MC1025217 says "Before rollout, we will update this post with new documentation." But I can't find any documentation and users in my organisation have this new feature. It's not in any of the blog posts here. Any thoughts on where to find useful end user materials?
Two different Delete-Only Retention Policies for Microsoft Teams chat
I have created two different delete-only retention policies for Microsoft Teams chat. Four of us use a 90-day deletion policy and the rest of our staff use a 30-day deletion policy. My question is: If I am using the 90-day policy and I chat with someone who uses the 30-day policy, will my chats remain visible for 90 days and theirs for 30? Or will the most restrictive policy take over and delete the chats from both sides after 30 days?
