Loading...

Upcoming Secure by Default Settings Changes for Exchange and Teams APIs

Upcoming Secure by Default Settings Changes for Exchange and Teams APIs

Starting late October to November 2025, Microsoft will require admin consent for third-party apps accessing Exchange and Teams content via Microsoft-managed default consent policy. This enhances security by restricting user consent, affecting new app permissions but not existing approved apps. Admins should review app access and configure consent workflows accordingly. As part of the Microsoft Secure Future Initiative (SFI) and in alignment with the “Secure by Default” principle, we are updating the Microsoft-managed default consent policy in Microsoft 365 Graph to align with Microsoft’s ongoing security improvements, help you to meet industry best practices, and harden your tenant’s security posture. These changes enable admins to better control third-party app access for Exchange and Teams content. This is the next step in a broader effort to evaluate and evolve Microsoft 365 defaults through the lens of SFI. This update follows our recent SharePoint and OneDrive changes that blocked legacy protocols and required admin consent for third-party apps accessing files and sites. The Exchange and Teams updates are a continuation of this same approach. admin consent for third-party apps accessing files and sites. The Exchange and Teams updates are a continuation of this same approach. When this will happen: These changes will begin rolling out by end of October 2025 and are expected to be completed by late-November 2025. How this affects your organization: The following settings will be updated: Change Impact Require admin consent for apps accessing Exchange and Teams content  For customers using the Microsoft-managed default consent policy, admin approval will be required for third-party apps accessing Exchange and Teams content via Microsoft Graph, Exchange Web Services (EWS), Exchange ActiveSync (EAS), POP3, and IMAP4. To preserve end-user experience, some Exchange email clients are exempted from this change. Administrators can review and modify as noted below. These changes will be reflected as an update to the Microsoft-managed default consent policy. With this change, any organization using the Microsoft-managed user consent policy will require admin consent for Mail, Teams Chat and Meetings functionality across various protocols. Learn more about Graph permissions. Organizations using other user consent policies will not be affected. These changes […]

The post Upcoming Secure by Default Settings Changes for Exchange and Teams APIs appeared first on M365 Admin.

Published on:

Learn more
Need help with this product?

We can help you with Upcoming Secure by Default Settings Changes for Exchange and Teams APIs

If you want help implementing, troubleshooting, or improving this product, contact us and we’ll point you in the right direction.

M365 Admin
M365 Admin

by João Ferreira

Share post:

Related posts

Dynamics 365 Contact Center: Quality evaluation – One-Time Evaluation Frequency

Quality evaluation plans now support a Once frequency type for both case evaluations and conversation evaluations. When creating an evaluation...

1 day ago

Microsoft Teams: Phishing Detection in Teams Messaging

Microsoft Teams is introducing AI-powered phishing detection that uses conversation context to identify phishing and social engineering in hig...

1 day ago

Microsoft Purview: Data Loss Prevention-Admin Units Support for Copilot & Cowork DLP

Microsoft Purview Data Loss Prevention is extending Administrative Units support to Microsoft 365 Copilot, Copilot Chat, and Cowork. This enab...

1 day ago

Take action: NTLMv1 hardening changes might affect network connections on devices without Credential Guard

Beginning with the October 2026 security update, Windows 11, versions 26H2, 25H2, and 24H2, along with Windows Server 2025 enforce restriction...

1 day ago

Power Platform – Recreate connections made to the Azure DevOps connector prior to September 2024

We identified that an app, flow, or agent in your environment utilizes a connection to the Azure DevOps connector that was created prior to Se...

1 day ago

Microsoft Purview | Data Loss Prevention: Count of labeled documents condition for Exchange Online

Microsoft Purview DLP introduces a new Exchange Online condition to detect emails with a high count of sensitivity-labeled attachments, enhanc...

1 day ago

Microsoft Teams: Automatic recording and transcription options align with admin policies

Microsoft Teams will update meeting options to show only automatic recording and transcription settings allowed by assigned policies, adding a...

1 day ago

Copilot Studio – Information regarding the end of support for selected AI models

We are announcing the end of support for selected AI models on the Standard and GitHub Copilot harnesses in Copilot Studio. Beginning on each ...

1 day ago

Updates available for Microsoft 365 Apps for all channels

We’ve released updates to the following update channels for Microsoft 365 Apps: Current Channel Monthly Enterprise Channel Semi-Annual E...

1 day ago

Microsoft Planner: AI-generated status reports in Planner Agent

Microsoft Planner now includes AI-generated status reports via Planner Agent in Microsoft 365 Copilot, summarizing plan progress, risks, and n...

1 day ago

Newsletter

Get the latest Dynamics 365 and Power Platform content in your inbox

A curated digest of community blogs, product news, videos, and podcasts — delivered without the noise.

Weekly updates Unsubscribe anytime Fresh community picks
We use your email only for the newsletter and you can unsubscribe at any time.
By subscribing, you agree to the privacy policy.