[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.
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
ShowInAddressListset toFalsewill 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.
- Teams will respect hidden user attributes (e.g.,
- 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
ShowInAddressListtoTrueif they should appear in search results.
- Online:
- 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.
[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. |
Source: Microsoft
Latest Posts
- (Updated) Microsoft Teams: Distinguish invites among Attendee, Presenter, and Co-organizer emails [MC1009930]
![(Updated) Microsoft Teams: Distinguish invites among Attendee, Presenter, and Co-organizer emails [MC1009930] 2 pexels googledeepmind 25630338](data:image/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==)
- (Updated) Microsoft 365 Copilot: Researcher agent output formats [MC1224569]
![(Updated) Microsoft 365 Copilot: Researcher agent output formats [MC1224569] 3 pexels pavel danilyuk 8438918](data:image/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==)
- Radar – Content Type Dimension for AI Bots in Cloudflare Radar

- Cloudflare Fundamentals – Introducing Markdown for Agents

![Teams Search now respects hidden user attributes without requiring "Scope Search" [MC1168293] 1 Teams Search now respects hidden user attributes without requiring “Scope Search” [MC1168293]](https://mwpro.co.uk/wp-content/uploads/2025/06/pexels-olly-3823488-1024x683.webp)
![(Updated) Microsoft Teams: Distinguish invites among Attendee, Presenter, and Co-organizer emails [MC1009930] 2 pexels googledeepmind 25630338](https://mwpro.co.uk/wp-content/uploads/2024/08/pexels-googledeepmind-25630338-150x150.webp)
![(Updated) Microsoft 365 Copilot: Researcher agent output formats [MC1224569] 3 pexels pavel danilyuk 8438918](https://mwpro.co.uk/wp-content/uploads/2025/06/pexels-pavel-danilyuk-8438918-150x150.webp)


![Microsoft Teams: Apps now supported in Shared Channels [MC1168294] 7 Microsoft Teams: Apps now supported in Shared Channels [MC1168294]](https://mwpro.co.uk/wp-content/uploads/2024/08/pexels-weekendplayer-93820-150x150.webp)