When "Secure by Default" Means "Microsoft by Default" | Simon GreenSkip to contentTheme

AboutWorkWritingNowContact

Call me cynical, but this feels an awful lot like an anti-competitive default masquerading as a security control.

Anybody deploying ChatGPT or Claude (or other!) against a Microsoft environment will now by default have a markedly worse experience out of the box than they did last week, with higher friction to getting it good.

Microsoft has introduced a new tenant-level setting controlling whether applications and agents can access Teams meeting transcripts through Microsoft Graph.

On the face of it, that sounds entirely reasonable.

Meeting transcripts are sensitive. They may contain commercially confidential discussions, personal information, customer details, financial decisions, and all sorts of things that organisations quite rightly need to govern carefully. Giving administrators another control over that data is not, in itself, a bad thing.

In fact, I generally want more controls, not fewer.

The problem is not that the control exists.

The problem is that Microsoft has implemented it globally, retrospectively, and switched it off by default.

That changes the nature of the thing completely.

Permission is no longer permission

Until now, an application wanting to retrieve Teams transcripts through Microsoft Graph needed the relevant Microsoft Graph permissions. Those permissions were already well gated and required admin approval to get. A regular user can’t just grant an app reg. in Entra.

For organisation-wide access, an administrator PIM’d up with the right role has to grant consent through Microsoft Entra. For application access to online meetings, Microsoft also documents the use of application access policies that authorise a particular application to access meeting artefacts on behalf of particular users. There is also a resource-specific consent permission that can limit an application to meetings where it has specifically been installed.

So to summarise the state before yesterday: an administrator has to register or approve the application, review the permissions being requested, grant consent and, depending on the access model, configure an additional policy describing whose meetings it may access.

It’s not like the door was hanging open…

Microsoft has now added another lock on another door.

The new Teams setting overrides all of that you did before. Microsoft’s own documentation is unambiguous about it: Graph access is off by default, and applications and agents cannot access transcripts regardless of their app-level permissions.

So an administrator can explicitly approve an application, explicitly consent to its transcript permissions, and explicitly scope its access, but the application will still receive a 403 error unless somebody separately discovers and enables a tenant-wide Teams setting.

At that point I think it is reasonable to ask what, exactly, the consent was consenting to.

Existing applications are being broken deliberately

This is not only a new safeguard applied to future app registrations.

The Message Center notification says that, once enforcement begins, applications that previously had access through Microsoft Entra permissions will receive access errors unless administrators explicitly enable transcript access. Microsoft gave administrators a 30-day configuration window and set 29 July 2026 as the action date.

That means Microsoft knew this would break existing integrations.

It knew administrators had already granted those integrations access.

It knew those applications might be embedded in operational workflows.

It knew that many tenants would not find and change the new setting in time.

It chose default off anyway.

This is the bit I struggle to accept as merely cautious security engineering.

Security changes normally try to preserve the customer’s explicitly stated intent unless there is evidence that the previous state was actively unsafe. If an administrator has already granted an application transcript permissions, that is a fairly strong indication of intent.

Microsoft could have enabled the new control automatically for tenants where transcript permissions were already in active use.

It could have preserved existing applications while applying the new default to future ones.

It could have created a per-application control rather than placing one global switch above the controls already available in Entra.

It did none of those things.

Instead, Microsoft has introduced a tenant-wide kill switch, set it to deny, and placed the burden on every customer and every third-party software provider to discover what changed.

That is not simply secure by default, that is disruption by default.

Speaker attribution is a different question

There are actually two controls here, and I think separating them is quite good. So, in fairness and credit where it’s due…

The first controls whether Graph applications can access transcripts at...