Anatomy of an Outage: How Microsoft focuses on Transparency during and post incident
Outages happen—no matter the hyperscale provider, no matter the architecture. What separates resilient organizations from the rest is how quickly they detect issues, how effectively they communicate, and how well they learn from the inevitable. Rick Claus had the opportunity to co-present a session on the topic of how Microsoft communicates during outages and what YOU can do to be more proactive on how your Azure based infra is weathering the storm. He and Tajinder Pal Singh Ahluwalia pull back the curtain on how Microsoft handles major incidents—from the first customer impact signal to the deep‑dive retrospectives that follow.
Require approval from IT to join a Team and/or Shared Channels
My company has two sides to its business. Both sides are under the same Microsoft 365 tenant. They can be called Group A and Group B. Group A should not be able to add those from Group B into teams and channels on their own. Likewise, Group B should not be able to add those from Group A. If either side wants to add the other to a team or channels, they should have to get approval from IT, with IT making the additions to the team or channel. We would rather not have this just done over emails. This has to be done while still allowing members of Group A and members of Group B the ability to have 1 on 1 and group chats. Does anyone have any suggestion how to do this?
Please tell me how to disable the Pin Copilot message
Morning! I wrote a message yesterday but nobody replied, so here's another one so it doesn't get lost Can somebody tell me how to disable the annoying "Pin Copilot Chat" popup? every morning I have to say "Maybe Later" when I really mean to say NEVER IN A THOUSAND YEARS
Teams build 25275.2601.4002.2815) instantly closes on launch ucrtbase.dll error 0xc0000409
After updating to Teams 25275.2601.4002.2815, the app opens for one second then closes—no UI, no error. Env: Win 11 Pro 23H2 (26100) WebView2 141.0.3537.92 Entra ID joined (AAD) Faulting module: ucrtbase.dll Exception code: 0xc0000409 Path: C:\Program Files\WindowsApps\MSTeams_25275.2601.4002.2815_x64__8wekyb3d8bbwe\ms-teams.exe Tried: cleared Teams/WebView2/AAD caches, reinstalled Teams + WebView2 + VC++, did Reset this PC and clean USB install — same result. Works fine for local admin + other Entra users and browser. Older builds (Aug/Sep 2025) work fine → likely regression in this release. Please confirm if known and being investigated.
Green Blocky Glitch on Shared Screen in New Teams Meeting
I have a user on New Teams that repeatedly has trouble with screens being shared in meetings by other people showing up as a Green Blocky mess on her end. So far we have cleared cache, uninstalled and reinstalled New Teams, updated graphics drivers, tested her internet connection (measured at 300Mbps down by 35Mbps Up and she is the only user on it) performed normal system maintenance (SFC, D.I.S.M, CHKDSK), and restarts galore. No luck. Any suggestions would be greatly appreciated.
Teams Calling Policies Rollout
I have been working on screen pops for inbound PSTN calls, specifically the "Open apps in browser for incoming PSTN calls" & "URL to open apps in browser for incoming PSTN calls" settings in Calling Policies. Is there any documentation on how the whole policy application process works in Teams? It seems to be frustratingly inconsistent. My experiences with updating the link used in calling policies with Windows Desktop clients: During the first production rollout, it took days for some clients to pick up changes to the link. I am logging which pop screen is activated and saw that some picked up the change in a couple of hours, but a few here and there took a couple of days. One lone straggler never picked up the policy change even after having him restart the app, then logout out of Teams and restart. He finally picked up the change after I toggled a policy switch off and on saving twice in between. If picked up within a few minutes. During testing this week, I changed the link in the calling policy, and it did not take effect even after 24 hours on the test clients. I again made a couple of tweaks to the policy, saved the policy, reversed the changes, saved again and within a few minutes, the policy applied to the test clients. A day later, I opened a client using the same Teams account on a different computer and it still had the old policy. Several hours later, it was still using the old settings. Signing out/into teams and restarting the app did not trigger an update to policies. About twelve hours ago, I made a policy change and so far, the client hasn't picked up the change. I shut down Teams, deleted the %appdata%\Teams folder and restarted the app. Interestingly, the %appdata%\Teams folder has not been recreated. Most apps recreate their folder right at launch, but it's been half an hour. The client is still using the old link setting. Questions: Does anyone know if the 24 hours for policies to deploy is for the cloud to deploy, or for the client to check for updates? Does anyone know a reliable way to force a desktop client to refresh policies? Do certain policy changes trigger a more immediate rollout? I seem to remember the Lync/Skype For Business clients having a scheduled update cycle for policies, but there were ways to force it to refresh by deleting files/folders, specific setting or running commands. Testing aside, the fact that a policy change was never picked up in a week by at least one client, makes me wonder how many clients are running on outdated policies that we can't verify.
