Under the hood
Settings metadata now tracks which config fields an M365 integration can read.
The internal settings-schema metadata module adds a CONFIG_READERS list including a new m365 reader alongside desktop, plus helpers isRemoteOnly, isHybridExcluded, isHybridDerived, readersOf, readersDeclared, isReadBy, and openEnumItemsOf for describing which config fields exist and their visibility, redaction, and remote policy. This is plumbing for exposing or restricting settings fields to a Microsoft 365 integration and to hybrid (local+remote) policy scopes.
Names in the bundlem365
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Added since
A small documentation edit on Sign in through the OS identity broker touched a line naming m365 after this was published.
What happens on Linux, or on a Windows or macOS device where the broker is unavailable, depends on the feature. For the inference sign-in flows (Foundry, gateway, and Workforce Identity), the app shows an error that names the browser flow …third-party/claude-desktop/entra-broker see the edit
Confirmed since
Anthropic's documentation has since written up m365, on Features.
| [Microsoft 365](/docs/third-party/claude-desktop/connectors-m365) and [GitHub](/docs/third-party/claude-desktop/connectors-github) connectors | ✓ | ✓ |third-party/claude-desktop/feature-matrix see the edit
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up m365, on Features.
Anthropic's release notes agree
Fixed Edit/Write/Read permission rules whose path contains parentheses being dropped as invalid or ignored by the Bash sandbox, which left…