Loading...

Security Update: New Authentication Requirements for integration with Microsoft Teams PowerShell Module

Security Update: New Authentication Requirements for integration with Microsoft Teams PowerShell Module

Microsoft Teams PowerShell Module requires updated application permissions—RoleManagement.Read.Directory and GroupMember.Read.All—for Entra app authentication starting September 15, 2025. Organizations must review and update these permissions in Entra ID to avoid service disruption. No changes needed for delegated permissions. Introduction We are reaching out to inform you of an important security and authentication update that may impact your integration with the Microsoft Teams PowerShell Module. As part of our ongoing commitment to strengthening security across Microsoft 365 services, we are updating the authentication requirements for application-based authentication in the Teams PowerShell Module. These changes are designed to ensure that Entra applications used for backend access to Teams PowerShell are properly scoped and secured. If your organization uses Entra applications to automate or manage Teams via PowerShell, action is required to avoid service disruption.  When will this happen This change will take effect on Monday, September 15, 2025. How this affects your organization If your organization uses Entra applications to authenticate against the Microsoft Teams PowerShell Module, you must update the Application permissions to avoid disruption. Specifically: RoleManagement.Read.Directory: Required for all Entra applications to verify association with an Administrative Unit. GroupMember.Read.All: Required if your application uses the following cmdlets: *-CsGroupPolicyAssignment *-CsGroupPolicyPackageAssignment No changes are required for delegated permissions. What you can do to prepare To ensure uninterrupted access: 1. Review your Entra applications: Go to Microsoft Entra ID > Roles and administrators. Check the Global Administrator, Teams Administrator, and Skype for Business Administrator roles for any Entra applications or service principals used with Teams PowerShell. 2. Update API permissions: 3. Test your integrations to confirm continued functionality. Compliance considerations Navigate to Microsoft Entra ID > App registrations. Locate the relevant application and add the following permissions: GroupMember.Read.All RoleManagement.Read.Directory View image in new tab Learn more: Application-based authentication in Teams PowerShell Module. No compliance considerations identified, review as appropriate for your organization. Message ID: MC1134747

The post Security Update: New Authentication Requirements for integration with Microsoft Teams PowerShell Module appeared first on M365 Admin.

Published on:

Learn more
Need help with this product?

We can help you with Security Update: New Authentication Requirements for integration with Microsoft Teams PowerShell Module

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

Microsoft Entra ID: Risk-based anti-bot verification (CAPTCHA) for SMS and voice multi-factor authentication

Starting mid-November 2026, Microsoft Entra ID will add risk-based CAPTCHA verification for SMS and voice MFA to prevent automated fraud. Some...

11 hours ago

[Outlook for iOS and Android] Copilot Chat in Outlook UX improvements

Copilot Chat in Outlook for iOS and Android is being updated with a refreshed, consistent design across Microsoft 365 apps, improved chat inte...

11 hours ago

Microsoft Word: Retirement of legacy compatibility settings

Microsoft Word will retire legacy compatibility settings for documents in Compatibility Mode starting December 2026 (Windows) and early 2027 (...

11 hours ago

Power Platform – Information regarding the end of support for SharePoint temporary authentication URLs

Starting April 1, 2027, SharePoint temporary authentication URLs will be retired. Power Apps and Automate functionality that relies on these U...

11 hours ago

Windows Office Hours: November 19, 2026

If you are an IT admin with questions about managing and updating Windows, we want to help. Every third Thursday of the month, we host a live ...

11 hours ago

Scheduled prompts in Microsoft 365 Copilot are moving to native Copilot scheduling and the Tasks view

Microsoft 365 Copilot is moving scheduled prompts from Power Platform to native Copilot scheduling, enabling automatic execution of one-time o...

11 hours ago

Prevent issues with NetApp SMB shares: Learn about new Windows Server security requirements

Microsoft introduced additional security requirements for LDAP authentication on Active Directory domain controllers starting with the October...

11 hours ago

60-day reminder: Hardening changes for ReFS volumes on removable media

Microsoft is making hardening changes to the Resilient File System (ReFS). The changes improve the security posture of Windows by adding visib...

11 hours ago

Microsoft 365 Copilot: Copilot Workspaces is replacing standalone agent selection with agentic chat

Microsoft 365 Copilot Workspaces will replace standalone agent selection (Researcher, Analyst, Designer) with an agentic chat that applies ski...

11 hours ago

Microsoft Teams: Updated recording and transcript access setting behavior for town halls and webinars

Microsoft Teams is updating the “Who has access to the recording or transcript” option for Events App town halls and webinars. It ...

11 hours 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.