TEAMS.TC.5042 - Scoped People Search Review
Description
This informational test reviews the status of scoped people search and access in Microsoft Teams.
Policy Statement
Scoped people search restricts directory searches to defined groups rather than the entire organization. This informational test reviews the setting for privacy and directory access considerations.
Why This Matters
When enabled, this setting restricts the people search directory to specific groups or organizational units, limiting which users can be discovered and contacted within Teams:
- Privacy: Controls user discoverability
- Security: Limits organizational visibility
- Segmentation: Enables organizational boundaries
- Compliance: Supports privacy requirements
- Access Control: Restricts communication paths
- Data Protection: Limits exposure of user information
Privacy and Security Considerations
Benefits of Scoped Search:
- Users only see relevant organizational segments
- Reduces information leakage
- Supports multi-tenant or complex organizations
- Protects sensitive user groups
- Enables role-based visibility
- Supports privacy regulations
Considerations for Full Directory:
- Improves cross-team collaboration
- Reduces friction in finding colleagues
- Supports organizational transparency
- Simplifies communication
- Reduces helpdesk inquiries about finding users
- Enables organic collaboration
Current Status Review
This test provides an informational review of whether scoped people search is currently enabled or disabled. Organizations should evaluate this setting based on their structure, privacy requirements, and collaboration needs.
Consider enabling if:
- Organization has multiple business units requiring separation
- Privacy regulations mandate restricted visibility
- Sensitive user groups need protection
- Cross-departmental communication should be limited
- Complex organizational structure requires segmentation
Consider disabling if:
- Open collaboration valued
- Full directory access needed
- Organizational transparency important
- Friction in finding users problematic
- Simple organizational structure
Implementation Considerations
Technical Setup:
- Requires address book policies
- Exchange Online configuration needed
- Directory segmentation defined
- User assignments configured
- Testing required for smooth rollout
User Impact:
- Users see limited directory results
- May need alternative methods to find certain colleagues
- Requires clear communication and training
- Help desk may receive inquiries
- Workarounds may be needed for cross-segment communication
Configuration Steps
- Navigate to Teams Admin Center - Org-wide settings
- Scroll to Search by name section
- Review Scope directory search using an Exchange address book policy
- Toggle based on your requirements
- If enabling, ensure Exchange address book policies are configured
- Click Save
Note: This setting requires corresponding Exchange Online address book policy configuration.
Best Practices
If enabled:
- Clearly define organizational segments
- Document which users belong to which scopes
- Provide alternative contact methods for cross-segment communication
- Train users on limitations and workarounds
- Regularly review and update scoping rules
If disabled (full directory):
- Monitor for privacy concerns
- Implement other controls if needed
- Ensure users understand directory visibility
- Consider selective restrictions for sensitive accounts