We are implementing a significant update in our service affecting applications that modify sensitive properties on non-draft email messages. These sensitive properties include the subject, body, reci...
Published Mar 24, 2026
Version 1.0
Blog Post
2 MIN READ
Upcoming Breaking Changes to Modifying Sensitive Email Properties via Graph API
Hello, how will those permissions interact with Mail.ReadWrite / Mail.ReadWrite.Shared permissions ? Advanced.* will have precedence, both will coexist, something else ?
I currently understand we must replace Mail.ReadWrite / Mail.ReadWrite.Shared permissions by Advanced.* permissions, as long as the application must interact with content outside of some management-related properties (read status, flags etc.)
tmech9000
Microsoft
MicrosoftHello Alban1998,
Best practice is to use the Mail-Advanced* permissions only when the code is modifying sensitive properties like subject, body or recipients on non-draft items. On draft items Mail.ReadWrite will continue to work the same way as today and you should continue to use it for the uses cases it is sufficient for rather than using Mail-Advanced* for everything (least privilege).
Using Mail-Advanced permissions for sensitive propertiesIn part to communicate the intention and awareness that the code is doing something that security sensitive that should be reviewed carefully.
Technically, though these permissions include everything Mail.ReadWrite can do in the same way Mail.ReadWrite includes everything Mail.Read can do.
I hope that helps,
Thomas Mechelke
Exchange Programmability PM