Loading...

Teams Search now respects hidden user attributes without requiring “Scope Search”

Teams Search now respects hidden user attributes without requiring “Scope Search”

Starting October 2025, Teams will respect hidden user attributes like ShowInAddressList without needing Scope Search, aligning with Outlook and Exchange. Admins should review and update attribute settings, disable Scope Search if only used for hiding users, and inform support teams accordingly. Introduction To improve consistency across Microsoft 365 services and reduce reliance on Scope Search, Microsoft Teams will now respect hidden user attributes—such as ShowInAddressList and HiddenFromAddressListsEnabled—without requiring Scope Search. This change aligns Teams behavior with Outlook and Exchange, simplifying user visibility management and resolving issues caused by Scope Search, such as difficulty locating Call Queues and Auto Attendants. When this will happen: Rollout begins early October 2025 and is expected to complete by late October 2025. How this affects your organization: Who is affected: Admins managing Microsoft Teams user visibility, especially those who previously used Scope Search to hide users. What will happen: Teams will respect hidden user attributes (e.g., ShowInAddressList, HiddenFromAddressListsEnabled, msExchangeHiddenFromAddressList) without requiring Scope Search. Guest users with ShowInAddressList set to False will no longer appear in People Search. Scope Search is no longer needed to hide users. If Scope Search is used for Information Barriers (IB), it should remain enabled. This change aligns Teams behavior with Outlook and Exchange. What you can do to prepare: Compliance considerations: Compliance Area Explanation Alters how existing customer data is processed Teams will now use hidden user attributes to determine visibility, changing how user data is surfaced in search. Includes an admin control Admins can manage visibility using hidden attributes (as mentioned above). Allows user visibility to be controlled indirectly Guest users and others can be hidden or shown based on attribute configuration. Review your current use of Scope Search. If used solely to hide users, disable it. Ensure hidden user attributes are correctly configured: Online: HiddenFromAddressListsEnabled On-premises: msExchangeHiddenFromAddressList Guest users: Set ShowInAddressList to True if they should appear in search results. Communicate this change to helpdesk and support teams. Update internal documentation to reflect the new behavior. For more details, refer to Microsoft Teams admin documentation. Message ID: MC1168293

The post Teams Search now respects hidden user attributes without requiring “Scope Search” appeared first on M365 Admin.

Published on:

Learn more
Need help with this product?

We can help you with Teams Search now respects hidden user attributes without requiring “Scope Search”

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 Sales: Choose the data sources AI-powered Data Enrichment uses, including CRM notes

AI-powered Data Enrichment now lets admins choose which data sources the agent uses to enrich records. Outlook emails, Teams meetings, and the...

2 days ago

Microsoft Teams: Pro Management portal Analytics & Reports Design Refresh

We are refreshing the way we organize the Analytics & Reports area in the Pro Management portal to make it more user-friendly. Product Mic...

2 days ago

Copilot: Audio overviews on PDF Reteirement

Microsoft 365 Copilot mobile app’s Audio Overviews on PDFs, which create AI-generated podcast-style summaries for commercial users, will...

2 days ago

Public CDN is becoming optional during Brand Center setup

Brand Center setup will no longer require enabling Public CDN by default, allowing organizations to use branding governance without it. Public...

2 days ago

Microsoft 365 Copilot and Power Apps: Retirement of App Builder agent and vibe.powerapps.com

Microsoft is retiring the App Builder agent and vibe.powerapps.com by November 30, 2026, consolidating app creation into Copilot Cowork and Mi...

2 days ago

Outlook: Reply With a Template in Rules

New Outlook for Windows and Outlook on the web will let users create inbox rules that auto-reply with saved templates, automating routine resp...

2 days ago

Microsoft Purview Audit: AuditLogQuery API generally available and Search-UnifiedAuditLog retiring

The Microsoft Graph AuditLogQuery API will be generally available in October 2026, replacing the Search-UnifiedAuditLog PowerShell cmdlet, whi...

2 days ago

Dynamics 365 Sales – Information regarding the retirement of the Dynamics 365 Sales Insights standalone add-on

Starting November 1, 2026, Dynamics 365 Sales Insights as a standalone add-on will have reached end of support. Sales Insights is a legacy off...

2 days ago

Work IQ: Updating documents in Office

Work IQ enables agents to create and edit Microsoft Office documents using organizational context, helping users produce and update content mo...

2 days ago

Microsoft Purview: Information Protection – Apply default SharePoint library labels to data at rest

Enables auto‑labeling of existing SharePoint files to match the default sensitivity label configured on their document library. This helps org...

2 days 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.