Mastering Teams Policies: Guest Calls, Retention Rules, Meeting Recording & Phone System
Microsoft Teams continues to evolve rapidly. It’s no longer just about chats and video calls — it’s also deeply entangled with compliance, governance, and enterprise telephony. As an Intune Admin and Teams supporter, you’ll want to stay current on policies that span guest privileges, data retention, meeting controls, and the growing Teams Phone System. We’ll walk through four core areas and highlight what’s changed recently.
🔒 1. Controlling Guest Users’ Private Call Permissions
Question: How does setting “Make private calls” to Off in the Teams Admin Center’s Org-wide Guest Access settings affect guest users?
Answer: It restricts guest users from initiating private calls.
Why this matters
- You’ve invited an external vendor or partner as a guest. By default, a guest can chat, join meetings, and collaborate in channels. But do you want them to initiate one-on-one voice or video calls with internal users? Maybe not.
- The setting Make private calls in Voice → Calling policies (or via Guest Access depending on your layout) governs whether those guests can start private calls. According to Microsoft’s calling policy documentation, the setting really controls all calling features for a user under that policy. (Microsoft Learn)
- Turning it Off means guests cannot make private calls. They still may join scheduled group calls or channel meetings depending on other settings, but cannot initiate direct voice/video calls.
How to configure
- In the Teams admin center, navigate to Voice → Calling policies (or depending on your layout, Org-wide settings → Guest access → Calling).
- Edit the relevant policy (or create a custom one for guest users).
- Set Make private calls = Off.
- Assign this policy to the guest user(s) or apply it as default for guests.
- Wait for policy propagation — usually up to a few hours but allow for some delay.
What’s new (2025 updates)
- Microsoft’s recent updates to calling policies stressed the importance of global org-wide calling controls (last updated Feb 2025). (Microsoft Learn)
- With teams increasingly used by external users, governing guest permissions is now a higher priority for many organizations.
- Also note: It may intersect with external access and shared channels usage (so guests through shared channels may bypass some guest-specific restrictions). (Microsoft Learn)
🗃️ 2. Configuring Message & Channel Data Retention
Question: Which data retention requirement must be configured in Teams to delete all messages in team collaborations after seven years? Answer: Requirement1.
Why this matters
- Data retention is a major compliance topic: You might need to retain data for a period (for legal, regulatory, or business requirements) and then delete it when it’s no longer needed.
- For Teams, this includes channel messages, private chats, and files. According to Microsoft docs, retention policies for Teams must explicitly target Teams channel messages and Teams chats. (Microsoft Learn)
- In your example, where “Litware” wants “delete all messages in team collaborations after 7 years,” that aligns with setting a retention policy for Teams channel messages (i.e., team conversations) to a 7-year deletion schedule. That maps to “Requirement1” in your scenario.
How to configure
- In the Microsoft Purview compliance portal, go to Data lifecycle management → Retention policies.
- Click + Create retention policy.
- Under Locations, select Teams channel messages (and optionally Teams chats if required).
- Set the action to Delete items automatically at end of retention period.
- Set the retention period to 7 years, and ensure the trigger is based on creation date.
- Name and save the policy, then assign it to relevant teams/users.
- Monitor policy status: For large orgs it may take up to 7 days for full effect. (Microsoft Learn)
Recent updates
- Microsoft now supports retention for shared channels too, but some limitations still apply (especially for private channel migrations). (Microsoft Learn)
- Teams retention policies continue to evolve; ensure your license covers it (E3/E5 or equivalent). (Microsoft Learn)
- Admins report delays or “pending” status — monitor the policy and track messages showing “deleted due to your org’s retention policy”. (NinjaOne)
🎥 3. Disabling Cloud Recording for Specific Departments
Question: To disable cloud recording for all Teams meetings organized by HR users, which configuration should be applied? Answer: Adjust meeting policies in the Teams admin center.
Why this matters
- Cloud meeting recordings are stored in the tenant’s storage (OneDrive/SharePoint) and may contain sensitive HR or legal information. Preventing recordings for HR can be a governance requirement.
- Teams uses Meeting policies to govern features like recording, transcription, lobby bypass, and more.
How to configure
- In the Teams admin center, go to Meetings → Meeting policies.
- Create a new policy (e.g., “HR-NoRecording”) or edit an existing one.
- Set Cloud recording = Off (or ensure “Recording = Disabled” depending on UI).
- Scope the policy: Under Users, assign the policy to all HR department users (via user assignment or group membership).
- Save and wait for policy enforcement (sometimes immediate, but allow recursion).
Recent updates
- The meeting policy controls now provide more granularity (e.g., selective recording permissions) and are tied into Teams Premium features.
- Since late 2024/2025, Microsoft has emphasized clear recording governance features especially for regulated industries.
- As Teams adds features like Facilitator AI and transcription enhancements, control of recordings becomes more important for departments like HR or Legal.
☎️ 4. Allocating Microsoft-Provided Phone Numbers for a Teams Phone System Pilot
Question: For a pilot project for 20 IT department users where you want to provide Teams calling (PSTN), what must you do? Answer: Allocate Microsoft-provided phone numbers.
Why this matters
- With the Teams Phone System, users can call in and out over the Public Switched Telephone Network (PSTN). To enable that, each user needs a phone number or service arrangement.
- Microsoft offers Microsoft-provided phone numbers (in many regions) which serve as a quick way to provision DID numbers for users.
How to configure
- In Teams admin center, go to Voice → Phone numbers.
- Select Add and choose Acquire phone numbers (Microsoft-provided) — select region, quantity (e.g., 20), location, and number type.
- Once numbers are acquired, go to Users → Manage users, select the pilot users and assign the new phone numbers to them (and assign a phone system license if required).
- Optionally, configure voice routing, call queues, and auto attendants for the pilot ring group.
Recent updates
- Microsoft continues to expand global availability of Microsoft-provided phone numbers; check region availability.
- Recent “What’s new” updates highlight enhanced calling features (Intelligent call transfer, prioritized call queues) in Teams Phone. (TECHCOMMUNITY.MICROSOFT.COM)
- Teams Phone integration with Copilot and AI capabilities means voice infrastructure is more than just numbers — ensure your pilot matches these emerging features.
🧠 Summary Table of Key Settings
| Objective | Action | Location in Admin Center |
| Restrict guest private calls | Set Make private calls = Off | Voice → Calling policies (or Org-wide Guest) |
| Delete channel messages after 7 years | Create retention policy for Teams channel messages | Microsoft Purview → Data lifecycle management |
| Disable recording for HR department users | Create meeting policy and set Cloud recording = Off | Teams Admin → Meetings → Meeting policies |
| Provide PSTN numbers for 20 IT users | Acquire Microsoft-provided phone numbers and assign them | Teams Admin → Voice → Phone numbers |
✅ Best Practices for 2025 Admins
- For guest users: Always apply least-privilege controls. Guests often don’t need full calling access.
- For retention: Review your retention policy annually. Make sure it covers new workloads (shared channels, private channels) and check your licenses.
- For meetings: With features like AI-driven transcripts and facilitation, recording controls are more important than ever. Map policies by department.
- For phone system pilots: Don’t just get numbers — align with Teams Phone features like intelligent transfer and AI-assisted call analytics.
- Stay updated: Microsoft rolls out many Teams enhancements quarterly (see “What’s new in Teams”) — keep your admin processes aligned. (Microsoft Support)
By mastering these four core areas — guest call permissions, data retention, meeting recording policies, and phone system provisioning — you’ll be well-positioned to support your organization’s Teams deployment. For someone deeply involved in Intune and enterprise device management like yourself, aligning device enrollment/management policies with Teams governance means you’ll deliver smoother, more secure collaboration across the board.
