I'm testing a Claude integration that lets a user search and access their Office 365 email. When I sent the user a message from Office 365 using OME's "Encrypt Only" option, Claude could not read the protected message body or the attached .rpmsg file. However, it was able to retrieve the first three lines through the Exchange Search Index. Is this expected behavior, and is there any configuration or supported method that would allow the connector to access the full encrypted message?
3 Answers
Blocking an AI integration from reading encrypted content is intentional from a security perspective. If the message is protected with OME, a third-party assistant should not be able to bypass that protection just because the user can normally open the message.
A possible alternative is to use the Microsoft-hosted assistant experience, since it can work with protected mail in supported scenarios. That isn’t necessarily equivalent to giving a third-party model full access, though, and external models or connectors may still have access and feature limitations.
That behavior is expected. Office Message Encryption prevents enterprise applications and connectors from reading the protected content, even when they’re operating with the user’s permissions. The search index may still expose limited text, such as the opening lines, but the actual encrypted body remains unavailable.
The supported Microsoft 365 route for retrieving encrypted messages is generally eDiscovery, not a normal connector or integration. This limitation also affects other systems that try to journal or archive OME-protected mail.
Right—it may be a practical workaround, but it should not be treated as a direct replacement. Third-party model access can be restricted or throttled, and the encryption boundary still applies.