Two recording controls

Learn it in 5 minutes

The Configure Teams Phone in the voice channel page says that when call recording is enabled, an announcement plays to notify participants. The voice-channel capabilities table also lists transcription and recording, and supervisor record and manage. That is the Dynamics side.

Teams compliance recording is configured with a recording policy and a recording application, on the introduction and setup pages this campus already cites. Enabling the Dynamics announcement does not grant that Teams policy, and granting the Teams policy does not by itself tell you the Dynamics announcement is on. Read both controls. Track 17’s recording room walks the Teams policy objects.

Dynamics documents a recording announcement. Teams compliance recording is its own policy. Test each one.

Room HTML

Visual

SVGPNGHTML

Worked example

I will check the Dynamics announcement and the Teams recording policy as two controls.

1. Dynamics Announcement when recording is enabled
2. Teams Compliance-recording policy
3. Check Each control on its own page
4. Join One call identifier in both places

If it fails: One system is recording and the other is silent, and the case notes say both are on.

Checklist HTML

Quiz

Flashcards

Ecosystem

Glossary

• Least active assignment The assignment-methods page says least active is available for voice and messaging only, and is the default selection when you create a voice or messaging queue. Config: The page says the last-capacity-release data is in msdyn_agentchannelstate. It also says not to use the feature for employment decisions. Fault: Least active is promised on a record queue.
• Quality evaluation plan The quality and coaching page, which applies to Dynamics 365 Contact Center only, says an evaluation plan sets the criteria, the conversations, the timing, and the actions. Config: The page names the Omnichannel Administrator role, plus consumption-based billing and capacity. It says not to use the feature for employment decisions. Fault: A plan is activated before any indicator exists in the quality library.
• Quality guardrail On the quality and coaching page, a guardrail defines a required or prohibited behavior. Guardrails are evaluated for violations rather than assigned numeric scores, and each has a priority. Config: Set priority and optional nudge text, then activate the guardrail before you add it to a plan. Fault: A prohibited behavior is given a numeric score because the indicator form was copied.
• Short-term forecast The forecasting overview says a short-term scenario predicts volume and average handle time in 15-minute intervals for a horizon of up to six weeks (42 days), using a linear trend on internal or external data. Config: The same page says a long-term scenario is daily, up to three years (1,096 days). Weighted average is marked preview. Fault: A six-week forecast is read as a daily three-year plan.

Sister technologies

Around the call: compliance recording, workforce management, emergency location, analytics, CRM screen pop, and an agent with a human escape. Each one has its own failure.

Config and troubleshooting

One system is recording and the other is silent, and the case notes say both are on.

Cross-platform bridges

Future hooks

Copilot Studio, Azure Communication Services, and Graph are later tracks in this lab. Treat any uncited limit as confirm before relying.

BridgesEcosystem