Prevent/Fix (Planned) - Search by Meeting ID in Call Quality Dashboard
From Microsoft 365 Message Center Archive by Merill Fernando · Microsoft may not have sent this notice to your tenant.Rollout
Rollout dates are often only in the text. When Microsoft moves them, the change shows under "What changed".
What the notice says
Microsoft’s text, safely structuredIntroduction
Beginning in March 2026, you may encounter issues in Call Quality Dashboard (CQD) when searching by Meeting ID. CQD is changing the Meeting ID value to match the numeric Meeting ID found in Teams meeting invites. The previous value used for Meeting ID in CQD will now be found in a separate dimension named Thread ID.
When this will happen
This change will take place starting mid-March 2026.
How this affects your organization
Who is affected
- Microsoft 365 administrators and IT staff who use CQD.
- Organizations that search for meetings in CQD using Meeting ID.
What will happen
- CQD will change the Meeting ID value to match the numeric Meeting ID shown in Teams meeting invites.
- The previous Meeting ID value will no longer appear under the Meeting ID dimension.
- The previous value will be available in a new dimension named Thread ID.
- Existing CQD reports or queries that rely on the old Meeting ID may no longer return expected results unless updated.
What you can do to prepare
- Update CQD queries and reports to use the numeric Meeting ID from Teams meeting invites.
- If needed, update reports to use the Thread ID dimension for the previous Meeting ID value.
- Notify helpdesk and support teams about this change.
- Update internal documentation and training materials related to CQD reporting.
Compliance considerations
No compliance considerations identified, review as appropriate for your organization.
What changed
Between archive captures, newest firstThe archive supplies one version of this notice.
Related public evidence
No related evidence found in this installation's recent collection. This does not establish that no announcement exists.
Not confirmed here
What this page cannot tell you- Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.