Weekly Update 15 September 2025 – callRecords in GCC/DoD, Teams tab dev change, Copilot amalgamate

This week:

Change to data visibility for Microsoft Graph callRecords APIs in GCC High and DoD

Microsoft quietly changed (broke?) Teams tab development (and how to fix it)

Microsoft Is Fixing its Copilot Branding and Pricing (A Bit)

You can also listen to the audio-only version of this episode here: Thoughtstuff Podcast – Tom Morgan on Teams Dev: Weekly Update 15 September 2025.

Find all my videos at thoughtstuff.co.uk/videos. You can also subscribe to the audio-only version of these videos, either via iTunes, Spotify or your own podcasting tool.

Transcript (AI-Generated)

Hello and welcome to another weekly update. I hope you’re doing well.

Couple of interesting things to talk through this week, so let’s get into it.

The first thing to talk about is a blog post from the Microsoft 365 Developer blog – and this is about Microsoft Graph. Specifically, this focuses on call records for Microsoft Teams. This functionality has been available for some time, allowing you to subscribe to call records generated at the wrap-up of a Teams call. These records contain valuable diagnostic data – like network quality, latency, packet loss – as well as insights on devices and network environments involved.

Back in March 2023, Microsoft changed what was available in federated environments (multi-tenant calls between orgs). Specifically, only telemetry for users within your own tenant is now made visible. That change is now rolling out to GCC High and DoD tenants from early October this year. So if you’re in one of those, heads up – admins will no longer see call data for external participants.

I added this note not just for those tenants specifically, but also to acknowledge how slow some changes roll out. Supporting technology at this scale – across geographies, across segmented tenants like DoD – means that yes, some changes take years to fully land. There are still developers today supporting changes scoped out two years ago. It’s often invisible work, but important to appreciate.

Speaking of changes – shout out to Andrew Connell for catching an issue with Microsoft Teams tabs. Specifically, if you have a combination of static tabs (like a dashboard) alongside configurable tabs, you might get strange behavior where only static tabs open. This is likely a regression on Microsoft’s side. If your Teams tab experiences just broke and you’re scratching your head – go read Andrew’s blog. He surfaced the bug and includes some not-great-but-usable workarounds.

And finally – yes, a Copilot update. This time it’s around naming and pricing. Over the last year we saw several standalone features become “Copilots” – like Copilot for Sales, Copilot for Finance, etc. That came with individual step-up pricing. Microsoft is now reversing that and simplifying.

Going forward, if you have Microsoft 365 Copilot, many of these “separate” copilots are included – no extra fees. I think that’s the right move. Marketing all these features as Copilot is a smart way to tell a unified AI story. But if every Copilot had a separate price tag – that gets very confusing, very fast.

There’s some weird naming too. For instance – the Viva Engage Copilot isn’t being developed anymore, but “365 Copilot in Viva Engage” is where new features land. Confusing? Yes. But also… fine. Not worth spinning around the axle over. It’ll settle out, and for those already paying, it’s good news. For others, it may even make Copilot more accessible.

And now – some personal news. Next week I’ll be speaking at CollabDays in the UK (Bletchley Park). I’ll be diving into building declarative agents for Copilot – updated post-Build with all the latest insights.

Thanks for tuning in. I hope you have a great day, and I’ll speak to you again next time.