Skip to main content
  1. Public practice questions
  2. AB-650 Practice Exams | Microsoft 365 and AI Services Administrator Associate
  3. AB-650 Case Study Set

Question 26 — AB-650 Case Study Set

Paideffort Teams Copilot Meeting Governance Modernization
 

Business Context

Paideffort uses Microsoft Teams for customer negotiations, executive briefings, internal design sessions, and regulated financial reviews. The organization is expanding Microsoft 365 Copilot to selected employees and wants meeting behavior to follow the information-handling requirement of each business process rather than applying a single Copilot configuration tenant-wide.

Account Managers require Copilot during customer meetings and must be able to review Copilot-generated information after each meeting. A saved transcript must exist whenever Copilot is used for these meetings, and organizers must not be able to change this requirement. All Account Managers selected for the rollout have the required Microsoft 365 Copilot add-on license.

Meeting Workloads

Account Managers need a durable Copilot experience during and after customer meetings. Compliance requires consistent transcript retention behavior and does not permit organizers to switch Copilot to an in-meeting-only mode.

Design Leads use Copilot primarily to catch up late participants and ask questions during live design discussions. They do not require a saved transcript afterward. Their current process asks organizers to manually change Copilot settings for each new meeting and verify that no transcript is retained.

Regional Sales Directors normally want Copilot available during and after meetings, but organizers must retain the ability to change individual meetings to Only during the meeting or Off when customer circumstances require it.

Financial Investigation meetings use end-to-end encryption because participants discuss highly sensitive transaction investigations. Investigators have Microsoft 365 Copilot licenses, and the security team does not permit removal of end-to-end encryption from these meetings.

Current Policy State

The Account Managers policy currently appears in the automation inventory as:

meetingPolicy: Tag:AccountManagers
allowTranscription: false
copilot: EnabledWithTranscript
organizerOverrideRequired: false

Regional Sales Directors are represented in the governance service by the following record:

{
  "policy": "Tag:RegionalSales",
  "copilot": "EnabledWithTranscriptDefaultOn",
  "organizerCanOverride": true,
  "defaultMeetingExperience": "DuringAndAfter"
}

A Python validation service evaluates whether a configured policy is suitable for post-meeting Copilot use:

def supports_post_meeting_copilot(policy):
    return policy["copilot"] in [
        "EnabledWithTranscript",
        "EnabledWithTranscriptDefaultOn"
    ]

Deployment Configuration

The collaboration team prepared the following PowerShell commands for the next policy deployment:

Set-CsTeamsMeetingPolicy -Identity "Tag:AccountManagers" `
    -AllowTranscription $false `
    -Copilot EnabledWithTranscript

Set-CsTeamsMeetingPolicy -Identity "Tag:DesignLeads" `
    -AllowTranscription $false `
    -Copilot Enabled

Set-CsTeamsMeetingPolicy -Identity "Tag:RegionalSales" `
    -Copilot EnabledWithTranscriptDefaultOn

During pilot validation, an Account Manager creates a meeting and sees During and after the meeting as the enforced Copilot mode, but Copilot cannot produce the expected durable experience because the meeting cannot create the saved transcript on which that mode depends. Design Leads can use Copilot during live meetings without retaining a transcript. A newly licensed Regional Sales organizer reports that the default experience is correct but wants assurance that individual meetings can still be changed.

Future Requirements

Paideffort expects the Copilot meeting rollout to expand to hundreds of organizers. Governance reporting must evaluate transcription and Copilot settings together rather than treating either property as sufficient on its own. Administrators also want automated checks for licensing and meeting security constraints, and the collaboration team wants policy defaults to minimize repeated organizer actions while still preserving per-meeting flexibility where the business requirement permits it.